WorkflowTax Compliance & Tax Technology

E-Invoicing Compliance

E-invoicing compliance that checks every invoice before it leaves, and turns every Peppol, KSeF or French platform rejection into a fix with registry evidence

Every invoice checked before it leaves, and every rejection fixed the same day.

See one case, screen by screen ↓
demo97.8%of 2,486 outbound invoices passed first time across Belgium, Poland and France on one Wednesday morning
demo26minutesfrom a KSeF rejection at 09:15 to a KSeF number at 09:41, with the master-data fix approved by a person
demo14more invoicesfound by the Checker that the same stale tax number would have broken, PLN 612,904.40, re-queued after one approval
demo€60,173input VAT heldon 23 of 1,904 inbound invoices, each with its reason, before the VAT was claimed
In short

What is E-Invoicing Compliance?

E-invoicing compliance means every invoice you issue or receive meets the format and rules of the country's clearance platform or network — Peppol in Belgium, KSeF in Poland, the approved platforms in France — so it is accepted, payable and good for input VAT. E-Invoicing Compliance does this with seven agents that validate every outbound invoice against EN 16931 and each country's rules before it is sent, fix rejections with registry evidence, and check inbound invoices before the VAT is claimed. A person approves every master-data change.

How to choose AI solutions for back-office and enterprise work →

Updated

The problem

Why a rejected e-invoice still costs a morning, and sometimes its full VAT

From 2026 an invoice in Belgium, Poland and France is valid only once a government platform or network accepts it: Peppol since 1 January, KSeF since 1 February, France's approved platforms since 1 September, and Germany from 1 January 2027. A rejected invoice cannot be booked or paid. The platform hands the rejection back to the sender as a code — KSeF 450 on Podmiot2/NIP, a Peppol receiver not found, a SIREN missing from the French directory — and an AR clerk has to work out which field it means, look the value up, ask the ERP team to change the customer master, and re-bill or resend. Most rejections come from stale master data: a tax number left behind by a merger, a missing Peppol ID, a SIREN never keyed.

The cost is cash and exposure. Every hour a rejection sits is an hour the invoice is not payable, and the same stale record breaks the next billing run as well. From 1 January 2027 Poland's penalty for an invoice issued outside KSeF can reach the full VAT on it; France charges €50 per invoice. Inbound, whether a supplier was an active VAT payer on the invoice date, or its bank account is on Poland's VAT white list, is checked by hand before the input VAT is claimed, if at all. And every platform changes its rules several times a year, with nobody testing what a new release would have rejected in your own invoices before it goes live.

typical100% of the VATthe maximum Polish penalty, from 1 January 2027, on an invoice issued outside KSeF
typical€50per invoicethe French penalty for a non-compliant e-invoice, up to €15,000 a year
demo96.1%of invoices passed first time in the week of 31 August, before the Fixer started on 7 September; 97.8% in the week of 12 October
Where an AR team's hours go on one day's rejectionsestimated
By hand27 days
With the solution1.9 days
  • Reading platform codes and finding the field that failed6 → 0.5 d
  • Looking the value up in registries and the customer master7 → 0.5 d
  • Asking the ERP team to change the master, and waiting5 → 0.5 d
  • Re-billing and resending, one invoice at a time4 → 0.2 d
  • Finding the other invoices that will fail the same way3 → 0.1 d
  • Recording what was changed, and why, for the auditor2 → 0.1 d

Estimated split of an AR team's hours on one day's 55 stopped invoices across three countries, by hand and with the solution.

How it works

How an invoice clears

Seven agents validate, fix, re-check and rehearse every country's rules; the AR lead approves every master-data change.

What comes in
Invoices in2,486 today · ERP billing runs, master data, registries
Agents at work
ValidatorEN 16931 + country rules
Then
Fixerregistry evidence
Checkerre-validates alone
Then
Mandate agentrehearses rule changes
Buyer agentinbound VAT
Then
VAT reconciliationties the return
Archive agentlegal retention
A person decides
AR Leadapproves every master-data fix
What comes out
Cleared invoices
Input VAT protected
Returns tied
One case, step by step

One rejected KSeF invoice, from the code to a KSeF number in 26 minutes

