AWRA OpsHub Search
Intermediate Certificate on pass

Petty Cash & Staff Advances

Run each cash box as an imprest float backed by its own ledger account, record vouchers with receipts and optional approval, and take a staff advance from request through issue, retirement, reimbursement or write-off — with overdue advances chased automatically.

5 lessons 55 min 10-question assessment 70% to pass

What you’ll learn

  • Read a float’s balance, available amount and top-up due, and explain why they come straight from the ledger
  • Record payment and top-up vouchers correctly and apply the approval rules
  • Take a staff advance through request, approval, issue, retirement and settlement
  • Use the ageing summary and reminders to keep advances from going stale

Course content

5 lessons · 55 min of reading
01
Lesson 1 of 5 Reading 9 min

A float is a ledger account, not a tally

Petty cash in AWRA is run on the imprest model. Each cash box is a float with a name, a level it is topped back up to, and optionally a custodian (the person who holds the box), a branch and a currency. Creating a float creates a dedicated asset account in your chart of accounts, named after the float, and the float’s balance is that account’s balance read straight from the journal. There is no second running total kept beside it, which is the whole point: the box on the shelf and the books cannot drift apart because there is only one number. You will find the floats under Accounting, Journal, then Petty Cash in the accounting sidebar, or from the Accounting quick actions.

Three figures appear on every float, and each answers a different question. Balance is what the account holds. Available is the balance less any payments still waiting for approval, so two vouchers queued at the same time cannot spend the same shillings. To top up is the float level less the balance; topping up by exactly that amount restores the float to its level, and it is offered as the default on the top-up form. When you set up a float you can also enter an opening top-up and the bank or cash account it came from. That first top-up posts immediately, without waiting for approval, so the box can pay its first voucher the same day.

In practice: a clinic in Nakuru sets up a Front Office float with a level of KES 20,000, funded by an opening top-up from its main bank account. After a week of fuel, stationery and courier vouchers the balance reads KES 6,500, and one KES 2,000 payment for a plumber is still waiting for approval. The float now shows a balance of KES 6,500, available of KES 4,500 (because the pending KES 2,000 is already spoken for) and a top-up due of KES 13,500. The accountant tops up exactly KES 13,500 from the bank, the balance returns to KES 20,000, and the ledger shows every shilling that left the box against the expense account it was spent on.

Key takeaways

  • Each float gets its own asset account; its balance is that account’s balance, read from the journal.
  • Available = balance less payments awaiting approval, so queued vouchers cannot overspend the box.
  • To top up = float level less balance; topping up by that amount restores the float.
  • An opening top-up entered at set-up posts immediately so the box can start paying.
02
Lesson 2 of 5 Practice 10 min

Vouchers, receipts and the approval switch

Every movement of cash in or out of a box is a numbered voucher of one of two kinds. A payment out of the box carries the date, payee, description, amount and the expense account it was spent on, and can be tagged to a department and a project; you attach a photo or PDF of the receipt (PDF, JPG, PNG, WEBP or HEIC, up to 10 MB), which is stored privately and opens only for people allowed to view petty cash. A top-up into the box records the money put in and the bank or cash account it came from. A payment posts a debit to the expense account and a credit to the float’s account; a top-up debits the float and credits the source account. Each entry carries the voucher’s department and project and the float’s branch, so petty spending lands correctly on a department or branch income statement.

Approval is a switch in Settings, Accounting Defaults, and it is off by default because a one-person office has nobody else to approve. With it on, every new voucher waits as pending and nothing posts until it is approved, under two rules: the person who recorded a voucher cannot approve it, and a pending payment already counts against what the box has available. A rejected voucher keeps its reason and posts nothing. Dates matter too: a voucher dated in a closed month is refused, but a voucher dated in an open month that was closed while it waited for approval still goes through on approval, and its entry lands on the first open day.

In practice: the guards catch the classic mistakes. A cashier at a Mombasa branch tries to move KES 5,000 from the shop float to the warehouse float by recording a payment — refused, because a payment must go to an expense account; the right move is a top-up on the receiving float from the account the money actually came from. Someone else tries to top a float up from itself — refused. A KES 8,000 payment against a box with KES 4,500 available is refused with the amount the box still holds, so the custodian tops up first. And the till drawer’s small spending belongs here, not in Expenses, which is for bills owed or paid from the bank.

Key takeaways

  • Payments go to an expense account with a receipt attached; top-ups come from a bank or cash account.
  • Approval is off by default; with it on, nothing posts until someone other than the recorder approves.
  • Moving cash between boxes is a top-up on the receiving float, never a payment.
  • A voucher dated in a closed month is refused; a late approval of an open-month voucher posts on the first open day.
03
Lesson 3 of 5 Practice 20 min

A staff advance from request to settlement

A staff advance (many organizations call it imprest) is cash given to a named member of staff for a trip, an event or field work; until it is cleared it is money owed by that person, and the ledger shows it that way. Finance works from Accounting, Journal, then Staff Advances in the sidebar. An advance starts as a numbered request naming the member of staff, the purpose and the amount, optionally with a department and project. If approval is switched on in Accounting Defaults it waits for approval, otherwise it is approved as soon as it is raised, and it can be rejected with a reason at any point before it is issued. Issuing is the moment it posts: you pick the bank, cash or petty cash account it was paid from and the date, AWRA debits Staff Advances and credits that account, and the retire-by date is set to the issue date plus the days in Accounting Defaults — 14 unless you change it. Issued from a petty cash float, it appears on that float as a payment voucher and is refused above what the box has available; an issue dated in a closed month is refused like any other posting.

