What is PINT-OM?

Every e-invoicing mandate needs to answer one deceptively hard question: what, exactly, does a valid invoice file look like? Which fields are mandatory, how is a tax rate expressed, what happens with a discount line, a prepayment, a credit note? Oman's answer is PINT-OM.

The family tree

PINT-OM didn't appear from nowhere. It sits at the end of a sensible chain of standards:

• UBL (Universal Business Language) — an international XML vocabulary for business documents. The raw grammar.
• Peppol PINT — the "Peppol International Invoice" model, which defines a common core of invoice rules that work across borders.
• PINT-OM — Oman's specialization of PINT: the shared international core plus the fields and rules the Oman Tax Authority requires, including mandatory VAT data.

The design is deliberate. The core of an Omani invoice looks like the core of a Singaporean or a Belgian one, which is what lets invoices cross borders over the same Peppol network. The "-OM" layer carries what's specific to Oman. The UAE did the same thing with its own flavor, PINT AE.

What it means for your data

Your ERP already stores most of what PINT-OM wants — party details, line items, quantities, tax amounts. The friction is rarely missing data; it's data in the wrong shape. Three examples we see constantly:

• Customer VAT numbers stored in a free-text "notes" field, or missing for cash customers
• Units of measure that don't map to the required code list ("pcs", "PCS", "piece", "unit" — pick one)
• Tax logic applied at invoice level when PINT-OM validates it line by line

None of these are hard to fix. All of them are annoying to discover during go-live week, which is the argument for mapping your fields early — well before your phase deadline.

Validation: where PINT-OM gets real

A PINT-OM file isn't valid because it parses; it's valid because it passes the rulebook — schema checks, code list checks, and Schematron business rules (things like "tax total must equal the sum of line taxes"). Accredited providers run these checks before anything is sent onward. A good one runs them early enough that a broken invoice never leaves your building.