3PL Rate Card vs Invoice: What Should Match and What Should You Check?

What should match between the rate card and invoice?

Not every column will have the same label, but each recurring invoice charge should resolve to a commercial pricing rule. The comparison becomes much easier when you normalize both sources to a common service code and billing basis.

The objective is traceability. You should be able to point from an invoice line to the rate-card entry that explains why the charge exists and how it should be calculated.

• Service or fee category.
• Billing basis.
• Applicable unit rate.
• Volume tier where relevant.
• Effective date.
• Minimum or threshold rule.
• Applicable surcharge condition.

Step 1: map invoice descriptions to rate-card services

Warehouses frequently use slightly different descriptions in operational systems, invoices and contracts. A rate card may say outbound order handling while the invoice says pick pack base. Those names can describe the same commercial service, but the mapping needs to be explicit.

Create one canonical service identifier for the audit. If a recurring invoice description cannot be mapped confidently, classify it as an unknown fee rather than guessing.

Step 2: compare the billed rate with the applicable rate

After the service is identified, compare the billed unit rate with the commercial rate that applied during the billing period. Check dates and tiers before calculating a variance.

A rate difference is strongest when both sides use the same billing unit. If the contract bills per order but the invoice effectively bundles multiple activities into one line, you may need additional detail from the provider before a direct rate comparison is meaningful.

Step 3: verify the quantity separately from the rate

A correct unit rate does not make the line correct if the quantity is wrong. Treat quantity as its own reconciliation test. The invoice quantity should correspond to the billing basis defined in the rate card and, where possible, to activity recorded in your own systems.

For example, if a first-pick fee is billed per order, compare it with eligible orders rather than total units shipped. If an additional-item fee is billed per extra unit, calculate the additional-item quantity according to the contract definition.

Step 4: recalculate the invoice line

For simple unit-based services, expected line amount is quantity multiplied by unit rate. Recalculate this independently. A line can contain the correct rate and quantity but still have an incorrect extended amount.

Keep arithmetic discrepancies separate from rate discrepancies. The source of the problem is different, and separating finding types makes the final query easier for both your team and the provider to understand.

Step 5: apply minimums and tiers after the basic line check

Minimums and tiers can make a correct invoice look inconsistent with a simple multiplication. First establish the raw activity charge, then calculate any contractual minimum adjustment or tier selection as a separate step.

This creates a clear audit trail: the underlying service lines reconcile first, and the commercial adjustment is then tested against the threshold rule.

What if the invoice contains a charge that is not on the rate card?

Do not automatically assign a value of zero and call it an overcharge. The fee may be governed by an amendment, separate surcharge schedule or approved one-off service. The correct finding is that the commercial basis is not present in the supplied rate card.

Record the description, billed amount, quantity and reference. Then ask for the agreement, approval or fee schedule that supports the charge.

The rate card cannot prove that the billed activity happened

A rate card tells you how a valid activity should be priced. It does not prove that the activity took place. That is why a complete reconciliation also needs operational data.

Once price logic is confirmed, match order, shipment, receiving or other activity references against your own records. A correctly priced charge can still deserve review if the underlying event cannot be found.

What the final rate-card comparison should produce

The useful output is a short exception list rather than a second copy of the invoice. Each exception should explain which rule was tested and why the line did not reconcile.

For a repeatable monthly process, preserve the service mapping and commercial rules. That means the next invoice starts with an established baseline instead of rebuilding the entire comparison from scratch.

• Invoice line or activity reference.
• Mapped rate-card service.
• Billed rate and expected rate.
• Billed quantity and expected quantity.
• Billed amount and calculated amount.
• Finding type.
• Financial difference where determinable.