When an IRD officer walks into your office for a VAT audit or assessment, the first thing requested is rarely a clever interpretation of the law. It is a stack of records. Sales invoices in serial order. Purchase bills with PAN of the supplier. Bank statements that tie to the cash book. Stock ledgers that explain the cost of goods sold. The businesses that survive these assessments without disputes are the ones whose digital records IRD Nepal officers can read, verify, and reconcile against the returns already filed.
Most Nepali businesses have moved past pure paper. Invoices are printed from accounting software, payments are routed through banks, and salary slips arrive by email. But moving away from paper is not the same as keeping a compliant digital trail. We have seen businesses lose input VAT credit during assessment because the scanned purchase bill had no clear PAN, or because the file was overwritten when the accountant changed last year. Digital records have to be organized, retained, and retrievable on the terms the IRD expects.
This article walks through what the IRD looks for in digital books, what counts as an acceptable electronic record, how to digitize legacy paper without breaking the audit trail, and how an accounting-first ERP holds the structure together as transactions are posted day to day.
What the IRD Actually Expects From Your Digital Books
Begin with the IRD's working definition of a record. It is any document, register, or data set that supports the figures declared on your VAT return, TDS return, or annual income tax return. That includes the obvious - tax invoices, debit and credit notes, bank statements, the general ledger - and the less obvious - approval emails, delivery challans, stock count sheets, fixed asset registers, and the VAT register itself in IRD format. If a figure ends up on a return, the source has to be reconstructable from records you can produce.
Acceptable electronic records share four traits. They are complete, meaning no transaction is missing from the period under review. They are accessible, meaning the IRD officer can view them in a format readable on a normal computer. They are tamper-evident, meaning any change to a posted entry leaves a visible trail of who edited what and when. And they are auditable to source, meaning a single voucher in the system can be traced to the original tax invoice or scanned bill that justifies it.
This last point is where most paper-to-digital transitions fail. The accountant enters a vendor bill into the software but does not attach the underlying scan. Six months later, during a VAT audit, the bill is misfiled in the cupboard and the input credit is at risk. A compliant digital record links the scan to the voucher inside the system - one click from a journal entry takes you to the original document image.
Digital records are not just files on a hard drive. The IRD expects complete, accessible, tamper-evident, and source-linked data that can be traced from any figure on the return back to the underlying voucher and document.
Retention, Format, and the Risk of a Missing Year
Under the VAT Act, registered businesses are required to maintain original tax invoices and supporting records for 5 years from the end of the relevant tax period. The Income Tax Act 2058 also imposes record-keeping obligations on taxpayers, and assessment can be reopened during this window. Specific retention periods and any subsequent Finance Act revisions should be verified with the IRD or your tax advisor before disposing of any historical books.
Format matters as much as duration. The IRD accepts records in the form they are normally generated - PDF for invoices and statements, Excel or CSV for ledgers and registers, system-generated reports for the VAT and TDS books. What it does not accept is a folder full of orphan files with cryptic names. Records have to be organized by fiscal year, by company, and by document type, and they have to be retrievable in minutes, not days.
Nepal's fiscal year runs Shrawan 1 to Ashadh 31. VAT filing follows two schedules - monthly for registered businesses above the higher transaction threshold and trimester (Shrawan-Kartik, Mangsir-Falgun, Chaitra-Ashadh) for those below. Your digital records have to be sliced by these periods, not by the Gregorian calendar, or reconciliation against IRD returns becomes painful.
Two record-keeping mistakes show up repeatedly during assessments. The first is the missing year - a business changes accountants or software, the old data is exported badly, and one fiscal year sits in a format nobody can open. The second is the silent overwrite - the same invoice number is reused after a printer mistake, and the original entry is replaced rather than reversed with a credit note. Both create gaps that an assessing officer will treat as suppressed income unless you can prove otherwise.
The IRD has statutory power to demand records during assessment, audit, or investigation, and failure to produce them within the period stated in the notice can trigger penalties, denial of input VAT credit, and best-judgement assessment. Verify the current penalty schedule under the VAT Act and Income Tax Act with the IRD before relying on any specific figure.
Retain VAT records for at least 5 years in a format the IRD can open, organized by fiscal year and document type, and verify any longer retention obligation under the Income Tax Act before disposing of historical books.
Digitizing Paper Without Breaking the Audit Trail
Most established Nepali businesses still have several years of paper records in cupboards. Going fully digital does not require backdated digitization of every old file, but the past three years of active records should be brought into a compliant digital structure - those are the years most likely to be opened during a VAT audit or income tax assessment.
Start with the highest-risk documents. Purchase tax invoices come first, because they back input VAT credit and are the IRD's favourite area to disallow. Each scan should be saved with a filename that ties to the voucher number in the books and the supplier PAN, and stored in a folder structure organized by fiscal year and month. The scan itself must be legible - the supplier name, PAN, invoice number, date, taxable value, VAT amount, and total all readable without zooming into a blur.
Once scanned, attach the file to the voucher inside the accounting system rather than leaving it on a shared drive. This is the single change that separates a digital filing cabinet from a compliant electronic record. When the IRD asks for the proof of an entry, your accountant opens the voucher and the scan is one click away - vendor name, date, amount, and tax breakup matching exactly.
Scanning quality matters more than scanning speed. A blurred purchase invoice where the PAN is unreadable is no better than a missing invoice during an IRD assessment - both carry the same risk of input credit disallowance.
For the journey forward, train staff to capture documents at the point of receipt rather than at month-end. A vendor bill that comes in the morning should be scanned and attached to the voucher the same day. This habit eliminates the year-end scramble where a stack of unscanned bills sits on a desk and the accountant chooses which ones to digitize based on what is left in the folder.
Digitize the last three years of active records first, prioritize purchase tax invoices and bank statements, and attach scans directly to the voucher inside the accounting system so the trail from return to source is one click.
Backup, Disaster Recovery, and Year-End Discipline
A digital record that exists only on one machine is not a compliant record. Drives fail. Laptops are stolen. Ransomware encrypts the accounting folder the week before the trimester VAT return is due. The IRD does not accept "the data was lost" as a defence during assessment - the obligation to produce records sits on the taxpayer regardless of the cause of loss.
The minimum standard is two copies in two locations, with at least one of them off the office premises. A daily automatic backup of the accounting database to a cloud storage account meets this baseline. A monthly export of the VAT register, TDS register, and trial balance to a separate location adds a second layer in case the accounting database itself is corrupted. Test the backup at least quarterly by restoring a known file - an untested backup is a hope, not a backup.
Year-end discipline closes the loop. At the close of each fiscal year - Ashadh 31 in Nepal - lock the period in the accounting system, export the statutory registers in IRD format, and archive a read-only copy of the full year's books. From that point on, no entry inside the locked year should be edited; corrections happen through prior-period journal adjustments in the current year with the audit trail intact.
Keep two copies of every fiscal year's records in two locations, test the backup quarterly, and lock the period at Ashadh 31 close so historical books cannot be edited silently.
During assessment the accountant has to hunt for the file matching each voucher number, and missing scans mean disallowed credit.
One click from any journal entry opens the original scanned tax invoice with PAN, VAT amount, and date visible.
Manual transcription introduces errors that show up only when the IRD reconciles the return against e-billing data.
The sales and purchase VAT register and TDS per-heading register update in real time as vouchers post.
Reconciling to IRD periods like Shrawan-Kartik requires manual conversion every trimester.
Every date is stored in both Bikram Sambat and Gregorian, and reports run on either without conversion errors.
A posted invoice can be changed and nobody knows who changed it or what the original figure was.
Every edit, approval, and reversal carries a user stamp and timestamp - the IRD officer sees the full history.
One ransomware attack or hard drive failure wipes out years of records the business is obliged to produce.
The accounting database backs up automatically with S3-compatible storage and a tested recovery path.
Frequently Asked Questions
The IRD accepts digital records that are complete, accessible, tamper-evident, and traceable to source. The original paper tax invoice should still be retained where it was the source document, because the IRD can ask to see the original during a VAT audit. Where the source itself is digital - an e-bill, an electronic bank statement, an emailed contract - the digital file is the original and no paper copy is required.
Under the VAT Act, registered businesses must maintain tax invoices and related records for at least 5 years from the end of the relevant tax period. The Income Tax Act 2058 also imposes record-keeping and assessment-reopening windows, and specific retention periods are subject to subsequent Finance Act revisions. Confirm the current retention period with the IRD or your tax advisor before disposing of any historical books.
The assessing officer can disallow the related expense or input VAT credit, raise additional tax, and impose penalties and interest. In repeated or serious cases the IRD can move to best-judgement assessment, which usually produces a higher tax liability than the actual figures would have. The taxpayer bears the burden of proof, so a missing record is treated as the absence of the underlying transaction unless reconstructed from other evidence.
Records That Are Audit-Ready by Default
MISAC is built around IRD compliance rather than retrofitted to it. The VAT register comes out in IRD format with sales and purchase splits, the TDS register lists deductions by heading code with both Nepali and English labels, and every date is stored in both Bikram Sambat and Gregorian so a Shrawan-Kartik trimester return reconciles to the books without manual conversion. The fiscal year follows Shrawan 1 to Ashadh 31 natively across every module.
The accounting-first architecture closes the audit trail at the source. Every voucher - sales invoice, purchase, payment, payroll - posts a complete double-entry journal in one save, and every scan attached to that voucher stays linked to the journal entry forever. When the IRD officer points at a figure in the return, the accountant clicks through to the voucher, the journal, and the original document in three clicks. Edits and reversals carry a tamper-evident audit trail with user and timestamp, so the history of any record is visible at any time.
For businesses moving from paper or from a system that cannot keep up with IRD requirements, MISAC Intelligence Pvt. Ltd. has worked alongside Nepali accountants and finance teams for more than a decade to design the platform around the assessments and audits they actually face. The structure is there from day one - records are organized, retained, and produced the way the IRD asks.
Ready to See MISAC in Action?
If your digital record keeping for IRD compliance still depends on shared drives and Excel, a short walkthrough can show what audit-ready books look like inside MISAC.