Integrations / RRA EBM 2.1
EBM 2.1 integration for ERPNext in Rwanda
Rwanda requires EBM invoices from every registered taxpayer, and the technology has shifted from black boxes to software. We connect ERPNext to RRA's EIS through the VSDC path.
Why this matters now
The Electronic Invoicing System has been in force since January 2021, extended to non-VAT registered taxpayers since October 2020. Every registered taxpayer must issue EBM invoices, VAT-registered businesses need an EBM at each sales location, and consumer receipt verification under Tengamara makes skipped invoices visible to RRA.
ERPNext and compliance in RwandaWhat the integration covers
ERPNext communicates with RRA through a Virtual Sales Data Controller, replacing physical billing machines with certified software flows.
Sales invoices, refunds and credit notes issued as EBM documents with RRA identifiers stored on the ERPNext record.
Each sales location's EBM obligation mapped to ERPNext branches, with per-location reporting.
The retry and circuit-breaker pattern from our KRA eTIMS module, so connectivity drops never lose an invoice.
Supplier EBM references captured on purchase invoices, keeping your deductions supported.
How we deliver
From discovery to verified go-live
Discovery and compliance mapping
We map your document flows, branches and item catalogue to RRA's EBM 2.1 requirements, and confirm registration status and credentials with the authority.
Sandbox integration
ERPNext is connected to the EBM 2.1 test environment. Sales invoices, credit notes and debit notes are generated and validated against the authority's schema before anything touches production.
Resilience engineering
Failed transmissions queue and retry automatically, with a circuit breaker for authority downtime. The pattern is proven in our KRA eTIMS module: zero lost receipts when the tax server is down.
Go-live and verification
Production credentials are registered, the first live documents are verified end to end, and your team is trained on exception handling and the EBM 2.1 verification workflow.
Support and rate-change watch
We monitor authority notices and ship configuration updates when rules change, under a support agreement with defined response times.
Frequently asked questions
Is this a shipped module?
No. EBM 2.1 integration is delivered as an engineering service on ERPNext, using the architecture proven in our Kenyan eTIMS module. VSDC registration, schema mapping and RRA validation are scoped per project.
Do non-VAT businesses need EBM invoices?
Yes. RRA requires taxpayers who are not VAT-registered but carry out sales to issue EIS invoices. The VAT registration threshold is FRW 20,000,000 over twelve months, but the invoicing obligation is broader than VAT.
VSDC or OSDC, which applies to us?
The Virtual SDC is software your system integrates with, suited to ERPs and POS systems with volume; the Online SDC is RRA-hosted. We recommend based on transaction volume, offline requirements and your branch structure during discovery.
Scope your EBM 2.1 integration
A discovery call covers your document flows, registration status with RRA, and a delivery plan with verification criteria. We reply within one working day.