Oman 🇴🇲

E-invoicing requirements and Peppol compliance for the Sultanate of Oman.

Overview

Aspect	Details
Tax Authority	Oman Tax Authority (OTA)
B2G Mandate	Active — Peppol network
B2B Mandate	Phased rollout (2025–2027)
Required CIUS	PINT OM (Official OpenPeppol PINT Oman)
Primary Scheme	0248 (Oman VATIN)
Currency	OMR (Omani Rial, 3 decimal places)
VAT Rate	5% standard rate
QR Code	Mandatory — Fatoora TLV format
Digital Signature	XAdES-BES enveloped signature

Oman Peppol Authority

Oman joined the Peppol network under the OpenPeppol umbrella. The Oman Tax Authority (OTA) mandates Peppol-based e-invoicing with additional national requirements (Fatoora CIUS) on top of standard Peppol BIS 3.0.

Oman PINT OM (Official Schematrons)

The official OpenPeppol PINT OM specification replaces the earlier Fatoora CIUS. It includes billing, self-billing, and Tax Data Document (TDD) Schematrons.

Customization IDs

<!-- PINT OM Billing -->
<cbc:CustomizationID>urn:peppol:pint:billing-1@om-1</cbc:CustomizationID>

<!-- PINT OM Self-Billing -->
<cbc:CustomizationID>urn:peppol:pint:selfbilling-1@om-1</cbc:CustomizationID>

<!-- TDD (Tax Data Document) -->
<cbc:CustomizationID>urn:peppol:taxdata:om-1</cbc:CustomizationID>

Profile IDs

<!-- Billing / Self-Billing -->
<cbc:ProfileID>urn:peppol:bis:billing</cbc:ProfileID>

<!-- Tax Reporting -->
<cbc:ProfileID>urn:peppol:taxreporting</cbc:ProfileID>

Schematron Packs

GoRoute runs the official OpenPeppol PINT OM Schematrons compiled with Saxon-HE 12.4:

Pack	Schematrons	Description
Billing Invoice	2 (preprocessed + jurisdiction-aligned)	Standard tax invoice validation
Billing Credit Note	2	Credit note validation
Self-Billing Invoice	2	Self-billing invoice validation
Self-Billing Credit Note	2	Self-billing credit note validation
TDD	1	Tax Data Document for CTC reporting

PINT OM documents are auto-detected by the urn:peppol:pint:billing-N@om-N or urn:peppol:pint:selfbilling-N@om-N CustomizationID pattern and skip baseline CEN+BIS Schematrons.

Ruleset 1.0.1 — the rules that reject invoices

PINT OM 1.0.1 layers 120 Oman-specific rules (IBR-…-OM) on top of Peppol BIS Billing 3.0. Most are structural and you will never see them. These are the ones that actually fail in production.

Document type codes

Code	Document	Notes
`380`	Commercial invoice	The standard case
`381`	Credit note	Requires a preceding invoice reference — see IBR-032-OM
`383`	Debit note	Same preceding-invoice requirement
`386`	Prepayment invoice
`389`	Self-billed invoice	Buyer issues on the supplier's behalf. Restricted by IBR-177-OM
`261`	Self-billed credit note	Requires a preceding reference and is restricted by IBR-177-OM

BTOM-001 — invoice transaction type

Every Oman document carries a 20-character bitmap of 1s and 0s with at least one bit set. It travels in the name attribute of the type code element, not as a separate field:

<cbc:InvoiceTypeCode name="00100000000000000000">389</cbc:InvoiceTypeCode>

Fifteen of the twenty positions are defined; the rest are reserved. Two examples that appear in the rules verbatim:

Bitmap	Meaning
`00100000000000000000`	Self-billed invoice / credit note
`00000000100000000000`	Invoice for import of services under reverse charge

IBR-001-OM enforces the shape — exactly 20 characters, [01] only. Several other rules then key off individual positions, so a structurally valid bitmap with the wrong bit set still fails.

IBR-032-OM — the one that catches everyone

Fatal. If the type code is 381, 383 or 261, the document MUST carry all three of the preceding invoice's reference, issue date and UUID. Missing any one is a hard rejection:

