AWRA OpsHub Search
Intermediate Certificate on pass

Supplier Bills, Returns & Payment Runs

Capture each supplier invoice once, against its purchase order or as an expense bill, take credit for goods sent back, and pay a batch of approved bills in a payment run that a second person approves before any money leaves.

5 lessons 70 min 11-question assessment 70% to pass

What you’ll learn

  • Capture a supplier bill against a purchase order or for an expense with no order, and explain what each one posts
  • Explain the checks that refuse a duplicate, an over-billed order, a mismatched supplier or a self-approved bill before money is owed
  • Take credit for returned goods or an agreed price reduction with a debit note, and see it offset in a payment run
  • Build, approve and pay a payment run by bank file, cheque, cash, M-Pesa or Paystack, and resolve bank lines, failures and M-Pesa timeouts

Course content

5 lessons · 70 min of reading
01
Lesson 1 of 5 Reading 11 min

Two kinds of bill, and what each one posts

A supplier bill is the supplier’s invoice captured once in AWRA, so that what you owe them is a record rather than a folder of paper. You open it from Procurement → Purchase Orders, in the row of links for purchasing and payables, and the bills list shows three figures across the top: what is owed to suppliers, what is overdue, and what is waiting for review. There are two kinds of bill and the difference matters for the books. A bill against a purchase order is for goods that came through receiving: the payable was already booked when the check-in was approved, so approving the bill posts nothing for the goods themselves — it is the document you pay and the third leg of the three-way match. If that bill carries VAT, approval books the VAT part to input tax against accounts payable.

A bill without an order is for rent, electricity, a consultant or a courier — anything that never went into stock. Here the bill is where the cost first reaches the books, so each line can carry its own expense account; a line without one falls back to the bill’s expense account, and then to operating expenses. Expense bills can also be tagged with a department, branch and project so the income statement can be read by those dimensions. When you capture a bill against an order, Prefill from the order brings in each line with the quantity actually received — what the supplier should be charging for — and the order price. With no due date entered, a bill falls due 30 days after its bill date. A bill against an order quoted in another currency is in that currency, and it reaches the books in your base currency at the exchange rate recorded on it: the bill page asks for the rate, an approver records it once, and nothing posts until it is there — unless the order’s goods were received at a rate, which the bill then takes.

In practice: a Nairobi hardware distributor receives 400 bags of cement against a purchase order at KES 780 a bag. The check-in is approved, which books KES 312,000 to inventory and accounts payable. The supplier’s invoice arrives for KES 361,920 including 16% VAT. The clerk captures it against the order, presses Prefill, enters the supplier’s invoice number and attaches the PDF. On approval the goods post nothing new; only the KES 49,920 of VAT is booked to input tax. The same week, the office rent invoice of KES 85,000 is captured as a bill with no order, its line set to the rent expense account and tagged to the Westlands branch — and that bill does post the expense on approval.

Key takeaways

  • A bill against an order posts nothing for the goods on approval — the payable was booked at check-in — only the VAT part.
  • A bill with no order is where an expense first reaches the books, line by line, with optional department, branch and project tags.
  • Prefill from the order uses the quantity received, not the quantity ordered.
  • With no due date, a bill is due 30 days after its bill date; a bill in another currency posts in base currency at its recorded rate.
02
Lesson 2 of 5 Practice 12 min

The checks that protect a bill, and bills from the vendor portal

Most of what goes wrong in payables is paying something twice or paying more than was agreed, so the bill carries several refusals that run on the server rather than relying on someone noticing. A supplier’s invoice number can be captured once per supplier: keying it again is refused, and the message names the bill it was already captured as. Approved bills against one purchase order may not add up to more than the order total, plus any price tolerance set for your workspace — zero unless support has set one — and a bill that would push past it is refused at approval. A purchase order from a different supplier, or a line that is not on the chosen order, is refused. And a bill against an order can only be paid if the order passes the same payment match check every supplier payment screen uses.

