Freight and 3PL Controls in Epicor Kinetic

Executive Summary

Epicor Kinetic enforces freight cost inside the purchase order and receipt workflow. It matches an invoice's freight and miscellaneous charge lines against a PO, applies configurable tolerance thresholds before an invoice can post, and allocates landed cost across received items on import shipments. That is a real control.

It stops the invoices that are wrong in the way the PO already anticipated: a freight charge that exceeds what the PO named, or a receipt that never happened.

What it does not do is read a carrier's rate schedule or a 3PL's service agreement. Kinetic has no field that stores a fuel surcharge index, a minimum weight break, or a detention accessorial's trigger condition, so it cannot test an invoice line against any of them. Two invoices for the same freight lane can both pass Kinetic's match and still be billed at different effective rates, because Kinetic never compared them to each other or to the underlying contract.

The gap is structural, not a configuration miss. It sits between the PO's dollar amount and the carrier tariff that produced it. Closing it needs a rate table and a surcharge calendar checked against every invoice line the ERP already approved, maintained outside Kinetic and reconciled back into it.

1. What freight and 3PL invoice controls does Epicor Kinetic enforce?

Epicor Kinetic enforces PO-based matching on freight: an invoice's freight or miscellaneous charge line is checked against the amount and receipt state recorded on the purchase order, within a configurable dollar or percentage tolerance. On import shipments, its landed cost function allocates freight, duty, and handling charges across received line items so unit cost reflects total delivered cost. Both are receipt-driven controls.

Neither reads a carrier tariff, a fuel surcharge table, or a 3PL service agreement, because Kinetic was not.

Kinetic's AP module runs a three-way match: purchase order, receipt, and invoice. When a freight or miscellaneous charge is added to a PO line, either as a flat amount or a percentage of the item cost, the invoice entry screen checks the billed freight amount against that PO value. If the variance exceeds the tolerance a controller configured, the invoice holds for review rather than posting automatically.

Landed cost works differently. It is designed for inbound international freight, where duty, brokerage, and inland freight need to be spread across the items they belong to so inventory valuation is accurate. It allocates cost; it does not validate that the freight rate charged was the contracted rate.

Both controls answer the same question: does this invoice match what was authorized in the PO? Neither answers a second question a contract-compliance review asks: was the amount authorized in the PO correct in the first place, given the carrier agreement that should have priced it?

2. How does Kinetic's three-way match actually treat a freight charge line?

Kinetic's three-way match treats a freight charge the same way it treats any miscellaneous PO charge: it compares the invoice amount to the PO amount and the receipt status, inside a tolerance a controller sets once and applies uniformly. It does not distinguish a freight accessorial from a restocking fee or a tooling charge. The match is a comparison of two numbers already inside Kinetic, not a comparison of the invoice to an external carrier rate or contract term.

This matters because the PO's freight amount is usually an estimate entered at order time, not a rate pulled from a carrier's tariff. If that estimate was wrong when the PO was cut, the match will pass an invoice that is wrong in exactly the same way, because the invoice agrees with the PO.

A tolerance band compounds this. A control set to accept a 5% variance will pass a fuel surcharge miscalculated by 4%, every time, on every invoice, because tolerance thresholds apply uniformly rather than checking whether a specific charge type was computed correctly.

The three-way match is still worth having. It catches a freight charge invoiced with no corresponding PO, a duplicate invoice number, and a receipt that was never logged. It was never built to catch a surcharge computed against the wrong fuel index or a rate applied past its expiration date, because nothing in the PO carries that reference data for the match to check against.

3. What does Kinetic check on accessorial and surcharge lines?

Kinetic checks that an accessorial or surcharge line has a PO or GL account to post against and that its amount falls inside tolerance. It does not check the accessorial itself: whether a detention charge's free time was actually exceeded, whether a fuel surcharge used the correct index for the invoice date, or whether a residential delivery fee applied to a commercial dock. Those checks require the carrier's own accessorial schedule, which is not a field anywhere in Kinetic.

