Hospital reporting and migration guide
Hospital billing-report parity and data migration in Nepal: an IRD-readiness guide
A report with the right name may still have the wrong columns, row meaning, calculations, or source data. Use this guide to compare exports and migration evidence before accepting financial continuity.
Report presence is not report parity
A menu item, endpoint, or export called Sales Register or Annex 5 proves only that something exists. It does not prove that the output matches the authority, institution, accountant, or source system used as the acceptance reference.
Parity requires a field-by-field and record-by-record comparison against an agreed workbook or specification. The comparison should be repeatable and signed by the responsible finance or compliance owner.
Use five checks for every report
The same method works for sales, sales returns, purchases, purchase returns, credit notes, VAT, Annex 5, claims, stock, and archived exports.
- Header schema: exact columns, order, labels, types, required values, and date or number format
- Row grain: one invoice, invoice line, payment, return line, tax rate, patient event, or supplier document per row
- Calculations: gross, discount, taxable, VAT, exempt, refund, net, rounding, and totals
- Source model: invoice, return, expense, purchase, stock receipt, claim, payment, or journal that actually supplies the row
- Lifecycle coverage: draft, issued, printed, synced, cancelled, returned, credited, refunded, archived, and corrected states
Preserve archives and corrections
Migration often focuses on active patients and opening balances while omitting archived invoices, credit notes, returns, printed state, synchronisation state, payment method, transaction reference, and historical reports. Those omissions appear later during audit or dispute.
The target system should not rewrite history to make it fit. Preserve the original document, its correction, reason, date, author, reference, and financial effect. If a source field cannot map, record the exception and agreed treatment.
- Issued invoice and original print or sync state
- Return, credit note, cancellation, refund, and reversal links
- Payment method, transaction reference, deposit allocation, and settlement
- Purchase, supplier invoice, receipt, purchase return, and payable history
- Archived report files, source extracts, control totals, and read-only access
Reconcile migration at three levels
Record counts catch missing rows, control totals catch missing value, and sample tracing catches broken relationships. Use all three. A matching row count can still hide wrong balances or disconnected documents.
Run at least one rehearsal from a frozen copy, fix mapping and quality issues, repeat the reconciliation, and retain the signed evidence. Final cutover should use the same tested process.
- Population: source, migrated, rejected, duplicate, transformed, and intentionally excluded counts
- Value: opening stock, receivables, payables, deposits, claims, cash, bank, tax, and journal control totals
- Trace: patient to visit, invoice to receipt, return to original, purchase to stock, claim to settlement, and report to source row
Require a financial continuity acceptance pack
The final pack should let an independent reviewer understand what moved, what did not, which reports were compared, how totals reconciled, which exceptions remain, and who accepted the risk.
- Signed data inventory and mapping specification
- Source extracts with hashes or controlled identifiers
- Migration logs, rejected records, transformation rules, and exception decisions
- Before-and-after row counts and financial control totals
- Report-parity workbooks with annotated differences and accepted outcomes
- Archive-access, retention, export, backup, restore, and exit evidence
Primary and authoritative sources
Sources support the Nepal context and official direction. Product-specific statements are based on the local Xodont implementation and remain subject to deployment acceptance.
- 1. Nepal IRD electronic-billing guidance
Official IRD context for electronic billing; listing, permission, formats, and production acceptance are authority processes.
- 2. MoHP Digital Health Infrastructure
Nepal public-health infrastructure, continuity, connectivity, security, and health-facility context.