E-invoices, prepared for NRS MBS.
MiTax prepares and validates invoices for the Nigeria Revenue Service Merchant-Buyer Solution (MBS) e-invoicing format and queues them for transmission. Transmission to MBS runs through an accredited provider once that channel is enabled; until then, no Invoice Reference Number is issued or implied.
Built to the NITDA National Regulatory Guideline for Electronic Invoicing (2025) and the PEPPOL/PINT-NG profile. MiTax does not currently hold NRS System Integrator or Access Point Provider accreditation.
What we conform to.
UBL 2.1 / PINT-NG
EN 16931 · BIS Billing 3.0Every invoice is a Universal Business Language 2.1 document on the Nigerian PEPPOL International (PINT-NG) profile: customization and profile identifiers, supplier and customer parties, tax categories and legal monetary totals.
IRN + CSID + QR
registry acknowledgementWhen MBS validates an invoice it returns the Invoice Reference Number, the Cryptographic Stamp Identifier and a QR code. MiTax stores only values the registry returns and never fabricates them.
TIN-verified parties
HSN · NGN · VAT 7.5%Counter-parties are validated against the NRS payee-party service before submission. Line items carry HSN commodity codes; VAT is applied at the NTA-2025 standard rate.
Draft to confirmed.
The registry steps below apply once transmission through an accredited provider is enabled for your integration. Before that, invoices are prepared, validated and held in the queue.
- validate-party: confirm the buyer’s TIN (or RC / phone) against the NRS payee-party validator. Positive results are cached for 24 hours.
- submit: post the UBL 2.1 document to the MBS validation endpoint. A successful response returns an
IRN,CSIDandQR; the invoice then moves tovalidated. - confirm: after the buyer accepts, finalise the IRN with MBS and move the invoice to
confirmed.
Request & response.
Requests authenticate with your API Rail key in X-API-Key, carry an Idempotency-Key, and set an environment of sandbox (default) or production. The full schema is in the live contract at api.mitax.io/v1/openapi.json and the developer documentation at api.mitax.io/docs.
Request
{
"customer_ref": "acme-cust-42",
"invoice": { /* BIS Billing 3.0 payload: seller, buyer, lines, totals */ },
"environment": "sandbox" // sandbox | production
}
Response
{
"ok": true,
"data": { /* queued e-invoice record */ },
"meta": { "correlation_id": "acme-req-42", "api_version": "v1" }
}
The call validates the invoice and places it on the MiTax e-invoicing queue. An Invoice Reference Number, CSID and QR code are returned only after MBS issues them through the accredited channel. A rejection from MBS is preserved verbatim; transport errors leave the invoice retryable.
A UBL 2.1 invoice.
The ubl_invoice_jsonb body carries a PINT-NG invoice. Below is the XML form of the same structure: identifiers, TIN-bearing parties, tax subtotals by category, monetary totals and HSN-classified lines.
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"> <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:peppol:pint:billing-1@ng-1</cbc:CustomizationID> <cbc:ProfileID>urn:peppol:bis:billing</cbc:ProfileID> <cbc:ID>MTX-B2B-2025-000481</cbc:ID> <cbc:IssueDate>2025-09-15</cbc:IssueDate> <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode> <cbc:DocumentCurrencyCode>NGN</cbc:DocumentCurrencyCode> <!-- AccountingSupplierParty + AccountingCustomerParty with PartyTaxScheme (TIN) --> <!-- TaxTotal → TaxSubtotal by category S/Z/E (VAT 7.5%) --> <!-- LegalMonetaryTotal + InvoiceLine[] with HSN ItemClassificationCode --> </Invoice>
Prepare your invoices for NRS MBS.
MiTax handles the format, the validation and the queue, with transmission through an accredited provider once that channel is enabled. Tell us what you’re building.
- UBL 2.1 / PINT-NG
- IRN + CSID + QR
- TIN-verified parties