Why your 3PL stock report and ERP balance disagree

The client’s ERP shows 1,000 units. The 3PL sends a warehouse report showing 940. The first request is to “correct the stock”, but neither team has established whether the reports describe the same stock.

Start by aligning the populations. An ERP balance might include held or newly received stock while a WMS export contains only units available for allocation. A stock adjustment made before that distinction is settled can create a genuine ledger error while appearing to resolve the original complaint.

Name the balance before comparing it

Write a comparison definition that both parties can read. Include the inventory owner, item cross-reference, unit of measure, warehouse/location scope, included statuses and cutoff. State whether in-transit, received-but-not-put-away, picked-but-not-dispatched and customer-held units belong in the report.

A useful question is: “If these units were physically counted, which locations and statuses would we visit?” If the two teams would inspect different places, their totals are not directly comparable.

Microsoft’s external-ERP warehouse documentation explicitly discusses the inventory dimensions and processing states included in reconciliation reports. The relevant configuration must be checked in the actual installation. Microsoft Dynamics 365 — Integrating warehouse management with an external ERP.

Build a bridge instead of a balancing entry

In this illustrative example, the agreed comparison includes all client-owned stock in warehouse custody, including held stock and completed receipts awaiting put-away. The WMS report separates those states.

The example assumes these three buckets are mutually exclusive and that there is no additional reserved or picked stock outside them. The initial 60-unit difference was a reporting-scope difference. Availability is still 940, so the operation must not promise all 1,000 units for dispatch. A matching total does not release the held units or finish put-away.

In an actual report, “available” may already exclude reservations, while a held receipt can appear in both a status report and a receiving report. Define each bucket as a set of stock records before adding totals. Include reserved stock that remains in custody once, and do not add the same held receipt twice.

Now change the facts: only ten of the 20 receiving units have evidence of a completed receipt. The other ten appear only on an expected inbound record. The bridge no longer proves 1,000 units in custody. The receiving lead must investigate before either team calls the remaining difference a timing issue.

Reconstruct the events that should connect the balances

Take the agreed opening balance and apply in-scope receipts, dispatches, transfers and approved adjustments. Retain stable transaction references and the relevant stock dimensions. A difference should lead to a small set of source events, not a new spreadsheet of guessed explanations.

For an illustrative single-SKU custody bridge, 900 opening units + 150 received − 50 dispatched = 1,000 closing units. If the ERP contains only 100 of those receipts, its corresponding closing balance is 950. Trace the missing 50 to the receipt references and destination acknowledgements. That evidence distinguishes a missing update from the earlier example's reporting-scope difference, although both first appeared as unequal totals.

A transfer between bins inside the chosen warehouse changes location balances but not its total custody. A transfer across the boundary does affect the warehouse total and may require a separate in-transit population. Apply the same boundary to both sides.

Do not let equal and opposite errors cancel out. Ten extra units on one SKU and ten missing on another do not make inventory correct. Compare at the dimensions needed for picking, ownership and customer reporting.

Distinguish a late event from a wrong event

A receipt can physically occur before the reporting cutoff but be posted after it. Store both times. If a late message changes the explanation of yesterday's balance, preserve the original report version and the corrected version rather than silently replacing the old statement.

The resolution depends on what failed. A missing interface event may need a supported replay. An incorrect receiving quantity may need a controlled source correction. A physical variance may require an approved stock adjustment. Applying all three treatments indiscriminately can count the same correction more than once.

The client and 3PL should agree who can authorise a quantity adjustment and what acknowledgement is required. The integration team can repair transport of an approved event; it should not invent the quantity needed to make two reports agree.

Use a queue that preserves the unresolved difference

A spreadsheet can work for a modest daily population if snapshots, mappings and decisions are versioned. Native reconciliation reports may fit when the systems expose the needed dimensions. A shared integration queue becomes useful when repeated manual matching obscures which differences are still open.

Investigation flow: align populations → reconstruct the movement bridge → classify the difference → route it to the source owner → approve the appropriate correction → reconcile again. If the cause remains unproven, retain the difference with its age and evidence. “Explained as timing” should have a specific pending event and a date for confirmation.

Measure unresolved units and value only where a trusted valuation basis exists. Also measure repeated causes and time to obtain evidence. A smaller difference after unexplained adjustments is not a reliable improvement.

Correct the cause before the balance

A useful reconciliation explains why two comparable records differ and how the approved correction restores their relationship. It should preserve the distinction between available stock, custody, missing messages and physical variance.

Next actions

1. Agree one client, warehouse and cutoff, including status and unit definitions.
2. Rebuild a sample SKU balance from the last agreed opening position.
3. Trace each unexplained difference to a source event or controlled count.
4. Record the authorised correction and confirm it in both systems.
5. Use recurring causes to scope a daily reconciliation workflow.

Scope a reconciliation assessment around one client's mismatched statements, including their cutoff and stock definitions.