If you are searching for Cass Information Systems alternatives and you move fewer than 1,000 loads a month, the useful answer is a question rather than another vendor name: do you actually need the payment half of freight audit and payment, or only the audit half? Cass-class providers bundle five jobs into one contract. Below enterprise volume, you usually need two or three of them, and the alternatives that fit split cleanly into four categories: full-service audit and payment competitors, audit-only services, contingency recovery firms, and flat-price reconciliation software you run yourself.
Which one fits depends on two things: your monthly volume, and whether a third party holding and disbursing your freight cash solves a problem you have. This post takes those in order.
Fair warning on our stake in this. We build flat-price reconciliation software, so we are in the fourth category. We are also not going to pretend Cass is a bad product. It is a serious one, built for a buyer with different problems from yours.
What freight audit and payment actually bundles
The category name hides how many separate jobs are in the box. Pull them apart, because the whole segmentation question depends on which ones you need.
- Document capture. Getting invoices, rate confirmations, BOLs and PODs out of EDI feeds, carrier portals, and email into a structured form you can compare.
- Audit. Reconciling each invoice against the rate agreement, recomputing fuel, checking accessorials against the shipment documents, catching duplicates.
- Payment. The provider holds your funds and disburses to carriers on your behalf, usually on a consolidated schedule.
- Allocation and GL coding. Splitting freight cost to cost centers, business units, and general ledger accounts, plus accrual reporting for month-end close.
- Reporting and analytics. Spend by lane, by carrier, by mode, with trend and benchmark views.
Jobs one and two are the audit. Job three is the payment. Jobs four and five are the finance layer that makes the bundle sticky, because once your GL depends on a provider’s coding, switching stops being a procurement decision and becomes a close-process decision.
Why the enterprise fit breaks under 1,000 loads a month
Nothing about a Cass-class provider is wrong at that volume. It is just built around problems you may not have.
The pricing is not published, so you cannot self-qualify. Cass’s freight audit and payment page discloses no pricing, no fee structure, and no pricing model. That is the category norm, not a Cass quirk: a buyer’s guide from ShipperGuide names the three models in the market and publishes no figures for any of them. The practical effect on a small shipper is that finding out whether you can afford the product requires a sales cycle, and that cycle costs you days.
Implementation assumes an integration budget. EDI 210 feeds, carrier onboarding, GL mapping, and cost center hierarchies are real work. That effort amortizes beautifully over 50,000 invoices a month. Over 600, it does not.
Payment services need scale to make sense. Consolidated carrier payment reduces AP transaction volume, which is a large win when you cut 4,000 payments a month down to one. Cutting 40 payments down to one is a smaller win, and it costs you direct visibility into carrier remittance.
The published content is aimed elsewhere. This is a soft signal but a real one. Cass’s blog is dominated by facilities, utility and telecom expense management plus freight news roundups, with no accessorial math, no fuel surcharge formulas and no dispute procedure in it. Trax’s blog operates at executive altitude, treating spend as a finance problem rather than an invoice problem. That tells you who these products are sold to: a VP of supply chain or a finance leader managing a program, not the person who has to decide today whether a liftgate charge on a dock delivery is owed.
The four categories of alternative
| Category | What you get | What you still do | Typical fit |
|---|---|---|---|
| Full-service audit and payment | All five jobs, including holding and disbursing funds | Approve exceptions, own carrier relationships | High volume, multi-entity, complex GL allocation |
| Audit-only service | Capture, audit, exception reporting, often analytics | Pay your own carriers, file or approve disputes | You want the audit but keep treasury control |
| Contingency recovery firm | A sweep of paid invoices, disputes filed, money chased | Nothing until the money lands, then you pay a cut | Historical look-back, or no internal bandwidth at all |
| Flat-price reconciliation software | Capture and audit, exceptions handed to you with evidence | File the disputes, pay your carriers, code your own GL | You have an AP person who will work a queue |
The categories are not exclusive. A common shape under 1,000 loads is software for the ongoing audit plus a one-time contingency sweep of the last 18 months of paid invoices, because those two jobs have genuinely different economics.
What the named vendors publish
You cannot judge a product from its blog, but you can judge who it is written for, and in a category this opaque that is one of the few free signals available.
- Intelligent Audit publishes the deepest vendor content in the category, concentrated on parcel carrier surcharge announcements and general rate increase analysis, with limited LTL and truckload reconciliation mechanics. If parcel is most of your spend, that focus is a signal in your favor.
- AFS Logistics publishes the most specific vendor content we found, including LTL reclassification and NMFC change coverage, though it stops at what changed rather than how to recompute and dispute it. Useful if your pain is LTL classification.
- Trax writes for the executive buyer. Read that as an indicator of who the implementation is designed around.
- Loop is case-study led, with recovery dollar figures and product posts, and publishes no audit logic or calculation methodology.
None of that tells you what any of them costs. Nobody in this category publishes that, which is the single most useful fact about the market and the reason the evaluation checklist at the end of this post exists.
The real question: do you need someone holding your money
This is the fork in the road, and most buyers never get asked it directly.
Arguments for bundled payment. One outbound payment instead of hundreds. Carrier remittance detail handled for you. Cleaner accrual reporting because the provider knows what is in flight. A single point of contact when a carrier says it was not paid. If your AP team is drowning in carrier check runs and your month-end freight accrual is a guess, this is a genuine problem being solved.
Arguments against, at your volume. Float. Your cash leaves your account before the carrier’s arrives, and the gap earns interest for somebody. Ask who, for how long, and at what rate, and ask it in writing. You also lose direct visibility into what each carrier was actually paid and when, which matters the first time a carrier claims non-payment on an invoice you disputed. And you add a switching cost: unwinding a payment provider means re-onboarding every carrier’s remit-to detail.
The middle path. Audit-only providers and reconciliation software both leave payment where it is. You get the exception detection without handing over treasury. Under 1,000 loads a month, that is usually the right unbundling, because the payment consolidation win is small and the switching cost is not.
Segmenting by volume
These bands are rules of thumb, not thresholds with a citation behind them. Your mix matters more than your count: 300 LTL loads generate far more audit surface than 300 truckload moves, because LTL carries classification, reweigh, and a much longer accessorial tail. Darrigo Consulting puts typical recovery at 1 to 3 percent of spend for truckload against 3 to 8 percent for LTL and 2 to 5 percent for parcel, which is a consultant’s benchmark rather than a measurement of your file, but the ordering matches what the documents will tell you.
Under about 200 loads a month. Honestly, no subscription and no service is likely to pay for itself on recurring fees alone. A flat monthly cost is a large share of a small recovery pool. Two things do work: a one-time contingency look-back on paid invoices, and a disciplined internal check on the three or four error types that account for most of the money. Start with duplicate freight invoice detection and a fuel surcharge recomputation from the DOE index, because those two are mechanical and need no tooling to catch. Our own FAQ says the same thing about our product at this volume, and we would rather say it here than after you subscribe.
200 to 500 loads a month. This is where flat-price software starts to beat everything else on cost, provided one condition holds: somebody in your shop will actually work the exception queue and send the disputes. Budget 10 to 20 minutes per exception for a drafted dispute you review and send. If nobody owns that job, buy a service instead, because software that produces a queue nobody works is a subscription to a to-do list.
500 to 1,000 loads a month. Both software and audit-only services are viable, and the deciding factor is usually the finance layer rather than the audit. If your controller needs freight allocated across cost centers and accrued at close, price an audit-only provider that produces that reporting against software plus your own coding work. If GL coding is simple, software wins on cost and you keep the recoveries.
Above 1,000 loads, or multi-entity. The enterprise providers start to earn their implementation cost, and bundled payment starts to make real sense. This is also where per-invoice pricing can beat a percentage of a large recovery base, which is worked out in what freight audit really costs across the three pricing models.
What actually recovers money, regardless of who you hire
The vendor question distracts from the error question. Across the exception types we see, a short list accounts for most of the recoverable dollars, and every one of them is checkable by a person with the right two documents.
| Error type | What proves it | Why it recurs |
|---|---|---|
| Fuel surcharge on the wrong index week | The published DOE weekly price and the contract’s effective-week language | A rating table set once and never re-checked |
| Duplicate invoice under a different number | Two invoices, one load, matched on origin, destination, date and weight | Rebills and re-submissions across month boundaries |
| Detention with no supporting times | The POD and the rate confirmation’s free-time terms | Facility has no gate system, so times are asserted rather than recorded |
| Accessorial not on the rate confirmation | The rate con and the BOL | Charges added at the billing stage by someone who never saw the facility |
| Invoice that does not match the rate confirmation | The rate con line by line against the invoice | Manual re-keying between the booking system and the billing system |
Notice what is not on that list: fraud. Nearly all of this is process artifact. A carrier’s rating table drifts, a billing clerk guesses at a facility, an invoice gets re-submitted after a payment query. Treating it as theft is both wrong and tactically counterproductive, because the fastest recoveries come from carriers who feel like you are helping them fix a system.
The two evidence-heavy cases are worth reading in full before you evaluate any vendor, because they define what a good audit output looks like: the documents that win a detention dispute and what to do when the rate confirmation and the carrier invoice disagree.
The evaluation checklist
Run this on any alternative, including us. It is written so that a provider who cannot answer plainly reveals itself early.
- Price, in a number, before a demo. If the answer requires a discovery call, note how many days that costs you and price the delay.
- The pricing model, named. Per invoice, percentage of recoveries, percentage of savings, percentage of spend, or flat subscription. Then ask what the percentage applies to. The difference is worked through in what a freight audit contingency fee percentage really costs.
- Implementation scope and elapsed time. What do you have to build, and who does the carrier onboarding?
- Does the provider touch your money? If yes: who holds float, for how long, and who earns interest.
- Who talks to your carriers, and in whose name. This decides who absorbs the relationship cost of a dispute.
- Recovery rate reporting, not just findings. Ask what percentage of flagged exceptions actually get collected, and require both numbers in the reporting.
- Root-cause reporting. A quarterly breakdown by carrier and charge code, so recurring errors get fixed rather than harvested.
- GL coding and accrual output. Does it match your chart of accounts, and what does month-end close look like on day one?
- Data ownership and exit. Export format, retention, deletion commitment, in the contract.
- Term, auto-renewal, and notice window. Then diary the notice date the day you sign.
- Free trial or paid pilot on your own invoices. A vendor confident in its detection will run your last 20 bills. One that will only show you a canned demo is telling you something.
Item eleven does most of the work. Every provider’s marketing claims a detection rate. The only number that matters is what it finds in your file, and any provider unwilling to prove that on real invoices before you sign has answered the question you were asking. If you want a fuller version of that evaluation, including the deadlines that bound what a historical sweep can even recover, the reference table is in every freight billing deadline that can cost you money, and the build-versus-buy version of this decision is in in-house versus outsourced freight audit break-even math.
Sources
- Cass Information Systems, Freight Audit and Payment (no published pricing, fee structure, or pricing model)
- Cass Information Systems blog (facilities, utility and telecom expense management plus freight news roundups; no accessorial math, fuel surcharge formulas, or dispute procedure)
- Trax, Freight Foresight blog (executive-altitude content rather than invoice-level procedure)
- Intelligent Audit blog (deepest vendor content in the category, concentrated on parcel surcharges and GRI analysis)
- AFS Logistics blog (most specific vendor content, including LTL reclassification and NMFC change coverage)
- Loop blog (case-study led, no published audit logic or calculation methodology)
- ShipperGuide, How to choose a freight audit provider (names the three pricing models, discloses no figures)
- Darrigo Consulting, Shipping audit and freight audit guide (recovery benchmarks of 1 to 3 percent truckload, 3 to 8 percent LTL, 2 to 5 percent parcel; consultant-authored)