Logistics ERP Consultant, KSA

Port branches, dry ports and one set of books

A Saudi forwarder's map often looks like this: a branch at Jeddah handling Red Sea cargo, another on the Gulf coast near Dammam, an operation linked to the dry port serving Riyadh, and perhaps desks at the main airports. Each branch clears, delivers and invoices its own jobs, yet many shipments involve two branches, for example arriving at one coast and being delivered inland by another team.

When each branch keeps its own spreadsheet or its own copy of a local accounting package, head office sees totals but cannot trust job margin. Inter-branch work is charged inconsistently or not at all, and the same client may receive invoices in different formats from different cities.

The design work covers:

• one customer and charge code master shared by every branch
• a branch dimension on every job, invoice and cost
• internal recharges when one branch performs work on another's job
• approval limits by branch for credit and negative-margin jobs
• reporting by branch, client, port and service line

I gather these through business analysis sessions with each branch manager, recorded so finance can review them later. The Saudi trading ERP page covers the importer's side of the same port flow.

Customs brokerage: where the ERP stops

Customs declarations in the Kingdom are lodged through the national trade and customs platforms, usually by licensed brokers using their own systems or the portals directly. That work needs specialists and should stay where it is. Trying to rebuild declaration logic inside an ERP adds cost and risk for little benefit.

What the ERP does need from the brokerage desk is every event that has a financial consequence: the clearance fee, the number of items declared, inspection attendance, extra document work, duties and fees paid on the client's behalf and any storage or demurrage incurred while cargo waits. If these are captured as structured data, the invoice is complete. If they are written in a notebook or an email, some of them are never billed.

I define that boundary in a short interface specification: what the brokerage side sends, in what form, how often and who fixes errors. Where the brokerage system has no integration options, a simple daily import with validation may be enough. I also cover how a cleared job is closed, because open jobs with stray costs are a common source of month-end surprises. The detail goes into the integration design and is tested with a real clearance during UAT.

ZATCA e-invoicing for freight and pass-through charges

Logistics invoices can be awkward under e-invoicing because they mix the provider's own services with costs paid on the client's behalf. A typical import invoice may include freight, clearance fees, delivery, and reimbursement of duty and port charges. How each of those lines is treated for VAT, and whether a reimbursement is presented as a disbursement, is a question for your tax advisor. How the ERP produces the e-invoice correctly once the treatment is decided is a system design question I can help with.

The points I test with each shortlisted platform include whether tax invoices and simplified invoices are generated in the required format, how credit notes link to the original invoice when a job is re-billed, how invoices raised by branches or by a connected freight system reach the authority where integration applies, and how Arabic and English content appears together on the document.

I ask vendors to demonstrate these steps on your scenarios rather than describe them. Requirements and timelines from ZATCA are confirmed with your advisor and the vendor; I keep a record of each vendor's stated approach in the selection file. There is more on this for one platform at Odoo in Saudi Arabia.

Land freight across the GCC

Road freight links Saudi Arabia with the UAE, Kuwait, Bahrain, Qatar, Oman and Jordan, and many Saudi forwarders sell full and part loads on those routes using subcontracted trucks. Quoting is straightforward. Costing is not, because the real cost of a trip includes waiting at border crossings, detention when consignees are not ready, permits, escorts for certain cargo and occasional rerouting.

If only the haulier's base invoice is recorded against the job, margin looks healthy until the extra charges arrive weeks later and are booked to general expenses. I design trip-level costing that accrues the agreed truck rate when the client is invoiced, then lets operations add border and detention charges against the same job as soon as drivers report them, with a flag for those that can be recharged under the client contract.

Payments to truck owners and small transport companies also need attention: advances to drivers, settlement after delivery and deductions for damage or delays. These are accounts payable processes, but they must be linked to trips. If you operate your own trucks as well, ERP for transportation covers fleet costing in more depth.

Choosing a platform and working remotely with Saudi teams

Saudi logistics companies often run an operational freight or brokerage system alongside an older local accounting package, with branches sending spreadsheets to head office. Larger groups may have outgrown that model as they add contract warehousing or regional subsidiaries. The decision is usually whether to keep the operational system and modernize finance behind it, or move to an ERP with freight extensions.

I run vendor selection with a scripted Saudi set: an import through Jeddah delivered to Riyadh by another branch, a brokerage-only job with an inspection, a truck to Dubai with border waiting charges, a warehouse billing cycle and an e-invoice with a credit note. The same scripts become UAT cases later.

Engagements are remote. Managers join live workshops scheduled across the Saudi working days, port staff on rotating shifts watch short recorded walkthroughs, and an on-site day at a port branch is possible by arrangement when it adds something. The Saudi ERP consultant page explains engagement options, the Saudi Arabia hub has notes on the Saudi market, while the general job model is set out in the logistics ERP overview. For storage-led operations, see warehousing ERP.