← All guides · How-to & workflow
The acceptance checker explained: how a verdict is computed from date, country and size
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
The acceptance checker computes — it does not look up prose. Give it an invoice date, the buyer's country and the buyer's size class, and it evaluates the mandate table for 12 countries to return one of three verdicts: structured required, PDF accepted until a named date, or PDF accepted (with the 1 July 2030 ViDA backstop in the record). The same computation stamps every conversion, so the check and the invoice never disagree.
What is the acceptance checker?
The acceptance checker is the free tool (§5 of the converter form) that computes whether a structured e-invoice is required for a given invoice. In the mandate module's own words, 'The checker COMPUTES its verdict from (invoice_date, buyer country, buyer size class) against these dates — no per-result prose is stored.' Its verdicts are structured_required, pdf_until and pdf_accepted, each with a headline and the mandate basis.
Three inputs, no opinions
Invoice date first: mandates are functions of time, and the relevant date is the invoice's own date — an invoice dated 31 March 2026 to Poland lives under different law than its twin dated 2 April. Buyer country second: the mandate attaches to the buyer's jurisdiction and systems, so the country asked for is the client's, not yours. Buyer size third: where a country phases by size (Poland, Germany, Spain), the buyer's class selects the phase date.
The discipline of three explicit inputs is the tool's honesty. Vague questions — 'is e-invoicing mandatory in Europe yet?' — have no answer; dated, placed, sized questions have exactly one. The checker refuses the vague form by construction: it cannot return a verdict until all three inputs exist, which teaches the user to ask answerable questions about their actual next invoice.
The mandate table it computes against
Twelve countries are modelled with their channels, phases and bases: Belgium (Peppol, all from 2026-01-01), Poland (KSeF, large 2026-02-01, all 2026-04-01), France (receive from 2026-09-01, issue phase 2027-09-01), Germany (receive from 2025-01-01, large 2027-01-01, all 2028-01-01), Spain (large 2027-10-06, all 2028-10-01), Italy (SdI, all since 2019-01-01), and the Netherlands, Austria, Ireland, Sweden, Denmark and Portugal with no B2B issue phases — each basis noting the ViDA backstop.
France and Germany also carry a receive_from date, because their receiving duties precede their issuing phases — a nuance a prose FAQ would flatten and a computation preserves. Countries outside the twelve return an honest unknown: not in the database yet, with the ViDA context stated. An unknown verdict is a feature — the checker never invents a mandate to seem complete.
The three verdicts, precisely
Structured required: the applicable phase date has passed for this buyer — headline 'Structured invoice REQUIRED — a PDF alone will be rejected'. PDF until: a phase date exists in the future — headline names it: 'PDF still accepted until {date} — structured required from that date'. PDF accepted: no phase applies — 'PDF still accepted — no B2B structured mandate in force for this date'. Each verdict carries the country's channel, its basis text, the required-from and receive-from dates where they exist, and the ViDA backstop.
Read the verdict as a property of the invoice, not the relationship. The same client can return pdf_until for this month's invoice and structured_required for next quarter's, because the date input moved. That is why the converter stamps the verdict onto each conversion result rather than storing a per-client flag: obligations attach to documents, and documents have dates.
Worked logic: how a verdict is chosen
The computation walks the country's phases: for each phase whose scope covers this buyer (all, or large when the buyer is large), it takes the earliest applicable required-from date. If the invoice date is on or after it, the verdict is structured required. If a required-from exists but lies ahead, pdf_until with that date. If no phase applies, pdf_accepted. Receiving duties ride alongside as context — the French and German cases where the buyer's systems are live before their issuing phase.
Simple logic, deliberately: the checker is an evaluator, not an oracle. Its trustworthiness comes from the table's fidelity and the rule's transparency — you can re-derive any verdict by hand from the phases printed in the result. Tools that answer legal-timing questions should be boring in exactly this way: explicit inputs, visible basis, reproducible output.
Using the checker well
Use it at three moments. At onboarding: run it for each new EU client and record the verdict and its date in the client file. At invoicing: trust the conversion's stamp for the document itself — it is the same computation with the invoice's real inputs. At planning: run future dates for your client base to see your own mandate wave coming — next quarter's flips are visible today, because the table already contains them.
And know its boundary: the checker answers acceptance, not correctness. A structured_required verdict does not validate your invoice, and a pdf_accepted verdict does not excuse sloppy data — the client's system in a mandate country and the client's patience in a voluntary one are different risks, and the converter's validation addresses the data risk in both. Checker for whether; validator for how well; both before sending, every time.
Using the acceptance checker in 5 steps
- Bring the three inputs: the invoice's date, the buyer's country, and the buyer's size class.
- Run the checker (§5) or read the identical stamp on your conversion result.
- Read all three verdict parts: the headline, the required-from date, and the mandate basis for that country.
- Record the verdict and its flip date in the client record — today's answer expires on a known day.
- For portfolios, track the verdicts over time with monitored clients instead of re-checking by memory.
Worked example: three inputs, three countries, three answers
One supplier, one invoice date — 15 March 2026 — three buyers. Belgium: phases cover all buyers from 2026-01-01, so the verdict is structured required, channel Peppol. Poland, standard-size buyer: the all-buyer phase is 2026-04-01, still ahead, so the verdict is pdf_until naming 2026-04-01. Netherlands: no phases at all, so pdf_accepted — with the basis noting Peppol's voluntary use and the 2030 ViDA backstop.
Same supplier, same day, same invoice shape — three different correct answers, each derived from printed phases anyone can audit. That is the entire argument for computing verdicts instead of publishing articles about them: the answer is a function, and functions do not go stale the way prose does.
Frequently asked questions
What inputs does the checker need?
Invoice date, buyer country and buyer size class. The mandate attaches to the buyer's jurisdiction and phase, so the country and size are the buyer's, not yours.
Which countries are covered?
Twelve: Belgium, Poland, France, Germany, Spain, Italy, the Netherlands, Austria, Ireland, Sweden, Denmark and Portugal. Other countries return an explicit unknown with the ViDA context.
What are the possible verdicts?
Structured required; PDF accepted until a named date; or PDF accepted (no B2B mandate in force for that date). Each carries the channel, basis and relevant dates.
Is the checker the same as the stamp on a conversion?
Yes — the converter runs the same mandate computation for the invoice's date, buyer country and size, and includes the verdict in the conversion result.
Does a PDF-accepted verdict mean I should send a PDF?
It means the mandate does not require structure for that invoice. Structured invoices still book faster in most clients' systems — the checker answers the legal question, not the strategic one.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Will my client accept a PDF invoice? How to know before you send
- Monitored clients: tracking each client's e-invoicing mandate status as dates move
- Belgium's Peppol e-invoicing mandate: what B2B suppliers must do from 2026
- Poland's KSeF e-invoicing mandate: dates, phases and what suppliers must send
- Convert your first invoice free: a walkthrough of the one-invoice job