ERP Consultant for Logistics

The logistics process map: inquiry to settlement

For a freight forwarder or logistics service provider, the unit of work is the job or shipment file. Written as a process map, a typical job runs like this:

Customer inquiry -> rate check with carriers and agents -> quotation -> booking -> job creation -> pickup and origin handling -> export customs -> main carriage by sea, air or road -> import customs -> delivery -> proof of delivery -> customer invoicing -> cost accrual against the job -> carrier and agent invoices matched -> agent settlement -> job closure.

Along the way, the job generates documents: house and master bills of lading or air waybills, customs declarations, delivery orders, arrival notices and commercial paperwork. Consolidations add another layer, because one master shipment carries many customers' house shipments and its costs must be split fairly between them.

The financial challenge is timing. Customers are often invoiced as soon as the shipment moves, but carrier, agent and port invoices may arrive weeks later. Without accruals, the job looks very profitable at first and loses margin later, and month-end figures are unreliable. I map every service line and its cost timing through ERP business analysis, because this is where most logistics systems succeed or fail.

Common pain points in logistics companies

Logistics providers usually describe a mix of operational and financial frustrations:

• Job profit is unknown until it is too late. Costs arrive after billing and are not accrued, so profit per job and per customer is only known months later.
• Two systems, double entry. Operations runs in a freight system, finance in an accounting package, and charges are re-keyed between them.
• Quotes built from scratch. Buy and sell rates live in spreadsheets and emails, so quotes are slow and inconsistent.
• Agent balances disputed. Statements from overseas agents do not match your records, across several currencies.
• Unbilled charges. Extra costs such as demurrage, storage or additional handling are paid but never recharged to the customer.
• Documents re-typed. Bills of lading, invoices and customs data are prepared separately from the same job information.
• No view by trade lane or customer. Management cannot see which lanes, services or customers actually make money.

These problems come from a missing link between operations and finance at job level. The fix is a design where every charge, revenue and cost, is attached to a job from the start and flows through to accounting automatically.

Recommended system modules for logistics providers

Logistics companies typically need operational freight functions and core finance. Whether these sit in one system or two is a key design decision.

General-purpose ERPs are strong on finance and multi-currency but rarely include freight documentation and consolidation logic as standard. Specialist freight systems are strong operationally but sometimes weaker on accounting depth. Many providers run a freight system for operations connected to an ERP for finance. I make that architecture decision with you as part of ERP solution design, based on your service lines and volumes.

Implementation checklist for a logistics ERP

Before configuration, I make sure these points are agreed by operations and finance together:

1. The system of record for jobs, rates, customers, agents and invoices.
2. Job numbering and structure for each service line, including consolidations.
3. The charge code list, mapped to revenue and cost accounts.
4. When revenue is recognized and when costs are accrued for each type of job.
5. How accruals are matched to actual invoices and how differences are handled.
6. Agent settlement rules, profit-share terms and currency treatment.
7. Approval for jobs with negative or low margin before invoicing.
8. Required documents and their formats for each service line.
9. Job closure rules: when a job is considered complete and locked.

During UAT I test with real job scenarios: a sea consolidation with several house shipments, an air shipment with an overseas agent, a customs-only job, and a job where the carrier invoice arrives after month end with a different amount. If those produce correct job profit and accounting entries, the routine jobs will be fine.

Integrations, data migration and choosing a platform

Logistics systems connect to many outside parties: carrier booking and tracking platforms, customs systems where local rules allow electronic filing, port and terminal systems, customer portals for shipment visibility, banks and sometimes e-invoicing platforms. I plan these with clear ownership and error handling through ERP integration design.

For migration, the critical items are open jobs with costs and revenue to date, open accruals, unsettled agent balances in each currency, customer and carrier receivables and payables, and active rate agreements. Closed jobs can usually stay in the old system for reference.

Zoho, Odoo, ERPNext and Microsoft Dynamics 365 can all handle the finance side well; none is a full freight forwarding system out of the box, which is why the operational layer needs careful thought. The fit summary on this page gives my view. If you operate your own trucks, see ERP for transportation; if you also store goods for clients, see ERP for warehousing. Importers buying goods for resale should read ERP for trading instead.