AWRA OpsHub Search

For Malawi

The invoice is approved. The kwacha is ready. The dollars are not.

Malawi has run short of foreign exchange for years, and the Reserve Bank has said so publicly while allocating what exists between fuel, medicines and everything else. For an importer, the practical consequence is a payable that is fully approved, fully funded in local currency, correctly documented, and unpayable — sometimes for months. Every accounting system in the world has a state for unpaid and a state for paid. Almost none has a state for "waiting", which is where the money and the risk actually sit.

Foreign currency
We cannot get you any, and nothing here shortens a queue. No software does. Be sceptical of any vendor who suggests otherwise.
What changes
The wait becomes visible, attributable and countable — which payables, for how long, worth how much, and what the elapsed time has cost in revaluation.
MRA
No filing, no return preparation, no fiscal device or e-invoicing connection, and no advice on your obligations.
Payroll
No PAYE bands and no pension contributions under the Pension Act. Our maintained payroll engine covers Kenya only.

The life of an import payable here

Six states, of which your system probably has two

This is the ordinary life of an import payable in Malawi. Nothing in it is a failure by anybody in your business, and none of it is visible in a standard ageing report, which shows a single number growing older for reasons it cannot distinguish.

  1. One

    Approved

    The purchase is authorised, the goods are ordered or already received, the invoice is matched. Every system models this. From here on, most of them stop.

  2. Two

    Funded in kwacha

    Your business has the local currency and has committed it. Internally the obligation feels settled — the money is set aside, the budget line is consumed, the decision is made. Externally nothing at all has happened.

  3. Three

    Lodged with the bank

    The application for foreign currency is in. There is a date, and often a reference. This is the last point at which anybody in your business does anything, and in most businesses it is also the last point that gets recorded anywhere.

  4. Four

    Waiting

    This is where the time goes. Days, weeks, in bad periods considerably longer. The supplier chases you, and the honest answer is that you do not know. Meanwhile the payable is denominated in a currency that is still moving against the one you have committed.

  5. Five

    Allocated, partly or wholly

    Some or all of the currency comes through. A partial allocation is common and is the state that breaks the most reports, because the payable is now two payables with two histories and one invoice number.

  6. Six

    Paid

    The supplier has the money, at a rate set months after the commercial decision that created the obligation. Your books record a payment and a difference. What they usually do not record is that the difference was produced entirely by the interval between states three and five.

The consequence worth stating plainly: an ageing report in this environment is not a measure of your payment behaviour. A supplier at 120 days might be a dispute, a cash problem, an oversight, or four months in a bank queue with a perfect file — and the report shows all four identically. Businesses respond by not trusting the report, which means the genuine problems in it stop being found. That is the actual damage, and it is bigger than the exchange loss.

Five questions worth asking inside your own business, before you ask any vendor

  1. How many of your supplier balances over 90 days are waiting for an allocation rather than for a decision by you? Can you produce that list without asking somebody?
  2. What is the total value of payables currently lodged with a bank and unallocated?
  3. How long has the oldest one been waiting, and who last spoke to the bank about it?
  4. What has the wait cost this year in revaluation, separately from anything you negotiated on price?
  5. When a supplier asks for a payment date, does the answer come from a record or from the person who happens to remember?

What this costs today

Four problems, and the smallest one is the exchange loss

The revaluation is the number that gets noticed because it lands in the accounts. The expensive one is quieter: a set of reports the business has stopped believing, so the genuine problems inside them stop being found.

Ageing that measures the bank, not your behaviour

A dispute, an oversight, a cash problem and a currency queue all appear as the same overdue balance, so the report stops being read and the real problems in it stop being found.

Exposure created after every approval

The purchase was authorised at one rate and settles at another, months later, and the difference lands in an exchange line that no budget holder recognises as theirs.

Landed cost that arrives long after the goods

Transport, clearing, duty and the eventual exchange difference settle over months. If they never reach the unit cost, margin is being measured against a purchase price on stock that has already been sold.

A supplier relationship managed by apology

When nobody can say which stage a payment is at, every supplier conversation becomes a negotiation about trust rather than an exchange of information — and the suppliers who tire of it quote higher or stop quoting.

Illustrative — run it with your own rates

What the wait costs, on one order

Illustrative figures, deliberately unremarkable ones, and you should run this with your own rates and your own worst wait rather than these. The purpose is to separate two things that ordinarily arrive as a single number in the accounts: the price you negotiated, and the time you spent waiting to pay it.

Invoice

USD 60,000

Goods received, invoice matched, payment approved. The commercial decision is complete and, as far as anybody internally is concerned, done.

Committed in kwacha at receipt

MWK 105,000,000

At an illustrative MWK 1,750 to the dollar. This is the number that entered the budget, the approval and everybody's mental model of the transaction.

Allocation arrives

day 140

Roughly four and a half months. Not an extreme case, and not a case anybody in the business did anything wrong to cause.

Settled in kwacha at allocation

MWK 115,800,000

At an illustrative MWK 1,930. The dollar obligation never changed. The kwacha required to discharge it did.

MWK 10,800,000 — about ten per cent of the order value, produced by the interval and by nothing else.

Two things follow from that number and they matter more than the number. First, it was never in a budget, because it was created after every approval in the process had already been given — no procurement control, no threshold and no negotiation could have caught it. Second, it is measurable in advance, in the sense that if you know your average wait and your typical exposure you know roughly what this costs you a year, and most businesses here have never calculated it because the data is spread across a bank file, a spreadsheet and somebody's memory. We cannot make the wait shorter. We can make it a number you have.

Scope, stated plainly

The first item is the only one that matters if you came here hoping otherwise

This page is not claiming to solve a macroeconomic condition. It is claiming something much smaller, and we would rather be precise about the size of it than sell you the larger version.

