Freight and 3PL Controls in Infor SyteLine

Executive Summary

SyteLine's accounts payable module runs three-way matching between the purchase order, the receipt, and the vendor invoice, and it holds an invoice that fails tolerance for quantity or unit price. That control works well for a freight line tied to a PO number with a fixed rate. It does nothing for the freight invoice lines that carry no PO at all, which is a large share of them, and it has no concept of an accessorial charge, a fuel surcharge index, or a minimum weight break.

The mechanism that causes drift is structural, not a bug: SyteLine's matching logic compares three numbers inside its own database. A carrier's rate schedule, a 3PL's accessorial tariff, and a fuel surcharge formula all live in PDFs and spreadsheets outside SyteLine, so nothing in the ERP tests an invoice against them.

What changes it is treating SyteLine's AP module as the receiving and matching layer it is, and putting a separate, deliberate check between the carrier's contract terms and the invoice before it posts. That check has to run on the accessorial list, the fuel index, and the rate schedule, none of which SyteLine reads today.

1. What does SyteLine's AP module actually check on a freight invoice?

SyteLine's Accounts Payable module runs three-way matching: it compares the purchase order, the receipt, and the invoice on quantity and unit price, within a tolerance the company sets. If a freight invoice is tied to a PO for inbound freight at a fixed rate, and the invoice quantity and price fall inside tolerance, SyteLine matches it and releases it for payment. Outside that narrow case, the match has nothing to compare the invoice against, so it passes by default rather.

Three-way matching is a receiving control first. It was built to confirm that what was ordered arrived and that the vendor billed the price on the PO. That logic transfers cleanly to a freight line when the line is itself a PO line: a fixed per-shipment rate, a defined lane, a quantity of one.

Most freight and 3PL invoicing does not work that way. A carrier invoice often lists a base rate plus a fuel surcharge, an accessorial for liftgate or residential delivery, and sometimes a detention charge, none of which was quoted as a PO line item at the time the shipment was booked. SyteLine has no field type for a variable surcharge that changes weekly, and no table that holds a 3PL's full accessorial tariff.

So the match either fails on a technicality it cannot explain, since the surcharge line has no corresponding PO line, or passes because the AP clerk manually keys a workaround. In both cases the invoice never gets tested against the carrier's actual contract terms.

2. Where does SyteLine's freight control stop and manual review start?

SyteLine's control stops at the PO line. Anything invoiced that does not map to a PO line item, which includes most surcharges, accessorials, and minimum charges, routes to a hold queue or gets keyed in manually by an AP clerk. From that point, whether the charge is correct depends entirely on whether the clerk has the carrier's rate schedule open next to the invoice, a manual step SyteLine has no way to enforce or record.

This handoff point is where drift accumulates, because it moves the decision from a system rule to an individual's judgment call, invoice by invoice.

A held invoice in SyteLine shows a variance amount and a reason code. It does not show whether that variance is legitimate, because SyteLine does not hold the carrier's tariff to compare against. The person clearing the hold has to go find that tariff separately, if they go find it at all.

A. Fuel surcharge lines

A fuel surcharge is typically calculated as a percentage of the base rate, tied to a published index that resets on a schedule. As of July 2026, the underlying gasoline series, BLS PPI Commodity WPU0571, stood at 302.759, up 37.1% year over year (read 2026-09-06). SyteLine has no mechanism to hold that index, apply it to a base rate, and flag a surcharge line that used a stale percentage.

The invoice arrives as a single dollar amount and SyteLine has no formula to check it against.

B. Accessorial charges

Liftgate, inside delivery, residential, and detention fees are defined in a 3PL's accessorial tariff, a document SyteLine never ingests. A charge that does not match a PO line is either rejected on a technicality or approved on trust. Neither outcome tests the charge against the tariff that actually governs it.

3. Can SyteLine's tolerance settings catch a mispriced freight line?

Tolerance settings in SyteLine catch a price that drifts from the PO price by more than a set dollar or percentage threshold. They cannot catch a price that is wrong relative to the carrier's contract but happens to match a previous, equally wrong invoice, because tolerance compares the invoice to the PO or to history inside SyteLine, never to the external rate card or tariff that defines the correct number.

Tolerance is a consistency check, not a correctness check. If a lane rate was keyed incorrectly into the PO at the start of a contract, and every subsequent invoice matches that PO price exactly, SyteLine's tolerance logic sees a match every time. The invoice is wrong. SyteLine has no reason to flag it, because nothing in the tool compares the PO price itself against the signed rate card.

The same failure mode applies to a rate that was correct on day one of a contract and has since expired. A minimum volume commitment, a rate step-down at a tier, or a contracted rate increase tied to a published index all change what the invoice should say over time. SyteLine's PO price does not update itself against any of those triggers, so tolerance keeps validating an invoice against a number that stopped being correct months earlier.

4. Does SyteLine track a carrier's rate schedule or accessorial tariff?

No. SyteLine has no data structure for a carrier's rate schedule, a lane-by-lane rate card, or a 3PL's accessorial tariff. Those documents live outside the ERP, typically as a signed PDF or spreadsheet attached to a contract file.

Whatever price protection a freight contract provides has to be checked by reading that document and comparing it to the invoice by hand, or through a tool built specifically for that comparison.

This is not a configuration gap that a SyteLine administrator can close by adding a field. The AP module's data model is built around POs, receipts, and vendor invoices, and a rate schedule is none of those things: it is a table of conditional prices that depend on lane, weight break, volume tier, and date.

A general freight tracking table would need to hold every lane, every weight break, every accessorial definition, and every effective date range for every carrier a company uses, then apply that table's logic to each invoice line before it posts. SyteLine's AP workflow was not designed to do that, and extending it to try means building and maintaining a second system inside the first, a significant undertaking for an internal IT team already supporting production and inventory modules.

