As an application designer, developing software for the freight payment industry, I've noticed one very consistent thing. Duplicate payments are a fact of life. Logistics Group, a leader in freight payment started out many years ago (before readily available PCs) as a post audit only company.
We found duplicate payments manually with our memory, Definitely not a fool-proof system, and yet... We still found plenty. Now we let our sophisticated software do the work. As our software is constantly in development, we are always looking for better ways of accomplishing a set task, which brings me back to the topic :
DUPLICATE PAYMENTS
Carriers have to go by
Federal guidelines when handling money they can't identify and apply. If you've paid a bill twice, they are supposed to send you a form you can fill out and send back to them, at which point they will refund you the amount (of the freight bill) in question. Problem is, are we all really ready to trust a carrier with always following the rules???
I DON'T THINK SO.
We have a client that has four divisions, and they are all treated as separate entities according to their wishes. While our systems used to perform key searches according to client parameters, when we first took this client on, we changed this behavior within our Freight Payment application, which we customized for them. And boy am I glad we had the forethought to do so.
Turns out many carriers, including,
Con-Way, and
SAIA, (among others) were billing both divisions on some inter-departmental shipping. Our client does quite a lot of location to location shipping and also plenty of cross-region shipping.
Needless to say we were quite surprised that the carriers were doing this, and while this behavior may seem quite unethical, I just chalk it up to experience and am thankful we caught these bills.
Anyway, when considering a freight payment provider, I highly suggest you question their effectiveness of catching duplicate payments. Question like: How old is your software? Can you adapt your systems to fit my individual needs? Are you using multiple-layer duplicate protection?
Since hardly any carriers uses a very consistent numbering system for invoice numbers (length) LGI uses special SQL commands to find bills that are duplicates, even if we put in an extra number or transpose a number within the sequence, we and our client are protected. Since we are using the newest technologies, and have an in-house development team, we have an advantage over companies using outdated systems programmed a decade or more ago.
Some carriers use their terminal prefix on their freight bills, like
R&L Carriers. Some
carriers put a bunch of "0s" on the front of their invoice numbers, and some do this on the back of the number. While from a logic standpoint I understand this. They are padding their strings in anticipation of growth. Some carriers like
UPS, even start recycling their tracking numbers. All in all, it adds up to quite a challenge when developing routines that prevent duplicate payments.
Needless to say, nobody is perfect, but the more thought that goes into a certain problem, then it just stands to reason that a better solution is the eventual outcome.
I've been dealing with application development in the freight payment business, as a provider for over ten years. Today, our numbers are being processed over a hundred different ways, all to ensure that those pesky dupes stay under control.
Yet, somewhere, some carrier is laughing, knowing exactly they are doing when they bill out the shipper and a consignee on a shipment, and while this wouldn't be a duplicate payment from the same company, it's tantamount to the same thing. Especially if no one is actually looking at the freight bills before payment.
And that is why I keep looking for better ways to keep our business intelligence, "intelligent"