<cac:BillingReference>
    <cac:InvoiceDocumentReference>
        <cbc:ID>INV-2026-00042</cbc:ID>                      <!-- IBT-025 -->
        <cbc:IssueDate>2026-07-14</cbc:IssueDate>            <!-- IBT-026 -->
        <cbc:UUID>7d4f1e2a-...-9c3b</cbc:UUID>               <!-- BTOM-031 -->
    </cac:InvoiceDocumentReference>
</cac:BillingReference>

The UUID is the one people omit, because BIS Billing 3.0 does not ask for it. It must be the original invoice's UUID, not a fresh one.

IBR-177-OM — self-billing is not general purpose

A self-billed invoice 389 or self-billed credit note 261 is only valid when BTOM-001 is one of a short list: self-billed, import of services under reverse charge, profit-margin self-billing, or import of goods. Self-billing outside those cases is rejected — this is a policy rule, not a formatting one.

IBR-002-OM — deterministic UUIDs

The invoice UUID must be a version 5 UUID, not random. Re-deriving the same invoice must produce the same UUID, which is what makes the preceding-invoice reference in IBR-032-OM verifiable.

IBR-034-OM — non-OMR invoices

If the invoice currency (IBT-005) is not OMR, the VAT accounting currency (IBT-006) MUST be present.

Zero-rating and exemption reason codes

A zero-rated or exempt line needs more than a Z or E category — it needs a reason code from the Oman code list. Without one, validation fails.

List	Codes	Used for
`VATZR-OM-01` … `VATZR-OM-16`	16	Zero-rating reasons
`VATEX-OM-01` … `VATEX-OM-12`	12	Exemption reasons

<cac:TaxCategory>
    <cbc:ID>Z</cbc:ID>
    <cbc:Percent>0</cbc:Percent>
    <cbc:TaxExemptionReasonCode>VATZR-OM-09</cbc:TaxExemptionReasonCode>
    <cbc:TaxExemptionReason>Export of service</cbc:TaxExemptionReason>
    <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
</cac:TaxCategory>

Two that matter most to importers and exporters:

VATZR-OM-09 — export of service
VATZR-OM-12 — re-export of goods

Medicines and Ministry-of-Health-approved medical equipment are zero-rated under Ministerial Decision 59/2021, made under Articles 51–53 of Sultani Decree 151/2020.

Validate before you send

POST /api/v1/invoices/validate/deep runs the full PINT OM 1.0.1 Schematron and returns every rule that fired, by identifier. Cheaper than a rejection, and the free sandbox is provisioned within 24 hours.

Identifier Scheme — 0248

Oman uses scheme 0248 (Oman VATIN) for participant identification, and the identifier keeps its OM prefix.

# Oman participant
participant = {
    "scheme": "0248",
    "identifier": "OM1100012345",
    "name": "Oman Trading Company LLC",
    "country": "OM"
}

Peppol ID Format

0248:OM<10-digit-VATIN>

Not 9959

Earlier revisions of this page said 9959. That is wrong for Oman and it is a costly mistake: 9959:1100012345 is not a registered participant, so the SMP lookup returns nothing and delivery fails with a transport error rather than a validation message. The authoritative sources are register-oman-tsmp.py (“Scheme : 0248 (Oman VATIN). Participant id: iso6523-actorid-upis::0248:OM<VATIN>”), the OTA sample invoices, and the live SMP registrations.

Example: 0248:OM1100012345

SMP Lookup

# Verify an Oman participant exists on Peppol
curl "https://smp-test.goroute.ai/iso6523-actorid-upis::0248:OM1100012345"   # registered, resolves

Currency — OMR (3 Decimal Places)

Oman uses the Omani Rial (OMR) which has 3 decimal places — unlike EUR/USD which have 2.

<!-- All amounts use 3 decimal places -->
<cbc:TaxAmount currencyID="OMR">50.000</cbc:TaxAmount>
<cbc:TaxInclusiveAmount currencyID="OMR">1050.000</cbc:TaxInclusiveAmount>
<cbc:PayableAmount currencyID="OMR">1050.000</cbc:PayableAmount>

3 Decimal Places

Always use 3 decimal places for OMR amounts (e.g., 1050.000, not 1050.00). This applies to all monetary fields in the invoice including line items, tax amounts, and totals.

VAT in Oman

