A truck arrives at the gate, parts are unloaded, and production keeps moving. Two weeks later the supplier calls, not about quality, but about an unpaid invoice. Finance looks in the ERP and sees “invoice blocked” or “not matched.” The warehouse swears the delivery was booked. Procurement says the price is correct. Quality is still checking a batch. Somewhere between the delivery note and the payment run, cash flow has slowed down, quietly, and nobody can point to one clear owner.
Most Tier suppliers know this pattern. It rarely shows up as a single dramatic failure. It shows up as a growing pile of small exceptions, a GR/IR account that never seems to clear cleanly, and a monthly routine of chasing documents that should have been attached to the transaction in the first place.
This article follows that path, delivery note to payment, and highlights the points where cash flow typically slows in German automotive component manufacturers with 20 to 500 employees. Not because people are careless, but because the process has been allowed to become “normal” in its current form.
The hidden workflow nobody draws
When people talk about “invoice processing” they often start with the invoice. That’s already too late.
For most direct materials, the real workflow begins earlier:
- Supplier ships goods, sometimes with ASN or EDI, often without
- Delivery arrives with a delivery note (Lieferschein), sometimes paper, sometimes PDF, sometimes mixed with labels and certificates
- Warehouse posts a goods receipt (Wareneingang) against a PO, or parks it, or posts it later
- Quality inspection may hold the stock, or release it partially
- Invoice arrives, EDI, PDF, portal, or paper
- AP runs the three way match (PO, goods receipt, invoice)
- Exceptions are handled, quantities, prices, missing PO, missing GR, wrong plant, wrong unit of measure, returns not posted
- Payment run picks up cleared items, blocked items are skipped
In SAP, this often sits around GR/IR and invoice block reasons. In Microsoft Dynamics, proALPHA, abas, APplus, and other mid market ERPs, the mechanics differ but the effect is the same. The bottleneck is rarely “the ERP.” It’s the document trail and the timing of postings.
The delivery note is the start of truth for what physically arrived. If the delivery note is missing, misread, or not linked, every downstream step gets slower.
Quiet slowdown point 1, the delivery note never becomes usable data
Many suppliers still handle delivery notes as paper at goods receiving. Someone stamps it, signs it, and puts it in a tray. Later it gets scanned, or filed, or sent to accounting, sometimes to the shared service center, sometimes to a local clerk. In some plants, delivery notes are photographed and emailed. In others, they disappear into “we will find it when the invoice comes.”
That’s not just untidy. It creates a predictable delay:
- Goods receipt posting happens without reliable reference to delivery note details
- If there is a discrepancy later, nobody can quickly verify what was delivered
- Certificates and batch numbers are separated from the receipt record
- For returns or shortages, the original reference is hard to retrieve
The problem isn’t that the delivery note is paper. The problem is that it isn’t captured as structured information at the point where it matters, at receipt.
In German automotive supply chains, delivery notes often carry details that are critical for downstream processes, packaging unit, batch, heat number, coil number, serial range, and reference to EN 10204 certificates or CoC. When those details are handled outside the ERP transaction, quality and finance end up chasing each other.
Quiet slowdown point 2, goods receipt timing is treated as flexible
Ask a finance director about cash flow, and you’ll hear about payment terms, DPO, supplier discounts, and liquidity planning. Ask a warehouse supervisor, and you’ll hear about unloading capacity, shift coverage, and quality inspection.
The connection between the two is the timing of the goods receipt posting.
If the goods are physically in the plant but the GR is posted days later, the invoice match cannot clear, even if the invoice is perfect. Many companies accept this lag because production comes first. But that lag has a cost:
- AP spends time investigating “missing GR” blocks that are simply late postings
- Suppliers get mixed signals, goods were accepted but invoices are blocked
- GR/IR positions age and accumulate, making the balance harder to explain
- Month end accruals become less precise because the timing of receipts is blurry
This is one of the most common “quiet” cash flow slowdowns. It is not a negotiation topic, it is internal discipline.
In practice, the lag often comes from understandable causes, overloaded receiving during peak delivery windows, missing PO numbers on the delivery note, wrong plant on the PO, partial deliveries, or quality holding the material so warehouse hesitates to post. But if you don’t define rules, every exception becomes a reason to wait.
A simple policy like “GR posted within 24 hours of physical receipt, even if quality inspection is pending” sounds easy until you look at the real process. It forces decisions about where to record holds, how to handle partial releases, and how to record blocked stock without blocking the financial clearing unnecessarily.
Quiet slowdown point 3, quality and finance run on different clocks
Automotive suppliers live under customer pressure, ppm targets, and audit readiness. Quality needs clean traceability, and they are right to be cautious. But quality related holds can create finance delays in ways that don’t show up in the quality KPIs.
Typical examples:
- Incoming inspection finds a deviation, stock is blocked, invoice is held “just in case”
- PPAP related documents or certificates are missing, so material is quarantined
- A batch is accepted for production use under deviation approval, but the paperwork trails behind
- A supplier’s EN 10204 certificate arrives separately, and is not linked to the receipt
If the process design couples “quality release” with “invoice release” without clear rules, you get a slow, cautious organization that delays payments even when contract terms and delivered quantities are correct.
This isn’t about paying bad suppliers faster. It’s about separating two controls that have different purposes:
- Quality control protects production and customer risk
- Invoice control protects financial correctness and compliance
When these are tied together informally, people act conservatively. Conservative in this context often means slow.
Quiet slowdown point 4, the three way match becomes an exception factory
Three way match works well when master data and purchasing discipline are stable. In many mid sized suppliers, it isn’t stable, and not because the team is incompetent. It’s because the business reality keeps changing.
Common exception drivers in Tier 1, Tier 2, and Tier 3 plants:
- Price changes not updated on the PO, especially surcharges and index based adjustments
- Units of measure differ between PO, delivery note, and invoice (kg vs pcs, reels vs meters)
- Partial deliveries and backorders, invoice covers multiple shipments
- Packaging charges or freight appear as separate lines without clear PO reference
- Wrong vendor number or plant assignment due to supplier master data drift
- Consignment and call off complexity where the “receipt” is not a simple event
Every exception triggers manual work. Not just in AP, but across procurement and warehouse. The slow part is rarely the actual correction. The slow part is finding the information, confirming it, and agreeing on who changes what.
Many companies underestimate how much exception handling consumes capacity because it hides in emails, calls, and ad hoc meetings. It also fragments accountability. AP sees blocked invoices. Procurement sees supplier complaints. Warehouse sees “finance problems.” Nobody sees the full queue.
Quiet slowdown point 5, missing document links create a search economy
A delivery note is scanned. An invoice PDF is stored. A goods receipt is posted. The documents exist. The problem is that they are not reliably connected to the relevant transactions.
So people search.
They search shared drives, Outlook folders, ERP attachments, DMS systems, supplier portals, and sometimes WhatsApp photos from the dock. In some organizations, the tribal knowledge is the system. “Ask Martina, she knows where those certificates are stored.”
This search economy has real costs:
- Payment approvals are delayed because approvers lack context
- Disputes drag on because nobody can quickly show the documentary chain
- Audits take longer because retrieval is manual, especially for quality related records
- Knowledge becomes person dependent, which is risky for smaller organizations
It is also one of the reasons automation efforts fail when they focus only on the invoice. You can extract invoice data perfectly and still block payment because the delivery note and GR evidence are not accessible where the decision happens.
Why suppliers accept it, because it rarely breaks production
If a process flaw stops a line, it gets fixed quickly. If it delays payment by two weeks, it becomes background noise.
That’s why these slowdowns persist. They sit in the gap between departments. Each department can justify its local optimization:
- Warehouse prioritizes throughput and physical flow
- Quality prioritizes risk reduction and traceability
- Procurement prioritizes supply continuity and price correctness
- Finance prioritizes controls, compliance, and closing the books
The system problem is the handover, and handovers are where documents matter.
Another reason is legacy habit. Many German suppliers grew with a mix of plants, acquisitions, and ERP add ons. Document handling evolved with each site. The result is not one process but several. A shared services team might support three plants, each with different rules for posting GR, handling delivery notes, and approving invoice blocks.
It’s hard to standardize because it feels like bureaucracy, until you measure the cost of not standardizing.
The operational costs that don’t show up in a P and L line
When cash flow slows between delivery note and payment, the first visible symptom is blocked invoices. The second is the time spent resolving them.
Operationally, you see:
- Overloaded AP and procurement teams doing manual exception handling
- Delayed goods receipt postings during peak periods, then backlog cleanup
- Increased supplier inquiries and statement reconciliations
- Higher effort at month end to clear GR/IR and explain aged items
- More credit notes and re invoices because disputes are handled late
In smaller suppliers, these tasks hit the same people who should be improving processes, negotiating supply, or supporting the plant. Instead, they become trackers of missing paperwork.
There is also a subtle impact on supplier behavior. When suppliers expect payment delays, they adapt. They send more reminders, they reduce flexibility, and in some cases they harden terms. Nobody needs a strategic supplier relationship damaged by avoidable administrative friction.
The financial costs, mostly working capital and predictability
Cash flow slowdown is not only about paying late. It is about predictability and control.
When goods receipts and invoices are not matched promptly:
- GR/IR becomes noisy, and it becomes harder to distinguish true issues from timing issues
- Accruals and cutoff become more judgment based at month end
- Forecasting becomes less reliable because liabilities are not clearly recognized
- Early payment discounts become harder to capture because approvals happen too late
- Audit work increases, because evidence is scattered and retrieval is manual
For CFOs and heads of finance, the frustration is that these are not “finance problems.” They are process problems that show up in finance metrics.
A practical way to see the bottleneck, follow one part number
If you want to diagnose where your cash flow slows down, don’t start with the invoice count. Start with one representative part number and follow the chain:
- What information arrives with the delivery, and in what format?
- When is the GR posted, and by whom?
- What happens if quality blocks the material, and where is that recorded?
- When the invoice arrives, what percentage match straight through without intervention?
- For exceptions, what is the average resolution cycle time, and what are the top three causes?
- Where do people go to find delivery notes, certificates, and proof of receipt?
This exercise often reveals that the bottleneck is not a single step, but the gaps between systems and roles.
It also reveals something uncomfortable. A lot of the effort is not value adding. It is administrative rework caused by missing or late information.
Process improvements that don’t require a big ERP project
Most suppliers don’t need a new ERP to improve this. They need tighter process design and clearer ownership.
Here are improvements that repeatedly make a difference in practice.
Standardize what “receipt complete” means
Define a minimum data set that must be captured at goods receipt to avoid downstream ambiguity. Depending on your materials, that may include:
- PO number and line reference
- Delivery note number
- Quantity and unit of measure, with clear conversion rules
- Batch or serial info where required
- Link to certificates or quality records when applicable
If the delivery note does not contain the PO reference, decide upfront what happens. Do you reject at gate, create a temporary receipt, or assign to a receiving clerk for clarification? If the answer is “we’ll figure it out later,” later is when cash flow slows.
Separate quality hold from financial posting rules
If quality needs to block stock, make sure the system supports that without freezing the financial chain unnecessarily.
A common approach is:
- Post GR promptly to recognize receipt
- Use stock status and inspection lots to manage quality holds
- Block invoice payment only when there is a defined dispute reason, not by default
This requires coordination between quality, warehouse, and finance. But it reduces the reflex of “hold everything until we are 100 percent sure.”
Reduce exception volume by fixing repeatable master data issues
Many three way match exceptions are repeatable and preventable:
- Tolerances not aligned with real world variance
- Unit of measure mismatches
- Price conditions not maintained consistently
- Missing info for packaging and freight lines
This is not glamorous work. It is the kind of work that reduces invoice blocks without changing headcount.
A useful practice is to classify invoice blocks by root cause, not by whoever is currently holding the ticket. “Price variance due to outdated condition” is a root cause. “Blocked in AP” is not.
Make the queue visible, across departments
Exception handling slows down when it lives in emails. A shared queue with clear statuses makes a difference, even if it is simple.
At minimum, you want clarity on:
- What is blocked, and why
- Who owns the next step, procurement, warehouse, quality, or AP
- How long the item has been waiting
- What document or data is missing
Some suppliers do this inside SAP workflow or a ticketing system. Others use ERP task lists. The tool matters less than the discipline of having one place where work is tracked.
Measure the right KPIs, not just invoice volume
Invoice volume is a workload metric. It doesn’t tell you where cash flow slows.
KPIs that tend to expose the quiet bottlenecks include:
- Time from physical receipt to GR posting
- Percentage of invoices that match straight through
- Blocked invoice aging by reason code
- GR/IR aging profile, not just the total balance
- Average exception resolution cycle time
- Missing document rate (delivery note, certificate, proof of receipt)
If you can’t measure these today, that is already a signal. It usually means the process is managed by effort, not by outcomes.
Where automation fits, after the process is defined
Once the process is clear, automation becomes practical. Not “automate everything,” but remove the manual steps that exist only because documents are unstructured and scattered.
This is where manufacturing document automation has matured in the last few years. Modern systems can:
- Capture delivery notes and link them to POs and goods receipts
- Extract key fields consistently, even when supplier formats vary
- Route exceptions to the right owner with the right context
- Keep a complete documentary chain attached to the transaction for audit and supplier queries
This matters because delivery notes, certificates, and invoices arrive in dozens of formats. Automotive supply chains are messy by nature. The goal is not perfection. The goal is to reduce the time humans spend retyping, searching, and reconciling.
If you want to see what this looks like in practice, OtoLab’s work on document intelligence for manufacturing teams is one example of the direction the market has taken, especially for suppliers who need to connect delivery notes, goods receipts, and invoice workflows without rebuilding their ERP.
Platforms in this category, including OtoDocs, are typically used to standardize document intake, extract relevant fields, and support workflow routing and ERP posting support. The key is to treat it as a control improvement, not an IT experiment. Clear process ownership, clear exception rules, and a small number of measurable KPIs still do most of the heavy lifting.
The companies that get this right don’t necessarily pay faster. They pay more predictably. They clear exceptions earlier, keep GR/IR under control, and reduce the background noise that turns routine procurement into constant follow up. That is usually where cash flow stops slowing down quietly, because the slow points are no longer invisible.
Hashtags