Kestrel & Vane Group bills from five entities in three live countries. It is Wednesday 14 October 2026, 09:40, in Wrocław. Since midnight 2,486 outbound invoices have entered the gates, and one of them, FV/2026/10/0412 for PLN 184,560.00, came back from KSeF. Here is the morning, screen by screen, in the working solution.

  1. 0109:40

    Every invoice of the day, flowing through its country's gate

    Katarzyna Nowak · AR Lead

    Katarzyna opens Clearance gates. Belgium 612, Poland 1,148 and France 726 invoices move left to right from the ERP, through the Validator's pre-check, through Peppol, KSeF and the approved platform, to Cleared. 2,431 of 2,486 passed first time. The 55 that stopped sit at their gate as red chips with the rule and the field, such as KSeF 450 on Buyer NIP or R0101047 on Buyer e-address, and a badge for who holds each one: the Fixer, or a person. Underneath, Germany runs as a rehearsal lane: 4,812 September invoices replayed against the 2027 rules, nothing sent.

    Needs you: “FV/2026/10/0412 · rejected by KSeF. Buyer NIP not active · the Fixer is on it.”

  2. 0209:15 · rejected

    The code, in plain words, and the agent already at work

    Fixer

    She clicks the chip and a drawer opens beside the stream. KSeF rejected the invoice with code 450 on Podmiot2/DaneIdentyfikacyjne/NIP. The Fixer has read the response, looked up NIP 527-284-61-91 in the VAT taxpayer list — Trans-Wisła sp. z o.o., removed on 30 Sep 2026, reason: merger — and found the surviving company in REGON: Wisła Trans Logistyka sp. z o.o., NIP 521-387-44-06, an active VAT payer since 2014. Address, bank account and contact in customer master C-204118 match; only the NIP is stale.

    “KSeF rejected it: the buyer’s NIP is not an active VAT taxpayer.”

  3. 0309:16

    The evidence, and a second agent that did not see the first one's working

    Checker

    The Fixer drafts the fix and regenerates the invoice: FA(3) schema valid, totals unchanged, confidence 98%. The evidence shows the master value against the registry value, with when each was read, and what else was checked: name and address match, VAT status active since 2014, bank account on the white list. Then the Checker re-validates on its own from the registries, agrees, and counts what else this record would break.

    Checker: “It did not see the Fixer’s working. Same result … 14 more invoices to this customer would fail the same way · PLN 612,904.40 gross.”

  4. 0409:41 · decided

    A person approves the master-data change, with a reason code

    Katarzyna Nowak · AR Lead

    The agents never change master data. Katarzyna clicks Approve the fix: the sheet shows the old and new NIP and that 15 invoices use this record — FV/2026/10/0412 is resubmitted at once and 14 more are re-queued. She picks MD-02, “Customer merged — registry evidence”, from four reason codes; a comment, if she writes one, is kept in the audit trail. The invoice is under PLN 500,000 gross, so she approves alone.

  5. 05Seconds later

    The master is fixed once, and KSeF issues its number

    Fixer

    ERP job MD-UPD-88412 updates customer master C-204118. The Fixer resubmits FV/2026/10/0412 to KSeF, signed with the company seal, and KSeF accepts it at 09:41:20 with KSeF number 5260250995-20261014-3F9A21C07B4E-8D. The UPO is stored in the archive, the 14 other invoices are re-queued with the new NIP, and the stop leaves the Poland lane: Fixed by agents goes from 38 to 39.

    “Approved by Katarzyna Nowak · MD-02 · 09:41”

  6. 06The other fixes

    Ten master-data changes, each with its registry evidence

    Fixer · Checker

    Master-data fixes holds every change the Fixer has proposed to a customer or supplier record: 10 waiting, which would fix 31 invoices, with the Checker disagreeing on none. Odra Steel Components S.A. split on 1 October and invoices to the new company at 91% confidence. Scheldt Freight NV's Peppol ID 0208:0793455128 came from the company register and the network directory; its stopped invoice is €116,668.20, above €100,000, so Sofia Marchetti, Head of Tax, approves after Katarzyna.

    “The Fixer proposes; the Checker re-checks; the record’s owner approves. One approval fixes every invoice that uses the record.”

  7. 0708:37 · inbound

    Input VAT held before it is claimed, with the request already drafted

    Tomasz Wójcik · AP Specialist

    Inbound, the Buyer agent checked all 1,904 invoices received from KSeF, Peppol and the French platform, and held the VAT on 23. FA/2026/2291 from Baltic Pallet Works sp. z o.o., PLN 61,500.00 gross with PLN 11,500.00 VAT: the supplier is an active VAT payer, the rate, order, goods receipt and duplicate checks pass, but the bank account on the invoice is not on the VAT white list for its NIP. The agent drafted the correction request; Tomasz keeps holding, sends the request or releases the VAT — each with a reason.

    “The account on the invoice is not listed for this supplier’s NIP. Paying it risks joint liability for the VAT.”

  8. 08After the fix

    A rejection becomes a new pre-check, rehearsed before anyone signs it

    Fixer · Élodie Garnier, Indirect Tax Manager

    Today the Validator checks only the NIP check digit before sending. After FV/2026/10/0412 the Fixer proposed checking a Polish buyer's VAT status as well, which would have stopped 6 of today's 9 KSeF rejections before they were sent. The proposal was rehearsed on 29,640 invoices from the last 30 days: 23 would have stopped, mostly buyers removed from the VAT list after a merger or a split. It goes live only when Élodie signs it.

    “Waiting for your signature” · effective on signature · owner Élodie Garnier

  9. 091 Jan 2027 · 79 days

    The next country, rehearsed on real invoices

    Validator · Jonas Weber, Finance Controller, Germany

    Germany requires sending from 1 January 2027. The Validator replayed September's 4,812 invoices from four German entities against the 2027 rules and sent nothing: 4,479 would pass, 93.1% against a 99.5% target held for two weeks. Three patterns explain the rest, each with an owner and a date — 212 invoices on the ZUGFeRD BASIC WL profile, 71 missing the buyer VAT ID (BT-48), 50 with payment terms as free text only (BT-20). The go-live checklist is 3 of 7 done; the last item is the Indirect Tax Manager's sign-off.

  10. 10Before the return

    Cleared invoices tied to the VAT return, every difference explained

    VAT reconciliation agent · Élodie Garnier

    The VAT reconciliation agent tied September's cleared invoices to the VAT ledger. Belgium ties at €4,118,402.55. Poland's JPK_V7M differs by PLN −2,212.30: credit note KOR/2026/09/0088 was booked on 30 Sep and sent to KSeF on 1 Oct, so it stays in September's return with its KSeF number noted. France differs by €128.10, rounding on 3 invoices from one billing template. Élodie accepts each explanation, then signs the tie-out; the agent never files a return.

    “VAT rounded per line in the ledger, per rate on the invoices. The invoice amounts are the legal ones.”