Oman introduced VAT at 5% in April 2021.

Category	Rate	Code	Description
Standard	5%	`S`	Most goods and services
Zero-rated	0%	`Z`	Exports, certain food items, healthcare
Exempt	0%	`E`	Financial services, residential rent

Z and E are not enough on their own

A zero-rated or exempt line must also carry a reason code — see Zero-rating and exemption reason codes. A Z category with no VATZR-OM-* code fails validation.

<cac:TaxCategory>
    <cbc:ID>S</cbc:ID>
    <cbc:Percent>5</cbc:Percent>
    <cac:TaxScheme>
        <cbc:ID>VAT</cbc:ID>
    </cac:TaxScheme>
</cac:TaxCategory>

QR Code Requirements (Fatoora)

Oman mandates a Fatoora QR code on all invoices. The QR contains TLV (Tag-Length-Value) encoded invoice data that allows offline verification.

TLV Fields

Tag	Field	Description	Example
1	Seller Name	Seller's registered name (UTF-8)	`Al Haya Trading LLC`
2	VAT Number	Seller's tax registration number	`OM1234567890`
3	Timestamp	ISO 8601 issue date/time	`2026-02-08T12:00:00Z`
4	Total with VAT	Tax-inclusive amount (3 decimals)	`1050.000`
5	VAT Amount	Total VAT (3 decimals)	`50.000`
6	Invoice Hash	SHA-256 digest (base64)	`A1B2C3...`

TLV Encoding

Each field is encoded as: Tag (1 byte) + Length (1 byte) + Value (UTF-8 bytes)

Tag 1: [20] = Al Haya Trading LLC
Tag 2: [12] = OM1234567890
Tag 3: [20] = 2026-02-08T12:00:00Z
Tag 4: [8]  = 1050.000
Tag 5: [6]  = 50.000
Tag 6: [44] = <base64 SHA-256 hash>

The concatenated TLV bytes are base64-encoded and embedded in the UBL XML.

QR Embedding in UBL

The QR data is stored in an AdditionalDocumentReference with ID QR:

<cac:AdditionalDocumentReference>
    <cbc:ID>QR</cbc:ID>
    <cac:Attachment>
        <cbc:EmbeddedDocumentBinaryObject mimeCode="text/csv" filename="QR">
            AQxBbCBIYXlhIExMQwIKT00xMjM0NTY3ODkw...
        </cbc:EmbeddedDocumentBinaryObject>
    </cac:Attachment>
</cac:AdditionalDocumentReference>

Invoice Hash

A SHA-256 hash of the invoice's business content is also embedded:

<cac:AdditionalDocumentReference>
    <cbc:ID>HASH</cbc:ID>
    <cac:Attachment>
        <cbc:EmbeddedDocumentBinaryObject mimeCode="application/octet-stream" filename="HASH">
            kX5xVq2F8a3pZ...base64-encoded-sha256...
        </cbc:EmbeddedDocumentBinaryObject>
    </cac:Attachment>
</cac:AdditionalDocumentReference>

GoRoute Handles This Automatically

When you send an invoice to or from an Oman participant via GoRoute, the QR code, hash, and digital signature are automatically generated by our Fatoora signing pipeline. You send a standard UBL invoice — we add the Oman compliance elements.

Digital Signature

Oman requires an XAdES-BES enveloped digital signature on invoices:

Algorithm: RSA-SHA256
Canonicalization: Exclusive C14N 1.0
Certificate: PKCS12 keystore (.p12)
Location: Inside ext:UBLExtensions (UBL DSig Profile)

<!-- Signature reference in the invoice body -->
<cac:Signature>
    <cbc:ID>urn:oasis:names:specification:ubl:signature:Invoice</cbc:ID>
    <cbc:SignatureMethod>urn:oasis:names:specification:ubl:dsig:enveloped:xades</cbc:SignatureMethod>
</cac:Signature>

<!-- Actual cryptographic signature in UBLExtensions (first child of Invoice) -->
<ext:UBLExtensions>
    <ext:UBLExtension>
        <ext:ExtensionContent>
            <sig:UBLDocumentSignatures>
                <sac:SignatureInformation>
                    <ds:Signature Id="invoice-signature">
                        <!-- SignedInfo, SignatureValue, KeyInfo -->
                    </ds:Signature>
                </sac:SignatureInformation>
            </sig:UBLDocumentSignatures>
        </ext:ExtensionContent>
    </ext:UBLExtension>
