Fiscal Invoice Response Structure

When fiscalisation succeeds, the response carries the invoice as URA recorded it, including the fiscal identifiers your ERP must capture:

{
    "response": "OK",
    "message": "Invoice fiscalised successfully",
    "data": {
        "sellerDetails": { "referenceNo": "INV-2026-001", ... },
        "basicInformation": {
            "invoiceNo": "322000150744", // The FDN (Fiscal Document Number)
            "antifakeCode": "31359767222004350398", // Verification code
            "issuedDate": "2026-05-30 10:30:00",
            ...
        },
        "summary": {
            "grossAmount": "200000.00",
            "qrCode": "02000000416B9C...", // Rendered as the QR image on the printed invoice
            ...
        },
        ...
    }
}

Want a working example of the invoice response? Chat with our team

Tax categories in the response

Each tax line in the response is labelled with its tax category. EFRIS reports standard-rated VAT, zero-rated and exempt supplies, deemed VAT, excise duty, and other levies such as stamp duty, local hotel service tax, and the UCC levy - each shown separately in the tax summary of the printed invoice.

Invoice display layout - the 6 URA sections

A compliant printed (or on-screen) e-invoice renders the response in this order, as a single scrollable column:

┌───────────────────────────────────────────┐
│  EFRIS     e-INVOICE/TAX INVOICE     1/1  │  ← Header
├───────────────────────────────────────────┤
│ SECTION A: Seller Details                 │
│   TIN · Legal Name · Address · Reference  │
├───────────────────────────────────────────┤
│ SECTION B: URA / Fiscal Information       │
│   FDN · Verification Code                 │
│   Issued Date · Device                    │
├───────────────────────────────────────────┤
│ SECTION C: Buyer Details                  │
│   Name · TIN (if B2B)                     │
├───────────────────────────────────────────┤
│ SECTION D: Goods & Services               │
│   Table: No | Item | Qty | Price | Tax    │
├───────────────────────────────────────────┤
│ SECTION E: Tax Summary                    │
│   Table: Category | Net | Tax | Gross     │
├───────────────────────────────────────────┤
│ SECTION F: Invoice Summary                │
│   Net · Tax · Gross (bold) · Amount words │
│   Payment mode · Remarks                  │
├───────────────────────────────────────────┤
│  *** END OF e-INVOICE/TAX INVOICE ***     │  ← Footer
├───────────────────────────────────────────┤
│  [QR CODE]  - Scan to verify on URA       │
└───────────────────────────────────────────┘

The qrCode from summary is printed as a QR image; scanning it verifies the invoice on URA's systems. The FDN and verification code must be printed in Section B exactly as returned.

Recovering a lost response

If your ERP times out during fiscalisation and never receives the response, do not resubmit the invoice. The fiscal data can be recovered with POST /query-invoices and POST /invoice-details - see Best Practices.