Choosing an E-Invoicing Platform: 12-Point Checklist for Multi-Jurisdiction Compliance
Global E-Invoicing Platform Series
This guide is part of a comprehensive series. Explore all 36 topics:
The right e-invoicing platform is the one that issues the local artefact (IRN, UUID, CSID-signed XML, AS4 message) end to end across every jurisdiction you invoice into, runs the regulator credential and queue inside the product, and prices the whole capability as a single tier — not as per-country add-ons. Use the 12-point checklist below to score any vendor before signing; the items map to the failure modes that show up in the first 90 days post-go-live.
At a glance
- Audience: Finance, IT, and compliance leads selecting an e-invoicing platform for multi-jurisdiction operations.
- Framework: 12 verification points, weighted toward operational rather than feature checks.
- Coverage tested: ZATCA Phase 1 + 2, MyInvois, GST IRN, NRS MBS, Peppol BIS Billing 3.0, MTD for VAT, plus regional regimes.
- Use case: RFP scoring sheet; vendor demo question list.
- Time to score a vendor: 60–90 minutes per platform if the vendor provides documentation access.
- Last reviewed: 20 November 2026 against live mandate dates.
Why pick a framework instead of a feature list?
Most e-invoicing RFPs collapse into feature checklists that every vendor passes on paper. The differences only show up in operations: who provisions the credential, what happens when the regulator's portal is down, who renders the QR on the buyer PDF, and how the platform absorbs the next mandate.
Most e-invoicing RFPs collapse into feature checklists that every vendor passes on paper. The differences only show up in operations: who provisions the credential, what happens when the regulator's portal is down, who renders the QR on the buyer PDF, and how the platform absorbs the next mandate. Score on those axes and the field narrows fast.
1. Mandate coverage today
List every jurisdiction you currently invoice into. Confirm the platform supports each as a source page with documented capability — not as a generic "international" feature toggle.
List every jurisdiction you currently invoice into. Confirm the platform supports each as a source page with documented capability — not as a generic "international" feature toggle. Coverage of ZATCA, MyInvois, GST IRN, NRS MBS, Peppol, and MTD is table stakes for any multi-country operation. Ask the vendor to walk you through their mandate matrix.
2. Mandate roadmap
The mandate landscape moves yearly. Confirm the published roadmap covers Belgium 2026 (B2B Peppol), France 2026–2027 (PDP onboarding), Germany phased through 2028 (XRechnung / ZUGFeRD / Peppol), Poland KSeF 2026, Greece myDATA, and the next ViDA milestones.
The mandate landscape moves yearly. Confirm the published roadmap covers Belgium 2026 (B2B Peppol), France 2026–2027 (PDP onboarding), Germany phased through 2028 (XRechnung / ZUGFeRD / Peppol), Poland KSeF 2026, Greece myDATA, and the next ViDA milestones. A vendor without a published roadmap is a vendor that will not absorb the next mandate in time.
3. Native local artefacts
The platform must issue the local artefact (CSID, IRN, MyInvois UUID, NRS verification QR, Peppol Participant ID) end to end — not via a third-party connector you have to procure separately.
The platform must issue the local artefact (CSID, IRN, MyInvois UUID, NRS verification QR, Peppol Participant ID) end to end — not via a third-party connector you have to procure separately. "We integrate with X for ZATCA" is a red flag; what you want is "we issue the CSID, sign the XAdES, and clear the invoice ourselves."
4. Clearance and reporting in one product
If you cross jurisdictions, you will straddle both clearance and reporting models. The platform should handle both in one tenant, not via separate SKUs or split products.
If you cross jurisdictions, you will straddle both clearance and reporting models. The platform should handle both in one tenant, not via separate SKUs or split products. Anything else multiplies your operational surface area by the number of regimes.
5. Signing key management
The platform must provision signing credentials (ZATCA CSID, NRS credential, LHDN certificate, Peppol AS4 keypair) without you ever exporting the private key. Confirm the CSR + OTP flow runs inside the product and that the private key is held in a hardware-protected key store.
The platform must provision signing credentials (ZATCA CSID, NRS credential, LHDN certificate, Peppol AS4 keypair) without you ever exporting the private key. Confirm the CSR + OTP flow runs inside the product and that the private key is held in a hardware-protected key store. A platform that asks you to upload a private key is a security incident waiting to happen.
6. Schema and Schematron validation pre-send
Every payload must be validated against the regulator's schema (UBL 2. 1 in KSA / Peppol, INV-01 JSON in India, NRS JSON in Nigeria) and Schematron rules before submission.
Every payload must be validated against the regulator's schema (UBL 2.1 in KSA / Peppol, INV-01 JSON in India, NRS JSON in Nigeria) and Schematron rules before submission. Failed validations should be surfaced to the operator with field-level error messages — not silently retried. Pre-send validation is the cheapest control you can put in place.
7. Regulator-side queueing
When the regulator's portal is down — and it will be — the platform must queue, retry with backoff, and surface status. Invoicing must never block on a regulator's uptime SLA you do not control.
When the regulator's portal is down — and it will be — the platform must queue, retry with backoff, and surface status. Invoicing must never block on a regulator's uptime SLA you do not control. Ask the vendor for their portal-downtime runbook; if they do not have one, they have not been in production long enough.
8. Buyer-facing artefacts on the PDF
The IRN, UUID, QR, and digital signature must appear on the buyer PDF in the exact format the buyer expects. The platform should render the PDF once with all artefacts bound, not after a separate sign-and-stamp step.
The IRN, UUID, QR, and digital signature must appear on the buyer PDF in the exact format the buyer expects. The platform should render the PDF once with all artefacts bound, not after a separate sign-and-stamp step. Misplaced QRs and missing IRNs are the most common cause of buyer-side payment delays.
9. Multi-currency and multi-VAT
Cross-jurisdiction invoicing means multi-currency totals (SAR, MYR, INR, NGN, EUR, GBP) and multi-VAT lines (different rates per line, reverse-charge categories, zero-rated exports). The platform must handle both without manual currency conversion or VAT splitting.
Cross-jurisdiction invoicing means multi-currency totals (SAR, MYR, INR, NGN, EUR, GBP) and multi-VAT lines (different rates per line, reverse-charge categories, zero-rated exports). The platform must handle both without manual currency conversion or VAT splitting. Confirm the FX-rate source and the rate-as-at-which-date logic.
10. Audit trail and archival
Every cleared invoice, every signature, every regulator response must be archived for the statutory retention period — 5 years in some Asian regimes, 6 years for ZATCA, 7 years for MyInvois, 10 years for most EU jurisdictions. Search and export must be self-service.
Every cleared invoice, every signature, every regulator response must be archived for the statutory retention period — 5 years in some Asian regimes, 6 years for ZATCA, 7 years for MyInvois, 10 years for most EU jurisdictions. Search and export must be self-service. WORM-style storage or object-lock S3 is the minimum acceptable backing.
11. Pricing predictability
Avoid per-jurisdiction add-ons. A platform that prices e-invoicing as a single tier (Invoicemonk includes the full mandate matrix in Professional) is easier to budget than one with per-mandate SKUs, per-invoice surcharges, or per-jurisdiction setup fees.
Avoid per-jurisdiction add-ons. A platform that prices e-invoicing as a single tier (Invoicemonk includes the full mandate matrix in Professional) is easier to budget than one with per-mandate SKUs, per-invoice surcharges, or per-jurisdiction setup fees. Get the three-year total cost of ownership before signing.
12. Local language and authority documentation
The platform's onboarding flow and error messages should be in the operator's working language. Authority-side documentation links (ZATCA, NRS, LHDN, NIC, HMRC, peppol.
The platform's onboarding flow and error messages should be in the operator's working language. Authority-side documentation links (ZATCA, NRS, LHDN, NIC, HMRC, peppol.eu) should be one click away from the error. A platform that hides the regulator's documentation behind support tickets is a platform that does not want you to debug.
RFP scorecard
RFP scorecard — 1: Mandate coverage — High.
| # | Item | Weight | What to ask the vendor |
|---|---|---|---|
| 1 | Mandate coverage | High | "Walk me through your mandate matrix for the jurisdictions on this list." |
| 2 | Mandate roadmap | High | "What does your published roadmap look like for the next 18 months?" |
| 3 | Native local artefacts | High | "Do you issue the CSID / IRN / UUID end to end, or via a third party?" |
| 4 | Clearance + reporting | Medium | "Show me both flows in one tenant, side by side." |
| 5 | Key management | Critical | "How do I onboard the ZATCA CSID without exposing the private key?" |
| 6 | Validation | Medium | "Show me a failed Schematron run and the operator-facing error." |
| 7 | Queueing | Critical | "What happens when the NIC IRP is down for 45 minutes?" |
| 8 | Buyer PDF | Medium | "Show me a buyer PDF with the IRN, QR, and signature placed in the regulator's prescribed positions." |
| 9 | Multi-currency / multi-VAT | Medium | "How do you handle a SAR invoice with one zero-rated and one standard line?" |
| 10 | Archival | Medium | "What is your retention configuration per jurisdiction?" |
| 11 | Pricing | High | "What is the three-year total cost for all jurisdictions I need?" |
| 12 | Documentation | Low | "Open an error and show me the link to the authority spec from inside the product." |
How Invoicemonk scores
Invoicemonk satisfies all 12 points across the supported jurisdictions: ZATCA Phase 1 + 2, MyInvois, GST IRN, Peppol BIS Billing 3. 0, NRS MBS, MTD for VAT, KRA eTIMS, GRA e-VAT, BIR CAS, SARS, ZIMRA FDMS, SRC, SEF Brazil, US B2G, CRA + Peppol Canada.
Invoicemonk satisfies all 12 points across the supported jurisdictions: ZATCA Phase 1 + 2, MyInvois, GST IRN, Peppol BIS Billing 3.0, NRS MBS, MTD for VAT, KRA eTIMS, GRA e-VAT, BIR CAS, SARS, ZIMRA FDMS, SRC, SEF Brazil, US B2G, CRA + Peppol Canada. See the mandate matrix for the full grid.
Key takeaways
Key takeaways includes: Score vendors on operations, not features — the differences only show up in production. Item 5 (key management) is the single most important verification; a platform that exposes private keys disqualifies itself.
- Score vendors on operations, not features — the differences only show up in production.
- Item 5 (key management) is the single most important verification; a platform that exposes private keys disqualifies itself.
- Item 7 (regulator-side queueing) tells you whether the vendor has actually run a clearance regime in production.
- Per-jurisdiction pricing add-ons compound; insist on a single tier.
- A vendor without a published mandate roadmap is a vendor that will miss the next deadline.
Related reading
Before you score vendors, read clearance vs reporting models and Peppol vs national portals. To understand the artefacts your vendor must issue, see what is a CSID and what is an IRN.
Before you score vendors, read clearance vs reporting models and Peppol vs national portals. To understand the artefacts your vendor must issue, see what is a CSID and what is an IRN. The pillar is global e-invoicing.
Authority sources
- OpenPeppol — Peppol BIS Billing 3.0
- ZATCA — E-Invoicing Detailed Technical Guideline v2
- NRS Merchant Buyer Solution portal — Nigeria
- NIC IRP — India IRN attribute mapping
- HMRC Developer Hub — VAT (MTD) API
- European Commission — VAT in the Digital Age (ViDA)
- NITDA — National Regulatory Guideline for Electronic Invoicing in Nigeria (2025)
More in this series (36 articles)
From this series
Mandate-compliant e-invoicing in 17 jurisdictions, with the local artefact (CSID, IRN, UUID, QR, digital signature) issued automatically.
Digital Marketing, SEO Specialist, Content Creator & Product Professional
Olayinka is a digital marketer, content creator, growth and SEO specialist with 10+ years helping businesses in Nigeria, the UK, the US, Australia, and Dubai achieve their goals online.