</ext:UBLExtensions>

Sending via GoRoute API

JSON Format (Recommended)

curl -X POST https://app.goroute.ai/peppol-api/api/v1/invoices \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "invoice_number": "OM-INV-2026-001",
    "issue_date": "2026-02-08",
    "due_date": "2026-03-10",
    "currency": "OMR",
    "sender": {
      "name": "Al Haya Trading LLC",
      "street": "Sultan Qaboos Street",
      "city": "Muscat",
      "postal_code": "100",
      "country": "OM",
      "vat_number": "OM1234567890",
      "peppol_id": "0248:OM1100012345"
    },
    "receiver": {
      "name": "Oman National Corp",
      "street": "Al Khuwair Road",
      "city": "Muscat",
      "postal_code": "200",
      "country": "OM",
      "vat_number": "OM9876543210",
      "peppol_id": "0248:OM1100054321"
    },
    "lines": [
      {
        "description": "IT Consulting Services - January 2026",
        "quantity": 160,
        "unit": "HUR",
        "unit_price": 25.000,
        "vat_rate": 5,
        "vat_category": "S"
      }
    ]
  }'

Python SDK

import requests

API_KEY = "YOUR_API_KEY"
BASE_URL = "https://app.goroute.ai/peppol-api"

invoice = {
    "invoice_number": "OM-INV-2026-001",
    "issue_date": "2026-02-08",
    "currency": "OMR",
    "sender": {
        "name": "Al Haya Trading LLC",
        "country": "OM",
        "vat_number": "OM1234567890",
        "peppol_id": "0248:OM1100012345"
    },
    "receiver": {
        "name": "Oman National Corp",
        "country": "OM",
        "vat_number": "OM9876543210",
        "peppol_id": "0248:OM1100054321"
    },
    "lines": [
        {
            "description": "IT Consulting Services",
            "quantity": 160,
            "unit": "HUR",
            "unit_price": 25.000,
            "vat_rate": 5,
            "vat_category": "S"
        }
    ]
}

response = requests.post(
    f"{BASE_URL}/api/v1/invoices",
    headers={"X-API-Key": API_KEY},
    json=invoice
)

result = response.json()
print(f"Transaction: {result['transaction_id']}")
print(f"Status: {result['status']}")
# QR code, hash, and signature are added automatically

UBL XML (Direct)

You can also send raw UBL XML. GoRoute will add the Fatoora QR, hash, and signature automatically:

curl -X POST https://app.goroute.ai/peppol-api/api/v1/documents/send \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/xml" \
  --data-binary @oman-invoice.xml

