Accounting and billing / Practical guide
Preparing and troubleshooting a CBMS integration in Nepal
Confirm the IRD process for your business, test an invoice and a return, and find where a failure happened before retrying.
Published by ERP Nepal · · Editorial approach
On this page
Onboarding is not configuration
Having the connection code does not mean your business is onboarded with IRD. Confirm the process and test arrangements first.
- A business and a technical contact.
- Company PAN/VAT and authorised credentials.
- Never post credentials in screenshots or issues.
References: IRD CBMS technical documentation noticeNepal Compliance CBMS Settings fields
Test an invoice and a return
Invoices and returns use different submission paths. Send test records only to an approved test destination.
References: Nepal Compliance CBMS implementation
Find where it failed
“Queued” does not mean accepted. Locate the failing stage before you retry.
| Stage | Evidence to collect | Next investigation |
|---|---|---|
| Local preparation | Invoice reference and application error | Settings, required values, and request preparation |
| Background execution | Job time and completion or failure record | Worker availability and application exceptions |
| Network exchange | Timestamp and transport status | Connection, approved destination, or interrupted response |
| Service response | Recorded response and related invoice | Acceptance, rejection, or an already-recorded transaction |
References: Nepal Compliance CBMS implementationIRD CBMS technical documentation notice
Questions and answers
Should I resend everything after a timeout?
No. Check what was recorded first.
Sources and further reading
Checked 28 September 2026.