← All guides · How-to & workflow
Country rule packs: the per-country layer on top of EN 16931 validation
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
A country rule pack is the per-country layer of checks and requirements that sits on top of core EN 16931 validation: the national specification (a CIUS like CIUS-PT or a profile like XRechnung), the identifier and channel expectations, and the mandate position for that country. Core validation proves the invoice is a valid European e-invoice; the pack checks it against the country it is actually going to.
What is a country rule pack?
Country rule packs are listed among Pro's features — 'country rule packs' alongside bulk conversion, monitored clients and accounting exports. They encode the per-country layer this product's architecture assumes: the mandate table holds each country's channel, phases and basis (Peppol for Belgium, KSeF for Poland, PDP/PPF for France, EN 16931 via XRechnung/ZUGFeRD for Germany, VeriFactu/EN 16931 for Spain, SdI/FatturaPA for Italy, CIUS-PT/SAF-T for Portugal), and the pack applies the relevant country's requirements to your invoices.
Why one European standard still needs country layers
EN 16931 harmonised the core, then deliberately let countries finish the job locally: national specifications (CIUS) tighten the model, channels differ (network, platform, public portal), mandates phase by size and sector, and public buyers add their own intake rules. A supplier invoicing six countries meets one standard wearing six national outfits. Pretending the outfits do not exist produces invoices that are core-valid and country-wrong.
The pack is the outfit, systematised. Instead of a wiki page per country that a bookkeeper must remember to consult, the country's requirements ride inside the conversion workflow: the invoice is checked against the layer that applies to its destination, and the exceptions — where any arise — arrive in the same list as core failures, with the same fix-and-revalidate loop.
What a pack actually checks
The substance varies by country because countries vary: the specification in force (CIUS-PT for Portuguese B2G, XRechnung's profile in Germany), the channel the invoice must be fit for (a Peppol BIS document for Belgium, KSeF-ready data for Poland, SdI-era data discipline for Italy), the identifiers the destination expects, and the mandate timing that decides whether structured is optional, imminent or already law for this buyer.
Underneath the variety, the pack's questions rhyme with the core's: is everything present that this country requires, do the codes match this country's lists, is the tax treatment expressed the way this destination books it. The core made your invoice European; the pack makes it Belgian, Polish, French — addressed, in the local sense, correctly.
Packs, the checker and monitored clients: one table, three faces
All three country-aware features read the same mandate foundation. The acceptance checker computes the whether-and-when verdict for a single invoice. Monitored clients keep that verdict current per client over time. Country rule packs apply the country's requirements to the invoice data itself. One source of truth, three moments of use: before invoicing (will they require it?), always (is this client about to flip?), and at creation (does this invoice satisfy where it is going?).
That shared foundation is what keeps the answers consistent: the pack cannot demand what the checker calls optional in a contradictory way, because both derive from the same country model — channel, phases, basis — that the converter also stamps onto results. When a country changes its position, the model updates once and all three faces move together.
When the pack earns its keep
Three moments repay the layer. First, public-sector work: B2G specifications (CIUS-PT, XRechnung) are where core-valid invoices most often meet extra national requirements. Second, phase boundaries: invoicing a Polish client across April 2026 or a German client across the 2027 line, where the country's expectations harden on a date and the pack keeps the invoice aligned with the new position. Third, portfolio scale: an agency billing into eight countries cannot hold eight specifications in one person's memory — the pack is the memory, applied mechanically.
If your billing is one country, one client type, one channel, the core may carry you for a while. The pack becomes essential exactly when variety arrives — and variety, in the mandate era, arrives for everyone eventually: ViDA's 2030 backstop ensures no EU-facing portfolio stays single-country simple forever.
Using packs without drowning in process
The workflow does not change shape: enter the invoice, convert, read exceptions, fix, download. The pack's checks join the same report, so the human process is identical — only the thoroughness grows. Keep client records rich (country, size class, sector, identifiers) because the pack selects and applies its rules from those facts; a client record that says 'Europe' gives the layer nothing to work with.
And keep the hierarchy straight when failures appear: core failures first (the invoice is not yet a valid e-invoice anywhere), country failures second (it is valid, but not yet right for its destination). Fixing in that order mirrors how the specifications themselves stack — the CIUS stands on the core — and prevents the confusion of polishing a national detail on an invoice whose totals do not yet reconcile.
Working with country rule packs in 5 steps
- Record each client's country, size class and sector (B2G vs B2B) — the pack selects its rules from these facts.
- Validate the core first: no country layer can rescue an invoice failing EN 16931 rules.
- Convert with the destination country's pack applied and read its exceptions alongside the core report.
- Fix in hierarchy order: core failures, then country failures, then re-validate the whole invoice.
- Re-check when monitored clients flag a country change — packs and phases move together.
Worked example: one invoice, two layers of questions
A firm invoices a German public-sector client EUR 12,400.00. Core validation passes: parties complete, identifiers present, lines at category S with agreeing rates, totals computed — tax EUR 2,480.00 at 20%, payable EUR 14,880.00. The German layer then asks its own questions, because this is a B2G relationship in XRechnung country: the profile expectations for a public buyer, applied before the invoice is issued through the client's stated route.
Without the pack, the firm would have learned those expectations from the client's intake rejection — the traditional, expensive way. With it, the country questions arrive in the same exception list as core questions, at the same cheap moment: before sending, while the invoice is still a draft and the deadline is still a date rather than a dispute.
Frequently asked questions
Are country rule packs part of Pro?
Yes — Pro ($19/month) includes bulk conversion, country rule packs, monitored clients and Xero/QuickBooks/CSV exports. The free tier converts and validates one invoice against the core rules.
What is the difference between core validation and a country pack?
Core validation proves the invoice satisfies EN 16931's business rules — valid anywhere. The pack applies the destination country's own layer: its specification, channel expectations and mandate position.
Which countries have the most distinct layers?
The ones with named national apparatus in the mandate table: Portugal (CIUS-PT/SAF-T), Germany (XRechnung/ZUGFeRD), Italy (SdI/FatturaPA), Poland (KSeF), Belgium (Peppol), France (PDP/PPF).
Do packs and the acceptance checker ever disagree?
They read the same mandate model — channel, phases and basis per country — so their answers are consistent by construction: the checker computes timing, the pack applies requirements.
When do I actually need the pack?
Public-sector invoicing, phase boundaries, and multi-country portfolios are where country layers bite. Single-country private billing may run on the core for a time — variety is what makes packs essential.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- What is a CIUS? How countries tailor the EN 16931 core invoice
- Monitored clients: tracking each client's e-invoicing mandate status as dates move
- The acceptance checker explained: how a verdict is computed from date, country and size
- XRechnung vs ZUGFeRD: Germany's two e-invoice formats compared
- Bulk invoice conversion: turning a whole billing run into validated e-invoices