NBR e-invoicing middleware: connect your system once, stay compliant
An e-invoicing middleware is the layer between the software that issues your invoices and the NBR platform. You keep the POS, ERP or accounting system you already use. The middleware does the compliance work around it.
What the middleware does for each invoice
- Receives the invoice through the API, a file import, a scheduled pull or a webhook.
- Checks the data and the VAT arithmetic against the NBR rules before anything is sent.
- Builds the UBL 2.1 XML and validates it with the NBR validator.
- Signs it with the device certificate and creates the QR code.
- Sends it to the NBR (clearance or reporting) and records the answer.
- Returns the status and QR code to the originating system by signed callback or status API.
Why not build it inside each system
Every POS and ERP would need its own signing keys, certificate handling, rule updates and NBR connection. A middleware keeps those in one place, so a rule change is made once, and a business with several systems or outlets gets one record of everything sent.
Built for the way Bahrain businesses work
- English and Arabic screens with right-to-left layout.
- One VAT number with several CR numbers and branches, each with its own device.
- A review and approval step you can switch on before anything is sent.
- A dry run that shows exactly what the NBR would say, without sending anything.
- Bilingual printable invoice with the QR code, and a PDF/A-3 file with the XML attached.
Safe by design
Each business sees only its own data. Device keys and secrets are encrypted at rest, every administrative action is logged, and an invoice is never sent twice by mistake: retries are safe and an uncertain outcome is held for a person to resolve.