A familiar scene in many plants: production is waiting on a material release that, according to the ERP, “should already be cleared.” Purchasing insists the supplier sent the confirmation. Quality says the certificate is “somewhere in the mailbox.” Engineering points to a newer drawing revision. Someone opens an Excel file named Lieferstatus_final_final_v3.xlsx, filters for the part number, then forwards a PDF from last week’s email chain as “proof.”
The ERP is running. But the process is not.
For German Tier-1, Tier-2, and Tier-3 automotive suppliers in the 20–500 employee range, this isn’t a sign of incompetence or lack of discipline. It’s the standard operating reality: critical decisions depend on unstructured documents and human routing—email, Excel, PDFs—and only later (sometimes much later) does the ERP get updated to reflect what actually happened.
The uncomfortable point is that this “shadow workflow” doesn’t just create admin work. It stretches lead times in ways that are hard to see until a delivery is at risk.
The ERP is the system of record—email is the system of work
Most mid-sized suppliers can describe their core process flows in SAP, Microsoft Dynamics, proALPHA, abas, APplus—or a combination after acquisitions and plant expansions. Purchase Orders exist. Goods Receipts can be booked. Engineering changes have a formal route. Quality records are defined. In theory, the ERP workflow is the backbone.
In practice, the backbone is often a set of workarounds that grew over time:
- RFQs arrive via email with a mix of PDFs, drawings, and customer portal exports.
- Supplier confirmations come as PDF attachments or semi-structured emails.
- Delivery notes are scanned at goods receipt, then manually keyed because the part number is missing or formatted differently.
- Certificates of Conformity and EN 10204 material certificates arrive as PDFs, sometimes days after the truck.
- PPAP documents are collected across shared folders and email threads, then referenced by file name rather than controlled metadata.
- Engineering drawings circulate as attachments because “the supplier can’t access our portal” or “it’s faster this way.”
These are not edge cases. They are routine, and they form an operational layer around the ERP that the ERP cannot “see.”
That’s where lead time quietly expands: not in machining minutes or cycle time, but in clarification loops, waiting states, and manual exception handling.
Where lead time really gets lost: the micro-delays between departments
When managers talk about lead time, they tend to think in material lead time, supplier lead time, and internal production lead time. The hidden category is document lead time: the time it takes for information to move from the moment it exists to the moment it becomes usable across purchasing, planning, quality, and finance.
In mid-sized automotive suppliers, these micro-delays often show up in predictable places.
RFQ turnaround that depends on “who saw the email”
RFQ processing is a good example because it combines commercial urgency with technical detail.
A typical RFQ package includes:
- Part list (often Excel or portal export)
- Drawing PDFs, sometimes multiple revisions
- Material requirements (e.g., EN 10204 3.1)
- Quality expectations (PPAP level, IMDS, special characteristics)
- Target price and timing assumptions
Even if an ERP has a quoting module, the RFQ rarely arrives in a way that can be cleanly ingested. So teams build an intake routine:
- A shared mailbox receives RFQs.
- A coordinator downloads attachments.
- Drawings go to engineering, timing to production planning, material to purchasing, quality requirements to the QM lead.
- Consolidation happens in an Excel sheet and then gets re-entered somewhere else.
The lead time impact is not the calculation itself—it’s the waiting. An RFQ sits in an inbox for half a day. A drawing revision question triggers a new email thread. A missing tolerance note leads to a customer clarification, and the updated file gets saved in a folder that not everyone uses.
RFQ turnaround becomes sensitive to individual availability. That’s not a “soft” problem. It directly affects hit rate, capacity planning, and how much time is left for industrialization when the nomination finally arrives.
Purchase Orders that are “in ERP” but confirmed in PDFs
Many suppliers can generate POs correctly. The issue starts with acknowledgements and changes:
- Supplier sends an order confirmation PDF with a delivery date that differs from the ERP schedule line.
- Partial deliveries are described in email text but not structured.
- A substitution (different batch, different alloy, different coating) is discussed informally to “keep the line running.”
Someone in purchasing updates the ERP—when they get to it. Until then, planning works on outdated dates. Expedite calls start. Production builds buffers. Lead time increases because the plan no longer reflects reality, and the corrective actions are delayed by document handling.
Goods Receipt blocked by missing or mismatched documents
At goods receipt, the “document gap” becomes physical. A truck arrives; the material is here. But release depends on matching:
- Delivery Note vs PO (quantity, part number, revision)
- Required certificates (CoC, EN 10204, special test reports)
- Sometimes serial number or batch traceability requirements
- Customer-specific labelling compliance
If the delivery note is a PDF with free-text positions, or the certificate references a heat number differently than the PO, someone has to interpret and reconcile it.
When the process is email-driven, the material can sit in quarantine—not because of a real quality problem, but because the paperwork hasn’t been connected to the ERP transaction. This is lead time in its most frustrating form: inventory on-site, but not usable.
Engineering changes that travel faster than the control process
Engineering Change Requests (ECR) and drawing revisions are another hotspot. In automotive supply, the change itself may be clear. The difficult part is ensuring that everyone is acting on the same revision across:
- Production
- Tooling
- Purchasing and suppliers
- Quality planning (control plan, PFMEA updates)
- Customer communication (PPAP resubmission triggers)
When revisions move by email attachment, two things happen:
- A “latest” drawing gets forwarded without context, while the formal approval workflow lags.
- Old revisions remain in circulation because people reuse an earlier email as a reference.
This doesn’t just create rework risk; it adds waiting time as teams verify which document is valid. Verification becomes a manual activity—another hidden lead time component.
Why this becomes “normal” in German mid-sized suppliers
It’s easy to say “just use the ERP properly.” That advice usually ignores the actual constraints on the shop floor and in shared services.
Several factors keep email/Excel/PDF workflows alive:
- Supplier heterogeneity: A Tier-2 dealing with 200 suppliers will see everything from EDI-ready partners to small job shops sending scanned PDFs from a multifunction printer.
- Customer heterogeneity: OEM and Tier-1 portals impose their own formats. Your ERP doesn’t control the intake format.
- Speed bias: When a line is threatened, people choose the fastest communication path. That path is almost always email.
- Module reality: Many firms own ERP modules they never fully implemented, or they implemented them in one plant but not another.
- Workarounds become institutional knowledge: The person who “knows which folder is the right one” becomes critical infrastructure.
- Audit pressure creates parallel documentation: Quality teams often keep separate evidence trails in shared drives to satisfy customer audits, because ERP attachments are inconsistent or hard to search.
None of this is irrational. But it creates an environment where the ERP is treated as a ledger, while execution runs elsewhere.
And that has measurable consequences.
The hidden operational costs: exceptions, rework, and fragile prioritization
Lead time increases not only because tasks take longer, but because exceptions multiply.
In automotive supplier operations, exception handling is where processes go to die:
- A delivery note uses a supplier’s internal part number, not yours.
- The PO references an old drawing index.
- The certificate arrives as a separate PDF without a clear link to the delivery.
- The RFQ includes a new requirement (e.g., special cleanliness spec) but it gets buried in a PDF page 17.
- The confirmation says “lieferbar KW 32,” while the ERP expects a date.
Every exception creates:
- An email
- A phone call
- A manual correction
- A delay while someone with the right knowledge becomes available
Over time, teams build informal prioritization: whichever issue is shouting loudest gets handled first. That is not the same as prioritizing by plant impact, customer criticality, or cost.
You can see this in daily life:
- Planners maintain Excel trackers because the ERP isn’t updated quickly enough.
- Purchasing maintains a second list of “real” delivery dates.
- Quality maintains a separate list of missing certificates.
- Finance later tries to do a three-way match and discovers goods receipts were booked late or not linked cleanly to delivery documents.
Even when each function is competent, the overall system becomes brittle.
The hidden financial costs: working capital, premium freight, and month-end friction
The document layer doesn’t just affect operations. It also pulls finance into operational noise.
A few typical patterns:
- Inventory that isn’t released: Material sits in blocked stock awaiting documents. That ties up working capital and can drive avoidable expedites.
- Premium freight driven by information latency: When confirmations and shipping notices are buried in emails, issues are discovered late. Late discovery triggers expensive corrections.
- Costing and variance analysis on stale inputs: If changes and deviations are handled “off-system,” the ERP’s data quality for cost analysis suffers.
- Month-end close pain: Goods receipts booked late, missing references, and manual corrections increase reconciliation effort. Even if the ledger balances, the effort rises.
- Audit trail gaps: When the “why” behind a decision is scattered across email, shared drives, and personal folders, evidence collection becomes a project.
None of these requires a catastrophic failure to matter. They accumulate as friction—extra hours, extra buffers, extra checking, extra escalation.
A practical way to think about it: measure document lead time like you measure production lead time
Many suppliers track OEE, scrap rate, and delivery performance with discipline. Document flow often escapes the same scrutiny because it looks like admin work rather than throughput.
A useful shift is to treat key document processes as measurable workflows with KPIs. Examples that decision makers can actually track:
- RFQ intake-to-assignment time: How long until engineering, quality, and operations have the full package and ownership is clear?
- RFQ clarification rate: How often does missing or ambiguous information trigger back-and-forth?
- PO confirmation latency: Time from PO release to confirmed delivery date entered in ERP.
- Goods receipt cycle time: Truck arrival to GR posting to release (including quality gate time where relevant).
- Certificate availability at GR: Percentage of deliveries where CoC/EN 10204 certificates are available at receipt, not days later.
- Engineering document revision confusion incidents: Count of cases where teams acted on an outdated revision.
- Manual touches per document: How many times does a human open, rename, forward, or re-key data from a PDF?
The point is not to create bureaucracy. The point is to identify where lead time is being added without anyone “doing anything wrong.”
Improvements that don’t require AI: standardize, structure, and tighten the handoffs
Before anyone talks about manufacturing document automation, there are straightforward improvements that consistently reduce friction—especially for suppliers operating with mixed ERPs, mixed customer requirements, and limited IT bandwidth.
1) Standardize intake and naming conventions where you actually can
Many problems start at the moment a document enters the company.
- Define a small set of required metadata for incoming RFQs (customer, program, deadline, revision index).
- Use a controlled naming convention for drawings and specifications.
- Enforce a single intake route (shared mailbox or portal) rather than personal emails.
This sounds basic. It is basic—and it works when management supports it and exceptions are handled consistently.
2) Reduce “free-text dependency” between suppliers and ERP
If suppliers send delivery notes and certificates as free-text PDFs, your internal process will remain interpretive.
Options that mid-sized suppliers use pragmatically:
- Ask for structured order confirmations (even a consistent Excel template is better than a PDF with random layouts).
- Use ASN-like data where possible, even if not full EDI.
- Align on consistent identifiers: your material number, PO number, line item, batch/heat number formatting.
This is supplier collaboration, not software. It takes effort, but it pays back in fewer blocked receipts and fewer clarification loops.
3) Tighten ERP workflow discipline at the critical junctions
You don’t need to push every email into ERP. You do need to ensure the ERP reflects the state that planning and finance rely on.
Critical junctions typically include:
- Confirmed delivery dates (schedule lines)
- Goods receipt posting and quality status
- Engineering revision status and effective date
- Supplier master data changes (bank details, address, certifications)
A common trap is implementing “workflow” as a generic concept. The reality is narrower: pick the transactions that drive lead time and make them reliable.
4) Make exception handling visible and owned
Exception handling is inevitable. The problem is when it becomes invisible.
Practical steps:
- Maintain an exception queue (not an email thread) for missing documents, mismatches, and clarifications.
- Assign ownership and target resolution times.
- Categorize exceptions (missing certificate, part number mismatch, revision mismatch, quantity discrepancy) so the root causes become visible.
This alone often reduces the “noise floor” that makes everything feel urgent.
Where intelligent document processing fits—and where it doesn’t
Once the process is defined and the handoffs are clear, the remaining bottleneck is usually the same: people are still reading documents and re-entering information because the ERP cannot interpret PDFs and emails.
This is where intelligent document processing and workflow automation can help in a practical, unromantic way:
- Extract key fields from RFQs, order confirmations, delivery notes, and certificates
- Validate identifiers (PO number, material number, batch/heat numbers) against ERP master data
- Route documents to the right queue (purchasing, quality, engineering) with context, not just attachments
- Attach the document and its extracted data back to the relevant ERP transaction (SAP, Dynamics, proALPHA, abas, APplus, DATEV environments vary, but the concept is consistent)
- Create an auditable trail of what was received, when, and how it was processed
The goal is not to “replace” the ERP. It is to reduce the manual interpretation work that currently sits between external documents and internal transactions.
One practical example of a platform in this space is OtoDocs, which focuses on document understanding and workflow around the kinds of PDFs and emails that manufacturers actually receive. The broader approach is described by the team at OtoLab’s document intelligence platform and is worth reading as a reference point—not because software is a cure-all, but because it frames the problem correctly: lead time is often lost in the document layer, not on the machine.
The real question for decision makers is simple: where is your process still depending on humans to copy, forward, rename, and interpret documents—and how often does that dependency delay a decision that affects production, delivery performance, or cash?
If the honest answer is “every day,” then the ERP isn’t the bottleneck. The workflow around it is.
Hashtags