Field Note / Operations

Complex billing is an operations problem, not a software problem.

Every company that struggles with complex invoicing eventually buys more software to fix it. A new ERP module, a billing add-on, a better spreadsheet. A year later they are still chasing the same line items. The reason is simple, and it is uncomfortable: the problem was never the software.

Complex billing is an operations problem because the invoice is not the first step in the process, it is the last. By the time a charge reaches the invoice, dozens of human decisions have already been made about rates, accessorials, exceptions, and approvals. Software that starts at the invoice cannot see those decisions, so it cannot fix what went wrong upstream.
Why the ERP cannot save you

The invoice is a consequence, not a cause.

An ERP or accounting system assumes the invoice is clean by the time it arrives. In real operations, especially in freight, the invoice is the consequence of a chain of judgments: which carrier got a manual rate override, which customer has a special accessorial deal, which exception is fine and which one is a problem. Those rules live in the heads of the people who have done the job for years. The software never sees them.

That is why the numbers stay bad no matter how much you spend:

20-40%
Of freight invoices contain errors, most favoring the carrier
Laneproof, Freightify
25%
Of shipping delays trace back to documentation problems, not the freight
Laneproof
5-7%
Of total transportation spend lost to freight audit and pay inefficiency
Supply Chain 247 / Capgemini

None of those are software bugs. They are operational decisions that never got captured.

The thing nobody wants to automate

The valuable part is the messy part.

Anyone can automate a clean, rules-based invoice. The money is in the exceptions: the tribal knowledge about who, when, and why. Most tools run away from that because it does not fit a tidy schema. It is the only part worth doing.

What actually fixes it

Capture the decisions, do not replace the system.

You fix complex billing by capturing the decisions, not by replacing the system that records them. Sit with the people who run it, write down the rules they carry in their heads, and turn those rules into agents that run on every load. Keep the agents inside the tools the team already uses, and keep a human on every consequential call. The invoice gets clean because the decisions upstream finally got encoded.

This is the whole idea behind Rigby. We do not sell you a new billing platform. We learn your rules, build agents that run them, and leave the money movement and the ledger exactly where they are. The carrier invoice audit and the AR inbox automation are not features, they are captured operations.

The takeaway

If buying more billing software worked, it would have worked by now.

Treat complex invoicing as what it is, an operations problem, and the fix changes from "migrate to a new system" to "capture the rules you already run." That is a far smaller, far cheaper, far faster project, and it is the one that actually moves the number.

FAQ

Frequently asked questions.

No. Keep your ERP. It is good at recording transactions. It is just not where the billing errors are created. Rigby sits on top of it and fixes the upstream decisions.

Capture the rules, fix the invoice.

Flat fee, live in days. Rigby encodes your tribal knowledge and runs it on every load.

Book a build call