An accessorial charge audit exists as a distinct discipline precisely because these charges are computed off a document the ERP never sees: the carrier's published or negotiated accessorial schedule. Kinetic has no table for detention free-time windows, liftgate fee schedules, or residential surcharge zones.

When an AP clerk keys a freight invoice with a detention line, Kinetic checks that a GL account or PO line exists to receive that cost and that the amount fits tolerance. It has no mechanism to ask whether the detention was actually earned, because that answer lives in a delivery appointment log and a carrier contract, neither of which Kinetic ingests.

The result is that accessorial charges post at whatever rate the carrier billed, unless a person manually checks each one against the underlying agreement. Kinetic's tolerance setting will catch a wildly wrong number. It will not catch a surcharge that is wrong by a smaller, still material, margin.

4. Can Kinetic detect duplicate freight billing across multiple carriers?

Kinetic checks for duplicate invoices within its own AP ledger, by vendor and invoice number, and that check works well for a single carrier billing twice. It has no mechanism to detect the same shipment billed by two different carriers, or by a carrier and the 3PL managing that carrier, because Kinetic has no shipment-level identifier that links invoices across vendor records.

Duplicate freight billing and the multi-carrier consolidation problem is a distinct failure mode from a straightforward double-keyed invoice. It happens when a 3PL invoices a management fee that already includes a line-haul charge the underlying carrier also bills directly, or when a shipment is rebilled after a rate correction without the original invoice being voided.

Kinetic's duplicate check operates on vendor ID and invoice number. Two different vendor records, a 3PL and the carrier it manages, will never trigger it, no matter how identical the underlying shipment is.

Catching this requires matching on shipment-level identifiers, a bill of lading number, a PRO number, a pickup date and weight, none of which Kinetic stores as a searchable key across vendors. That match has to run outside the ERP, against freight documents Kinetic never ingests in the first place.

5. Does Kinetic enforce rate card terms or minimum volume commitments on freight invoices?

Kinetic has no rate card table for freight. It stores a PO price, which a buyer or planner entered, but it does not store the carrier's negotiated rate schedule, a minimum volume commitment, or the trigger point where a volume tier should have applied. An invoice that bills the un-discounted rate because a volume threshold was missed will pass Kinetic's match cleanly, because Kinetic has no reference rate to compare it to.

Rate card enforcement in Kinetic, to the extent it exists, happens through the PO price field. A buyer negotiates a rate, keys it into the PO, and every invoice against that PO is compared to that single number. If the underlying agreement has tiered pricing that steps down past a volume threshold, or a rebate that should apply after a quarterly minimum, nothing in Kinetic tracks the running total against that threshold.

The practical failure looks like this: freight volume crosses a contracted tier mid-quarter, the carrier keeps billing the prior tier's rate, and every invoice matches its PO because the PO was never updated to the new rate. Kinetic's control performed exactly as designed. The rate it was checking against was stale.

This is the same failure that shows up on the labor side, where an off-contract resources problem happens for the identical reason: the system enforces whatever price was keyed, not the price the contract actually specifies for current volume.

6. Why does freight cost pressure make this control gap more expensive now?

Truck transportation of freight rose 10.9% year over year through July 2026, per the US Bureau of Labor Statistics Producer Price Index for series WPU3012, read September 6, 2026. Long-distance truckload freight rose 8.1% over the same period, per BLS series PCU484121484121, also read September 6, 2026. As base rates move, a stale surcharge reference or an unenforced volume tier compounds against a larger invoice, not a smaller one.

Fuel surcharge schedules are usually indexed to a published diesel or gasoline benchmark and recalculated on a set cadence. Gasoline prices, per BLS series WPU0571, read September 6, 2026, rose 37.1% year over year through July 2026. A surcharge formula that references last quarter's index instead of the current one produces a growing dollar error as the underlying commodity price moves, even if the formula itself was never changed.

Kinetic has no mechanism to recompute a surcharge against a current index value, because it does not store the index or the formula. It posts whatever the carrier billed, checked only against the PO's flat freight estimate.

This does not mean freight rates are being manipulated. Rising input costs are a legitimate reason for a carrier to raise rates, and distinguishing that from margin drift matters: see margin drift vs. a legitimate price increase for how to tell the two apart. The point here is narrower.

