Every VAT-registered business in Burundi is now required to issue invoices through the OBR EBMS (Electronic Billing Management System). If you run ERPNext, that mandate creates a painful gap: ERPNext produces a perfectly good Sales Invoice, but it has no idea EBMS exists. It won't submit the document to OBR, it won't attach the fiscal signature and fiscal number the tax authority requires, and it can't map your ERPNext tax templates onto the EBMS VAT codes. Teams end up re-keying every invoice into a separate OBR portal — double entry, mismatched totals, and real audit exposure when the ERPNext record and the fiscal record disagree.

ECOSIRE builds a dedicated Frappe app — a proper installable module with its own DocTypes, not a pile of loose customizations — that closes that gap. On Sales Invoice submission, a hooks.py doc event calls a whitelisted server method that assembles the EBMS payload from the invoice, its items, and your tax mapping, then posts it to the OBR EBMS API. The fiscal signature, fiscal invoice number, and EBMS reference come back and are written onto the invoice on custom fields, so the compliant, signed document is the one your staff already work in. A configuration Single DocType holds your OBR credentials, TIN, device/branch identifiers, and endpoint URLs, guarded by a dedicated role profile so only authorized users can touch tax settings.

Under the hood we map ERPNext Item Tax Template and tax categories to the correct EBMS VAT classes (standard-rated, exempt, zero-rated), so the VAT you report matches what OBR expects line by line. Credit notes and returns are handled as EBMS refund/credit transactions that correctly reference the original fiscal invoice, rather than being sent as fresh sales. Every submission writes to an EBMS Submission Log DocType with the request, the response, the returned fiscal data, and a status field (Pending, Submitted, Signed, Rejected). A Frappe scheduler event retries transient failures and reconciles any invoice left in a pending state, so a dropped connection to OBR never silently leaves a document uncompliant. Client scripts surface the EBMS status and fiscal number on the invoice form, and role-based permissions keep the whole flow auditable. It targets ERPNext/Frappe v15 and v16.

Because this is genuinely tax-authority integration and not a generic download, we build it to order. After a short scoping call we confirm your exact OBR EBMS onboarding details, invoice types, and VAT treatments, then deliver a working app on a staging bench for UAT, typically 2 to 4 weeks from confirmed scope. You get the source code, install and configuration, documentation, a training session, and a post-go-live support window — so the day the OBR requirement bites, your ERPNext is already issuing compliant electronic invoices.