Example Oman Invoice (Full UBL)

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
    
    <!-- Oman PINT OM -->
    <cbc:CustomizationID>urn:peppol:pint:billing-1@om-1</cbc:CustomizationID>
    <cbc:ProfileID>urn:peppol:bis:billing</cbc:ProfileID>
    
    <cbc:ID>OM-INV-2026-001</cbc:ID>
    <cbc:IssueDate>2026-02-08</cbc:IssueDate>
    <cbc:IssueTime>12:00:00Z</cbc:IssueTime>
    <cbc:DueDate>2026-03-10</cbc:DueDate>
    <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
    <cbc:DocumentCurrencyCode>OMR</cbc:DocumentCurrencyCode>
    <cbc:BuyerReference>PO-2026-456</cbc:BuyerReference>
    
    <!-- Seller (Oman company) -->
    <cac:AccountingSupplierParty>
        <cac:Party>
            <cbc:EndpointID schemeID="0248">OM1100012345</cbc:EndpointID>
            <cac:PartyName>
                <cbc:Name>Al Haya Trading LLC</cbc:Name>
            </cac:PartyName>
            <cac:PostalAddress>
                <cbc:StreetName>Sultan Qaboos Street</cbc:StreetName>
                <cbc:CityName>Muscat</cbc:CityName>
                <cbc:PostalZone>100</cbc:PostalZone>
                <cac:Country>
                    <cbc:IdentificationCode>OM</cbc:IdentificationCode>
                </cac:Country>
            </cac:PostalAddress>
            <cac:PartyTaxScheme>
                <cbc:CompanyID>OM1234567890</cbc:CompanyID>
                <cac:TaxScheme>
                    <cbc:ID>VAT</cbc:ID>
                </cac:TaxScheme>
            </cac:PartyTaxScheme>
            <cac:PartyLegalEntity>
                <cbc:RegistrationName>Al Haya Trading LLC</cbc:RegistrationName>
                <cbc:CompanyID>1234567890</cbc:CompanyID>
            </cac:PartyLegalEntity>
        </cac:Party>
    </cac:AccountingSupplierParty>
    
    <!-- Buyer (Oman company) -->
    <cac:AccountingCustomerParty>
        <cac:Party>
            <cbc:EndpointID schemeID="0248">OM1100054321</cbc:EndpointID>
            <cac:PartyName>
                <cbc:Name>Oman National Corp</cbc:Name>
            </cac:PartyName>
            <cac:PostalAddress>
                <cbc:StreetName>Al Khuwair Road</cbc:StreetName>
                <cbc:CityName>Muscat</cbc:CityName>
                <cbc:PostalZone>200</cbc:PostalZone>
                <cac:Country>
                    <cbc:IdentificationCode>OM</cbc:IdentificationCode>
                </cac:Country>
            </cac:PostalAddress>
            <cac:PartyTaxScheme>
                <cbc:CompanyID>OM9876543210</cbc:CompanyID>
                <cac:TaxScheme>
                    <cbc:ID>VAT</cbc:ID>
                </cac:TaxScheme>
            </cac:PartyTaxScheme>
            <cac:PartyLegalEntity>
                <cbc:RegistrationName>Oman National Corp</cbc:RegistrationName>
            </cac:PartyLegalEntity>
        </cac:Party>
    </cac:AccountingCustomerParty>
    
    <cac:PaymentMeans>
        <cbc:PaymentMeansCode>30</cbc:PaymentMeansCode>
    </cac:PaymentMeans>
    
    <cac:TaxTotal>
        <cbc:TaxAmount currencyID="OMR">200.000</cbc:TaxAmount>
        <cac:TaxSubtotal>
            <cbc:TaxableAmount currencyID="OMR">4000.000</cbc:TaxableAmount>
            <cbc:TaxAmount currencyID="OMR">200.000</cbc:TaxAmount>
            <cac:TaxCategory>
                <cbc:ID>S</cbc:ID>
                <cbc:Percent>5</cbc:Percent>
                <cac:TaxScheme>
                    <cbc:ID>VAT</cbc:ID>
                </cac:TaxScheme>
            </cac:TaxCategory>
        </cac:TaxSubtotal>
    </cac:TaxTotal>
    
    <cac:LegalMonetaryTotal>
        <cbc:LineExtensionAmount currencyID="OMR">4000.000</cbc:LineExtensionAmount>
        <cbc:TaxExclusiveAmount currencyID="OMR">4000.000</cbc:TaxExclusiveAmount>
        <cbc:TaxInclusiveAmount currencyID="OMR">4200.000</cbc:TaxInclusiveAmount>
        <cbc:PayableAmount currencyID="OMR">4200.000</cbc:PayableAmount>
    </cac:LegalMonetaryTotal>
    
    <cac:InvoiceLine>
        <cbc:ID>1</cbc:ID>
        <cbc:InvoicedQuantity unitCode="HUR">160</cbc:InvoicedQuantity>
        <cbc:LineExtensionAmount currencyID="OMR">4000.000</cbc:LineExtensionAmount>
        <cac:Item>
            <cbc:Name>IT Consulting Services - January 2026</cbc:Name>
            <cac:ClassifiedTaxCategory>
                <cbc:ID>S</cbc:ID>
                <cbc:Percent>5</cbc:Percent>
                <cac:TaxScheme>
                    <cbc:ID>VAT</cbc:ID>
                </cac:TaxScheme>
            </cac:ClassifiedTaxCategory>
        </cac:Item>
        <cac:Price>
            <cbc:PriceAmount currencyID="OMR">25.000</cbc:PriceAmount>
        </cac:Price>
    </cac:InvoiceLine>
</Invoice>

What GoRoute Adds Automatically

