Italy has been running mandatory clearance for domestic business-to-business invoicing longer than any other Member State. That makes it the only European jurisdiction where you can ask a genuinely useful question: after the project ends and the novelty wears off, what is still difficult?
The answer is not the format, and it is not the platform. It is the same two things that are difficult everywhere.
How the system works
Every domestic invoice is submitted to a national exchange system rather than sent to the buyer. The system validates it, and either rejects it with a reason code or accepts it and delivers it to the recipient. Delivery is to an address the recipient has registered, identified by a recipient code carried in the document itself.
The consequences of that arrangement are the general consequences of clearance: the invoice exists when the platform says so, the buyer collects rather than receives, and evidence of delivery is produced by the platform rather than by you.
The national format
Italy uses its own XML schema. It predates EN 16931 and was designed around the clearance system rather than around a European semantic model.
For a business operating in several countries, that is the first real cost. Producing a European core invoice for Belgium and a national document for Italy from the same source is a mapping exercise, and mappings are where silent data loss happens. A field that exists in one target and not the other has to go somewhere or be deliberately dropped, and "deliberately" is the operative word — an undocumented drop is a defect that surfaces years later, during an audit, in the form of an archived document that does not say what the ledger says.
| Aspect | European core invoice | Italian national format |
|---|---|---|
| Origin | Semantic model, two syntax bindings | National schema built for the exchange system |
| Addressing | Participant identifier in a scheme | Recipient code registered with the system |
| Delivery evidence | Depends on the network | Produced by the exchange system |
| Document types | Invoice and credit note | A wider national set of document type codes |
What is still difficult after years of operation
Addressing
The recipient code is the single most common cause of a document going somewhere useless. It does not fail loudly. A wrong but well-formed code delivers the invoice to a destination that is not the buyer's accounts payable system, or falls back to a portal that nobody in that company has logged into since onboarding.
This is the Italian instance of a general problem: an electronic address is two things, a scheme and a value, and collecting one without the other produces a data set that looks complete and is not.
Exception handling
Rejections arrive asynchronously. Somebody has to be watching, has to understand the reason codes, and has to be able to correct and resubmit within the period that keeps the original date. In practice this is where mature implementations still leak: not because the process was not designed, but because it was designed for a project team and then handed to a function with no capacity for it. See exception handling once volume is flowing.
Document types
The national set of document type codes is richer than "invoice" and "credit note", and it carries meaning that affects treatment. Choosing the wrong one is not a validation failure — the document is accepted — so the error is invisible until somebody reconciles. This is a good argument for the general rule in corrections, credit notes and cancellations: a correction mechanism that is easy to use incorrectly will be used incorrectly.
Italy demonstrates that clearance is not the hard part. Clearance is a well-defined technical interface with a specification. The hard parts are the parts a specification cannot fix: whether your data is right, and whether somebody is watching when it is not.
Scope widened, and kept widening
One feature of the Italian history is easy to miss from outside and matters to anyone facing a newer mandate: the scope at the start was not the scope now.
Categories of taxpayer that were originally outside the obligation have been brought in progressively. Cross-border transactions, which sat in a separate reporting arrangement, were moved into the same channel. Thresholds that once excluded smaller businesses were lowered and then removed. None of that required a new architecture; it required the same architecture applied to more people.
The lesson generalises, and it is not the reassuring one. A business that implemented against the scope in force at the time, treated the project as finished and did not revisit it will eventually find itself out of scope of its own solution — issuing documents through a route that no longer covers what it does, or relying on an exemption that was withdrawn two amendments ago.
That makes scope a standing review rather than a project input. The practical version is modest: a note of which entities are in scope, on what basis, with the source and the date it was checked, revisited when the law is amended rather than when somebody notices a rejection. It costs an hour a year and it is the difference between a mandate that stays implemented and one that quietly stops being.
Data quality becomes visible to somebody else first
The other durable observation from a decade of live running is uncomfortable and worth stating plainly.
Under clearance, the administration sees your document at the same moment your customer does — which means it sees your data quality before you do. A pattern of rejections, a recurring reason code, a spike when a new product line launches: all of that is visible to the platform's operator as it happens, and it is visible to you only if somebody is reading the notifications and aggregating them.
Most businesses do not aggregate them. They work individual rejections and never look at the distribution, which means the administration holds a better picture of their invoicing hygiene than they do. That asymmetry is not a legal problem, but it is a negotiating one, and reversing it costs nothing except deciding to look.
What clearance genuinely gives you
It is worth being fair about the benefits, because they are real and they are usually described badly.
- Certainty of state. Every document is accepted or rejected, and you know which. Compare that with a network model, where an invoice can sit unread in a buyer's inbox for a fortnight.
- A single source of delivery evidence. The platform holds it, and it is not something you have to construct from your provider's logs.
- A shorter argument in an audit. The administration already holds the document. What is left to argue about is the treatment, not the existence.
What it does not give you is protection from an assessment. Acceptance means the document passed validation. It does not mean the VAT treatment was right, and a business that reads clearance as approval has misunderstood the mechanism.
