Logistics ERP Consultant, Qatar

Why the job file decides whether a forwarder is profitable

A Qatari forwarder might quote an import from Asia that involves ocean freight, an origin agent, destination handling at Hamad Port, customs clearance, container return and delivery to a site in Lusail or the industrial area. The client receives one invoice. Behind it sit charges from a shipping line, an overseas agent, the port, a transporter and sometimes a storage provider, arriving over several weeks and in more than one currency.

If those costs are booked to general expense accounts as they arrive, the business knows its monthly result but not which clients, routes or salespeople make money. I design the job file as the place where every cost and revenue line meets. Each charge has a code, the code determines both the revenue account and the matching cost account, and the job shows a margin that updates as bills come in.

The hard part is timing. Clients are often invoiced before all supplier bills arrive, so I define accruals: when the job is invoiced, expected costs are posted from the quotation or from rates agreed with carriers, and replaced by actual bills as they are received. A job is closed only when no expected costs remain open. The general logistics ERP page covers this lifecycle from inquiry to settlement.

Port, airport and the road from Saudi Arabia

Qatar's cargo flows through three main doors, and each one generates a different pattern of costs. Sea freight through Hamad Port brings shipping line charges, terminal handling, container detention and demurrage risk, and sometimes transshipment through another regional port. Air cargo brings airline and handling agent charges, often for urgent spare parts or high-value goods, with quick turnaround expected. Road freight enters through the single land border with Saudi Arabia, and costs can include waiting time, permits and transfer of goods between trucks.

I make the mode and the entry point fields on every job, with charge templates per mode so a road job prompts for border-related charges and a sea job for detention. That makes quoting more consistent and allows profit reports by mode and route.

Project cargo deserves separate treatment. Construction and energy projects can involve oversized items, staged deliveries and long-running jobs that span many months. For those, I recommend a parent project job with child shipment jobs, so the overall project margin is visible while each movement is still costed and billed on its own. Milestone billing against the parent and costs gathered from the children give management a clear view of the contract.

Customs brokerage and money paid on the client's behalf

Many Qatari forwarders also act as customs brokers, and brokers routinely pay duties, port fees and refundable deposits for clients before recovering them. These amounts are not your revenue, but they move through your bank account and can be large. When they are mixed with service income, revenue looks inflated, margins look thin, and nobody is sure which client still owes which duty payment.

I keep these disbursements in their own ledger accounts. When a broker pays duty, the payment posts against the client's job as a recoverable amount. When the client is invoiced, the disbursement line clears that balance without passing through revenue. Deposits, such as those for containers, are tracked until the shipping line refunds them, with aging so stuck deposits are chased.

The declaration itself stays in the customs system or with your brokerage software; rebuilding it inside an ERP rarely makes sense. What the ERP needs from the brokerage desk is every event with a financial consequence: the clearance fee, inspection attendance, extra documents, duties paid and storage incurred. Tax treatment of these lines is simpler in Qatar than in VAT jurisdictions, since as far as I know a general VAT is not in force there. Still, review the present rules with your tax advisor and keep tax codes on each charge line in case that changes.

Agent networks and reciprocal settlements

Most Qatari forwarders rely on overseas agents at origin, and many also act as destination agent for partners abroad. Each relationship produces charges in both directions: you owe an origin agent for pickup and export clearance, while that agent owes you for handling its own clients' shipments in Qatar. Profit shares on joint business add another layer. Settlement usually happens by periodic statement, netted and paid in one currency, often US dollars.

When agent charges are recorded only when the statement arrives, jobs close with missing costs and disputes surface months later. I set up each agent as both a customer and a supplier, with charges and credits posted to individual jobs in the agent's currency as soon as they are known. A statement view then shows open items on both sides, so netting is a matter of agreeing a list rather than reconstructing it.

Exchange differences between job date and settlement date go to a separate account, not into job margin. With the riyal fixed against the US currency, statements in dollars rarely move much, but agents billing in euros or other currencies still need revaluation rules. I also define approval limits for writing off small agent differences, which keeps statements from staying open over trivial amounts.

Freight software, ERP and the platform decision

The landscape I usually find in Qatari logistics companies is a freight or customs operations system, an accounting package fed by manual entries, spreadsheets for job profit and email for agent statements. The key decision is whether the operations software stays and only the accounting side is replaced, or whether one ERP with freight functions takes over both. Each path has risks, so I test both against your own scenarios rather than a vendor's preferred demo.

My scripts include a sea import with late detention charges, an air shipment for an urgent spare part, a road load from Saudi Arabia with border waiting time, a brokerage-only job with duty paid for the client, and an agent statement with charges on both sides. Each vendor runs those shipments live in the demo, and the same set later drives acceptance testing.

Migration concentrates on open work: jobs not yet closed with their accruals, unrecovered disbursements, refundable deposits, and agent balances in original currency. I work remotely with operations and finance through online workshops and a shared tracker, while the implementer builds the interfaces I specified. If you also run storage, see the Qatar warehousing ERP page; for traders you serve, the Qatar trading ERP page, and for my wider approach, ERP consulting in Qatar.