Contact Info
What does a logistics ERP consultant do for US forwarders, brokers and 3PLs?
I help US freight forwarders, customs brokers and third-party logistics providers decide how shipment files, buy and sell rates, cost accruals, duty advances and warehouse billing should flow into finance. I map the work from booking to settlement, separate what the freight or brokerage software owns from what the ERP owns, and then guide platform selection and implementation so every job shows real margin.
Last reviewed by Vikas Saroj
I work remotely with US logistics service providers: forwarders booking ocean and air freight, licensed customs brokers clearing entries for importers, and 3PLs running contract warehouses for several clients at once. Each of them earns a margin on a service, while large sums pass through their books for duty, carrier freight and terminal charges that belong to someone else.
That mix is what breaks generic accounting setups. A broker can advance duty on Monday and only recover it weeks later, while a 3PL may bill one client by pallet, by order line and by labor hour. I start by tracing how a real shipment and a real billing cycle move today, then decide which system should own each step.
Most US logistics firms I talk to already own good operational software. What they lack is a finance design that trusts it.
I follow a live ocean import, an air export and a domestic truckload from quote to closure, noting every charge, who pays it, who is billed and where someone types the same figure twice.
Duty, fees and carrier freight paid for importers are designed as recoverable balances, never as revenue, with aging by client so finance sees exactly how much cash is tied up in advances.
Expected carrier, drayage and terminal costs are booked against the file when it is invoiced, then matched when the vendor bill lands, so month-end gross profit does not swing on paperwork timing.
Storage, receiving, pick and pack, accessorials and minimum charges defined client by client, so billing comes from warehouse activity data rather than a spreadsheet rebuilt every month.
Overseas partners who handle the other end of your shipments get clear statements, agreed profit-share rules and a netting process, so balances can be settled without a quarterly argument.
I score ERP options and freight or warehouse software combinations against scripted US scenarios, review implementer proposals line by line and stay involved through testing and go-live.
An ERP for logistics should make these numbers available without a spreadsheet. I design the data model and reports around them from the start.
Shipments, advances and contracts
Rules both teams sign off
Cutover without losing open files
Take an ocean import handled door to door. The forwarder quotes using a carrier contract rate plus origin charges from an overseas agent, the importer accepts, and a file is opened. The advance security filing for ocean cargo is made, the container sails, and the broker prepares the entry. At arrival there are terminal charges, possibly exam fees, then drayage to a warehouse or the importer's dock. Every one of those steps produces a buy cost, and most produce a sell charge.
The trouble in many US firms is that the file lives in forwarding or brokerage software while the ledger lives in QuickBooks or a mid-market accounting package. Charges are rekeyed, invoices go out before drayage and terminal bills arrive, and gross profit per file is only visible once someone reconciles by hand.
I write these flows down service line by service line through process mapping, then agree a simple rule set: which system creates the customer invoice, which one holds vendor bills, when expected cost is accrued and what happens when the actual bill differs. The logistics ERP overview covers the general model; this page focuses on how it plays out for American operators.
A customs broker often pays duties and fees on an importer's behalf, either directly or by arranging payment through the client's own account. Forwarders do something similar with ocean freight collected from a consignee and paid on to a carrier. Treated as revenue, these amounts inflate the top line and distort margin. Treated loosely, they become unrecovered cash that no one owns.
The ERP design needs a few clear rules:
Whether duty is paid through the broker or directly by the importer depends on the arrangement and current CBP processes, so I document what your firm actually does rather than assume. Your CPA should confirm how pass-through amounts are presented in the financial statements. I then test the design with a file where duty, a fee and an exam charge all hit the same invoice.
Contract logistics in the US is billed in many small pieces. One client pays per pallet position per month, another per carton received, per order picked and per label printed, with minimum monthly charges and special project fees on top. The warehouse management system knows what happened. The ERP has to turn that activity into an accurate invoice without a coordinator assembling it in a spreadsheet.
I build a billing catalog per client during requirements gathering: the billable events, the unit of measure, the rate, any tiers or minimums and the evidence a client may ask for. Then we decide whether the WMS rates the activity and passes priced lines to the ERP, or passes raw activity for the ERP to rate. Both work; mixing the two does not.
Some 3PLs also operate warehouses inside a foreign-trade zone, where goods can be held with duty deferred until they enter US commerce. Zone inventory control and reporting are specialist territory, usually handled in dedicated software that zone operators approve. The ERP's job is to bill the zone services and keep client inventory off your own balance sheet. More on the storage side sits in ERP for warehousing.
Sales tax touches US logistics less than it touches product businesses, because many freight and transportation services are not taxable in most states. Less is not never, though. Delivery charges bundled with a taxable sale, some warehousing or fulfillment services and certain handling fees can be treated differently from one state to the next, so I list every charge code and ask your tax advisor to classify it before tax rules are configured. The classification is their call; my part is a tax setup that applies it the same way on every invoice.
Entity structure matters too. Many groups keep a brokerage company, a forwarding company and sometimes a trucking or warehouse company under common ownership, invoicing each other for shared work. Intercompany charges should be generated from the job, not posted by memory at month end.
Finally, the overseas agent network. Agents in Asia, Europe and Latin America bill you and are billed by you, often in their own currency, under profit-share arrangements agreed by email years ago. I document each arrangement, design a statement and netting routine and make sure exchange differences land in the right accounts. For a broader currency design, see multi-currency ERP.
The typical US pattern I see is specialist forwarding or brokerage software that the operations team likes, sitting next to an accounting package that finance has outgrown. Replacing the operational system is rarely the first move. More often the question is which ERP should sit behind it, how charges and invoices flow across, and whether the warehouse side needs its own WMS.
During vendor selection I give each shortlisted option the same scripted week: a consolidation with several house bills, a brokerage entry with a duty advance, a 3PL billing run with a minimum charge, a late drayage bill that differs from the accrual and an agent statement to net and settle. Vendors that handle that week on screen tell you more than any feature list.
For migration, the priorities are open files with accrued costs, unrecovered advances, open agent balances by currency and active client rate cards. I work remotely across US time zones, holding live sessions when your East and West Coast teams overlap and using recorded walkthroughs for warehouse staff on shifts. The US ERP consultant page and the US hub explain how I engage more generally.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
Usually not. Entry preparation and filing belong in brokerage software built for current CBP processes and kept up to date as they change. The ERP should receive the resulting charges, advances and invoices, hold client balances and report margin. I define that boundary clearly so neither system tries to do the other's job and nothing is typed twice.
Start with a billing catalog for each client: billable events, units, rates, tiers and minimums. Then decide whether the warehouse system prices the activity or passes raw counts for the ERP to price. Either way, the invoice should be generated from recorded activity, with a review step for exceptions, rather than rebuilt by a coordinator every month.
Often freight services are not taxable, but rules vary by state and depend on how the charge is described and whether it is bundled with a taxable sale. Warehousing and fulfillment charges can also be treated differently. I list every charge code for your tax advisor to classify, then configure the ERP to apply their decisions consistently.
Yes. Most engagements keep the operational system and change what sits behind it. I document the data each side must exchange, review the vendor's integration options and test the connection with real files during UAT. Being independent means I have no reason to push a replacement unless the current software genuinely blocks what the business needs.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.