How do machine builders collect down payments and retention?

Machine builders collect by trigger document: a down payment request at order, progress invoices, a final invoice after acceptance, then a retention. German machine builders held EUR 55.9 billion of customer down payments in 2023, almost twice their trade receivables.
Ascending glass vessels with metallic spheres visualizing sequential payment stages in machinery receivables collection flow

Key Takeaways

  • German machinery companies held EUR 55.9 billion of down payments received against EUR 28.7 billion of trade receivables in their 2023 accounts (Deutsche Bundesbank, 2025).
  • CollectPulse actions 100% of overdue invoices within 24 hours, against 30-40% for manual teams (Transformance customer data, 2026).
  • In an illustrative EUR 2.4 million order, EUR 120,000 of the final payment is a retention due 24 months after acceptance, not a deduction.
  • ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes (Transformance customer data, 2026).

In This Article

Why are machinery receivables different from other B2B receivables?

Machinery receivables differ because cash falls due against down payment requests, milestones, acceptance and retentions; German machine builders held EUR 55.9 billion in customer down payments in 2023.

Machinery receivables are the open items of a machine or plant order billed in stages, from a down payment request (Anzahlungsanforderung) through progress and final invoices to a retention paid out after warranty. US construction calls the retention “retainage”.

In their 2023 financial statements, German machinery companies reported EUR 55.9 billion of down payments received against EUR 28.7 billion of trade receivables, on revenue of EUR 336.9 billion (Deutsche Bundesbank, 2025; extrapolated sector figures). By our rough calculation, receivables equal about 31 days of revenue and down payments about 61 (receivables include VAT, revenue does not).

‍

‍

Down payments received are cash already paid but not yet set off against a final invoice: a liability, not money owed. Each one still had to be requested, matched and later cleared.

A standard AR process misses unpaid requests. In SAP, a down payment request does not update the account balance, and the payment and dunning programs process it only if you specify this explicitly (SAP Help).

The VDMA expects real machinery production to fall 2% in 2026, the fourth year of decline in a row, while order books fill, mainly from outside the euro area (VDMA via dpa, 17 Sep 2026). More orders mean more down payment requests; slower production stretches the milestones behind them. German machinery exports reached EUR 99.3 billion in the first half of 2026, down 0.8% nominal (VDMA via Computer&Automation, 2026). For late payment overall, see the German Mittelstand in 2026.

‍

‍

Which documents does a machine order bill, and when?

A machine order typically bills a down payment request at order, a progress invoice at shipment and a final invoice after acceptance; a retention falls due at warranty end.

Document (EN / DE)TriggerSAP objectCash application matchCollections rule
Down payment request / AnzahlungsanforderungOrder confirmationBilling document type FAZ; noted item, special G/L indicator F; payment posts with AAgainst the request by PO, project number and amount; never on accountOwn report of open F items; dunned only if the procedure includes them
Progress invoice / AbschlagsrechnungMilestone, e.g. readiness to shipBilling plan date, unblocked by the milestoneInvoice or milestone referenceTerms from the milestone date
Partial invoice / TeilrechnungDelivery of a separable partPartial billing on the order itemInvoice number and amountNormal reminder cycle
Final invoice / SchlussrechnungAcceptance (Abnahmeprotokoll)Final invoice with down payments to be clearedRemainder after earlier payments are clearedSigned protocol first; punch-list points to the project owner
Retention / SicherheitseinbehaltEnd of warranty, or a warranty bondSeparate open item or special G/L transaction (configuration varies)Reclassify the short final payment; not a deductionDunning block; release request one month before due
LC payment / AkkreditivComplying documents presentedOpen item with the LC referenceLC number; bank charges by policyDocuments before the LC deadline
Spare parts and service / Ersatzteil- und ServicerechnungDelivery or signed service reportStandard or service orderInvoice number, often bundledAutomated reminders to the maintenance contact

Payment schedules read “30/60/10” or “a third with the order, a third at readiness to ship, a third after acceptance”; every contract differs, so treat any split as an example, not a benchmark.