Who it’s for

Built for everyone who owns an e-invoice, from billing run to VAT return.

The same Wednesday morning, seen by five of the people who carry it — what their day looked like, and what it looks like now.

KN
Katarzyna NowakAR Lead, Group Shared Services, Wrocław · approves master-data fixes for customers
AR Lead
Before
Owns the outbound stream for Poland, Belgium and France and spends her mornings decoding platform codes and waiting on the ERP team. “A rejected invoice is an unpaid invoice. I want it fixed before lunch.”
Now
Sees every invoice of the day at its gate; opens a stop to find the cause in plain words, the corrected value with registry evidence and the Checker's verdict, and approves the change once with a reason code.
ÉG
Élodie GarnierIndirect Tax Manager, Lyon · signs rule changes, VAT tie-outs and country go-live
Indirect Tax Manager
Before
Learns what a new Peppol release or decree breaks on the morning it lands. “When a rule changes, I want to know what it would have rejected before it goes live.”
Now
Gets each rule change with its source and a rehearsal on the last 30 days of invoices, signs it into production or defers it, and signs each country's VAT tie-out once every difference is explained.
TW
Tomasz WójcikAP Specialist, Poznań · inbound invoices from KSeF, Peppol and the French platform
AP Specialist
Before
Books inbound invoices and checks VAT recovery by hand, if at all. “I can't claim VAT on an invoice from a supplier who isn't on the white list.”
Now
Starts with the 23 invoices the Buyer agent held, each with its reason and a drafted supplier request or suggested refusal; releases, keeps or refuses each one with a reason code.
PJ
Pieter JanssensERP Administrator, Antwerp · connections, master-data jobs and set-up
ERP Administrator
Before
Gets a stream of requests to correct customer records one invoice at a time. “Every fix should land in the master, once, not in a hundred invoices.”
Now
Runs the connections, the master-data jobs and entity set-up, with no approvals of his own. Master data stays locked to a person's approval, and an approved change reaches the master once, through one ERP job.
SM
Sofia MarchettiHead of Tax, Amsterdam · second approver above the threshold
Head of Tax
Before
Owns the regulatory exposure and reads about it after the fact. “Show me the penalty we didn't pay and the cash we didn't wait for.”
Now
Second-approves fixes to invoices above PLN 500,000 or €100,000 gross, with the evidence and the first approver's reason in front of her, and follows first-time pass, stops by cause and time to fix in the reports.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents validate, fix, re-check and rehearse every country's rules; the AR lead approves every master-data change.