Approval is maker-checker, the same rule payment runs follow: whoever entered the bill, or last edited it, cannot approve it, and is told someone else has to. The one exception is a workspace where nobody else active holds the approve supplier bills permission, so a one-person finance team is not locked out. Once approved, a bill is fixed: only a draft, submitted or rejected bill can be edited, so changing an approved one means cancelling it and capturing it again. Cancelling works only while nothing has been paid or credited against it, and cancelling an approved expense bill reverses its journal line for line, tags included. The balance on a bill is never typed: it is recomputed from confirmed payments and applied debit notes, net of any withholding, and the bill moves to Partly paid and then Paid on its own. Suppliers can also submit bills themselves. A supplier signed in to the vendor portal opens one of their purchase orders and uses Submit an invoice, with their invoice number, date, quantity, price and VAT per order line, and a required invoice file. It arrives as Submitted by supplier, everyone who can approve bills is notified, and nothing is payable until someone on your side approves it under the same checks.

In practice: an accounts clerk keys invoice INV-2207 from Mombasa Steel for KES 240,000 on Monday. She cannot approve it herself — she entered it — so it waits for the finance officer. On Thursday a colleague, working from a forwarded email, tries to key INV-2207 again and is refused with the name of Monday’s bill. Later that month Mombasa Steel submits INV-2241 from the vendor portal against an order worth KES 500,000, of which KES 420,000 is already billed. Their bill is for KES 95,000. The approver opens it, sees the match panel, and presses Approve for payment — and AWRA refuses it, because KES 515,000 would pass the KES 500,000 order total with no tolerance set. The approver rejects it with a reason; the supplier sees that reason on the order page in the portal, corrects the quantity and resubmits, and the corrected bill comes back as submitted for review.

Key takeaways

  • A supplier’s invoice number is accepted once per supplier, and approved bills on one order cannot exceed the order total plus the price tolerance, zero by default.
  • Whoever entered or last edited a bill cannot approve it, unless nobody else active holds the approve permission.
  • An approved bill cannot be edited; cancel and recapture it, and only while nothing is paid or credited against it.
  • A portal-submitted bill is not payable until your side approves it under the same checks as a bill your team keyed.
03
Lesson 3 of 5 Reading 11 min

Supplier returns and debit notes

When goods go back to a supplier, two things must happen together: the stock has to leave the warehouse and the supplier has to owe you for it. A supplier return does both. You open Returns & debit notes from the same row of links, press Return goods, and optionally pick the purchase order the goods came on, which fills in the supplier and items and suggests the VAT rate from that order’s bills. You choose the warehouse and location the goods leave from, the date, the VAT rate the supplier charged and the reason, then add the items in whole units — naming the serial numbers for a serial-tracked item. Leaving the unit cost empty uses the order price, or the item’s average cost when there is no order. The return is saved as a draft and approved with Approve — goods have left, which takes the stock out, marks the serials as returned to the supplier, and raises the debit note in the same step.

A return checks what it can. Against an order, every item must be on that order and you can return no more than was received on it and not already returned. Without an order, the item must have been bought from that supplier before. The warehouse and location must hold the quantity at approval. If your team wants preparing and approving to be two different people, an administrator switches on the second-approver setting under Settings → Procurement Defaults; it is off by default for small teams. For credit with no goods moving — a price agreed down after billing, a short-delivery credit or a rebate — Debit note without a return records the amount the supplier owes back including VAT, and the VAT part separately. On approval a return posts Dr accounts payable for the gross value, Cr inventory at what the stock cost and Cr input tax for the VAT, with any gap between the agreed price and the stock cost going to purchase price variance so the inventory account keeps agreeing with the stock valuation.

