OFFLOAD
Book a call

Fieldstone Home

Turning thousands of 3PL charges into a focused review queue

Keel checks each charge against what shipped and what the contract allowed, then gives finance the evidence needed to review and recover genuine discrepancies.

The story in 30 seconds

Before
A monthly 3PL invoice could contain thousands of charges, each dependent on a different operational fact. Verifying them meant comparing the invoice with Shopify fulfilment data and the contract line by line, so most invoices could only be spot-checked.
What changed
A reconciliation platform that applies the contracted rules to every charge, clears the lines that agree and places the remaining discrepancies into a focused review queue with their supporting evidence attached.
After
Finance could start with the small set of charges needing attention instead of a spreadsheet containing every charge. Approved discrepancies could move into a documented dispute, and recoveries could be tracked through to credits actually received.
Client
Fieldstone Home
Product
Keel fulfilment reconciliation
3PL
ShipBob monthly invoice
Commerce
Shopify orders and fulfilments
Screens
Demonstration data, not client results
Demonstration dashboard showing a monthly 3PL invoice moving from reconciliation through review, dispute and credit tracking.

Before: finance could only inspect a fraction of the invoice

A 3PL invoice can contain thousands of lines for picking, packing, shipping, returns and surcharges. Each line has to be checked differently: a pick fee depends on units shipped, a return charge depends on whether the return was received, and shipping depends on zone, weight and service level.

Checking a charge properly meant holding three records together: what the 3PL billed, what happened in Shopify and what the contract allowed on that date. Doing that manually for every line was not realistic, so incorrect charges could pass unnoticed alongside correct ones.

The goal was simple: check every line without asking finance to investigate every line.

The screens below use demonstration data to show how the workflow operates. Their figures are not presented as measured client results.

Every charge checked in the same workflow

Keel turned the agreed rate card into dated rules, connected each invoice line to the relevant Shopify fulfilment and calculated what the charge should have been. Differences within an agreed tolerance cleared automatically; the rest moved forward for classification.

This gave the reviewer one place to see the invoice line, the operational event and the contract rule together.

The new workflow

  1. Import the invoice
  2. Match the fulfilment
  3. Apply the contracted rule
  4. Clear or flag
  5. Review the evidence
Demonstration review screen showing the 3PL charge, the corresponding Shopify fulfilment and the contract rule used to calculate the expected amount.
The billed charge, operational record and contract rule are reviewed together instead of assembled by hand.
The hard part

Separating genuine overcharges from missing information

A difference between billed and expected amounts did not automatically become a dispute. It could represent an incorrect rate, a duplicate charge, an operational event that never occurred—or simply a gap in the contract or source data.

Keel classified the reason before asking somebody to act. A confident discrepancy could move to review, while missing rules and unmatched records stayed with the team for clarification rather than being presented as money owed.

Finance saw which differences were ready to review and which ones first needed better information.

From an approved finding to a documented recovery

Approved discrepancies were grouped into a dispute package with the relevant invoice lines and supporting evidence attached. The package could be exported as a spreadsheet with a ready-to-send explanation for the 3PL.

Keel kept potential, approved, disputed and credited amounts separate. Finance recorded a recovery only when the credit actually arrived, so the platform’s reporting reflected completed outcomes rather than every amount it had flagged.

Demonstration dispute package showing the approved charge lines, their evidence and separate fields for the amount disputed, accepted and credited.
Disputed, accepted and credited remain separate so finance can see exactly where each recovery stands.

After: a short queue replaced a full-invoice investigation

The delivered workflow checked every invoice line while keeping a person in control of each dispute. Routine charges could clear without attention, and reviewers received a focused queue containing the evidence needed to make a decision.

Once approved, those decisions moved into consistent dispute packages and remained visible until finance recorded the final credit.

Before
Spot-check a large invoice and investigate discrepancies across separate records.
After
Review a focused queue, approve supported findings and track the resulting credits.

Finance no longer had to search for the problem before it could decide what to do about it.


Next case study

Enterprise fintechComplex RFPs without the copy-and-paste workflowAll case studies

Talk through your workflow

Have a process like this? Bring us one example.

We’ll help you see where the time goes, what should stay human, and whether automation is worth it. No deck, no preparation, no obligation.

Usually starts as one of these

  • Exceptions and manual review
  • Handoffs between teams
  • Reporting and reconciliation
Bring us a process

What happens on the call

  1. 01You walk us through one process, start to end, in whatever detail you have.
  2. 02We map where the time actually goes, and which parts a machine could take.
  3. 03You get a straight answer. Sometimes that answer is that it is not worth doing.

Thirty minutes. Nothing to prepare.