Make German Project Invoices Survive Corrections

02These events can be related without being interchangeable.

03Assign a distinct record to the commercial event before creating the invoice that represents it.

04The BMF explains that required invoice information belongs in the structured content.

05It also addresses corrections, partial payments and final invoices, with specific conditions and exceptions.

06[1] Treat that guidance as the factual starting point, then have finance establish the treatment for your contract.

07The implementation choice is to preserve event identity through every document.

08If commissioning is delayed, the invoice system should not silently rename a delivery milestone to fit the amount someone wants to bill.

09It should show which contractual condition remains unresolved and who can decide it.

02A single project balance cannot explain whether a difference comes from an unapproved variation, an invoice correction or a payment allocation.

03Generate the structured document from an approved snapshot of these records.

04Freeze that snapshot with its issue identifier.

05Later edits to the project master should create a new state without rewriting what the customer originally received or what accounting originally posted.

06KoSIT's published XRechnung validation configuration is a technical reference for checking the resulting document.

07[2] Use validation alongside commercial reconciliation.

08Neither an XML check nor a PDF preview can establish that a changed scope was accepted by the customer's authorised representative.

02They may require different accounting treatment.

03The software should ask finance for the route instead of treating every event as a generic negative invoice.

04Use the table as an implementation checklist, not a statement of mandatory tax treatment.

05Its purpose is to reveal missing evidence before a document leaves the organisation.

06Give the original document and its successor separate statuses.

07Marking an old invoice as deleted can destroy the trail that explains the customer statement.

08A cancellation or replacement should remain visible as a business event with an accountable author.

02The supplier has invoiced EUR 30,000 and then EUR 50,000.

03The customer has paid both amounts.

04An approved scope reduction lowers the contract total by EUR 5,000 before final settlement.

05The revised project value is EUR 95,000.

06Subtracting the EUR 80,000 already paid leaves EUR 15,000 commercially outstanding.

07This arithmetic does not determine the legally appropriate invoice or credit documentation.

08Finance must choose the correct treatment and reflect it consistently.

09A weak system might generate the original EUR 20,000 final milestone and leave the reduction in an email.

10A stronger system displays the revised contract, the approved reduction, prior invoices and payments together.

11The issuing employee can explain the EUR 15,000 balance without reconstructing the entire project from memory.

02Capture the contracting entity, delivery location and buyer reference separately.

03Combining them into one customer name creates avoidable rejection when the invoice reaches central accounts payable.

04Test edge cases using fictional records: a site relocation, a different acceptance contact, a disputed accessory and a correction after year-end.

05Include the customer's expected document route when known.

06A workflow that handles only the initial invoice has not addressed the expensive parts of project administration.

07There is a tradeoff between richer records and excessive data entry.

08Make fields conditional on the event.

09An ordinary spare-part sale needs less milestone evidence than a bespoke production line.

10A final settlement still needs reconciliation, even when the screens look similar.

02If they cannot, improve the record structure before adding automatic reminders or customer-facing AI explanations.

03A useful acceptance pack contains the approved commercial history, structured documents, validation results and payment allocations.

04Include the reason for every correction and a link to its approval.

05Keep the pack understandable to both finance and the project team responsible for customer discussions.

06The next step is one difficult completed project, suitably anonymised.

07Rebuild its document chain and identify every point where the ERP relied on email interpretation.

08Automate those relationships in order of recurrence, preserving a finance decision whenever the contractual or tax treatment is genuinely uncertain.