In practice: a pharmacy chain returns 20 cartons of a short-dated syrup bought at KES 3,000 a carton plus 16% VAT. Approving the return removes the stock and raises a debit note for KES 69,600: Dr accounts payable 69,600, Cr inventory 60,000 (the stock cost matched the order price), Cr input tax 9,600. The supplier has an open bill of KES 150,000. The finance officer opens the debit note, chooses that bill under Set against a bill and applies KES 69,600 — nothing posts, because the payable already fell when the note was raised, and the bill now owes KES 80,400. Had the supplier no open bill and refunded the money instead, Record the supplier’s refund would post Dr bank, Cr accounts payable. If the supplier later refuses the goods, the return is reversed — but only after the application to the bill is undone first.

Key takeaways

  • Approving a return takes the stock out and raises a debit note in one step; approve when the goods are actually leaving.
  • Against an order you can return no more than was received and not already returned.
  • A debit note is entered including VAT, with the VAT part stated separately.
  • Applying a note to a bill posts nothing — the payable already fell when the note was raised — so the same credit cannot be taken twice.
04
Lesson 4 of 5 Practice 25 min

Payment runs: maker-checker, six methods and the bank file

A payment run pays a batch of approved supplier bills in one sitting, one person preparing it and a different person approving it before any money leaves. Open Payment runs from the purchasing row of links, or press New payment run on the bills list: it lists every approved bill with something owed that is due by the Bills due by date — a week from today unless you change it — and is not already in another open run. You set a pay date and the account to pay from for bank, cheque and cash lines, and tick the bills. Each line starts at what is owed less any open debit notes from that supplier, applied when the run is paid, and you can lower an amount to pay part of a bill; the method defaults to bank transfer when the supplier has bank details, otherwise M-Pesa to their phone. A run moves from draft to submitted to approved, then processing and completed. Whoever built or submitted it cannot approve it, unless nobody else holds the approval permission — the audit log then records it as approved by its preparer — and an approver can send it back to draft with a reason. Approval fixes each line’s payee details, so a bank account or M-Pesa number changed afterwards refuses that line at payment until an approver retries it to accept them. Lines are checked again at approval and at payment, so a bill paid by hand, cancelled or credited meanwhile cannot be overpaid, and Pay now is refused before the pay date.

Each line pays by one of six methods. Bank transfer is the one that surprises people: Pay now moves a bank line to Awaiting bank, not to paid, and the approver downloads the Bank file — a CSV of beneficiary, bank code, account number, amount, currency, reference and narrative — for the bank’s bulk payment screen. Nothing posts until someone confirms with Confirm all bank payments and the date they were paid; a line the bank did not pay is marked Bank didn’t pay with a reason. Cheque and cash lines are recorded as paid at Pay now. M-Pesa B2C pays the supplier’s phone, M-Pesa B2B their paybill or till, and Bank Transfer (Paystack) their bank account once transfers are set up; these show Sent — awaiting confirmation until the provider confirms. M-Pesa and Paystack pay in KES only, M-Pesa in whole shillings, and a B2C line above KES 150,000 is refused so you can split it or pay by bank. Each line is claimed before money moves, so a double-click cannot pay it twice; a failed line keeps its reason and can be corrected and retried, but an M-Pesa timeout means the outcome is unknown — it shows Check with Safaricom and cannot be retried until someone checks the statement and marks it paid or not paid. A confirmed line is an ordinary supplier payment — Dr accounts payable, Cr the account paid from, under Vendor Payments — and the run completes on its own when nothing is still in flight.

In practice: on the 24th the payables officer at a Nakuru distributor builds a run for the 25th — KES 410,000 to a packaging supplier and KES 96,000 to a transporter by bank, KES 180,000 to a printer by cheque, whose open KES 30,000 debit note starts the line at KES 150,000, and two M-Pesa B2C lines of KES 42,000 and KES 18,500. The finance manager approves on the 24th, but Pay now that afternoon is refused because the pay date is tomorrow. Overnight the transporter sends new bank details; on the 25th that line is refused while the rest go through, until the manager checks the details by phone and presses Retry. The cheque is recorded as paid at once, the bank lines wait under Awaiting bank while the file is uploaded, the first M-Pesa line confirms and the second times out with Check with Safaricom. Next day the bank statement shows the transfers, which she confirms with the 25th as the paid date, and the M-Pesa statement shows the KES 18,500 never left, so it is marked not paid and becomes a failed line to retry. Until she confirmed them, the bank lines were in nobody’s ledger.