Scope in Malawi, stated before the demo

Running in the product today

  • Supplier balances and ageing with the underlying documents attached, so a query is answered from the record rather than from a folder.
  • Multi-currency held at the rate actually applied, with the original currency retained on the transaction rather than discarded after conversion.
  • Landed cost on the consignment, so transport, clearing and duty reach the unit cost.
  • One register for money out, covering transfers, cash and mobile wallets, including partial settlements against a single obligation.
  • Approvals that block above a threshold, with a full audit trail of who changed what and when.
  • Multi-site stock, confirmed transfers and counts with variance attributed to a place and a period.

Not built — and the first one is the only one that matters if you came here hoping otherwise

  • We cannot get you foreign currency, and nothing here shortens a queue. No software does. What this page offers is that the wait becomes visible, attributable and countable instead of being absorbed into an ageing bucket. If you were hoping for more than that from a software vendor, be sceptical of anyone who offers it.
  • No stage tracking specific to a bank's allocation process. The stages described above are modelled using the ordinary tools — statuses, dates, documents and alerts — configured to your process. There is no built-in "forex queue" module, and there is no integration with any Malawian bank.
  • No MRA integration. No electronic filing, no return preparation, no fiscal device or e-invoicing connection, and no advice on your obligations.
  • No Malawian payroll. No PAYE bands, no pension contributions under the Pension Act, no statutory schedules. Our maintained payroll engine covers Kenya only.
  • No treasury, hedging or forward-cover functionality. We record what happened. Deciding what to do about currency exposure is a conversation with your bank and your advisers, and it is genuinely outside what we do.
  • No local office and no Malawian implementation partner. Support is remote from Nairobi, in English.

The distinction to hold on to: this page is not claiming to solve Malawi's foreign exchange problem, which is a macroeconomic condition and not a software category. It is claiming something much smaller and, we think, genuinely useful — that a business absorbing a cost of this size should at least be able to say how large it is, which of its suppliers it affects, and how long the wait has been running. Most cannot, and the reason is record-keeping rather than economics.

How this starts

Three moves, and the first two produce a board-pack number

01

List every payable currently waiting on an allocation

Value, supplier, date lodged. If assembling that list requires asking somebody rather than running something, you have found the gap this page is about — and the list itself is usually larger than the finance team expects.

02

Price one wait

Take a single import settled in the last year, find the rate at commitment and the rate at payment, and calculate the difference. Then multiply roughly by how many of those you do. That number is the honest size of the problem, it belongs in a board pack, and you do not need software to produce it once.

03

Then decide what you are actually buying

You are not buying access to currency. You are buying the ability to see and account for a delay you are already paying for. That is a smaller purchase than most vendors would let you believe and it is the only one anybody can honestly sell you here.

Questions we are asked here

Answered in full, including the ones that lose us the deal

Can you help us get foreign currency faster?

No. This is the first answer on purpose, because it is the one worth being unambiguous about. No software product obtains foreign currency, influences an allocation, or moves you up a queue, and a vendor who implies otherwise is selling you something they cannot deliver. What changes is that the wait stops being invisible: which payables are in it, for how long, worth how much, and what the elapsed time has cost in revaluation. That is a real improvement over the usual position, which is that nobody can produce the list at all.

How do you actually model a payable that is waiting?

With ordinary tools rather than a special module, and it is fair to know that before a demo. The payable carries a status you define, the date it was lodged, the bank reference and the supporting documents, and an alert fires when it passes a threshold of days in that state. Reporting then groups by stage rather than only by age. There is no built-in forex-queue feature and no bank integration — it is configuration, applied to a process you describe to us during onboarding.

What about the parallel rate?

We record transactions at the rate actually applied and we hold no opinion about which rate is the right one — the same design decision we made for Zimbabwe, for the same reason. Where you source currency, and on what terms, is a commercial and legal question for you and your advisers, and it is not one we advise on or build features around. What the system does is make sure that whatever rate was used is on the transaction, so the accounts describe what happened rather than what the rate table thought should have happened.

Do you connect to the MRA?

No. No electronic filing, no return preparation, no fiscal device connection and no e-invoicing integration. We hold the transaction detail a return is built from; the filing itself stays with your accountant or the accounting system you already use for it.

Do you handle Malawian payroll?

No. No PAYE bands, no pension contributions under the Pension Act, no statutory schedules. Our maintained payroll engine covers Kenya only. We do attribute labour cost to projects, sites and cost centres, which is what makes the numbers useful once your payroll provider has produced them — and for donor-funded organisations, which are a real part of this market, that attribution is often the more valuable half anyway.

We are an NGO rather than an importer. Does any of this apply?

Parts of it, and honestly not the headline. If your funding arrives in dollars and is converted as needed, you have the mirror image of the problem on this page rather than the problem itself. Where we are genuinely useful to donor-funded organisations is elsewhere: cost attributed to the right grant and budget line, procurement that will not exceed an authorised amount, assets under named custody across sites, and an audit trail a donor can be walked through. There is a body of work behind that in the corpus, and it is a better starting point for you than this page.

Malawi is a small market. Why would you support us properly?

The fair answer is that market size is a reasonable thing to worry about and you should ask it of every vendor, including us. Support is remote from Nairobi, in English. Malawi is UTC+2 and Nairobi is UTC+3, so one hour — effectively the same working day, which is the easiest support relationship of any market outside East Africa. There is no Blantyre or Lilongwe office and no local implementation partner. Ask what happens when the person who implemented your system leaves; that question separates vendors more reliably than any feature list.

Ask for the list of payables waiting on an allocation

Value, supplier, days lodged. If it can be produced in ten minutes, your record-keeping is in better shape than most and this page is not urgent for you. If it takes a week and three people, that is the conversation — and you now know what it is worth.