Solution / e-invoicing
Dispute handling is the weak link
of electronic invoicing.
The reform automates agreement. When an invoice is refused, the work leaves the system: an email, an attachment, a reminder, a new version.
Discuss a first dossier01 / The breaking point
The status “refused”
does not settle the dispute.
The supplier has to work the disagreement, keep the elements that support its position and document what follows. Right there, the structured chain stops and the work goes back to email.
The data is structured.
The work no longer is.
What the reform provides when the invoice is refused
The DGFiP writes it: the « refused » status « does not settle the dispute between the parties ». The supplier must « instruct the disagreement, keep the elements supporting its position and document the follow-up » — three obligations, with no dedicated tool. And the refusal is only the visible case: many disagreements carry no status at all — the invoice simply goes unanswered.
Source: DGFiP, practical guide to electronic invoicing (official PDF)02 / The dispute
In a dispute, nobody wants to play away.
Today one of the two parties has to host the work. Nobody wants to be the guest of the party they are up against. Nobody wants to host the party contesting them.
At theirs
They control access, the log, the evidence.
You work your own dossier inside the system of the party you are contesting.
At yours
You carry the load.
The security of their access, the integrity of their data, the hosting of their work: your responsibility.
03 / The RIGA arrangement
The dispute's dossier has its own place.
Not at yours, not at theirs. No access to open in your systems. One record, the same for both parties, that each can verify on its own side.
Supplier
Customer
Two parties work the same dispute. Neither opens its system to the other.
04 / The process
From refusal to answer,
one dossier.
01
The documents gathered
Refusal reason, quote, order, delivery note, invoice: the dossier opens with what the disagreement rests on.
02
The questions handled
Each question goes to the party concerned. The answer stays with the dossier.
03
The positions documented
What each party holds, and on what basis, is written once, in one place.
04
The same documents on both sides
What is exchanged has no private version. Each party sees what was passed to it.
05 / Automation resumes
On that basis, automation resumes.
Refusal reason, quote, order, delivery note, invoice: the elements are structured. Matching and drafting an answer can be handed to an AI assistant, within the limits set by the person delegating it.
Use the space as is.
Plug in your AI assistant.
Integrate it into your flows by API and MCP.
06 / Detection
The refusal opens the dossier.
Connect your invoicing platform from your account. When a refusal appears, the dossier can open with the invoice and its reason. The first connections are being set up now.
07 / Proof
The record verifies without us.
A record where any alteration is detectable. Each entitled party can verify it on its own side, offline, with the VAL verifier — no account with us, no connection.
See the protocolPilot programme
First dossiers from September, supported end to end.
No fees during the pilot. The dossier stays yours, whatever happens next.
Conditions
- —A real dispute
- —Both parties identified
- —One contact who owns the receivable
08 / To close
A disputed invoice
needs a place to be worked.
Not the supplier's portal. Not the customer's. A shared record and workspace, outside both systems.
Neither host nor guest. RIGA.