Rwanda Revenue Authority's Electronic Billing Machine programme mandates that registered businesses issue EBM-validated invoices. Advatech integrates your ERP or POS to the EBM v2 Gateway API, with no physical device required for qualifying businesses.
Share your system details and branch count. We confirm EBM v2 API scope, MRC signing setup, and a delivery timeline.
Start KYC onboardingRwanda Revenue Authority's Electronic Billing Machine (EBM) programme requires registered businesses to issue invoices validated by an RRA-approved billing system. EBM version 2 introduced an API Gateway approach, replacing the requirement for physical EBM hardware for qualifying businesses and enabling direct software-to-authority data exchange.
Every invoice issued through EBM v2 receives a Machine Reference Code (MRC): a cryptographic signature tied to the business's EBM registration, along with a timestamp and a QR code that links to RRA's public invoice verification portal. Customers and auditors can scan the QR code to confirm the invoice's authenticity.
Advatech integrates your ERP or POS to the EBM v2 Gateway API, handling MRC signing, invoice schema mapping, credit note flows, and transmission to RRA. For businesses on older physical EBM hardware, we manage the migration path to v2 API.
Confirm TIN, EBM v2 eligibility, current device status, and the invoice data model in your ERP or POS.
Register API credentials, configure MRC signing, and map your invoice fields to the RRA EBM v2 schema.
Test the full signing cycle, QR code generation, and RRA portal verification in the sandbox environment.
Production cutover with transmission monitoring, reconciliation checks, and support for RRA schema updates.
Single-location setups with a modern ERP or POS typically complete in 7–10 business days after KYC sign-off.
Multi-branch rollouts or migrations from physical EBM hardware typically take 2–4 weeks, depending on field mapping complexity and RRA registration processing time.
Scope and milestones are confirmed during the KYC discovery call.
RRA's EBM programme requires registered businesses to issue invoices validated by an approved electronic billing system. The requirement applies to VAT-registered businesses and has been progressively extended to other registered taxpayers above certain turnover thresholds. If you operate commercially in Rwanda and are registered with RRA, you are likely in scope.
EBM v1 required a physical Electronic Billing Machine device connected to the point of sale. EBM v2 introduced an API Gateway approach, allowing businesses to integrate directly via software without purchasing or maintaining physical hardware. The v2 system also introduced the Machine Reference Code (MRC) as a cryptographic invoice signature and QR codes on every invoice for public verification.
No. For businesses eligible to use the EBM v2 Gateway API, physical hardware is not required. The software-only path uses API credentials and MRC signing to validate invoices electronically. Some older registrations or specific business categories may still require hardware. Advatech confirms your eligibility during KYC and manages any migration from v1 hardware.
An MRC is a cryptographic signature code tied to your EBM v2 registration with RRA. It is embedded in every invoice issued through the API and serves as digital proof that the invoice was processed through an RRA-approved system. The MRC, combined with the QR code, allows RRA and customers to verify invoice authenticity without re-querying the API.
Advatech builds a middleware layer between your ERP or POS and the RRA EBM v2 Gateway API. We register API credentials, implement MRC signing, map your invoice data to RRA's schema, handle credit notes and corrections, and set up transmission monitoring. For most common ERP environments we have pre-built integration templates, reducing custom development time significantly.