Cross-Border Procurement in East Africa: Sourcing Across Currencies & Borders
Sourcing across East African borders adds three things to every purchase: a foreign currency, a longer lead time, and a customs step between the order and the goods. The procurement disciplines that keep control when your supplier is in another country — and the honest line on where operations software stops and a clearing agent begins.
Buying from a supplier down the road is a solved problem: agree a price, receive the goods, match the invoice, pay. Buying from a supplier across a border breaks that clean loop in three places. The price is in a currency that moves before you pay it. The lead time is long enough that what you ordered and what arrives can drift apart. And between the purchase order and the goods on your shelf sits a customs process that adds cost the order never mentioned. A regional group that runs cross-border procurement on the same controls it uses for local buying will lose margin it cannot see. This guide is about the controls that hold across a border.
The three things a border adds to a purchase
- A currency that moves. The purchase order, the payment and the period-end are three different exchange rates, and the gap between them is a real cost — the multi-currency discipline applied at the buying end.
- A landed cost the invoice hides. Freight, insurance, duty and clearing turn a supplier invoice into a much larger true cost; pricing off the invoice is the classic cross-border margin error, worked through in what is landed cost.
- A customs step you record but do not run. Duty and clearing fees are part of the unit cost and belong in your records — but the declaration itself happens with a clearing agent and the revenue authority, not in your operations system.
The controls that survive the distance
The core procurement controls do not change across a border — they matter more. The procure-to-pay loop is the backbone; here is what each control has to do when the supplier is in another country.
| Control | Local buying | What changes across a border |
|---|---|---|
| Approval before spend | Requisition routed by value | Same, plus currency and forex exposure visible at approval |
| Competitive sourcing | Local quotes compared | Quotes normalised to one currency to compare fairly — RFQ discipline |
| Purchase order | Priced in home currency | Priced in supplier currency, rate recorded, home-currency value shown |
| Goods received | GRN on delivery | GRN against what actually cleared — quantities can differ after customs |
| Three-way match | PO = GRN = invoice | Match still holds; landed-cost lines added before the item is costed |
| Payment | Local transfer | Foreign payment at the rate paid, FX difference booked explicitly |
The control that earns its keep hardest across a border is three-way matching: with a long lead time and a customs step in the middle, the odds that the invoice, the order and what physically arrived all agree without checking are low — and a goods-received note against every shipment is what turns "roughly what we ordered" into a number you can pay against.
The honest boundary: not a clearing system
AWRA records the landed cost of cross-border goods — the duty, clearing and freight you enter — and loads it onto the stock so your true cost is right. It does not file customs declarations, compute tariffs or classify goods; that is the work of your clearing agent and the revenue authority. A vendor claiming their ERP "handles customs" across East African borders is describing something to interrogate closely, not a feature to assume.
Supplier management when suppliers are regional
- One supplier record, many currencies. A supplier you buy from in dollars and settle partly in shillings is still one relationship — spend, terms and reliability tracked in one place, not split across entities.
- Approvals that respect entity and value together. In a group, a cross-border purchase may commit one entity to pay for another's goods — the approval and the resulting inter-entity balance both need to be explicit.
- Lead time treated as a cost, not a surprise. A supplier two borders away has a lead time that drives your reorder point; the drc corridor trade shows how corridor realities reshape stock planning.
- A supplier audit trail that crosses borders. When procurement is donor- or governance-scrutinised, the file — requisition, quotes, PO, GRN, invoice — must assemble itself regardless of which country the buying happened in.
Why one system beats a buyer per country
Groups often let each country run its own procurement, and then cannot see that three entities buy the same item from the same regional supplier at three different prices. One system across the EAC surfaces exactly that — consolidated spend by supplier, negotiated once for the group, controlled locally — which is the commercial half of the one-ERP-across-the-EAC argument. Control stays with each country's approvers; visibility and buying power move to the group.
Control procurement across every border
Multi-currency purchase orders, landed cost loaded onto imported stock, three-way matching against what actually cleared, and one supplier view across the group — with an honest line on where clearing agents take over.
See procurement in AWRAFrequently asked questions
Can we raise purchase orders in a supplier's foreign currency?
Yes — the PO is priced in the supplier's currency with the exchange rate recorded, and the home-currency value shown alongside so approvers see the real commitment. When you pay, the rate you actually paid is applied and any FX difference is booked explicitly, so the purchase reflects true cost rather than a stale assumption.
Does the system handle customs and import duty?
It records them as landed-cost components and loads them onto the imported stock so your unit cost is honest — but it does not file customs declarations, calculate tariffs or classify goods. That work is done by your clearing agent and the revenue authority. Think of the system as the place the customs cost lands in your books, not the place the declaration is made.
How does three-way matching work when goods cross a border?
The purchase order, the goods-received note and the supplier invoice still have to agree before payment — and across a border the goods-received note matters more, because quantities can differ after a long transit and a customs step. Landed-cost lines (freight, duty, clearing) are added before the item is costed, so the match protects both the quantity and the true price.
Can one entity buy on behalf of another in the group?
Yes — a cross-border purchase where one entity pays for another's goods is recorded with the approval it needs and the inter-entity balance it creates, posted on both sides so the two companies' books agree. That keeps a genuinely common practice from becoming an undocumented loan that surfaces at audit.
Why not let each country manage its own suppliers?
Because you then cannot see that several entities buy the same goods from the same regional supplier at different prices — losing both negotiating power and control visibility. One system keeps buying decisions local (each country's approvers stay in charge) while giving the group consolidated spend by supplier, so terms can be negotiated once for everyone.
