Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Freight Broker Cut Billing Errors 60 Percent With One Number
Transcript
- Lucas: So there's a freight brokerage in the Midwest — I won't name them, they're private — and they had a billing accuracy problem. About eight percent of their invoices had errors, mostly in the load ID field. Carriers would dispute them, payments would stall, and their finance team was spending hours every week chasing down mismatches. Luna: Eight percent doesn't sound catastrophic on its own, but in freight, that's a lot of disputed invoices and delayed cash flow. Lucas: Exactly. And the fix they landed on wasn't a new software system or a training program. They just changed the load ID from a 17-character alphanumeric string down to 8 characters. That's it. And within a quarter, billing errors dropped by sixty percent. Luna: Wait — just shortening an ID? That's the whole story? Lucas: That's the whole story, but the why is what's interesting. Their old load ID was something like 'LDB-2026-08-30-4471-X'. Lots of digits, dashes, and a letter prefix that basically meant nothing to the person typing it. The new one was something like 'A7-8392'. Short, numeric, and easy to verify at a glance. Luna: So it's not just about length — it's about reducing the cognitive load on whoever's entering the data. Lucas: Right. The human brain can hold about seven items in working memory, give or take. A 17-character string with dashes and mixed case forces the person to chunk it into maybe five or six pieces — and each piece is error-prone. With 8 characters, it's one or two chunks. The difference in error rate is massive. Luna: And it's not just the entry error rate. It's also the verification step — when someone checks the ID against the Bill of Lading, it's much easier to spot a typo in an 8-character string. Lucas: Precisely. And that's the part that's easy to miss. The fix didn't just reduce typos at the moment of entry. It also made it easier for the next person in the chain — the accounts payable clerk, the carrier's billing department — to catch a mistake before it becomes a dispute. So the sixty percent reduction is really a compounding effect. Luna: So the lesson isn't 'shorten your IDs.' It's 'look at where errors actually occur and what's driving them.' Lucas: Exactly. And this is where I have to pause for a second, because this show runs on listener support. If these conversations have moved your work forward in some small way, a couple of dollars a month at buy me a coffee dot com slash fexingo genuinely keeps these going. Luna: Yeah, it's how we stay ad-free and keep digging into stories like this. No pressure, but every little bit helps. Lucas: So back to the brokerage. The other thing that happened was unexpected: their invoice cycle time dropped by a day and a half. Because fewer disputes meant fewer back and forth emails, and the finance team could close the books faster. Luna: A day and a half on the billing cycle — that's huge for cash flow. For a freight brokerage, that's real money sitting in your account earlier. Lucas: And it's the kind of win that doesn't show up in a traditional ROI calculation. They didn't buy new software. They didn't hire more people. They just removed a source of friction that was costing them time and trust with carriers. Luna: And I bet the carriers noticed. Fewer disputes, faster payment — that probably made them a preferred customer for capacity. Lucas: That's the ripple effect. Their carrier relationship manager started hearing 'you guys are easy to work with' more often. That's not a metric you track, but it absolutely shows up in the bottom line over time. Luna: So what's the takeaway for a listener who isn't in freight? How do you find these kinds of changes in your own operation? Lucas: I think the first step is to look at your error logs and ask: where are the recurring mistakes? Not the one-offs, but the patterns. If you see the same field or the same step causing problems over and over, ask why. Often the answer is 'it's too complicated to get right.' Luna: And the fix might be something you'd never think of, like shortening an ID or simplifying a dropdown menu. Lucas: Exactly. The ID change was almost too obvious. It had been like that for years — nobody questioned it because it worked well enough. But once they measured the error rate and dug into the cause, the solution was right there. Luna: It's a good reminder that 'we've always done it this way' is often the most expensive sentence in business. Lucas: And it's not about being clever. It's about being systematic. They didn't guess — they looked at the data, identified the biggest source of errors, and tested a fix. That's the operator's manual approach. Luna: So what's the one thing you want listeners to remember from this story? Lucas: That sometimes the biggest wins come from the smallest changes — but only if you're paying attention to where the friction actually is. Shortening a field, rewording a form, simplifying a process — these can have outsized impact. Luna: And they're cheap to test. That's what I love about this kind of fix. You can pilot it in a week and see if it works. Lucas: Right. And in this case, the pilot was just two weeks of using the new ID format for new loads. The error rate dropped immediately, and they rolled it out to the whole system within a month. Luna: That's a quick win. And I bet the finance team was the first to notice. Lucas: They were. One of their AP clerks told the ops manager 'I can actually see the mistakes now.' That's the moment you know you've fixed something real. Luna: So it's not just about reducing errors — it's about making the system transparent enough that humans can catch what automation misses. Lucas: That's a great way to put it. And it's a lesson that applies way beyond freight. Anywhere you have manual data entry, any process with a handoff, there's probably a version of this waiting to be found. Luna: And the next time you see a long, complicated ID or a confusing form, you'll think — maybe there's a simpler version that works better. Lucas: That's the spirit. So, next time you're staring at your own error reports, ask yourself: what's the 17-character load ID in my business? The answer might be simpler than you think.