firs-nrs-einvoice-api.html

FIRS NRS e-Invoice API Documentation

Provider:

Matt O' Bell Limited

Integration Model:

Access Point (UBL 2.1 Compliant)

Supported Profiles:

B2B, B2C, B2G

1. Standards & Compliance

Standard	Specification
UBL Invoice	Version 2.1
Namespace	urn:oasis:names:specification:ubl:schema:xsd:Invoice-2
Encoding	UTF-8
Transport	HTTPS (TLS 1.2+)
Authentication	OAuth2 / API Key (Access Point dependent)

2. Invoice Submission Endpoint

Method: POST

Endpoint: /api/v1/invoices

Required Headers

Authorization: Bearer {access_token}

Content-Type: application/xml

X-Request-ID: Unique Request Identifier

3. Request Payload (UBL 2.1)




  urn:fdc:ng.gov:firs:e-invoice:1.0
  NRS-B2B
  INV-2026-001
  550e8400-e29b-41d4-a716-446655440000
  2026-02-06
  380
  NGN

4. Supported Invoice Profiles

B2B: ProfileID = NRS-B2B

B2C: ProfileID = NRS-B2C

B2G: ProfileID = NRS-B2G

5. Successful Response


{
  "status": "ACCEPTED",
  "irn": "b1946ac92492d2347c6235b4d2611184e7a0cce3e1e5a1e9f3a0c3c5b8f7d9e2",
  "qrCode": "BASE64_ENCODED_QR_PAYLOAD",
  "validationTimestamp": "2026-02-06T14:22:10Z",
  "requestId": "REQ-20260206-001"
}

6. IRN & QR Code Handling

IRN and QR Code are generated by the FIRS NRS platform and returned via the Access Point. The system does not generate IRN locally. QR content is rendered exactly as returned without modification.

7. Audit & Logging

The system stores submitted UBL XML, IRN, validation timestamp, status, and response logs for compliance and audit purposes.

FIRS NRS e-Invoice API Documentation​