Key takeaways

  • A run lists approved bills due by the chosen date and not in another open run; open debit notes are offset on the line.
  • The preparer or submitter cannot approve unless nobody else holds the permission; payee details are fixed at approval.
  • Bank lines wait under Awaiting bank after Pay now and post nothing until confirmed; cheque and cash are paid at Pay now.
  • Gateways pay KES only, a B2C line above KES 150,000 is refused, and an M-Pesa timeout cannot be retried until marked paid or not paid.
05
Lesson 5 of 5 Reading 9 min

Reorder to purchase order

Payables begin with buying, and for routine restocking AWRA offers a shorter road than requisition, RFQ and quotation every time. Reorder, in the same row of links, lists every item at or below its reorder point, with its stock, its reorder point, what is already on open orders, and a suggested quantity, supplier and price. An item appears only once it has a reorder point set. The supplier suggested is the item’s preferred supplier, else whoever it was last ordered from; the unit price is the last price paid to that supplier, else the item’s buying price. The quantity is the item’s reorder quantity when it has one, otherwise enough to bring stock up to twice the reorder point — in both cases less what is already on order, so the suggestion is zero when enough is on its way.

With more than one warehouse, Stock in at the top counts stock and open orders for a single warehouse, so a branch that is short shows up even when the total looks fine; a user tied to one warehouse always sees, and orders into, that warehouse. Choosing a warehouse also brings in its own minimum and maximum, set on the item’s Stock tab under Min / max per warehouse: an item is offered once that warehouse holds its minimum or less — even an item the warehouse has never stocked — and the suggestion fills it up to the warehouse’s maximum, less what is already on order there. A warehouse with no row of its own falls back to the item’s reorder point and the rule above; one with a minimum but no maximum uses the item’s reorder quantity on top of what it holds, else twice the minimum. You choose where the goods should arrive and, if you use them, a location. Every value on a row can be changed before anything is created, and every ticked item needs a price above zero, because the order goes to the supplier as soon as it exists. Create and send orders makes one purchase order per supplier and emails each one straight away, landing you on the purchase orders list with their numbers; a supplier with no email address on file is named in a warning, and that order has to be sent by hand. These orders skip quotation approval, so an administrator can cap them with Largest order the Reorder page may send under Settings → Procurement: an order to one supplier above it is refused and has to go through a requisition. Each order is labelled as a direct award, so it is clear it skipped a competitive RFQ, and from then on it behaves like any other order — receiving, the three-way match, the supplier bill and payment. Reorder needs the same permission that creating purchase orders needs.

In practice: a Kisumu agrovet has 14 items at or below their reorder points on Monday morning. A maize seed with a reorder point of 50 bags and 18 on hand, no reorder quantity and nothing on order is suggested at 82 bags (twice 50, less 18). A fertiliser with a reorder quantity of 100 and 40 already on an open order is suggested at 60. A new herbicide shows no supplier because it has never been ordered and has no preferred supplier; the buyer picks one on the row. She unticks two items the branch is discontinuing and presses Create and send orders: five purchase orders go out, one per supplier, each marked as a direct award. When the goods arrive and are checked in, each supplier’s invoice is captured as a bill against its order, prefilled with the quantity received.

Key takeaways

  • An item appears once it has a reorder point and stock at or below it — or, with a warehouse chosen in Stock in, at or below that warehouse’s minimum, filled to its maximum.
  • Supplier: preferred, else last ordered from. Price: last price paid to that supplier, else the buying price.
  • Quantity: the reorder quantity, else enough to reach twice the reorder point — less what is already on order.
  • One order per supplier is created and sent at once, labelled as a direct award — and an optional cap in Settings → Procurement refuses an order above it.

Finished the material?

Take the 11-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center