
Danny Dever, senior product manager at TransmetriQ, a Railinc brand, and Steven Kilger discuss Transmetriq's new Freight Payables module in this episode of the Feed & Grain Podcast.
Dever explains how the module audits rail freight invoices against contracted rates and tariffs, flagging incorrect rate authorities, unannounced rate changes and fuel surcharge errors. The conversation covers the challenges of Rule 11 billing, where several railroads on one route bill separately for their portions of a shipment. Dever also explains why tying transportation and accounting data together in one system makes things easier for small teams.
Find out how one early customer was spending at least 50 hours a month checking invoices by hand, and learn how automation and managed services can free up staff to focus on keeping grain moving.
Steven Kilger: Hello, my name is Steven Kilger. I’m the managing editor of Feed & Grain magazine and the host of the Feed & Grain podcast. I want to thank you so much for joining me today as we dive deep into the issues affecting the feed manufacturing, grain handling, and allied industries.
Today’s episode is brought to you by The BinWhip from Pneumat Systems. The powerful dual impact BinWhip removes the toughest buildup and blockages in industrial storage silos without hazardous silo entry. Learn more today at binwhip.com.
Today my guest is Danny Dever, senior product manager at TransmetriQ, a Railinc brand. We’re talking about a task that can eat up valuable time at grain elevators and feed mills: checking rail freight invoices. Danny explains how TransmetriQ’s new Freight Payables module helps shippers catch incorrect rates, fuel surcharge discrepancies and other billing errors without reviewing every invoice by hand. We also dig into the complications of Rule 11 billing, where multiple railroads bill separately for their portions of a shipment, and how bringing transportation and accounting into one system can help small teams spend less time chasing paperwork and more time keeping that grain moving.
I hope you enjoy the interview. If you want to help out with this podcast and are listening in a podcasting app, please rate us and subscribe. If you’re listening online, sign up for the Feed & Grain newsletter Industry Watch to see when new podcasts drop and to stay up to date with news from all around the industry.
Now, onto the show.
Kilger: Hi, Danny. Thanks so much for joining me today.
Danny Dever: Hey, thanks for having me.
Kilger: It’s always nice to hear what’s going on in the transportation sector, and you guys are always such a great source for it. So we really appreciate you. Can you start, though, by telling people who may not be familiar with your work a little bit more about yourself and your role at TransmetriQ?
Dever: Yeah, happy to. I’m Danny Dever. I’m a senior product manager at TransmetriQ, a Railinc brand. On our side, we help shippers manage rail transportation services. We do that through our platform called TransmetriQ, which is a rail TMS for operators, and we also help the shippers through our managed services team that can also handle rail operations on behalf of our customers.
My job is to work closely with the shippers to understand the challenges, operational and system-wise, that they’re facing, and then after hearing those pain points, try to develop solutions that address their challenges. One of the examples is the Freight Payables solution, and that was generated through what we call our Voice of the Customer program, or VOC, where we talk to shippers that have invested in either our TMS or other TMSs, and they’re still having pain points reviewing their freight invoices manually. It could be across hundreds or thousands of different shippers every month. We spent time with them, listening to those pain points, how they validate charges, how they research the discrepancies, how they manage Rule 11 billing. We ultimately took all that feedback and created a solution called Freight Payables.
Kilger: Ah, so those surveys that people send me actually do get back to somebody, and someone listens.
Dever: We actually take that very seriously at our organization because it is what drives what we do. There’s no reason to go build something that nobody’s going to use. So we want our customers and shippers to tell us what they need.
Kilger: That’s great. Yeah, customer forward. That’s always a good place to be. What brought you to the industry, though? Did you go to college for it? Did you fall into it? How did you end up in your position? It’s always really interesting to me to see how people come to our industry.
Dever: I actually was a sports management major and worked in the minor leagues for a little while. I got into transportation back in the late ’90s through a company called C.H. Robinson, where I learned about third-party logistics, truck brokerage and intermodal. From there, I went on to work for a company called NYK Logistics, which was part of the larger NYK Line back in the day.
Then, about 15 years ago, I joined Railinc in Cary, North Carolina, as an industry relations director, because of the time I’d spent in the industry, and then learned all the different applications that Railinc has that help support the industry. I then moved into the product management role, specifically in our commercial space called TransmetriQ, where I could work with shippers and get back to where I started, trying to figure out the best ways to move product and the systems we could build out to make that happen.
Kilger: Very cool. A lot of us don’t end up where our majors are. I majored in book publishing and editing, and I’m on a podcast with you. Life works out.
Dever: Very true.
Kilger: You mentioned the Freight Payables module, which is why you’re on. You guys recently launched it, announced it. What is a Freight Payables module, for people who might not do this as their day-to-day job but are listening to this podcast? What was the problem that your customers brought to you, and what does it solve for shippers?
Dever: So, the 10,000-foot view: the Freight Payables module is a place where all the auditing can happen for the freight invoices that the shippers are getting, right? Today, a lot of folks are doing this manually. They get in these PDF bills, and they look at them. They need to make sure that the invoice matches the contracted or tariff rate that they have, not to mention that the fuel surcharge or any other accessorial charge that might show up on the invoice matches what it should, before they can bless it to be paid.
This system does all of that. We have a portion of the Payables module we call Rates and Tariffs, and that’s where a customer can go input and manage the contracted or tariff rates that they use. They can upload the information, or they can put it in manually. We can do it for them, and we basically house all the rates that they need for these invoices and shipments that they’re doing.
Once a shipment occurs, we then do what we call rating the shipment. We’ll rate that shipment using the information off the waybill and off of the contracted rates they have, and we’ll put it in a place where they’re like, “Yep, that O-D pair, the waybill, all the information matches,” and therefore the shipment’s rated and it all looks good.
So when the actual invoice comes in via an EDI message, instead of PDFs, the EDI message will come into the system, and it can match against that rated shipment and bless it to be auto-approved to be paid. That’s the 10,000-foot view of what it is and what it does. But basically, it helps the customer answer two questions: Is the bill correct? And it also gives them the status, right? Is it approved to be paid, or does it need to be reviewed, like a human-in-the-loop situation?
Obviously, the invoices can be very complex. There are line haul charges, fuel surcharges, accessorials. Is it a contract? Is it a tariff? You can also generate multiple invoices off of just one shipment, and then there’s the complexity of Rule 11, which I would think some of the grain folks might have. They’re going to be shipping from one origin to one destination across multiple railroads, but those railroads only want to invoice on the part that they move and not the whole shipment. So those invoices can come in at multiple different times. Obviously, you’ve got to know the different fuel surcharges, and the system kind of handles all that for them. It adds exceptions, creates a workflow and just brings transportation and accounting all into one place to speed up the process and hopefully take away a lot of the manual reviews that are happening.
Kilger: You mentioned Rule 11 here in your announcement. Can you tell me exactly what Rule 11 is and why it’s causing so much difficulty?
Dever: Yeah. So with Rule 11, let’s just say we have three different railroads in the shipment. It’s going to start at one origin on Class I Railroad A, and then it transfers, or interchanges, to Class I Railroad B, and then let’s say it finishes on a short line. So, in Rule 11, you’ve got to have three different rates to figure out the whole complexity of the shipment from origin to destination. Class I A will have their rate and fuel surcharge, Class I B will have their rate and fuel surcharge, and the short line will have their rate and fuel surcharge.
It gets real complex when you have to start doing A plus B plus C pricing, and then you get A plus B plus C invoicing. The invoices come in all separately, and what we’ve heard through some of our customer pain points is that with some of the other solutions out there, or even trying to do it manually, they have to wait for all three of those to come together to put it into their system to be paid.
With our system, you don’t have to do that. You can rate segment A, segment B and segment C all separately. The invoices will come in separately, and then you can pay them separately. So that kind of takes away some of the complexity.
Kilger: Yeah, I would imagine, especially with a business like a grain elevator, right, where you tend to have pretty small staffs and you also have really busy seasons. You have slow seasons, and then you have really busy seasons where you’re shipping a ton of grain, trying to get bins ready for harvest or whatever. It seems like it would get really complicated really fast trying to keep track of all those different invoices and things.
Dever: Yeah, and especially, let’s just say, with the unit trains that they do, if they did go over multiple railroads and they’re Rule 11, then you’ve got hundreds of cars on one invoice. It starts to become a math problem at that point.
Kilger: I get frustrated during our very mild busy season, so I can’t imagine sitting in a grain elevator office trying to figure all this stuff out.
One of the things you mentioned in your report, which I thought was really cool, is that your data shows you guys have detected more than 20 different types of invoice errors. Can you talk a little bit about what types of errors you guys are detecting, what’s most common, and maybe give an example of what this is actually costing a shipper?
Dever: Obviously, there’s a range of exceptions, but rate mismatching is probably the number one. Fuel surcharge discrepancies would probably be number two. Then there’s missing the rate authority altogether, or they put a rate authority on the invoice that the customer isn’t even associated with. That happens quite often. There are different variance thresholds, like the car counts being wrong. It’s really trying to catch all the things, whether they’re large or small, and trying to understand why that invoice isn’t matching the rated shipment that we did in the beginning.
But the biggest one is obviously the rate mismatching. Unfortunately, the railroads might be putting a different rate authority in the system than what the customer thinks it should be. So then you obviously have to dispute those, and that’s always, unfortunately, a pain.
But those are probably the main ones: rate mismatching, fuel surcharge discrepancies, missing the rate authority altogether, and then the car counts not matching, or the effective date. With the effective dates of the rate contract, sometimes they get them right and sometimes they get them wrong. And then, unfortunately, the railroads will sometimes change the rates without providing any kind of notification, so the customer doesn’t even know. We’re trying to hook all that into the system to make it easier for the customer.
Kilger: I think a good way to think about all that stuff is, it’s a pain to miss any of those things and have to go back and change them. But you also have to remember it’s a customer service thing. If you’re constantly getting the wrong information on invoices or paying stuff out wrong, it’s a bad look. You want to make sure that everything is going through smoothly every time, right?
Dever: Correct.
Kilger: And with the way traceability is working through the system now, you can have soybeans, high oleic soybeans, different protein content, all these different things. So audits and traceability are all becoming a lot more common, and I would think that this would make all that stuff a lot easier. Having this kind of digital system that’s there catching stuff for you seems like such a huge step up from doing it by hand. Do you have any advice for people who are still doing it by hand on where to start with this process of switching over?
Dever: You could give us a call, and we can help people through the process. But on a serious note, if you really are doing it by hand on a daily basis, with all the AI tools available out there right now, if you’re allowed to use them, you could sit down with some data and some information and really start asking AI to at least help point you in the right direction: Where would I start to make this more automated?
But there definitely are services out there like ours, either the system or even our own managed services, that could help you through that. One of the first folks we talked to was spending a minimum of 50 hours a month, over a week’s worth of somebody’s time, manually going through this every month to make sure they got their invoices correct. With our system, that just goes away. Somebody gets a whole week back to do probably more profitable things than working through this stuff on a daily basis.
Kilger: So, say someone does want to go through you guys. What would that process be like?
Dever: We have a team of business solutions managers, along with solutions engineers and my product team. We would get on a call and discuss a demo. We’re not only going to show you the things that we already have, but we want you to tell us about your pains. What are you trying to solve? Where can we help you? And then we build a plan.
If what we already have is exactly what you need, then maybe we roll into a pilot, and we can pilot that system to show you the value, right? Then once you see the value, we talk about how we move it into production, because that’s really what we’re trying to accomplish: a value-based approach to helping our customers, or anybody really in the industry.
Kilger: Fantastic. And if people want to find more information about the new module or about you guys, where should they go?
Dever: They can go to TransmetriQ.com. You can also get to us through Railinc.com, which is our parent organization.
Kilger: Danny, thanks so much for joining me today.
Dever: Thanks for having me.
Kilger: I really appreciate it.
Dever: Happy to.
Kilger: And thank you out there to everyone listening. Until next time, please stay safe.


