Mixing up a progress invoice, which the final invoice sets off, with a partial invoice, which is final for its part, is how a final invoice ends up with the wrong open amount.

SAP names project billing in plant engineering and construction as a typical use of milestone billing: plan dates stay blocked until their milestone is confirmed, and the final invoice copies the down payments in as “down payments to be cleared” (SAP Learning, 2026). More in how AI agents work with SAP for AR.

Change orders (Nachträge) are billed separately or added to the plan. A contested one is a frequent reason a customer pays the final invoice net of “disputed scope”; that gap is a dispute, not a retention.

How does cash application match down payments, milestones and final invoices?

Cash application matches a down payment to its request, a milestone payment to its invoice, and a final payment to what remains once all earlier payments are cleared.

Customers rarely quote your down payment request number; they quote their PO, the project or commission number (Kommissionsnummer) or your order confirmation. Amount works for one large payment until it arrives net of a retention, bank charges or a contested change order. Then it needs an investigation.

Three failure modes recur:

  • The down payment posts on account (Akontozahlung) instead of against the request. The final invoice then bills EUR 720,000 too much in the example below.
  • The retention is booked as a deduction. A final payment short by the agreed retention is a security retention (Sicherheitseinbehalt): its own open item with a due date and a dunning block.
  • Small invoices hide under a large one. One payment covers a milestone invoice plus spare parts invoices, and the small items stay open and get dunned.

AI-native platforms such as Transformance take the reading and routine matching off the team. DocSense reads payment advices in any format with over 97% extraction accuracy across 100+ document types and 170+ languages, with no templates. ClearMatch reaches a 95% auto-match rate, runs end to end in under 8 minutes and validates 100% of postings; nothing posts without human sign-off (Transformance customer data, 2026).

How should collections chase acceptance payments and retentions?

Collections should chase each machinery payment by its trigger: the down payment request before production, the acceptance payment once the protocol is signed, the retention on its release date.

How to collect a machine order in 7 steps:

  1. Record the payment schedule from the order confirmation: each payment, its trigger document, its terms and its owner on both sides.
  2. Issue the down payment request at order confirmation and set the delivery or production block the contract allows.
  3. Match each down payment to its request, never on account, so the final invoice can clear it.
  4. On the day of site acceptance, ask for the signed acceptance protocol and send open punch-list points to the project or service owner with a date.
  5. Send the final invoice with every down payment and progress payment listed and cleared.
  6. Book any retention as its own open item with a due date and a dunning block until then.
  7. Request the retention release, or offer a warranty bond, before the due date, and chase it like any invoice after.

If a customer holds the acceptance payment, open points on the punch list (Restpunkteliste) are often the reason. Collections follows the date each point is due to be fixed, like a promise to pay, instead of sending reminders.

‍

‍

CollectPulse actions 100% of overdue invoices within 24 hours, against 30-40% for manual teams, and Vero handles 60-80% of routine touches (Transformance customer data, 2026). For export customers, the AI calling agent makes 15-20 calls an hour in 70+ languages and identifies itself as AI at the start of every call.

What changes for export orders, letters of credit and long terms?

Under a letter of credit the bank pays only against documents that comply with the credit, so export collections becomes a document task: complete, consistent and presented on time.

A letter of credit (Akkreditiv) usually follows the ICC rules UCP 600 (ERA 600 in German). A discrepancy holds payment until it is corrected or the buyer waives it; a deferred payment LC creates a long-dated receivable that should carry the LC reference.

The payment arrives from a bank, often net of charges, quoting the LC number; a small residual is a policy decision, not a dispute. Record documentary collections and federal export credit guarantees on the order too, so whoever chases a late export payment knows they exist.

Report export orders on 60-day terms or longer separately from 30-day spare parts invoices, or your DSO mixes two businesses. For groups with sales companies abroad, see cash application and forecasting for industrial manufacturers.

How do service and spare parts invoices fit into the same account?

