Troubleshooting and resources

Troubleshooting

"Amount must have 3 decimal places"

"Scheme not recognized" / "Unknown identifier scheme: 0248"

What you may see. A CSV or Excel import of an Omani invoice is refused with the rule EDEC-ICD-0248 and the message Unknown identifier scheme: 0248, pointing at buyer.peppol_id or seller.peppol_id.
Your VAT number is not the problem. 0248 is a valid, active Peppol participant identifier scheme — OM:VAT, the Oman Value Added Tax Identification Number issued by the Tax Authority, Oman. It has been in the official Peppol code lists since version 9.6. A refusal here is about the code list our validation is comparing against, not about your data, so there is nothing to correct on the invoice.
A route that works today. The same invoice is accepted by POST /api/v1/invoices and by POST /api/v1/invoices/validate, which do not check identifier schemes against that list. Note that POST /api/v1/invoices/validate/deep runs the same check as the import, so it reports the same finding.
Please tell us if you see it — see Support — quoting the rule EDEC-ICD-0248, so we can bring the code list on your cell up to date.

"QR code shows gibberish when scanned"

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

"CustomizationID validation failed"

Use one of the three PINT OM identifiers exactly as written, on its own, with nothing before or after it: urn:peppol:pint:billing-1@om-1 for an invoice or credit note, urn:peppol:pint:selfbilling-1@om-1 for a self-billing invoice or credit note, and urn:peppol:taxdata:om-1 for a Tax Data Document.
For a billing or self-billing document the check is the fatal rule ALIGNED-IBRP-001-OM, which requires the specification identifier (IBT-024) to start with the value for the kind of document you are sending. For a Tax Data Document it is the fatal rule ibr-tdd-01, which requires the identifier to be exactly urn:peppol:taxdata:om-1.
Do not add a #conformant# suffix, and do not put anything in front of the identifier. No Omani identifier has a #conformant# part. That convention belongs to CEN EN 16931 conformant CIUSes such as Singapore's, where the CIUS identifier follows urn:cen.eu:en16931:2017#conformant#…. Written that way round for Oman, the value no longer starts with urn:peppol:pint:billing-1@om-1 and ALIGNED-IBRP-001-OM fails. Appended instead, it gets past that rule and then breaks the send in a harder place to diagnose: the document type no longer matches the entry published in the Peppol document-type list, so the receiver lookup finds nothing. Earlier revisions of this page said the suffix was required. That was wrong — a leftover from the retired Fawtara CIUS — and following it made a document worse, not better.

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