Which VAT Category Code Carries Each Norwegian Rate in an EHF Invoice
Norway's 25%, 15%, 12% and 11.11% rates all carry one VAT category code: S. The rate belongs in the percentage field, and inventing a code fails BR-CL-17.
Norway's 25%, 15%, 12% and 11.11% rates all carry one VAT category code: S. The rate belongs in the percentage field, and inventing a code fails BR-CL-17.
Your shop order does not say the e-invoice was delivered. What each state on the order means, which ones need you, and how to reissue or resend from the order.
EHF Reminder 3.0, Forward Billing 3.0 and Payment Request 3.0 have no Peppol BIS Billing equivalent. What each is for, and the SMP opt-in each one needs.
Neither Australia nor New Zealand makes e-invoicing compulsory for a business. What that means for an online shop, its checkout and its business buyers.
A German XRechnung invoice crosses Peppol unchanged, but Oman reports a self-billed PINT OM invoice built from it. See every rule it meets on the way to Oman.
A private Norwegian company does not register in ELMA. That registry is for public bodies; everyone else is published in a provider's SMP under scheme 0192.
Germany has required every domestic business to receive e-invoices since January 2025, and issuing starts in 2027. What both dates mean for an online shop.
San Marino has two e-invoicing rules: cross-border trade with Italy via HUB-SM, live since October 2021, and a domestic mandate compulsory on 1 January 2027.
Belgium has required structured e-invoices between businesses since 1 January 2026. What that means for an online shop's checkout, its invoices and its refunds.
Belgium's B2B e-invoicing rule cuts both ways: your suppliers must send your shop structured invoices. What it takes to be reachable, and to read what arrives.
An invoice from outside Oman cannot produce a tax data document, so your provider raises a self-billed PINT invoice instead and never sends it to the seller.
Receiving an Oman e-invoice is your provider's job, not your inbox's. What has to be registered, what format actually arrives, and who answers the sender.
Switching Oman e-invoicing providers: the outgoing provider removes you from the SMP in one working day, the incoming one has three. How to control the gap.
Your provider accepting on Fawtara is not the same as being reachable. What Oman SMP registration creates, its three-working-day clock, and how to check it.
Four things are agreed with an Oman e-invoicing provider outside the Fawtara portal, and your free exit closes the moment that provider accepts your request.
Appointing an accredited e-invoicing provider in Oman is a request you raise on the Fawtara portal. What it carries, what each status means, and what follows.
A cleared Oman e-invoice that never reached the buyer is a delivery fault, not a document fault. What Submit, Resubmit and Disregard do, and what not to issue.
A deposit invoice cleared by Oman's Tax Authority cannot be withdrawn. What the credit note must reference, why the prepayment flag is a trap, and what breaks.
When the buyer raised the invoice, the buyer issues the correction — a self-billed credit note, type code 261. What it must reference and carry to pass.
An Oman e-invoice reported to the Tax Authority cannot be withdrawn. What a credit note must reference, when a debit note applies, and how to confirm it.
IMDA publishes two lists: accredited Access Points and InvoiceNow-Ready solutions. How to check a provider against both, and what to ask before you sign.
Three ways a Peppol registration happens: your provider makes it, you buy it on its own, or a tax authority creates it centrally. How to tell which is yours.
A Peppol ID is a business number you already hold plus a code for the register it came from. Which number is yours, country by country, and how to register it.
Joining Peppol needs three things: a participant identifier, a record in an SMP, and somebody to send and receive for you. Here is who does each step.
Sage 50, Sage 200 and Sage Business Cloud reach Oman's Fawtara programme through GoRoute. What a Sage invoice already carries, and what Oman asks for on top.
Connecting your own billing, POS or ERP software to Oman's Fawtara: what your code must produce, what GoRoute adds on top, and the order to build it in.
Xero reaches Oman's Fawtara programme through a connector, the API or a spreadsheet. What a Xero invoice carries, and the four fields it has no room for.
Suppliers to Dutch central government must invoice electronically, and every public buyer must accept EN 16931. What SI-UBL 2 is, and how to reach a buyer.
QuickBooks Online reaches Oman's Fawtara programme through a built connector. What it sends, the three fields QuickBooks cannot hold, and what Desktop users do.
Zoho Books reaches Oman's Fawtara programme through an authorised connection to GoRoute. What travels, and the Oman fields an ordinary invoice does not carry.
UBL 2.1 is the schema Peppol billing runs on and UBL 2.0 still validates under it. What the Universal Business Language defines, and the six elements 2.1 added.
A recorded walkthrough shows how an invoice leaves Microsoft Dynamics 365 Business Central, is validated against Oman's rules and reaches the Tax Authority.
A recorded walkthrough follows a live transaction out of an Oracle APEX application, and names the Oman rules the resulting tax report has to satisfy.
Oman e-invoice rejections come from named rules, not opinions. What each identifier means, and why a rule worded should can still refuse the document outright.
Check a real Oman e-invoice against the PINT OM rule packs before sending: how to run it, what each class of failure means, and why a warning is not a failure.
The invoice goes to your customer over Peppol and a data set goes to IRAS. Who sends it, what travels, and what happens to sales that never touch the network.
InvoiceNow-ready means two things in Singapore: an accreditation the vendor holds, and whether your own system can send. Six checks to tell them apart.
An Oman e-invoice is a UBL 2.1 XML document in the PINT OM profile. Where the XML/JSON structured invoice question comes from, and where JSON actually fits.
Before you appoint an Oman e-invoicing software vendor, put six questions in writing: what accreditation covers, who builds the Tax Data Document, how you exit.
A recorded demo shows an invoice raised in Odoo validated against Oman PINT OM rules and cleared. What it covers, what it does not, and how to watch it.
Sending Oman e-invoices from S/4HANA is configuration, not development: one standard communication scenario, a communication user, and the right master data.
Shortlist only from the Ministry of Finance's published list, then compare providers on integration, onboarding time, support hours, pricing and exit.
Does the UAE's 30 October 2026 deadline apply to your business? It covers persons subject to the eInvoicing system with revenue above AED 50 million a year.
The UAE deadline to appoint an Accredited Service Provider moved to 30 October 2026 for revenue above AED 50 million. Implementation is still 1 January 2027.
Oman's amended Article 146 puts simplified tax invoices on the Article 143 timeframes. Retail, fuel and exchange counters share the 2027 dates. What POS needs.
Oman's Article 143 bis 1 obliges taxpayers to secure the invoicing system, handle breakdowns and recover lost data. What it means for IT, and who carries it.
Oman's Article 143 requires an e-invoice when you receive payment before supply, and on deemed supplies. Most ERPs raise neither. What to change before 2027.
Oman's e-invoicing threshold is OMR 5,000,000 of annual supplies. Above it you start 1 April 2027, at or below 1 October 2027. Plus what is left undefined.
Oman's e-invoicing deadline is 1 April 2027 above OMR 5m and 1 October 2027 below it, set by Decision 189/2026. The full timeline, thresholds and exemptions.
Whether Belgium's B2B mandate applies to a foreign company turns on fixed establishment. What it means, what still reaches you, and who can serve you.
Belgian e-invoicing fines run 1,500 to 5,000 euro per offence within three months. The larger cost is an invoice a compliant buyer will not book.
From January 2028 Belgium reports invoice data in near real time on a five-corner Peppol model, with supplier and customer filing separately. What to build.
Belgian participants must use scheme 0208, the enterprise number. Why 9925 is a breach, the mod-97 check digit, and the rule that rejects a bad one.
Belgium and France are both live and enforcing. Germany issues from 1 January 2027 above EUR 800,000 turnover. Three mandates, three shapes, what differs.
Hermes closed on 31 December 2025. Belgian companies are no longer pre-registered on Peppol, so an unreachable buyer is now a real and visible failure.
Four GCC e-invoicing regimes at different stages, and what a business invoicing across the region has to reconcile. Where the mandates diverge, and why.
Qatar has not published a technical specification, but most of the work does not depend on one. A readiness plan that holds up whatever the GTA publishes.
Qatar has no VAT, yet its e-invoicing law is approved. That reverses the GCC pattern and breaks the assumption that scope follows VAT registration.
Most Qatar e-invoicing guides state a technical model as fact. Here is the line between what the GTA has published and what is inference from Saudi and the UAE.
Qatar's Cabinet approved its e-invoicing law on 6 May 2026. What the law establishes, what it leaves to the regulations, and when the mandate is expected.
Not one Qatar e-invoicing date is official beyond 6 May 2026. Which dates the GTA has actually published, which come from press commentary, and how to tell.
Who should own an e-invoicing project, finance or IT? Why mandates fail when run as integrations, and the decisions only a tax owner can make.
Most Omani small businesses invoice from a spreadsheet. How to send Fawtara-compliant e-invoices straight from Excel, and what Oman actually requires.
Oman PINT OM specifications and Fawtara testing keep evolving. What service providers, ERP teams and finance leaders should prepare — without the jargon.
Tally Peppol integration explained: how TallyPrime connects to the Peppol network, why a local agent is required, and how vouchers map to UBL invoices.
Tally e-invoicing Oman explained: how TallyPrime users meet the Fawtara mandate with PINT OM invoices, TDD reporting and a certified Peppol Access Point.
What ATO e-invoicing accreditation verifies for a Peppol service provider - security, interoperability testing and obligations - and why it matters to buyers.
Supplying a Commonwealth agency: how to address a Peppol e-invoice to a federal buyer, register your participant ID, and qualify for 5-day payment terms.
Choosing a Peppol service provider in New Zealand: the accreditation to ask for, how to verify it yourself, and when one trans-Tasman provider covers both.
Peppol software providers explained: the types of provider, what a certified Access Point and SMP do, and how to choose the right one for e-invoicing.
Send test invoices on a Peppol test bed and clear every validation error before go-live. How to get sandbox access, and the test cases that catch problems.
Trans-Tasman e-invoicing: how the AU and NZ joint Peppol approach, PINT A-NZ, and mutual accreditation let a single provider serve both markets.
Australia eInvoicing 2026: the ATO targeted 30% of invoices received via eInvoicing by 1 July, with automated processing by December. What to do now.
New Zealand government e-invoicing: from 1 January 2026, agencies handling over 2,000 domestic trade invoices a year must be Peppol-capable.
PINT A-NZ explained: the Australia-New Zealand Peppol billing profile, how it relates to PINT and BIS Billing 3.0, and who governs it (ATO and MBIE).
PINT A-NZ is now the only accepted Peppol billing profile in Australia after the May 2025 retirement of legacy ANZ. What changed and how to stay compliant.
How to send e-invoices to New Zealand government agencies via Peppol: get on the network, register your ID, produce a valid PINT A-NZ invoice and deliver it.
The UK's move toward e-invoicing: the government consultation, the anticipated 2029 timeline, Peppol's role via the NHS, and how to prepare early.
How to choose a Peppol service provider in Australia: what ATO accreditation means, what to look for, and the questions to ask before you commit.
New Zealand e-invoicing explained: MBIE as Peppol Authority, the PINT A-NZ format, the 2026 agency rule and 2027 large-supplier rule, and what falls in scope.
How New Zealand defines a large supplier for e-invoicing: total revenue over NZ$33 million in each of the two preceding accounting periods. Worked example.
What a Peppol Access Point does in Australia and what the ATO requires to accredit one: PINT A-NZ conformance, SMP, incident reporting and annual review.
Singapore's InvoiceNow explained: the Peppol-based national e-invoicing network, IMDA's role, the IRAS GST transmission rollout and how to get ready.
GoRoute (POP000991) is on the ATO's Peppol service provider register as an accredited provider for Australia — testbed passed for PINT A-NZ and self-billing.
How e-invoicing works in Japan: the Peppol-based PINT JP profile, the Qualified Invoice System for consumption tax, and how to send compliant invoices.
From 1 January 2027 New Zealand government agencies must require large suppliers to e-invoice via Peppol. What a large supplier should decide and do now.
France's e-invoicing mandate is live. The universal receive obligation, the approved platform (PDP) model, e-reporting, Factur-X formats and what to do now.
Germany's B2B e-invoicing mandate explained: the 2025 receive obligation, 2027–2028 issue deadlines, and the XRechnung and ZUGFeRD formats you need.
Malaysia's MyInvois e-invoicing explained: LHDN's four turnover phases ending 1 January 2026, the RM1 million exemption, the clearance model and Peppol.
Saudi Arabia's ZATCA e-invoicing (FATOORA) explained: Phase 1 vs Phase 2, clearance and reporting, standard vs simplified invoices, and how to comply in 2026.
How to choose a Peppol Access Point: the certification, country coverage, validation, security and support criteria that separate safe from risky.
The invoice validation errors that cause silent Peppol rejections — and the layered checks that catch them before a document ever leaves your access point.
Integrate each e-invoicing mandate yourself and you own its formats, validation packs, identifiers and every change. Here is the work a single API absorbs.
What is a Peppol Access Point? How the four-corner network, SMP lookup and AS4 exchange work, and how to tell if your business needs one in 2026.
Peppol vs PINT explained: what BIS Billing 3.0 and PINT actually are, how they differ, when each applies and why it matters for global e-invoicing in 2026.
The Nigeria e-invoicing mandate explained: the clearance platform behind it, who is in scope, the JSON invoice format, dated rule changes and how to prepare.
What Peppol 5-corner model compliance means in Oman: the six obligations, what the fifth corner receives, and why the tax report carries the whole invoice.
Peppol e-invoicing does not change GST reporting or BAS lodgement in Australia. What the ATO still expects, and how GST is carried in a PINT A-NZ invoice.
GoRoute is an OTA accredited service provider in Oman, accredited 29 July 2026 through Union Digital Technologies SPC, and how to check any provider's claim.
Poland KSeF: both mandate waves are live — 1 February 2026 above PLN 200m of 2024 sales, 1 April 2026 for everyone else. FA(3), clearance, Peppol bridging.
Belgium B2B e-invoicing 2026: what changed in January, the Peppol BIS baseline, the five-corner roadmap, scope, exemptions, and a checklist.
UAE PINT-AE readiness: the deadline to appoint an Accredited Service Provider is 30 October 2026 above AED 50 million, and implementation stays 1 January 2027.
Live tracker of 2026 e-invoicing mandates: Belgium, Poland, Croatia, UAE, Malaysia, France, Singapore and more — deadlines, models, and Peppol readiness.
PINT Oman explained: what PINT OM is, and every CustomizationID, ProfileID, document type code and Schematron pack for billing, self-billing and the TDD.
The Oman Tax Data Document is the XML report the Tax Authority receives as corner five: what it carries, the 66 rules it must pass, and how it is generated.
A step-by-step runbook for connecting to Nigeria's e-invoicing platform: registration, API keys, validate and sign, the IRN and QR code, webhooks and go-live.
FIRS e-invoicing Nigeria: how the Merchant-Buyer Solution works, who is in scope, how invoices are cleared, the JSON invoice format and a readiness checklist.
Revenue Ireland digital reporting: practical 2026 steps for SMEs and exporters to align with ViDA, EN 16931 and Peppol BIS Billing 3.0 well before deadline.
Ireland e-invoicing under ViDA: the 2028–2030 roadmap, Revenue's digital reporting plans, Peppol BIS readiness, and what to build during 2026.
How to choose a Slovakia Peppol Access Point in 2026: certification, BIS coverage, SLAs, security, pricing and procurement questions for finance buyers.
Slovakia e-invoicing mandate 2027 explained: eFaktúra scope, Peppol BIS profile, deadlines, B2B obligations and what suppliers must build now to be ready.
How does e-invoicing work? A clear guide to structured invoice formats, Peppol AS4 transport, SMP discovery, validation gates, and clearance models in 2026.
Peppol readiness in Oman: PINT OM document types, the Tax Data Document, how a participant and access point are registered, and what the Tax Authority needs.
A practical Peppol onboarding checklist for finance teams: participant IDs, SMP registration, AP setup, validation gates and go-live controls.