Validator

Runs EN 16931, Peppol BIS 3.0, KSeF FA(3), the French rules and registry checks on every outbound invoice before it is sent, records each rule result with its ID and field, and rehearses countries not yet live.

  • Never sends an invoice that fails a fatal rule
  • Never edits an invoice
Fixer

Turns a platform code into plain words, finds the corrected value in master data or a public registry — VAT taxpayer list, VAT white list, REGON, VIES, company registers, the SIREN directory — records where and when it read it, counts every other invoice the record affects, and regenerates and resubmits the invoice.

  • Never writes master data: every change goes to its owner with the evidence
  • Asks a person below 90% confidence, even for fixes it may make alone
Checker

Re-runs the rules and the registry lookups for every fix without seeing the Fixer's working, compares the result with the proposal, and counts the other invoices affected in the billing schedule.

  • Cannot clear its own flag
  • Escalates any difference to a person, never averages
Mandate agent

Reads platform release notes, official gazettes and tax authority pages, drafts each rule change and rehearses it on the last 30 days of invoices, so the Indirect Tax Manager sees what it would have rejected.

  • Never puts a rule into production
  • Always cites the source
Buyer agent

Checks each inbound invoice before its input VAT is claimed: the supplier's VAT status and bank account on the invoice date, the rate and reverse charge, the order and goods receipt, and duplicates; drafts the request to the supplier or suggests the French refused status.

  • Never refuses an invoice alone
  • Never releases held VAT alone
VAT reconciliation agent

Ties cleared invoices to the VAT ledger and the return per country — JPK_V7, the Belgian periodic return, CA3 — and explains every difference.

  • Never files a return
  • The Indirect Tax Manager accepts each difference and signs the tie-out
Archive agent

Keeps each invoice with its platform receipt and statuses for the legal period — 10 years in Poland, Belgium and France, 8 in Germany — verifies integrity nightly and answers retrieval.

  • Never deletes before the period ends
  • A legal hold overrides it
AR Lead

Approves every master-data fix. The agents propose; a named person decides.

Ask in plain words

Ask about any invoice, customer, rule or country

The assistant answers from the platform responses, the registries and the rules, cites each source, and opens the screen where you act.

Why was FV/2026/10/0412 rejected?

KSeF rejected it at 09:15 with code 450 on Podmiot2/NIP: the buyer's NIP 527-284-61-91 is no longer an active VAT taxpayer. It belonged to Trans-Wisła sp. z o.o., removed on 30 Sep 2026 after its merger into Wisła Trans Logistyka sp. z o.o., NIP 521-387-44-06. The Checker agrees, and 14 more invoices to this customer would fail. I have opened the fix for you to approve.

Which customers will fail in the next billing runs?

Three records will stop invoices this week unless they are fixed: Wisła Trans Logistyka (NIP, 14 invoices, PLN 612,904.40), Odra Steel Components (company split 1 Oct, 6 invoices) and Lys Valley Foods (no Peppol ID, 6 invoices). All three proposals are on Master-data fixes.

Are we ready for Germany on 1 January?

Not yet: the September rehearsal passes 93.1% (4,479 of 4,812) against a 99.5% target. 212 invoices use the ZUGFeRD BASIC WL profile, which is not an invoice from 2027; switching three entities to EN 16931 lifts the pass rate to about 97.5%. Four checklist items are open, with owners.

How much input VAT is on hold today?

€60,173 of input VAT is held on 23 of today's 1,904 inbound invoices. The largest reason is bank accounts not on the VAT white list (6 invoices, among them FA/2026/2291 from Baltic Pallet Works, PLN 11,500.00); then prices above the order in France (5). Each has a draft request or a suggested refusal for Tomasz Wójcik.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

