Why don't my pallet balances match the pool provider's statement?

Because the two balances are reconstructed independently. Your records capture movements at the moment they physically happen and close on your finance calendar. The pool provider records movements when they are confirmed or reported, applies its own validation rules, and closes on its own cycle. Timing differences, unconfirmed transfers and different classification of the same movement mean the two ledgers diverge even when both are internally consistent and no pallets are actually missing.

What causes pallet balance discrepancies?

Four structural causes: timing differences between when a movement is recorded by each party; independent counting authorities (you, the pool provider and each partner each keep separate books); unrecorded or mis-classified movements such as short deliveries, wrong pallet types and internal transfers; and condition or pool segmentation, where owned versus rented and usable versus damaged stock are netted together. These rarely cancel out, so small differences compound over time.

How do you reconcile pallet balances?

Reconciliation means forcing independently maintained ledgers back into alignment and explaining every remaining difference by location, partner and movement. Doing this reliably requires a single source of truth rather than several spreadsheets reconciled after the fact, continuous updating as movements happen rather than assembly at period close, and responsibility assigned per party and location so each difference has an owner rather than just a number.

Is a pallet balance difference always a loss?

No. Most differences at period close are timing artefacts, pallets in transit between two reporting clocks, or transfers awaiting counterparty confirmation. The risk is not the difference itself but the inability to explain it. A discrepancy you can attribute to a specific movement is an operational fact; a discrepancy you cannot explain, left until the trail goes cold, is what eventually gets written off as a loss.

Why Pallet Balances Do Not Match, and How to Reconcile

The Recurring Moment

It happens at every period close. Finance opens the pool provider’s statement, opens the internal balance, and the two numbers disagree. Not by a rounding error, by hundreds of pallets, or thousands.

The movements were all recorded. Dispatches were scanned. Returns were logged. Yet the balances do not match. And no one can immediately say why.

A balance is not something you read off a screen.

It is something you reconstruct, and reconstructions diverge.

A Balance Is a Reconstruction, Not a Fact

Every pallet balance is the result of the same arithmetic:

Opening balance + Inbound − Outbound ± Adjustments = Closing balance.

If two parties run that arithmetic over the same physical reality but with different inputs, different timing, or different classification rules, they arrive at different closing balances. Both are internally consistent. Both are wrong about the other.

The question is never whether a discrepancy can appear. In any network of scale, it always will. The question is whether you can explain it, by location, by partner, by movement, before it becomes a write-off.

Reason One: Timing

A dispatch is recorded the moment pallets leave. The matching return may be logged days or weeks later, by a different party, in a different system. Between those two events, the balance is mathematically correct and physically misleading.

Pool providers cut their statements on their own calendar. Your finance team closes on yours. A movement that lands on the wrong side of a cut-off date appears in one record now and the other one next period. The pallets never moved twice, the books just disagree on when.

Most “missing” pallets at month-end are not missing. They are in transit between two reporting clocks.

Reason Two: Independent Counting Authorities

In a pooled environment, at least three parties keep their own books: you, the pool provider (CHEP, EPAL), and each trading partner. None of them is obliged to match the others in real time. Each applies its own validation logic, its own acceptance rules, its own timing.

Your Records

Operational truth

Recorded at the moment of physical movement
Reflects what your team scanned and posted
Closes on your finance calendar
Knows your intent, not the counterparty’s confirmation

Pool / Partner Records

Counterparty truth

Recorded when the other side confirms or reports
Reflects their acceptance and classification
Closes on their cycle, not yours
May reject or hold a transfer you consider complete

When two authorities count the same reality separately, agreement is the exception, not the default. Reconciliation is the work of forcing them back into alignment, and without structure, that work is manual, retrospective and never finished.

Reason Three: Unrecorded and Mis-Classified Movements

Some movements never make it into the balance cleanly:

A short delivery, 95 received against 100 dispatched, recorded without the deviation that explains the gap
The wrong pallet type accepted into stock and counted against the wrong pool
An internal transfer between two of your own sites that shifts a deficit without anyone owning it
A return accepted physically but never posted against the originating partner

Each of these is small. Each is invisible in isolation. Each survives until a reconciliation cycle, or a physical count, forces it into the open.

Reason Four: Condition and Pool Segmentation

A balance of “100 pallets” is rarely one number. It is owned versus rented. Usable versus damaged. CHEP versus EPAL versus one-way. A statement that nets these together can tie at the top line while every sub-balance underneath it is wrong.

When owned and rented stock are not tracked separately, a rental liability hides inside an owned position. When damaged units are counted as usable, an availability figure overstates what the operation can actually deploy. The total looks healthy. The structure underneath is not.

The Nordic Context

Where small mismatches compound fastest

Nordic distributors run dense store networks alongside pooled pallets. Many also operate CC-wagons, wheeled roll containers owned directly by the distributor, with no pool provider to arbitrate the balance.

With CC-wagons, there is no external statement to reconcile against. The only record is the distributor’s own. A store-by-store drift of a handful of units per delivery accumulates silently across hundreds of stores until a physical count reveals a deficit that has been building for months.

The fewer external authorities check your balance, the more your own discipline becomes the only thing holding it together.

Why Small Mismatches Become Large Gaps

A few pallets out of step per movement is noise. The problem is that the noise accumulates in one direction. Timing gaps, unconfirmed transfers and silent internal shifts rarely cancel out, they compound.

It starts as a rounding-sized differenceIgnored at first because chasing it costs more than the gap appears to be worth.
It persists across cyclesThe same structural causes repeat every period, so the gap widens rather than closing.
The trail goes coldBy the time the difference is large enough to investigate, the movements that caused it are months old.
It is settled, not solvedUnable to assign the difference, parties negotiate, and the imbalance is written off rather than explained.

What “Matching” Actually Requires

Balances do not match because there is no single, continuously maintained position that every movement updates. Getting them to match requires three things that periodic spreadsheets cannot provide:

A single source of truth, one running ledger, not several reconciled after the fact
Continuous reconciliation, positions updated as movements happen, not assembled at close
Responsibility per party and location, so every difference has an owner, not just a number

Pallet balances do not match because they are reconstructed independently, on different clocks, by parties with different rules. That is structural, not accidental. The goal is not to eliminate every difference, it is to make every difference explainable while the trail is still warm.

A discrepancy you can explain is an operational fact. A discrepancy you cannot explain is a loss waiting to be booked.

Ledgeron, by Edgeon AS

From explaining differences to preventing them.

Reconciling pallet balances after the fact is investigative work, tracing cold movements across systems that were never designed to agree. A structured accounting layer changes the order of operations: every movement updates a single running position, and differences surface with an owner attached while the trail is still warm.

Ledgeron provides that layer for Nordic retail, wholesale and logistics operations. It works alongside existing tracking and ERP systems, turning recorded movements into reconciled, accountable balances.

Request a Ledgeron demo →

Why Pallet Balances Do Not Match