/ THE SHORT ANSWER
- 01Keep the original file separate from its viewing copy.
- 02Distinguish format errors from purchasing disagreements.
- 03Give every exception an owner and a return route.
/ dotSuper point of view
dotSuper analysis: invoice automation creates value when it assigns and resolves uncertainty before posting.
Receipt is a capability, not a payment decision
It distinguishes these from ordinary PDF invoices and allows different issuance transitions.
[1] The operational implication is a mixed inbox, even when the receiving company has modern software.
Treat each arrival as a case with an immutable receipt identifier.
Record arrival time, supplier claim, file type and intended purchasing entity.
A plant mailbox and a central finance mailbox may receive the same invoice, so both routes should resolve to that identifier.
Avoid forcing every supplier into an elaborate portal before understanding intake failures.
An accessible route with clear instructions may work better for a small toolmaker.
The useful question is whether finance can trace every received document to a resolved accounting decision.
Keep three kinds of evidence distinct
A document can pass one gate and fail another.
Combining these statuses into a single green icon hides decisions that belong to different teams and encourages accidental approval.
KoSIT publishes a configuration for validating documents against the German XRechnung standard.
[2] That provides a relevant technical reference.
It does not establish whether the goods arrived, whether a service was accepted, or whether the bank account belongs to the supplier.
Preserve the original alongside the validation result and any human-readable rendering.
Store the rule configuration used, because an unexplained validator upgrade can change outcomes.
When staff correct internal mappings, distinguish that accounting enrichment from a correction issued by the supplier.
Design the exception queue around decisions
Missing order reference is different from unknown buyer, and both differ from unreceived goods.
The person resolving the case should see exactly what evidence would move it forward.
The following table is an original operating proposal.
Agree the owners with finance and purchasing before choosing software.
Ownership matters more than an ambitious target for automatic posting, especially where several plants share suppliers.
Make reassignment explicit.
A case sent to purchasing should retain its receipt time and history.
Otherwise teams can improve their apparent queue age simply by bouncing difficult items elsewhere, while the supplier continues waiting without an intelligible answer.
| Exception | Decision owner | Evidence needed |
|---|---|---|
| Invalid structure | Finance systems | Original file and validation report |
| Missing order reference | Purchasing | Approved order or justified exception |
| Quantity disagreement | Goods receiving | Receipt record and delivery note |
| New bank details | Supplier master team | Independent supplier confirmation |
| Possible duplicate | Accounts payable | Prior receipt and posting history |
A hypothetical Baden-Wuerttemberg machining supplier
Eighty lack a usable order reference, and each takes twelve minutes of finance effort.
That is 960 minutes, or sixteen hours, before considering the purchasing team's work.
These are illustrative assumptions, not industry averages.
The team discovers that fifty of those eighty invoices concern maintenance callouts.
Adding the approved maintenance request identifier to supplier instructions prevents a recurring ambiguity.
It would be premature to assume all fifty cases disappear, because technicians may still commission emergency work outside the planned route.
Measure the next comparable group of callouts separately.
If unresolved references fall but goods-receipt disputes rise, intake has exposed another bottleneck.
Record both results, including the effort spent changing instructions, so the business case does not count displaced work as eliminated work.
Avoid making the exception process its own factory
Start with a few causes that lead to different decisions.
If two categories have the same owner and resolution evidence, combining them may make the system easier to use without losing operational insight.
Set escalation rules around consequences.
An invoice blocking a critical repair supplier may deserve attention before a larger routine invoice.
Finance should see disputed amount, supplier dependency and the next production commitment, rather than relying on invoice age alone.
Do not train an assistant to invent missing order numbers from similar historical transactions.
It may suggest candidates with visible evidence, but uncertainty should remain visible.
A confident wrong match can be harder to unwind than a clearly unresolved invoice, particularly after accounting periods close.
Close the loop with suppliers and accounting
If a supplier must reissue the document, identify what is wrong precisely.
Avoid vague rejection messages that send the supplier back through the same cycle without actionable information.
Review a small set of completed exceptions with the people who handled them.
Look for repeated missing fields, unclear purchasing authority and mismatched identifiers between ERP and maintenance systems.
Change the upstream process when the same cause appears across otherwise unrelated suppliers.
Choose the first improvement by recurring effort and operational importance.
A reliable maintenance reference may beat a sophisticated extraction model.
Success means fewer unresolved cases, traceable approvals and less repeated clarification, with the original evidence still available when finance needs to explain a posting.
What this page cannot conclude
- 01BMF guidance concerns German tax treatment; public procurement and individual transactions require separate assessment.
- 02The workflow and figures are hypothetical recommendations, not measured customer results.
- 03This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Sources
- 01E-Rechnung FAQ, March 2026Federal Ministry of Finance (BMF) · accessed Sep 15, 2026
- 02XRechnung validator configurationKoordinierungsstelle fuer IT-Standards (KoSIT) · accessed Sep 15, 2026
This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 15, 2026). Build an E-Invoice Inbox That Resolves Exceptions. dotSuper. https://dotsuper.net/feeds/applied-systems/germany-einvoice-receipt-exception-workflow