Freight Forwarding & Logistics Services
Per-shipment job costing for forwarders and logistics service providers: recover every advance, keep buy and sell rates apart, and know the margin on each booking instead of discovering it at month end.
Who this page is for: Freight forwarders, NVOCCs, customs brokers, project-logistics providers and supply-chain service companies invoicing clients per shipment or per consignment, with overseas agents and multi-currency settlement. This page assumes the goods are never yours and the invoice is mostly somebody else's money. If your revenue is time-based rather than per shipment, read professional services instead.
How the business actually flows
Seven steps every freight forwarding & logistics services system has to chain together. Software that breaks the chain at any point just moves the spreadsheet one step downstream.
1. Quotation and booking
A client asks for a rate on a lane, the forwarder quotes a sell rate built from a buy rate plus margin, and the booking is accepted before the carrier cost is final. The gap between the two rates is the entire business, and it exists from the first minute.
2. Cost incurred with third parties
Ocean or air freight, THC, customs fees, trucking, insurance, agent handling at destination. These are paid or accrued in the forwarder's name but on the client's behalf, which is why they cannot be posted as ordinary cost of sales.
3. Documentation and milestones
House bill, master bill, packing list, certificate of origin, customs declaration where applicable. Each document is evidence for a cost or a charge, and the job is late if a milestone is missed rather than if an invoice is late.
4. Client invoicing
One invoice, several charge lines, each with its own currency and its own basis — freight, origin charges, destination charges, and the advance recovery. Consolidating these into one line destroys the only data that shows which charge makes money.
5. Agent settlement
The destination agent collects from the consignee or advances costs and bills the origin office. The two sides rarely agree on the first statement, so netting and reconciliation have to happen at job level, not at balance level.
6. Cost finalisation
Carrier invoices arrive after the client has been invoiced. The difference between accrued and actual cost is the real margin, and if the system cannot reopen a closed job, that difference never reaches the job that caused it.
7. Collection and credit control
Credit terms differ by client and by agent, and a single defaulting client can exceed the margin on a month of jobs. Ageing in original currency plus a credit limit that blocks release is the minimum control.
Common challenges
- !Nobody knows the real margin on a job until the carrier invoice arrives weeks later
- !Advances paid to carriers and overseas agents get buried in operating cost
- !Buy rates change mid-quarter and the quoted sell rate is already committed
- !Agent balances sit in a spreadsheet that nobody reconciles until year end
- !Job volume is too high for project-based costing and too complex for a sales invoice
How a modern ERP helps
- ✓Job file with its own revenue, third-party cost and margin
- ✓Disbursement recovery rules instead of manual re-invoicing
- ✓Per-job FX so exchange movement does not vanish into a monthly total
- ✓Agent statement reconciliation against job-level balances
- ✓Volume-oriented job costing rather than one project per shipment
Must-have functionality
If a product cannot do these, the rest of the demo is irrelevant.
- ✓Job-level P&L: every shipment carries its own revenue, third-party cost and margin
- ✓Disbursements held as recoverable, with a rule for how they are billed back
- ✓Buy rate and sell rate as separate data, so margin is calculated rather than remembered
- ✓Per-job multi-currency with FX gain or loss posted to the job, not to a monthly pool
- ✓Accrued versus actual cost, with the ability to reopen and restate a closed job
- ✓Agent payable and receivable netted per agent with statement reconciliation
- ✓Volume without project objects: hundreds of jobs per month, opened in minutes
Worth paying extra for
Optional only in the sense that the must-haves come first — in practice one of these is often the reason a project pays for itself.
- ◇House and master bill generation with milestone tracking
- ◇Client portal showing status and downloadable documents
- ◇Credit limit per client and per agent, with release blocking
- ◇Customs declaration data handoff to the single window
- ◇Lane-level margin analytics by carrier, agent and salesperson
Candidate products and why they are on the list
Every candidate is listed with the reason it is on the list and the limitation that could remove it. Fit is judged against the must-have list above, not against brand reputation, and it is a judgement about the shape of the requirement — not a statement that the features work.
Fit
Our judgement of whether the product covers the must-have list above — the shape of the requirement, not proof that any feature works. Evidenced means the capability question is also answered; potential — needs validation means the scenario matches but the deciding capability is still unproven, so the card is a possible candidate and never a recommendation.
Capability
Verified means we read it on the vendor’s own page on a stated date. Partly evidenced means some requirements are documented and the deciding one is not. Unverified means we found no evidence — which is not the same as unsupported.
Delivery
Confirmed would mean our sales side has confirmed we can contract for the product, the version and the implementation. Everything here is TBD, so no card is an offer.
Commercial disclosure. ERP Guide Hub is an editorial resource. We do not present ourselves as an authorised partner, reseller or distributor of any product named on this page. We may receive commission or referral fees on products we cover, Chanjet products included. That does not buy placement, a better position in a list, a softer verdict or the removal of a limitation. Nothing here is an offer to supply any product named on this page. Any figure or feature claim still needs checking against the vendor's current documentation. Read our editorial policy for the full terms.
This page specifically. Every candidate above is a fit judgement against the must-have list for Freight Forwarding & Logistics Services, not proof that the features work. Delivery is still TBD for all of them, so no card here is an offer to contract.
Chanjet HaoYeCai — project and job costing
The finance half is genuinely covered: business documents post to vouchers automatically, so cost and the statutory ledger share one dataset, and project contract accounting already models budget versus actual with profitability analysis.
Watch out: The model is project-shaped, not shipment-shaped. Nothing on the official pages documents job costing at forwarder volume, buy/sell rate pairs, disbursement recovery rules or agent netting. Treat the statutory finance side as covered and per-shipment costing as unproven until demonstrated.
Verified capability sheet →Freight-specific forwarding systems (CargoWise, Descartes, CargoFlash class)
Built for exactly this operating model: job files, charge codes, buy and sell rates, documentation and agent settlement, at forwarder volume. If per-shipment margin is the whole business, this is the shape of the requirement.
Watch out: We do not sell or implement these, so nothing here is an offer. Their centre of gravity is operations, not PRC statutory finance — expect a separate China ledger or an integration, and expect implementation cost to scale with charge-code complexity.
Finance-first platforms with job or project costing (Sage Intacct, NetSuite class)
Strong on multi-entity, dimensional reporting, multi-currency and revenue policy, which is what a forwarder with several offices needs once the operational side already exists somewhere else.
Watch out: Not a forwarding system: no house bills, no charge-code library, no agent statements. China statutory work and the fapiao workflow normally arrive through a local partner, and the total cost assumes a finance team that will maintain the configuration.
Still unverified
These are commonly assumed but we found no official evidence. They are questions for the vendor, not selling points.
- Job-level costing at forwarder volume — hundreds of open jobs per month
- Buy rate and sell rate held as separate objects with calculated margin
- Disbursement recovery rules applied automatically at invoicing
- Agent network netting and statement reconciliation
- Accrued-versus-actual cost with job reopening after carrier invoice
- Customs declaration handoff to the single window
Ask the vendor this
Put these in writing during the demo. An answer that arrives only in the follow-up email is not an answer.
- 1Is margin calculated from a buy/sell rate pair, or entered as a markup?
- 2How are advances to carriers and agents held, and how are they recovered at invoicing?
- 3Can a closed job be reopened and restated when the actual cost differs from the accrual?
- 4How many open jobs per month does this configuration support in production today?
- 5How is an overseas agent statement reconciled against individual jobs?
- 6Which system holds the PRC statutory ledger, and what is the reconciliation between the two?
What is verified, what is partial, what is unknown
Each requirement is marked against what we could actually read on a vendor’s own page. “No evidence” means we could not verify it — not that the product cannot do it. Ask for a demonstration before you remove a product for that reason.
On a phone, swipe the table sideways to see the evidence column.
| Requirement | Status | Evidence |
|---|---|---|
| Business documents post to the finance ledger automatically | Verified | HaoYeCai documents state that business documents post to vouchers automatically, so cost and ledger share one dataset. hyc.chanjet.com, read 2026-10-29. |
| Budget versus actual and profitability analysis at contract level | Verified | HaoYeCai project management — budget control, progress, profitability analysis, project dashboard. hyc.chanjet.com/xiangmujingli/, read 2026-10-29. |
| Job costing per shipment at forwarder volume | No evidence | The documented object is a project with a budget and a team. No official page describes per-shipment job files or forwarder-scale volume. Absence of evidence, not evidence of absence. |
| Disbursement recovery and buy/sell rate pairs | No evidence | No official documentation found for charge-code level costs, recoverable advances or dual-rate pricing. |
| Agent network netting and statement reconciliation | No evidence | No official evidence. Do not assume a supplier statement equals agent netting. |
Where these projects actually go wrong
Four areas, the failure each one produces, and the control that prevents it. None of this is vendor-specific — it is what the projects have in common.
Charge codes multiply during rollout, and every new code becomes a small configuration project until the team stops asking for them and goes back to Excel.
Control: Freeze the charge-code list before go-live, cap it at what invoicing actually needs, and agree who may add one.
The forwarding system owns jobs and the finance system owns the ledger, so margin in one disagrees with revenue in the other and nobody knows which is right.
Control: Decide which system owns revenue, then require an automatic, reconcilable posting — not a monthly journal typed from a report.
Job opening becomes slower than the operations team can tolerate, so jobs are opened late or in batches, and accruals become fiction.
Control: Time the open-a-job flow against real volume before rollout; if it takes more than a couple of minutes, redesign before training.
Freight and logistics services exported to overseas clients have their own VAT treatment and evidence requirements, which differ from goods exports and from domestic transport.
Control: Confirm the treatment with your tax adviser for each service line, then check the system can hold the contract, invoice and settlement evidence against the same job.
Selection checklist
Work through this before you accept a demo. It takes an afternoon and removes most of the avoidable risk.
- 1Take one real shipment and trace its margin end to end, including a carrier invoice that arrived after the client was billed.
- 2Count how many charge codes you use in a month. If the number is above twenty, ask how they are maintained without a developer.
- 3Ask to see the buy rate and the sell rate on the same job screen. One number with a markup is not buy/sell.
- 4Ask how an agent statement is reconciled: at balance level, or against individual jobs.
- 5Confirm the job volume the system handles before performance degrades, in your own numbers per month.
- 6Check whether a closed job can be reopened when the carrier invoice differs from the accrual.
- 7Ask who owns the China statutory book, and how the two datasets are reconciled monthly.
What makes Freight Forwarding & Logistics Services ERP different
The invoice is not the revenue
A forwarder's invoice can be eighty per cent somebody else's money. Freight, terminal handling, customs fees, trucking and destination charges pass through the invoice, and only the spread between the buy rate and the sell rate belongs to the forwarder. A system that treats the invoice total as revenue produces a company that looks large, grows quickly, and cannot explain why cash is short.
That is why the unit of analysis has to be the job rather than the invoice, and why the job has to carry both sides. When the buy rate and the sell rate live in the same record, margin is calculated. When they live in two systems, or in one number with a markup typed on top, margin is estimated — and estimated margin always looks better than the truth.
The second consequence is about timing. Carrier invoices arrive after the client has been billed, sometimes weeks after. If the system closes the job at invoicing, the variance between accrued and actual cost has nowhere to land except a general pool, where it silently reprices every job in the month. Reopening a closed job is not an accounting nicety; it is the difference between job profitability and an average that hides everything.
Where forwarders actually lose the margin
Three leaks account for most of it, and none of them are software bugs. The first is unbilled advances: a cost paid to an agent or a carrier that never reaches an invoice line because nobody matched it back to the job. The second is FX: a job quoted in USD, costed in USD, settled in RMB, where the exchange movement is posted to a monthly total and the job keeps a margin it never earned. The third is agent disputes, where statements are reconciled at balance level, so an overcharge on one job is offset by an undercharge on another and both survive.
The controls are unglamorous. Every advance gets a reference to the job at the moment it is paid. Every job carries its own currency and its own FX result. Every agent statement is matched job by job, with differences parked against the specific job rather than netted away. None of this requires artificial intelligence; it requires a data model that holds a job, a charge line, a currency and an agent in one place.
For the China-side accounting interface — fapiao, VAT filing, the ledger that the tax authority sees — see statutory reporting requirements. For the multi-currency mechanics that apply to services rather than goods, see multi-currency for trading companies.
In-depth Freight Forwarding & Logistics Services ERP guides
Practical selection and deployment guidance for freight forwarding & logistics services teams operating across China and overseas.
ERP for Manufacturing: Modules, Features & Selection Tips
What a manufacturing ERP must do — MRP, BOM, shop-floor, quality — across make-to-stock, make-to-order, and engineer-to-order, plus how to shortlist vendors.
Read guide →IndustryERP for Retail & Omnichannel Commerce: Unifying Store, Web, and Warehouse
How retail ERP handles POS, e-commerce, inventory, and merchandising across channels, the integrations that make or break it, and which platforms fit.
Read guide →IndustryERP for Wholesale Distribution: Inventory, Pricing & Supply Chain
Distribution ERP essentials — lot/serial tracking, tiered pricing, dropship, and demand planning — for distributors competing on service level and margin.
Read guide →Compare the shortlist
Head-to-head pages on the same fixed dimensions, with each price carrying its source and the date it was read.
Sage Intacct vs Xero
Comparing two cloud financial platforms for businesses that need strong accounting as their ERP foundation.
Read comparison →Cloud ERP vs On-Premise ERP
A comprehensive guide to choosing between cloud-hosted and self-managed ERP — covering cost, security, control, and future-proofing.
Read comparison →Other industries
The must-have list changes with the operating model, so the shortlist does too.
Frequently asked questions
Why is per-shipment job costing different from project accounting?
A project has a budget, a team and a duration; a shipment has a booking, a charge breakdown and a carrier invoice that arrives late. Costing hundreds of shipments a month through project objects usually collapses under its own administration, which is why forwarders need job costing at volume.
What is disbursement recovery and why does it matter?
Most of a forwarder's invoice is money paid on the client's behalf — freight, duty, handling. If those advances are posted as ordinary cost, gross margin looks stable while cash drains and unprofitable lanes stay invisible. Recovery means holding them as recoverable and billing them back by rule.
Do we need both a forwarding system and an ERP?
Usually yes, unless one product genuinely spans both. Operations need documentation, milestones and charge codes; finance needs the statutory ledger, tax filings and consolidation. The decision is which one owns revenue — and whether the posting between them is automatic.
How do we handle buy rates that change after we have quoted?
Record the buy rate at booking, record the actual when the carrier invoices, and let the difference post to the job. If the system cannot reopen a closed job, the variance moves to a general cost pool and the job that caused it looks more profitable than it was.
Can a China-based forwarder keep the statutory books in the same system?
Often that is the deciding constraint: fapiao, VAT filing and statutory reports must run somewhere. The practical question is whether that somewhere also holds job cost, or whether the two are reconciled monthly by hand.
Ready to unify your global operations on one ERP?
Book a free scoping conversation with our ERP team. We help Chinese companies going global build a unified system across HQ, overseas factories, and international sales — finance, procurement, inventory, production, and operations in sync.
Book a Free Consultation