Clearance gatesEvery outbound invoice of the day, flowing through its country's gate; stops sit at their gate with the rule and the field; Germany as a rehearsal lane; what needs you and the seven agents at work.
The Fixer at workA KSeF rejection in plain words, and the Fixer's steps through the VAT taxpayer list, REGON and the customer master, each timed.
Evidence and the CheckerThe master value against the registry value with when each was read, what else was checked, and the Checker's own verdict with the 14 other invoices affected.
Approve with a reason codeOne master-data change, the invoices it resubmits and re-queues, and the reason code the decision needs.
Resubmitted and clearedThe ERP job, the resubmission and KSeF's acceptance with its KSeF number; the UPO stored and 14 invoices re-queued.
ExceptionsEvery invoice stopped today, at pre-check or by a platform, with its rule and field, owner and time left against the 4-hour limit.
Master-data fixesEach proposed change to a customer or supplier record, with its registry evidence, confidence and the invoices it fixes; one approval fixes them all.
Inbound VAT checkThe Buyer agent's checks on an inbound KSeF invoice, the reason its VAT is held, and the drafted request to the supplier.
Rule changesEach country's rule changes with their source, effective date and a rehearsal on real invoices, waiting for a signature.
Germany rolloutThe 2027 rules rehearsed on 4,812 September invoices, the patterns that would stop with owners and dates, and the go-live checklist.
VAT reportingCleared invoices tied to the VAT ledger and the return, country by country, with each difference explained before the tie-out is signed.
Audit trailEvery step by people, agents and platforms, append-only, with reason codes on decisions and an evidence pack to export.
Rules and thresholdsWhat the Fixer may fix alone, master data locked to a person, the confidence floor, the second-approver threshold and the rehearsal window.
Governance

Built for a tax audit: every stop cited, every fix re-checked, every change approved, on the record.

Every stop cites its rule, every fix its evidenceA stopped invoice shows the rule ID, its version and the field that failed. A proposed fix shows the registry record it came from — the VAT taxpayer list, REGON, the company register, the SIREN directory — and the time it was read.
A second agent re-performs every fixThe Checker re-runs the rules and registry lookups without seeing the Fixer's working, counts the other invoices the record affects, escalates any disagreement to a person and cannot clear its own flag.
Master data changes only with a person's approvalThe Fixer may correct rounding, formats, derived mentions and order references alone, if Settings allows. Tax numbers, Peppol IDs, SIRENs and bank accounts always need the owner's approval with a reason code; that setting cannot be switched on.
Two approvers above the thresholdA fix to an invoice above PLN 500,000 or €100,000 gross needs a second approver, the Head of Tax. Inbound refusals and VAT releases are the AP specialist's; rule changes, VAT tie-outs and a country's go-live are signed by the Indirect Tax Manager.
Rule changes rehearsed before they are signedNo rule reaches production without a signature. Each change carries its source and a rehearsal on the last 30 days of invoices, and the Indirect Tax Manager signs, rehearses again or defers it. Changes to Settings are versioned and need her approval too.
An append-only trail and an evidence packEvery step by people, agents and platforms is recorded in order, and each decision carries its reason code. An evidence pack exports the invoice, the platform receipt, the rule, the fix, the evidence and the decision; the statutory auditor reads everything and changes nothing.
Configuration

Your thresholds, your approvers, your clocks

What the Fixer may fix alone, when a person must decide, and how fast. Changes are versioned and need the Indirect Tax Manager.

SettingDefaultChoose from
The Fixer may fix aloneRounding and totals · formats · derived mentions · order referencesEach switched on or off
Master data: tax numbers, Peppol IDs, SIRENs, bank accountsAlways needs a personLocked; cannot be switched on
Confidence floor90%Any percentage; below it the Fixer asks a person even for allowed fixes
Second approver abovePLN 500,000 · €100,000 gross of the stopped invoiceAny amount per currency
Inbound price tolerance2%Any percentage of the unit price against the order
Rehearsal window30 daysAny number of days of invoices replayed for a rule change
Rejection fixed within4 business hours · alert at 3 hoursAny time, with its alert; KSeF offline upload has its own clock: by the end of the next working day, alert at 15:00
Inbound VAT decision2 days, before the payment runAny number of days, with notifications on or off
Connections

Works with the systems your invoices already run through