When this invoice is sent via GoRoute, the following Fatoora elements are added before Peppol transmission:

QR Code — AdditionalDocumentReference[ID='QR'] with TLV-encoded data
Invoice Hash — AdditionalDocumentReference[ID='HASH'] with SHA-256 digest
Digital Signature — ext:UBLExtensions with XAdES-BES enveloped signature
cac:Signature — Signature reference element

You do not need to generate these yourself.

Validation

GoRoute applies multi-layer validation to Oman invoices:

Layer	Check	Rule
1	UBL 2.1 XSD	Structural XML validity
2	Business rules	Totals, calculations, required fields
3	eDEC Code Lists	Participant schemes, currencies, process IDs
3B	PINT OM Schematron	Official OpenPeppol jurisdiction rules (IBR-OM)
3C	TDD Schematron	Tax Data Document validation (CTC reporting)

PINT vs Baseline

PINT OM invoices (detected by urn:peppol:pint:billing-N@om-N in CustomizationID) skip the baseline CEN-EN16931 + Peppol BIS Schematrons. They run only the official PINT OM Schematrons, which already incorporate all required European and Peppol rules along with Oman-specific jurisdiction rules.

TDD (Tax Data Document)

Oman's CTC (Continuous Transaction Controls) protocol requires a Tax Data Document to be submitted to the Oman Tax Authority within 15 minutes of invoice issuance. GoRoute generates the TDD automatically:

Root element: pxs:TaxData (namespace urn:peppol:schema:om-taxdata:1.0)
Receiving party: Oman Tax Authority (0242:000773)
Validated against TDD-OM-peppol-om-tdd.xslt before submission
Supports document types: Send, Receive, Withdraw, Forward

Comparison with Saudi Arabia (ZATCA)

Oman's Fatoora system is inspired by Saudi Arabia's ZATCA but with key differences:

Feature	Oman (OTA)	Saudi Arabia (ZATCA)
Network	Peppol	ZATCA platform
Base Standard	Peppol BIS 3.0	UBL 2.1 (no Peppol)
QR Format	TLV (Tags 1-6)	TLV (Tags 1-9)
Signature	XAdES-BES	XMLDSIG
Currency Decimals	3 (OMR)	2 (SAR)
Tax Rate	5%	15%
Clearance	Via Peppol AP	Via ZATCA portal
Certificate	Peppol AP cert	ZATCA-issued cert

Troubleshooting

Common Issues

"Amount must have 3 decimal places"

OMR uses 3 decimal places. Use 1050.000 not 1050.00.

"Scheme not recognized"

Ensure you're using the latest eDEC code lists. GoRoute updates these automatically.

"QR code shows gibberish when scanned"

Fatoora QR codes contain TLV binary data, not plain text. Use a Fatoora-compatible reader or the GoRoute dashboard to verify.

"CustomizationID validation failed"

Use the exact Oman CIUS CustomizationID shown above. The #conformant# suffix is required.

Resources

GoRoute API Reference — Full endpoint documentation
Oman Tax Authority — Official OTA portal
OpenPeppol — Peppol specifications
GoRoute Dashboard — Send and manage invoices

Overview​

Oman PINT OM (Official Schematrons)​

Customization IDs​

Profile IDs​

Schematron Packs​

Ruleset 1.0.1 — the rules that reject invoices​

Document type codes​

BTOM-001 — invoice transaction type​

IBR-032-OM — the one that catches everyone​

IBR-177-OM — self-billing is not general purpose​

IBR-002-OM — deterministic UUIDs​

IBR-034-OM — non-OMR invoices​

Zero-rating and exemption reason codes​

Identifier Scheme — 0248​

Peppol ID Format​

SMP Lookup​

Currency — OMR (3 Decimal Places)​

VAT in Oman​

QR Code Requirements (Fatoora)​

TLV Fields​

TLV Encoding​

QR Embedding in UBL​

Invoice Hash​

Digital Signature​

Sending via GoRoute API​

JSON Format (Recommended)​

Python SDK​

UBL XML (Direct)​

Example Oman Invoice (Full UBL)​

Validation​

TDD (Tax Data Document)​

Comparison with Saudi Arabia (ZATCA)​

Troubleshooting​

Common Issues​

Resources​

Further reading​