Whatever the true cause of a rate change, Kinetic's control was never built to verify it, so the verification has to happen somewhere else.

7. Should a Kinetic manufacturer buy freight audit software or run a diagnostic first?

A manufacturer running Kinetic should find out what is actually leaking before buying a tool to prevent it, because a forward control configured against the wrong rate table enforces the wrong rate table. A one-time diagnostic reviews historical freight invoices against actual carrier agreements, names which drift types are present in that specific freight book, and produces the rate reference data a forward control would need to be worth configuring.

This is not a case for or against any specific product. It is a sequencing question, and it is answered the same way whether the ERP is Kinetic, an ERP like Infor CloudSuite SyteLine, or a shop-floor system like Plex: buy the diagnostic before the software, when the current gap between contract and invoice has not yet been measured.

The reasoning holds regardless of ERP. Software that checks an invoice against a rate table is only as good as the rate table it was configured with. If nobody has yet gone through the actual carrier agreements, accessorial schedules, and volume tiers and reconciled them against a sample of paid invoices, the software gets configured against a guess.

A diagnostic also separates what a Kinetic environment can fix internally from what needs an external control. Some of what surfaces is recoverable through credit memos on invoices already paid; some is preventable only by adding a check Kinetic does not run today. That split, covered in recoverable vs. preventable leakage, decides where the ROI of any next step actually comes from.

For the wider pattern this sits inside, start with the margin drift guide.

8. Frequently Asked Questions (People Also Ask)

Does Epicor Kinetic have a built-in freight rate audit feature?

No. Kinetic matches invoices to purchase orders and applies landed cost allocation on inbound shipments. It has no table for carrier rate schedules, fuel surcharge indexes, or accessorial charge definitions, so it cannot independently verify that a billed freight rate matches a contracted rate.

Can Kinetic catch a fuel surcharge calculated against the wrong index?

No. Kinetic does not store a fuel index or a surcharge formula. It checks the invoiced freight amount against the PO amount and tolerance, so a surcharge miscalculated within that tolerance band posts without being flagged.

Will Kinetic's three-way match catch duplicate freight invoices from different carriers?

It will catch a duplicate invoice number from the same vendor. It has no shipment-level identifier that links invoices across different vendor records, so the same shipment billed by two carriers, or by a 3PL and the carrier it manages, will not be flagged.

Does Kinetic track volume-based freight rebates or tiered pricing?

Kinetic tracks a PO price, entered manually, not a tiered rate schedule. If a contract specifies a lower rate past a volume threshold, nothing in Kinetic monitors cumulative volume against that threshold or flags when the rate should change.

What is landed cost in Epicor Kinetic and does it validate freight rates?

Landed cost is a Kinetic function that allocates freight, duty, and handling charges on inbound shipments across the received items, for inventory valuation purposes. It distributes a cost that was already billed. It does not check whether that cost was billed at the correct contracted rate.

Should I turn on tighter tolerance settings in Kinetic to catch freight drift?

Tighter tolerance thresholds catch larger errors sooner, but the tolerance is compared to the PO amount, not to a carrier rate table. If the PO amount itself is wrong or stale, a tighter tolerance still passes an invoice that matches a wrong number precisely.

Does this gap apply to other ERPs, or is it specific to Epicor Kinetic?

The gap is structural to PO-based ERPs generally, not specific to Kinetic. Any system that matches invoices to purchase orders rather than to carrier rate schedules has the same limitation, including QuickBooks Enterprise; see freight and 3PL controls in that environment for the comparison.

What data would a freight rate control need that Kinetic does not store?

It needs the carrier's negotiated rate schedule, the accessorial charge definitions and their trigger conditions, the fuel surcharge formula and index, and any volume tier thresholds, none of which are fields in Kinetic. That reference data has to be maintained and checked against invoices outside the ERP.

Is a freight audit finding always recoverable through a credit memo?

Not always. Some overbilling is recoverable retroactively through a credit memo once identified. Other drift, like a rate table that stays stale going forward, is only stopped by adding a forward control, which is a different fix with a different payback path.