The practical result: the rate schedule exists, the contract that governs freight pricing is real and enforceable, and none of it touches the software that pays the invoice.

5. What does a freight PPI trend mean for a SyteLine-run freight budget?

The BLS Producer Price Index for general freight trucking, long-distance truckload, series PCU484121484121, read 195.575 in July 2026, up 8.1% year over year (read 2026-09-06). A rate that rises with an index like this is not something SyteLine's static PO price accounts for. If a contract ties rate increases to a published index, SyteLine will keep validating invoices against whatever price was typed into the PO, regardless of what the index has since done.

An index-linked rate clause is a common feature of multi-year freight contracts, because it protects the carrier from cost increases without forcing an annual renegotiation. The related PPI Commodity series for truck transportation of freight, WPU3012, read 170.984 in July 2026, up 10.9% year over year (read 2026-09-06), giving a sense of the direction input costs have moved.

Whoever manages the freight budget in a SyteLine shop needs a process, outside the ERP, that checks whether an index-linked increase was applied correctly and on the right effective date. SyteLine will not flag a rate that increased too early, too late, or by the wrong percentage, because it has no connection to the index in the first place. That check has to happen against the contract language and the published index value directly.

6. What should a SyteLine-run AP team put in place to close this gap?

A SyteLine AP team needs a control layer that sits between the carrier invoice and SyteLine's posting step, one that reads the actual rate schedule, accessorial tariff, and any index-linked clauses, and tests each invoice line against them before it reaches the three-way match. SyteLine's own tolerance and matching logic should stay in place for the PO-based lines it already handles well; the gap is everything outside that scope.

None of this requires replacing SyteLine. The ERP's receiving and matching functions are doing their job within the scope they were built for. The work is building, or buying, the layer that tests a freight invoice against the contract terms SyteLine was never designed to hold, and doing it before the invoice posts rather than after the payment has gone out.

1. Pull the actual contracts: Collect the signed rate schedules, accessorial tariffs, and any index-linked clauses for every freight and 3PL vendor, since these live outside SyteLine entirely.
2. Map non-PO freight lines: Identify which invoice lines never had a corresponding PO line item, because these are the lines SyteLine's matching logic cannot evaluate at all.
3. Test held invoices against the tariff: For invoices sitting in a variance hold, check the variance against the actual contract terms rather than clearing it on the clerk's judgment alone.
4. Decide who owns index tracking: Assign responsibility for checking index-linked rate changes against the published series and the contract's effective date language.

For the wider pattern this sits inside, start with the margin drift guide. See also diagnostic or software: what to buy first and build vs. buy: can you do contract-to-invoice matching in excel?.

7. Frequently Asked Questions (People Also Ask)

Does SyteLine do three-way matching on freight invoices?

Yes, when the freight invoice ties to a purchase order line with a fixed quantity and price. SyteLine compares the PO, the receipt, and the invoice within a set tolerance. Freight lines without a matching PO, such as many surcharges and accessorials, fall outside this check entirely.

Can SyteLine check a fuel surcharge against the correct index?

No. SyteLine has no connection to a fuel index and no formula field for calculating a surcharge percentage against a base rate. A fuel surcharge line arrives as a flat dollar amount and SyteLine has no way to test whether that amount used the correct index value for the invoice date.

Why does a freight invoice with no PO get harder to control in SyteLine?

Three-way matching needs a PO line to compare against. An invoice line with no corresponding PO, common for accessorials and surcharges, has nothing for SyteLine to match it to, so it either gets held on a technicality or approved manually without a systematic check against the carrier's contract.

Will SyteLine catch a freight rate that was wrong from the start of the contract?

No. SyteLine's tolerance logic compares the invoice to the PO price, not to the signed rate card. If the PO price itself was entered incorrectly, every invoice that matches it passes cleanly, because the comparison never reaches back to the original contract document.

Does SyteLine store a 3PL's accessorial tariff?

No. SyteLine's data model holds purchase orders, receipts, and invoices. An accessorial tariff, which defines charges like liftgate or residential delivery fees, is a separate document that lives outside the ERP and has to be checked against invoices by a person or a dedicated tool.

What is the difference between a freight PPI and a company's own freight rate?

A PPI series like BLS series PCU484121484121 measures an industry-wide price trend, read at 195.575 in July 2026, up 8.1% year over year (read 2026-09-06). A company's own contracted rate is a separate, negotiated number. The index is useful mainly when a contract explicitly ties rate changes to it.

Should we build a custom SyteLine module to track rate schedules?

That is an option, but it means building and maintaining a second system, covering every lane, weight break, and accessorial definition, inside a platform not designed to hold it. Some teams find it more practical to run that check as a separate, dedicated layer rather than extending SyteLine's core AP tables.

Does a variance hold in SyteLine mean the invoice is wrong?

Not necessarily. A hold means the invoice fell outside the tolerance set against the PO. Resolving it correctly requires comparing the variance to the actual carrier contract, something SyteLine's hold queue does not do on its own.

Can Infor CloudSuite SyteLine handle minimum weight break pricing?

SyteLine has no field type built for a weight-break rate structure, where the per-unit price changes at defined volume thresholds. A PO can hold one price at a time, so a shipment that should have priced at a lower weight-break rate has to be checked against the rate schedule outside the system.

What is a practical first step to find out how much freight drift exists in our SyteLine data?

Pull twelve months of freight and 3PL invoices, separate the lines that never matched a PO, and check a sample of those against the actual rate schedule and accessorial tariff. That sample alone usually surfaces whether the exposure is worth a full review.