Stop assembling e-invoicing deadlines from vendor blogs. We built you a free checker.

Every finance lead running a European group has done this exercise. Fifteen browser tabs. Four vendor blogs, two of them selling you something. A Big 4 PDF from last year. An EC factsheet that still lists Croatia as “planned” when Croatia went live months ago.

Three hours later you have a spreadsheet you don’t trust, and you still can’t answer the only question your board asked: what hits us, and when?

So we built the thing we kept wishing existed.

The E-invoicing Mandate Checker is free, takes about ninety seconds, and asks for nothing. No email, no sign-up, no “book a demo to see your results”.

What it actually does

You tell it where you have legal entities. It then asks at most two size questions, and only the ones your selected countries actually need. Germany alone asks about turnover; add France and it also asks headcount. Nobody answers a question that cannot change their answer. You say what you invoice: domestic B2B, public sector, consumers, cross-border EU. You tell it what you’re running: D365 F&O, Finance, AX 2012, Business Central, or “not sure”.

Then it gives you four things.

One consolidated timeline. Every selected country on one axis with a “today” marker, ordered by urgency rather than alphabetically. This is the view that goes into the steering-committee pack.

A card per country. Status, the deadline for your size band, format, transmission model, e-reporting, archiving, penalties. Plus the rule that produced the conclusion, a link to its source, and the date we last checked it.

The Dynamics 365 answer. Deduplicated across your footprint: how many distinct ER format configurations your countries imply, in how many of them you need AP inbound, and whether a single access point covers the lot.

The negative answer. “We checked all 31 and nothing else applies to you today.” Reassurance is a deliverable too, and it makes the urgent findings more credible.

Run a fairly typical group. French, German, Polish, Italian, Spanish, Romanian and UK entities, mid-size, invoicing B2B plus public sector plus cross-border. You get six countries already live, one upcoming, and seven distinct invoice formats implied by that footprint. Factur-X, XRechnung, ZUGFeRD 2.x, FatturaPA, FA(3) via KSeF, RO_CIUS and Facturae.

Seven format configurations is not a compliance detail. That’s a programme.

Why we built it the way we did

Three decisions did most of the work. They’re worth explaining, because they’re the reason you can lean on the output.

Every fact carries a source and a date

Not a footnote at the bottom. Each of the 84 country facts and 124 applicability rules in the registry carries its own source URL and its own verified date. Where a primary source exists, that is what we cite: a tax authority, an official gazette, a national legislation portal. Never a single vendor blog.

Cross-checking those 31 countries against the EC country factsheets and an independent tracker found seven errors in our own first draft, including Belgian archiving (7 vs 10 years), a Greek B2G date and a Finnish rule that asserted a duty to send where the Act gives only a right to demand. We fixed all seven and moved ten countries onto national legal sources.

Worth knowing: the EC factsheets lag. During that cross-check they still had Croatian and Greek B2B as “planned” and Norway as having no B2B mandate. Where a national source disagreed with them, the national source won every time.

The build breaks on purpose

Here’s the part I actually like. A gate runs on every build and fails the site if any fact or rule is older than six months without re-verification.

That means roughly once per country per half-year, publishing anything to drdynamics.co.uk becomes impossible until someone re-reads the source. The fix is to re-check and update. Never to bump the date or raise the threshold.

Most compliance content rots quietly. This one can’t ship while it’s rotting. That friction is the feature.

It shows its working

The correction that shaped the whole design: early on, a mockup asserted that a German company selling B2B into France picks up a French e-reporting obligation. That was wrong, and it came from memory rather than from the DGFiP.

What the DGFiP actually says: e-invoicing applies only to taxable persons established in France. E-reporting is triggered by carrying out transactions located in France for which you’re liable for French VAT, not by holding a VAT number. Intra-Community supplies and exports are excluded. Belgium goes the other way and excludes non-established entities from its B2B mandate entirely.

The error wasn’t in a date or a penalty. It was in the logic mapping answers onto obligations, which a gate that only checks whether facts have sources would never have caught.

So applicability rules are treated as data, not code. Same citation requirement, same verified date, same gate. And every conclusion renders with the rule that produced it, so your tax adviser can check our working instead of taking our word.

Three things most trackers get wrong

Silence is not clearance. The checker keeps three states visually distinct and never confuses them: no obligation (researched, nothing applies), not yet covered (we haven’t verified this country, not a claim that no mandate exists), and not assessed (you skipped a question that country needed). A tool that renders all three as green is lying to you.

A group is not one taxpayer. The same country can catch two of your entities under different rules at once. A French subsidiary established locally, and a parent liable for French VAT without an establishment. Treat “established” as one exclusive answer per country and you lose the second obligation entirely. That’s exactly the case an international group needs a checker for.

A date can be real and still not be yours. Finland and Estonia give the buyer a right to demand rather than imposing a duty to send. Croatia’s date turns on VAT registration. Poland defers micro-entrepreneurs issuing invoices up to PLN 450 with monthly sales under PLN 10,000 to 1 January 2027. Rendering those identically to a hard obligation overstates them, the same failure as understating one. The checker flags them conditional and prints the trigger sentence.

And one thing that’s easy to miss: cross-border EU has an answer everywhere. Council Directive (EU) 2025/516 (ViDA) makes structured e-invoicing and transaction-level digital reporting mandatory for intra-Community B2B supplies from 1 July 2030, identically across all 27 member states. Countries that have legislated their own cross-border position keep it. National law is the more specific statement.

What it deliberately won’t do

No readiness score. No D365 gap analysis. No named ER configuration paths or feature-management flags. Those change every D365 release, and a checker that tracked them would need its own staleness gate on top of 31 countries. That detail belongs in a scoping call, not a web page.

No email capture anywhere on the page. Gated content can’t be cited by AI answer engines, and more to the point, a compliance question shouldn’t cost you a place in someone’s nurture sequence.

And it isn’t tax advice. We’re Dynamics 365 specialists, not tax advisers. Every fact links to its source and shows when we last checked it. Confirm anything you plan to budget against with your adviser. A disclaimer that points at the evidence is a statement of confidence; one hiding in 9px grey is something to skip.

Use it, then argue with it

Take your five hardest countries and run them. If a conclusion looks wrong, the rule and its source are right there on the card. Send me the counter-source and I’ll fix the registry.

Run the checker →

Already know your footprint and want the D365 side scoped properly? Book a call and we’ll walk your countries through together.