Retiring is accounting for the money: one line per receipt — what it was spent on, the expense account, the amount, its own department and project if needed, and a photo or PDF of the receipt — plus any cash handed back and the account it went into. You can retire in more than one go, whatever is not yet accounted for stays outstanding, and returning more cash than is outstanding is refused with the amount still open shown. The retirement debits each expense line and the returned-cash account and credits Staff Advances up to what is outstanding. Two endings settle the rest. Spending beyond the advance is credited to Staff Reimbursements Payable — it is now owed to the person — and paying it out is one step, debiting that account and crediting the bank or cash account you paid from. Money that will never come back is written off by somebody with approval rights to the expense account they choose; you cannot write off your own advance, and a write-off waits until any pending retirement has been approved or rejected. Staff Advances and Staff Reimbursements Payable are kept by the advance itself, so choosing either on a receipt line is refused — a receipt charged to the advance account would clear it on paper while the ledger still showed it owed.

In practice: a community health NGO in Kitui raises a KES 45,000 advance for a field officer’s three-day outreach, tagged to the Outreach department and the Maternal Health project. The programme manager approves it and on 3 March it is issued from the main bank account, so the officer owes KES 45,000 on Staff Advances with a retire-by date of 17 March, and the project’s spending is visible from the day the cash leaves. The officer returns with receipts for KES 31,200 of fuel and KES 16,300 of venue and refreshments, KES 47,500 in all. Retirement debits Fuel KES 31,200 and Meetings KES 16,300, credits Staff Advances KES 45,000 (clearing it) and credits Staff Reimbursements Payable KES 2,500, which finance reimburses by M-Pesa from the cash account. Had the officer spent only KES 40,000, the KES 5,000 handed back would be recorded on the same retirement and the advance would close at zero, with nothing owed either way.

Key takeaways

  • An advance posts at issue — Staff Advances against the bank, cash or petty cash account — and is owed by a named person until retired.
  • The retire-by date is the issue date plus the Accounting Defaults setting (14 days unless changed); from a float it is refused above the available amount.
  • Retirement is receipt lines plus any cash returned, in one go or several; spending beyond the advance becomes Staff Reimbursements Payable, paid out as a reimbursement.
  • A write-off needs approval rights, cannot be your own advance and waits for any pending retirement; the two advance accounts cannot be chosen on a receipt line.
04
Lesson 4 of 5 Reading 8 min

Separation of duties and self-service

With approval switched on, both the advance and each retirement wait for somebody with the approve permission, and two people are always excluded: whoever raised it, and the member of staff it is for. The second rule holds whatever role that person has — even an administrator cannot approve the receipts for their own advance — because the person holding the money has the strongest reason to approve their own receipts, and that is the one control imprest exists to provide. Permissions are split four ways: view staff advances, manage staff advances (raise for anyone, issue, retire and reimburse), approve staff advances (approve or reject, and write off), and request staff advances.

A member of staff who holds only the request permission sees My Advances in the accounting sidebar and the Accounting quick actions instead of the finance list. There they can request an advance and retire it with receipts, but only for the employee record linked to their login — they cannot raise one for anyone else. If the page says the login is not linked to an employee record, HR has to link the user to the employee record first. Petty cash has its own three permissions in parallel: view (floats, vouchers and receipts), manage (create floats and record vouchers) and approve (approve or reject pending vouchers).

In practice: a Kampala distributor gives its sales reps the request permission only. A rep requests KES 60,000 for a regional trade fair from My Advances, finance issues it from the bank, and after the fair the rep photographs each receipt into the retirement. The regional manager, who holds the approve permission, signs off the retirement; the rep could not approve it even if they were later given the approve permission. Finance never re-types a receipt, and the rep never sees anyone else’s advances.

Key takeaways

  • Neither the raiser nor the person the advance is for can approve it or its retirement.
  • That rule holds for every role, administrators included.
  • The request permission gives My Advances: request and retire your own advances only.
  • A login must be linked to an employee record before My Advances works.
05
Lesson 5 of 5 Practice 8 min

Overdue advances, reminders and ageing

An issued advance with money still outstanding after its retire-by date is marked overdue. Every morning AWRA emails the member of staff, copying the person who raised it, with the amount outstanding and how many days late it is. Each advance is reminded at most once every three days, so a slow retirement is chased steadily without flooding anyone’s inbox, and nobody in finance has to keep a spreadsheet of who owes what.

At the top of the Staff Advances list, finance sees an ageing summary in five buckets: not yet due, then 1–30, 31–60, 61–90 and over 90 days late. That strip is the month-end conversation in one line — the older buckets are where write-off decisions and difficult conversations live. Because every issue and retirement is a posting, an advance also respects the period lock: dating an issue or a retirement in a closed month is refused, and a retirement that was waiting for approval when its month closed still posts on approval, on the first open day.

In practice: at the end of June a school in Eldoret has KES 380,000 in advances outstanding. The ageing strip shows KES 210,000 not yet due, KES 140,000 1–30 days late and KES 30,000 over 90 days late on one teacher who has since left. The bursar lets the reminders work on the 1–30 bucket, which typically clears within a week as receipts come in, and asks the head to write off the KES 30,000 to staff welfare expense after HR confirms it cannot be recovered — a decision recorded with its reason rather than an unexplained balance carried into the next year.

Key takeaways

  • Outstanding money past the retire-by date marks an advance overdue.
  • A daily email goes to the staff member, copying whoever raised it — at most once every three days per advance.
  • The ageing summary splits outstanding advances into not yet due, 1–30, 31–60, 61–90 and over 90 days.
  • Issues and retirements respect closed months like every other posting.

Finished the material?

Take the 10-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