← All guides · Formats & conversion
What is a CIUS? How countries tailor the EN 16931 core invoice
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 CIUS — Core Invoice Usage Specification — is a published specification that takes the EN 16931 core invoice model and states exactly how it applies in one country or context: which optional elements become mandatory, which code lists apply, which extra rules hold. Portugal's CIUS-PT and Germany's XRechnung are CIUS-style specifications. The core model never changes; a CIUS narrows how it is used.
What is a CIUS?
A CIUS (Core Invoice Usage Specification) is a formal specification, recognised by EN 16931, that restricts and clarifies the core invoice model for a specific community — typically a country. This product's mandate table encounters them directly: Portugal's channel is 'CIUS-PT / SAF-T', and Germany's EN 16931 channel is delivered as 'XRechnung / ZUGFeRD'. Country rule packs in Pro exist to handle this per-country layer.
Why countries tailor a shared standard
A European core model must serve a Portuguese municipality, a German federal agency and a Belgian wholesaler at once. It therefore contains optionality — fields that may appear, codes that may be used — which each community then pins down for its own processes. A CIUS is that pinning-down, published formally so suppliers can build to it instead of guessing.
The alternative would be twenty-seven incompatible national formats, which is what EN 16931 was created to prevent. With a CIUS, the national variation is a delta on a shared base: a supplier who produces a correct core invoice is most of the way to every country's specification, and the remaining distance is documented rather than tribal.
What a CIUS is allowed to change — and what it is not
The EN 16931 framework constrains its CIUS children: a CIUS may restrict the core (make an optional element mandatory, narrow a code list, add business rules, require specific identifiers) but it may not contradict the core model or remove its mandatory content. An invoice conforming to a CIUS therefore still conforms to the core — compatibility flows upward by construction.
Practical consequence: validation stacks. Your invoice must satisfy the core BR rules and the applicable CIUS rules. This product's engine implements the core layer — the foundation every CIUS stands on — and country rule packs in Pro address the per-country tightening for the countries your billing actually touches. Passing the core is necessary everywhere; the pack tells you what else a given country asks.
CIUS-PT and XRechnung: two specimens
Portugal's CIUS-PT is the national specification behind its B2G structured invoicing, sitting alongside SAF-T reporting. Germany's XRechnung is the public-sector profile of EN 16931, itself a CIUS of the European core, used across German government invoicing — while ZUGFeRD serves the hybrid-document world beside it. Both appear in this product's mandate table because both are what suppliers actually meet.
Notice the family resemblance in how clients talk about them: 'send us a CIUS-PT invoice', 'we need XRechnung'. They are asking for the core invoice, expressed with their community's restrictions. The supplier's correct response is not a new billing system per country — it is core-clean invoice data, plus the country's specific requirements checked before sending.
How a CIUS affects your invoice data
Most CIUS requirements land on the same pressure points as the core rules, only harder: identifiers (a national CIUS often mandates specific identifier schemes), addresses in fuller form, stricter code lists, and additional mandatory elements for its sector — references a public buyer needs for its own processing, such as order or contract references where the specification demands them.
The supplier workflow absorbs this without drama if the base data is complete. Fields a CIUS makes mandatory are fields the core already defines; a template that collects full party details, identifiers and line-level VAT treatment from the start rarely meets a CIUS requirement it cannot satisfy by simply filling in what it already gathers. The invoices that fail CIUS checks are the ones that were already skating on the core's minimums.
Building once for many specifications
The economics argue for the layered approach this product takes: validate the core mechanically on every invoice; apply country rule packs where your clients are; and let monitored clients flag when a country's position changes — a specification revision, a mandate phase arriving — so the layer you depend on is re-checked rather than remembered.
By 2030, with ViDA making intra-EU B2B structured invoicing mandatory, CIUS-style national specifications will be the texture of ordinary trade. Suppliers who learned the core early will experience each CIUS as a short appendix. Suppliers who learned one portal's quirks by hand will start again at every border. The core is the asset; the CIUS is the local accent.
Handling CIUS requirements in 5 steps
- Identify which specification your client invoices under — ask; CIUS names like CIUS-PT or XRechnung are stated in their supplier guidance.
- Validate the invoice against the EN 16931 core first: no CIUS conformance exists on a failing core.
- Check the country layer with the rule packs: identifiers, mandatory extras, code lists for that country.
- Collect full data at onboarding so CIUS-mandatory fields are never a last-minute chase.
- Re-check when monitored clients flag a country change — specifications and phases both move.
Worked example: core-clean, then country-checked
A services firm invoices a Portuguese public body EUR 4,600.00. Step one is core discipline: the invoice validates cleanly here — complete parties, identifiers present, lines with agreed VAT categories and rates, totals computed (net EUR 4,600.00, tax per the confirmed treatment, payable derived, never typed). Step two is the country layer: CIUS-PT governs this B2G relationship, so the firm's Pro country rule pack checks the Portuguese specification's additional requirements before the invoice is issued through the client's route.
Had the order been reversed — country fields guessed first, core validation later — a BR failure would have invalidated the whole assembly. Core first is not pedantry; it is the dependency order the specifications themselves assume.
Frequently asked questions
Does CIUS conformance replace EN 16931 conformance?
No — a CIUS restricts the core model, so a CIUS-conforming invoice also conforms to EN 16931. You need both layers: core rules plus the specification's tightenings.
Which CIUS specifications will I meet most?
In this product's mandate table: CIUS-PT for Portuguese B2G invoicing and XRechnung as Germany's public-sector EN 16931 profile. Peppol BIS is the network's own profiling of the same core.
Can a CIUS remove a core requirement?
No. A CIUS may only restrict and clarify — making optional elements mandatory, narrowing code lists, adding rules. It cannot contradict the core model.
What are country rule packs?
Pro's per-country layer: the additional requirements a country's specification and mandate position place on top of the core validation, checked for the countries you invoice.
How do I know which CIUS applies?
Your client's supplier guidance names it — public-sector buyers especially. Ask at onboarding and record it in the client file next to their identifiers.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- E-invoicing in Portugal: B2G structured, B2B PDF with ATCUD — for now
- XRechnung vs ZUGFeRD: Germany's two e-invoice formats compared
- Peppol BIS Billing 3.0 explained: the profile your Peppol invoice must fit
- What is EN 16931 and why does your invoice need to follow it?
- Country rule packs: the per-country layer on top of EN 16931 validation