Service and spare parts invoices are small, frequent and short-dated, so they need a volume process, while the same customer’s project invoices need a contract process with its own triggers.

Spare parts and field service are ordered by the customer’s maintenance team, often via web shop or EDI, on 30-day terms; the machine was bought by purchasing. A service invoice rests on the technician’s signed service report, and queries are about hours and travel.

A credit hold on spare parts because an acceptance payment is late can stop the customer’s production and delay acceptance further; route that decision to a person. One customer can owe a retention, a contested change order and twenty spare parts invoices at once, which makes the account, not the invoice, the unit of work.

What does an AI agent with Customer 360 change in machinery receivables?

An AI agent like Vero from Transformance investigates each reduced or unmatched machinery payment from Customer 360, then proposes the match or next step with evidence; a person approves.

Customer 360 is one graph per customer and Vero’s working memory. When a final payment arrives short, Vero starts from that record, fetches information from internal and external sources to find more matches, and proposes the posting or next step with evidence. Whether the gap becomes a retention item, a dispute or a residual is decided by a person on your team.

Vero acts within a 4-level approval model (read, recommend, execute, post) with a full audit trail. Transformance connects to SAP S/4HANA and ECC, Oracle, NetSuite and Dynamics, keeps data hosted in your region, and runs a proof of value in 4-5 weeks on one entity.

Illustrative example: one EUR 2.4 million machine

In an illustrative EUR 2.4 million machine order, EUR 120,000 of the final payment is a security retention, not a deduction, and falls due 24 months after acceptance.

Machine builder A sells to Plant operator B (fictional, net amounts, no VAT) on a 30/60/10 plan with a 5% retention for a 24-month warranty.

  • Order confirmation: down payment request of EUR 720,000, paid and matched to the request.
  • Readiness to ship: progress invoice of EUR 1,440,000, 30 days net, paid.
  • Site acceptance: six weeks late, because of four punch-list points.
  • Final invoice: EUR 2,400,000 less 720,000 less 1,440,000 leaves EUR 240,000.

Matched by document (after): Plant operator B pays EUR 120,000 and withholds EUR 120,000. The right handling is a EUR 120,000 retention item, due 24 months after acceptance, with a dunning block and a release request one month before. Sum check: 720,000 + 1,440,000 + 120,000 + 120,000 = 2,400,000.

Posted on account (before): had the down payment been posted on account, the final invoice would show EUR 960,000 open, and Plant operator B would be reminded about EUR 840,000: EUR 720,000 already paid, EUR 120,000 not due for two years. The money was never at risk; the AR process was.

Conclusion: bill by trigger, match by document, chase by date

Machinery receivables stay under control when each payment is tied to its trigger document, matched to that document, and chased on the date the trigger occurred.

Treat the payment schedule as AR master data, report down payment requests and retentions separately, and follow acceptance as a project date. Vero investigates from Customer 360, ClearMatch matches, CollectPulse chases what is overdue, and a person approves.

‍

‍

Frequently Asked Questions

What is the difference between a down payment invoice, a progress invoice and a final invoice?

A down payment invoice asks for money before delivery, a progress invoice bills part of the contract during the work and is set off later, and the final invoice bills the total less everything already paid.

Why do unpaid down payment requests not show up in the AR aging?

In SAP a down payment request is a noted item that does not update the account balance, so a balance-based aging misses it, and dunning runs include it only if the dunning procedure is set to.

How should cash application treat a retention withheld from the final payment?

Treat a retention as its own open item with a due date and a dunning block, not as a deduction or a write-off, because the contract makes it payable later.

What do you do when a customer holds the acceptance payment?

Ask for the signed acceptance protocol and the punch list, route each open point to the project or service owner with a date, and follow that date instead of sending reminders.

SAP cash application and AR automation module

Can AI match milestone and final payments in SAP?

Yes, AI agents like Vero from Transformance investigate unmatched and reduced payments from Customer 360 and propose each match with evidence; a person approves. ClearMatch reaches a 95% auto-match rate.

Continue reading