Germany’s move towards structured e-invoicing makes invoice data easier to validate and process. It does not tell a finance team whether a customer disputes delivery, who approved a change or when automation should hand a case to a human.
Accounts-receivable software is good at detecting a missed due date. It can send reminders, update an ageing report and show that an expected payment has not arrived.
The harder question begins after those actions fail. Is the customer missing a document? Does it dispute part of the work? Did the invoice reach the wrong entity? Has somebody promised payment without authority to release it?
A system designed only to issue invoices will usually answer none of these questions. Finance teams need a deliberate handoff from payment automation to human recovery work. The handoff should preserve five events: identity, obligation, performance, invoice delivery and every exception or payment commitment.
Machine-Readable Is Not Evidence-Ready
Germany’s electronic-invoicing changes show the value and the limit of structured data.
The German Federal Ministry of Finance explains that a qualifying e-invoice uses a structured electronic format that permits automated processing. It also notes that technical validation can identify missing or logically inconsistent mandatory fields. That can reduce rekeying and catch data problems before an invoice enters a customer’s workflow.
But a structured invoice does not prove that a service was accepted, explain a pricing change or resolve a commercial dispute. Germany’s Finance Ministry itself separates tax invoice guidance from technical implementation and individual civil-law questions.
The distinction matters beyond Germany. An invoice record helps a system ask for payment. An evidence-ready recovery record helps a person understand why payment is due and what is blocking it.
Preserve Five Events, Not One PDF
A final invoice PDF or XML file is only one event in the transaction. A useful handoff connects five.
1. Identity
Record the exact contracting entity, billing entity, invoice recipient and relevant contacts. Similar trading names can hide the fact that a contract, delivery and invoice refer to different companies.
2. Obligation
Connect the signed contract, accepted proposal or purchase order to the agreed price, payment terms, governing terms and approved changes. A current amount should never depend on somebody remembering which version was final.
3. Performance
Preserve evidence that goods were delivered or services completed. That may include delivery records, milestone approvals, work logs, acceptance emails or a documented absence of an expected objection.
4. Invoice delivery
Keep the invoice in its original form and record when, where and to whom it was sent. If a portal or structured network returned a status, preserve that status rather than replacing it with a screenshot.
5. Exceptions and commitments
Capture disputes, missing-document requests, internal approval problems and every promised payment date. A reminder log that shows only “email sent” loses the most important information: what the customer actually said.
Together, these events create a chain that a person can follow. Without it, the team has an efficient invoice process and an inefficient investigation.
Use Statuses That Explain the Next Action
Many finance systems put every missed due date into one overdue bucket. That is useful for reporting but weak for decisions.
Use operational statuses that describe the current obstacle, such as:
- debt confirmed, payment date promised;
- document or approval missing;
- amount or performance disputed;
- customer details inconsistent; or
- no substantive response.
The status should have an owner, a next action and a decision date. Automation can route the work and enforce the date. It should not decide whether a dispute is valid or whether formal escalation is proportionate.
This classification also prevents a common failure. If the customer disputes one line item, the entire balance should not silently disappear into a generic dispute queue. The system should preserve the disputed amount, the undisputed amount and the evidence connected to each.
Put Escalation Triggers In Policy
Do not rely on the account manager to decide from memory when a case has become serious. Define internal triggers before the next invoice becomes late.
Useful triggers may include the value at risk, the number of failed payment promises, an unresolved entity mismatch, a material dispute, new orders that would increase exposure or a contractual notification deadline. Different customers and invoice values may justify different thresholds. The point is consistency, not one universal number.
When a trigger fires, stop automatic messages long enough for a person to review the file. The next step might be correcting a document, separating a dispute from an accepted balance, agreeing a documented payment plan or obtaining specialist advice. When the case is ready for a local route, the same evidence file should support recovering unpaid invoices in Germany without forcing the finance team to rebuild the history.
Apply The 15-Minute Handoff Test
Ask a finance colleague who was not involved in the sale to open the record. Within 15 minutes, can that person answer five questions?
- Which legal entity owes the money?
- What agreement created the obligation?
- What was delivered and accepted?
- What exactly is disputed or delayed?
- What happens next, who owns it and by what date?
If the answers require searching individual inboxes or messaging the salesperson, the workflow is not ready for recovery. Fix the data links while the people involved still remember the transaction.
The test does not prove a claim or replace professional advice. It measures whether the company has retained enough operational context to make a competent next decision.
Better Recovery Starts Before The Due Date
The EU Payment Observatory’s 2025 report says more than half of surveyed companies experienced difficulties from late payments in 2024. It also identifies the administrative burden of pursuing late payment as one of the consequences.
Automation should reduce that burden, not merely accelerate the first reminder. The best time to create the recovery record is during onboarding, contracting, delivery and invoicing, when the information already passes through the business.
Structured e-invoicing is a useful part of that design. The missing part is the handoff that connects invoice data to the people, promises and performance behind it. Build that handoff well, and the finance team can move from an overdue alert to a deliberate decision without reconstructing the transaction from scratch. For companies managing customers in several markets, European debt collection coverage can provide the wider map while each local case keeps its own evidence and decision trail.
Author bio
Lars Holdgaard founded Debitura and has 10+ years of experience across debt collection, accounts receivable, technology, and startups. Before Debitura, he co-founded and led product and technology work at startups and scaleups, building software for financial administration and receivables management. Lars studied at the IT University of Copenhagen and the Technical University of Denmark.
Lars Holdgaard, Founder of Debitura