ERP billinggroup and plant billing runs, read every 5 minutes; the customer and supplier master, written only by the approved ERP job
Clearance platformsa certified Peppol access point, KSeF with a company-seal certificate and offline mode, and the French approved platform with lifecycle statuses 200, 210, 212 and 213
Public registriesVAT taxpayer list, VAT white list, REGON, VIES, company registers and the SIREN directory
AP and paymentsinbound invoices, holds and the payment file, with orders and goods receipts for price checks
VAT ledgeroutput and input VAT by period, tied to JPK_V7, the Belgian periodic return and CA3
Archivewrite-once store for each invoice with its receipt and statuses, 8 to 10 years by country
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0
invoices issued outside a clearance platform; in Poland each can cost up to its full VAT
target
99.5%
of invoices passed first time, and every rejection fixed the same day
Six weeks ago96.1%
Today97.8% → 99.5%
estimated
€2.1M
of input VAT a year checked before it is claimed
23 of 1,904 held today
each with its reason

“demo” = seen in the working solution, on its sample data · “typical” = published figures (Polish VAT Act as amended: KSeF from 1 Feb / 1 Apr 2026, penalties from 1 Jan 2027 up to 100% of the VAT; French Finance Act 2026: €50 per invoice, €15,000 cap a year) · “estimated” = our estimate · Other dates are named as context: Belgian Royal Decree (Peppol B2B from 1 Jan 2026), German Growth Opportunities Act (sending from 1 Jan 2027). Kestrel & Vane Group, its entities, customers, suppliers, documents and the people named on this page are fictional — characters and sample data in the working solution.

Questions

What heads of tax, AR and AP leads ask us.

What is E-Invoicing Compliance?

E-invoicing compliance means every invoice you issue or receive meets the format and rules of the country's clearance platform or network — Peppol in Belgium, KSeF in Poland, the approved platforms in France — so it is accepted, payable and good for input VAT. E-Invoicing Compliance does this with seven agents that validate every outbound invoice against EN 16931 and each country's rules before it is sent, fix rejections with registry evidence, and check inbound invoices before the VAT is claimed. A person approves every master-data change.

How does it handle a KSeF or Peppol rejection?

The Fixer reads the platform's code, says in plain words which field failed, finds the corrected value in a public registry or the customer master, and regenerates the invoice. The Checker re-validates on its own and counts the other invoices the same record would break. In the sample, a KSeF code 450 at 09:15 was cleared with a KSeF number at 09:41, and 14 more invoices were re-queued with the new NIP.

Does it change our customer master on its own?

No. The Fixer may correct rounding, formats, derived mentions and order references alone if you allow it in Settings, but tax numbers, Peppol IDs, SIRENs and bank accounts always need the owner's approval with a reason code, and that setting is locked. Above PLN 500,000 or €100,000 gross a second approver signs as well. An approved change reaches the master once, through the ERP job.

Can it check inbound e-invoices before we claim input VAT?

Yes. The Buyer agent checks every inbound invoice from KSeF, Peppol and the French platform: the supplier's VAT status and bank account on the invoice date, the rate and reverse charge, the order and goods receipt within the price tolerance, and duplicates. In the sample it held the VAT on 23 of 1,904 invoices, €60,173, each with its reason and a drafted request or suggested refusal for the AP specialist to decide.

How does it keep up with rule changes and new countries like Germany in 2027?

The Mandate agent reads platform release notes, gazettes and tax authority pages, drafts each change and rehearses it on the last 30 days of your invoices: the November Peppol release would have failed 41 of 15,780 Belgian invoices. A country not yet live runs as a rehearsal lane — Germany's 2027 rules on 4,812 September invoices, nothing sent — with a readiness score, owners for each failure pattern and a go-live checklist.

Does it tie cleared invoices to the VAT return?

The VAT reconciliation agent ties cleared invoices to the VAT ledger and the return per country — JPK_V7M, the Belgian periodic return, CA3 with French e-reporting — and explains every difference, such as a credit note booked on 30 September and sent to KSeF on 1 October. The Indirect Tax Manager accepts each explanation and signs the tie-out; the agent never files a return.

Do people stay in control?

Yes. The agents validate, propose and check; they never send an invoice that fails a fatal rule, never change master data, never refuse an inbound invoice or release held VAT, and never put a rule into production. The AR lead approves master-data changes, the AP specialist decides inbound holds, and the Indirect Tax Manager signs rule changes, tie-outs and go-live, each with a reason code on the audit trail.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your entities and registrations, platform connections, approval limits and a recent month of invoices and rejections — and it goes live once every quality gate has passed. A guided set-up adds each entity, checks its registrations, and starts it as a rehearsal or a live gate.

See it on
your invoices.

We'll run E-Invoicing Compliance on your own last month of invoices — your billing runs, your customer master and the rejections that came back.