Lesson Overview
By now you can run the front of a purchase. You know that procurement spends the Principality's money and is a public trust, you can write a specification, you can source suppliers and compare quotes fairly, and you can raise an order, receive and check the goods, and pay only when the order, the goods-receipt, and the invoice all agree. This lesson is about the part that holds all of that together and joins it to the stores: the administration. It is the least glamorous work in the whole speciality and the most important, because it is the administration, the records kept and the spending watched, that turns a series of separate purchases into an account the force can trust. A purchase that is made well but recorded badly is, to anyone who looks at it later, no better than a purchase made badly.
Two threads run through the lesson. The first is the audit trail: the unbroken chain of records that follows a single purchase from the moment a need is identified, through the order, the goods-receipt, and the payment, and on into the stores ledger, so that any one item of stores can be traced back to the dollar that bought it and any one dollar can be traced forward to the thing it became. The second is the budget: the money the force has been given to spend, and the running watch you keep on how much of it is already committed and how much remains, so that the force never promises money it has not got and never finds at the year's end that it has spent more than it was given. Underneath both sits a control you have met before, the separation of duties, the simple discipline that the person who asks for a purchase is not the only one who approves it and ideally not the one who pays for it or receives it. None of this is complicated. All of it is exact, and exactness is the whole point.
This is the knowledge layer. Reading will teach you what records to keep, how to keep an audit trail unbroken, how to track spend against a budget, and why the duties are split, but the hands-on stores work this administration serves, the signing for receipts and issues, the stocktaking, and the storekeeping that keeps the ledger true, is practised and signed off in person, where supervision allows, on the storehouse floor. By the end you will be able to keep the records that link a purchase from requirement to order to goods-receipt to payment to the stores ledger as one unbroken audit trail, set up and read a simple budget and commitment tracker so you always know what has been committed and what remains, apply the separation of duties as a control against fraud and error, file and reference documents to the standard of basic staff duties, and explain why honest, complete administration is the integrity of the whole supply system.
Key Terms
- Supply administration: the paperwork and record-keeping that ties procurement to stores, keeping the orders, receipts, payments, ledgers, and budget figures that let the force account for what it has bought and what it holds.
- Audit trail: the unbroken set of linked records that lets anyone trace a single purchase from the first requirement through the order, goods-receipt, and payment to the stores ledger, and back again, with nothing missing.
- Requirement: the identified, written need that starts a purchase; the first link in the audit trail.
- Purchase order (PO): the document that records what was ordered, from whom, at what agreed price, and on what terms; the order link in the trail.
- Goods-receipt: the record made on delivery that the right goods arrived in the right quantity and serviceable condition, checked against the order; it feeds the stores ledger.
- Invoice: the supplier's bill, requesting payment for what was supplied.
- Three-way match: the control that an invoice is paid only when the purchase order, the goods-receipt, and the invoice all agree on item, quantity, and price.
- Stores ledger: the running record of what stores are held, kept under LOG 201, into which every goods-receipt and every issue is entered.
- Budget: the sum of money the force, or a part of it, has been allotted to spend over a period; the limit within which all purchasing must stay.
- Commitment: money promised by an order that has been placed but not yet paid; it is spoken for even though it has not yet left the account.
- Committed spend: the running total of money committed by orders placed, whether or not the invoices have been paid yet.
- Remaining budget (uncommitted balance): the budget less everything committed and spent; the money still genuinely free to spend.
- Separation of duties: the control by which the duties of requesting, approving, paying, and receiving a purchase are held by different people, so that no one person can complete a fraudulent purchase alone.
- Reconciliation: checking two records that should agree, such as the budget tracker against the actual account, or the ledger against a physical stocktake, and investigating any difference.
Why administration is the integrity of the system
It is tempting to treat records as the boring tail of the real work, something done grudgingly after the buying and the storing are finished. This is exactly backwards. The records are not the tail of the work; they are the proof that the work was done honestly, and without them the work cannot be trusted at all. A force that buys well but keeps poor records does not know what it has, cannot show where its money went, and cannot tell an honest mistake from a theft. A force that keeps complete and honest records can answer any question put to it, can find any error, and can prove its integrity to the nationals whose money it spends. The administration is not the support to the supply system. In a real sense it is the supply system, because the system is only as good as the account it can give of itself.
Think of what the records have to survive. People move on, memories fade, and the person who made a purchase may be nowhere near when a question is asked about it a year later. The only thing that endures is the written record, and if it is complete, the answer is there for anyone to find, while if it is patchy, the gap cannot be filled by anyone's recollection and the force is simply unable to account for itself. This is why the discipline is exactness rather than effort. A record that is nearly right is wrong, because the value of a record is precisely that it can be relied on without checking, and a record that cannot be relied on is worse than none, because it gives false confidence. The standard, here as in PME 210, is that what is written is true, is complete, and is filed where it can be found.
The audit trail: from requirement to ledger
The heart of supply administration is the audit trail. A single purchase passes through a handful of stages, and at each stage a record is made; the audit trail is the discipline of linking those records together so that the whole chain holds and can be read end to end. You met the stages in the ordering lesson: a requirement is identified and written down; an order is placed and recorded on a purchase order; the goods arrive and are checked and recorded on a goods-receipt; the invoice is matched against the order and the receipt and paid; and the goods-receipt is entered into the stores ledger under LOG 201, so the thing bought now lives in the running record of what the force holds. The audit trail is what makes those five records one story rather than five loose scraps.
The way you link them is by reference. Every record carries its own number and carries the number of the record before it, so that the chain can be followed in either direction. The purchase order quotes the requirement it answers; the goods-receipt quotes the purchase order it fulfils; the payment quotes the order, the receipt, and the invoice it settles; and the ledger entry quotes the goods-receipt that brought the stores in. Follow the references one way and you can start from any item on the shelf and trace it back to the dollar that bought it and the need that justified it. Follow them the other way and you can start from a single line in the budget and trace it forward to the thing it became and the place it now sits. An auditor's first test of any supply system is to pick one item and try to walk the chain; if every reference is there and every record agrees, the system is sound, and if the chain breaks at any link, that break is exactly where trouble hides.
THE AUDIT TRAIL · one purchase, traced from need to shelf
REQUIREMENT "Section needs 200 blankets for a
REQ-26-014 cold-weather relief task, by 14 days"
| (justifies)
v
PURCHASE ORDER "200 wool-blend blankets, Supplier A,
PO-26-031 ----refs---> REQ-26-014 $2,000 agreed"
| (fulfils)
v
GOODS-RECEIPT "200 received, checked, serviceable,
GR-26-048 ----refs---> PO-26-031 13 days, signed"
| (settles)
v
PAYMENT / THREE-WAY "PO + GR + INVOICE INV-7741 all agree:
MATCH ----refs---> PO-26-031, GR-26-048, INV-7741
PAY-26-052 200 @ $10 = $2,000 PAID"
| (records the stock)
v
STORES LEDGER (LOG 201) "+200 blankets IN, ref GR-26-048,
ledger line 0207 balance now 200, location B-3"
READ DOWN: a need became an order, a delivery, a payment, and
stock on a shelf. READ UP from the shelf: every blanket traces
back through a receipt, an order, and a written requirement to
the dollar that bought it. No link missing. The chain holds.
Notice two things about the chain. First, no link may be skipped. There is no honest purchase that has an order but no requirement behind it, or stock on the shelf with no goods-receipt that brought it in, or a payment with no order and receipt to match. A missing link is not a tidy gap; it is the precise shape of how money and stores go astray, because what cannot be traced cannot be checked. Second, the trail is built as you go, not assembled afterwards. Each record is made at the moment of the event it records, the receipt when the goods arrive, the ledger entry when they are taken on charge, while the facts are fresh and the person who knows them is present. A trail reconstructed weeks later from memory is not an audit trail; it is a guess written down, and it has none of the value of the real thing.
Filing and referencing: keeping the trail findable
A complete trail that cannot be found is no better than an incomplete one, so the second half of the discipline is filing. The principle is the same one taught in PME 210: a record exists to be retrieved, so it must carry a clear reference, be filed in a known and consistent place, and be cross-referenced to the records it links to. For a small force this need not be elaborate. A simple, consistent numbering scheme, a register that lists what has been raised, and one folder per purchase that gathers the requirement, the order, the receipt, the matched invoice, and the proof of payment together, is enough to keep any purchase one step from being found.
Keep the scheme plain and keep it consistent, because a system only half-followed is worse than a simple one followed every time. Number records in a way that sorts and that shows the year, so that a glance tells you what a document is and when it was raised. Hold the documents of a purchase together, whether in a physical folder or a digital one, so that nobody hunting for the goods-receipt has to search four separate places. And keep a register, a single running list of the requirements, orders, receipts, and payments raised, so that you can see at once whether a purchase has reached the stage it should have and so that nothing started is quietly forgotten before it is finished. The register is also your early warning: an order placed weeks ago with no goods-receipt against it is either a late delivery to chase or a record not yet made, and either way it is something you want to see.
The budget: spending within what you were given
Records account for what has been bought; the budget governs what may be bought at all. A budget is simply the sum of money the force, or a section or a task, has been allotted to spend over a period, a quarter, a year, or a single operation. It is a limit and a plan at once: a limit, because purchasing must stay inside it, and a plan, because the figures within it say what the money is meant to do. The whole point of having a budget is that the force decides in advance, openly, how its limited money will be spent, rather than spending until it runs out and discovering the shortfall too late to do anything about it. Spending to a budget is not a constraint on doing the job; it is part of doing the job honestly, because the money is finite and someone else's, and a budget is how a force keeps faith with the people who gave it.
The single most important idea in budgeting, and the one most often missed by the inexperienced, is the difference between money committed and money spent. Money spent has already left the account; you can see it gone. Money committed is money you have promised by placing an order, but which has not yet been paid, because the goods have not yet been invoiced or the invoice not yet settled. To watch only what has been paid is to flatter yourself with a balance that is not real, because the orders you have already placed will have to be paid, and the money for them is gone in every way that matters except that it has not yet physically left. The remaining budget that actually matters is the budget less everything committed and everything spent: the money still genuinely free. A buyer who tracks only payments will keep spending against money that is already promised, and will overcommit the budget without ever seeing it happen until the invoices land.
So the rule is: count a commitment the moment you place the order, not when you pay it. The instant a purchase order goes out, the money it promises is committed and must come off the free balance, even though no dollar has yet moved. Track it that way and your remaining figure is the truth, the money you could still spend without breaking the budget. Track it any other way and the remaining figure is a comfortable fiction.
The commitment tracker: knowing what remains
The tool that makes this concrete is a commitment tracker, sometimes called a commitment register or a budget ledger. It is nothing more than a running list of every order placed against a budget, with its committed amount and, when it is paid, its actual cost, and a running balance of what remains. It need not be elaborate; a single sheet or a simple spreadsheet does the work, and what matters is not its sophistication but that it is kept up to the minute and that the remaining balance it shows is the true free balance after everything committed. Set it up at the start of the period with the budget at the top, and from then on every order, the moment it is placed, goes on as a commitment that reduces the remaining balance at once.
Read the tracker like this. The budget is what you were given. The committed column adds up every order placed but not yet paid; that money is spoken for. The spent column adds up every order now paid; that money is gone. The remaining balance is the budget less both, and it is the only figure that tells you the truth about what you can still buy. When a commitment becomes a payment it simply moves from committed to spent; the remaining balance does not change at that moment, because the money was already off the free balance from the day the order was placed, which is exactly the point. Before you commit to any new purchase, you check the remaining balance, and if the purchase would not fit, you do not place it, you take it to whoever holds the budget for a decision, because committing money the budget has not got is precisely the failure the tracker exists to prevent.
COMMITMENT TRACKER · cold-weather relief task (illustrative, USD)
BUDGET ALLOTTED FOR TASK ............................ $5,000
+--------+----------------------+-----------+--------+-----------+
| Ref | What | Committed | Spent | Remaining |
+--------+----------------------+-----------+--------+-----------+
| - | Opening balance | | | 5,000 |
| PO-031 | 200 blankets (A) | 2,000 | | 3,000 |
| PO-033 | 50 hot-water bottles | 400 | | 2,600 |
| PO-035 | Flasks + transport | 750 | | 1,850 |
+--------+----------------------+-----------+--------+-----------+
| ...later, invoices arrive and are paid (3-way match): |
+--------+----------------------+-----------+--------+-----------+
| PO-031 | blankets PAID | | 2,000 | 1,850 |
| PO-033 | bottles PAID | | 400 | 1,850 |
+--------+----------------------+-----------+--------+-----------+
| TOTALS | committed + spent | 750 | 2,400 | |
+--------+----------------------+-----------+--------+-----------+
REMAINING (free to spend) = 5,000 - 750 committed - 2,400 spent
= $1,850
KEY POINT: PO-035's $750 is still only COMMITTED (ordered, not
yet paid), but it ALREADY came off the remaining balance the day
the order went out. When a PO is PAID it moves committed -> spent;
the remaining balance does NOT drop again, because the money left
the free balance back when the ORDER was placed. Track payments
only and you would wrongly think $2,600 was free, and overspend.
A word on what the tracker is for, beyond not running out. Kept honestly, it answers in one line the questions a commander or an auditor will ask: how much of the budget is gone, how much is promised, and how much is genuinely left. It lets the force plan, because a glance shows whether a new task can be afforded from what remains or whether more money must be sought first. And it is itself part of the audit trail, because each line references the purchase order behind it, so the budget figures and the purchase records tie together and can be reconciled. At the end of the period you reconcile the tracker against the actual account, the real record of money in and out, and any difference is investigated, because a tracker that does not agree with the account has an error in one of them and you must know which.
Separation of duties: the control against fraud and error
Records and budgets account for purchasing; separation of duties is the control that keeps purchasing honest in the first place. The idea is simple and you have met it in CIS 220, where the same principle protects records and access: no single person should be able to complete a sensitive action alone, because a single hand on the whole chain is a single point at which fraud can happen unseen and at which an honest error has nobody to catch it. In purchasing, the sensitive chain is request, approve, pay, and receive, and the control is that these duties are held by different people. The person who asks for a purchase should not be the only one who approves it, and ideally not the one who pays for it or receives the goods.
See why this works by imagining it failing. If one person could request a purchase, approve their own request, place the order, receive the goods, and authorise the payment, then that person could invent a supplier, pay public money to it, and sign off on goods that never arrived, and nobody would ever be positioned to notice, because every check was in the same hand that committed the fraud. Now split the duties. The requester writes the need but cannot approve it; an approver, who is not the requester, must agree it before any order is placed; the goods are received and checked by someone other than the requester, so the receipt is independent evidence that real goods arrived; and the payment is released by someone who confirms the three-way match rather than simply being told to pay. Fraud now needs not one dishonest person but several acting together, which is far harder and far more likely to be exposed, and an honest mistake by any one person is caught by the next pair of eyes rather than passing straight through. The separation does not assume anyone is dishonest. It simply removes the opportunity, and removing the opportunity protects the honest as much as it deters the dishonest, because a person who cannot complete a purchase alone can never be wrongly suspected of having done so.
SEPARATION OF DUTIES · one purchase, four roles, not one hand
+-----------+ +-----------+ +-----------+ +----------+
| REQUEST | --> | APPROVE | --> | RECEIVE | | PAY |
| the need | | the spend | | & check | | on 3-way |
| | | | | the goods | | match |
+-----------+ +-----------+ +-----------+ +----------+
| Corporal | | Sergeant | | Storekeep | | Budget |
| (writes | | (agrees, | | -er (not | | holder |
| the req) | | budget | | the | | (confirms|
| | | checked) | | requester| | PO+GR+ |
| | | | | | | invoice)|
+-----------+ +-----------+ +-----------+ +----------+
\ | | /
\_________ DIFFERENT PEOPLE, each checking the last _/
No one person closes the whole loop. To push a false purchase
through, several would have to collude, which is hard and exposed.
An honest error by any one is caught by the next. The control
protects the honest by making sure no one can act alone and so
no one can be wrongly blamed for acting alone.
For a very small force the SAME person may hold two adjacent roles
from necessity, but NEVER request-and-approve-own and NEVER the one
who both receives and pays. Where roles must double up, the budget
holder or QM NCO reviews, so a second pair of eyes always exists.
For a small, young force this raises a fair question: what if there are simply not enough people to fill four separate roles? The honest answer is that you separate the duties as far as your numbers allow and never collapse the two pairings that matter most. One person may, from necessity, both request and receive, or both approve and hold the budget, but no person should ever both request a purchase and approve their own request, and no person should ever both receive the goods and release the payment, because those two pairings are the ones that let a single hand complete a fraud. Where numbers force two roles onto one person, the answer is an independent review: the Quartermaster NCO or the budget holder looks over the purchase afterwards, so that a second pair of eyes always exists even when a second person was not available at the moment. The principle survives a small force. It just has to be applied with judgement rather than abandoned because the textbook arrangement will not fit.
In Practice: A storekeeper administers a relief purchase from need to ledger
Corporal Mensah, who sourced the blankets in the last task, is now keeping the books for a small cold-weather relief effort, with a task budget of five thousand dollars. Her job this week is not to buy so much as to make sure that everything bought is recorded, that the trail holds, and that the budget is watched, so that when the effort is over the force can show exactly where every dollar went and account for everything it now holds.
She begins by setting up her commitment tracker with the five thousand dollars at the top and the remaining balance, for now, the same. When the blanket order goes out at two thousand dollars, she enters it at once as a commitment, and the remaining balance drops to three thousand, even though no money has yet been paid, because the order has promised it. A second order for fifty hot-water bottles at four hundred dollars and a third for flasks and transport at seven hundred and fifty dollars follow the same way, each committed the day it is placed, and her remaining balance now reads eighteen hundred and fifty dollars: the truth of what is still free, not the flattering figure she would see if she counted only what had been paid. When a section commander asks whether the effort can stretch to a delivery of batteries, she does not guess; she reads the tracker, sees that the batteries would fit within the remaining balance, and confirms it, and had they not fit she would have said so and taken it to the budget holder rather than commit money the budget had not got.
She is equally careful with the trail. Each purchase has a folder: the written requirement that justified it, the purchase order that placed it, the goods-receipt made when the storekeeper, who is not herself, checked the goods in, and, when the invoice comes, the three-way match and the proof of payment. The blankets, when they arrive, are checked and receipted by the storekeeper, entered on the goods-receipt, and taken on charge in the stores ledger under LOG 201, the goods-receipt number quoted on the ledger line so the two records tie. Mensah keeps the roles apart deliberately: she requested and tracks the spend, but a sergeant approved each order, the storekeeper received the goods, and the budget holder confirms each three-way match before paying, so that no single person, herself included, ever closes the whole loop. When the effort ends, she reconciles the tracker against the actual account and the ledger against a quick physical count of what is left, finds both agree, and is able to lay before her commander an unbroken trail from each written need to each item on the shelf and each dollar of the budget accounted for. The relief was delivered, and the force can prove, to anyone who asks, that it was delivered honestly.
Check Your Understanding
- A buyer tells you the task budget is fine because only $2,400 of the $5,000 has actually been paid, so $2,600 is left. Three orders totalling $750 have been placed but not yet invoiced. Explain why the buyer's figure is wrong, state the true remaining balance, and explain the difference between money committed and money spent.
- Walk the audit trail for a single purchase from requirement to stores ledger, naming each record in order and saying what reference links it to the one before. Then explain what an auditor learns by finding the chain unbroken, and what a missing link would suggest.
- In a small section there are not enough people to give the request, approve, receive, and pay duties to four different people. Which two pairings must never be held by one person, why are those the dangerous ones, and what should be done where two roles unavoidably fall to the same person?
Reflection (write a short paragraph): Think about a time you, or a group you were part of, spent shared or limited money, a household, a club, a trip, without keeping a running track of what was already promised as well as what was already paid. What happened when the bills came in, and how would a simple commitment tracker, counting money the moment it was promised rather than only when it left, have changed what you knew and the decisions you made?
Summary
- Supply administration, the records kept and the spending watched, is not the tail of the buying work but the integrity of it; a purchase made well and recorded badly cannot be trusted, because the only thing that endures is the written record.
- The audit trail links a single purchase from requirement to purchase order to goods-receipt to payment to stores ledger, each record carrying its own reference and the reference of the one before, so any item traces back to the dollar that bought it and any dollar forward to the thing it became. No link may be skipped, and the trail is built as you go, not reconstructed afterwards.
- File and reference to the PME 210 standard: a clear, consistent numbering scheme, one folder per purchase, and a register of what has been raised, so any record is one step from being found and nothing started is quietly forgotten.
- A budget is the money allotted to spend over a period, a limit and a plan at once. The key idea is the difference between money committed (promised by an order placed) and money spent (already paid); the true remaining balance is the budget less both, and counting a commitment the moment the order goes out is the only way to keep that figure honest.
- A commitment tracker is a running list of orders against a budget with committed and spent columns and a true remaining balance; kept up to the minute it tells the force in one line what is gone, what is promised, and what is genuinely free, and it ties to the audit trail and is reconciled against the actual account.
- Separation of duties splits request, approve, pay, and receive among different people so that no one hand can complete a purchase alone; it protects the honest as much as it deters the dishonest. Never let one person both request and approve their own request, or both receive and pay; where a small force must double roles, an independent review supplies the missing pair of eyes.
- Builds on Lesson 01 · Procurement as a Public Trust, Lesson 02 · Identifying and Specifying a Need, Lesson 03 · Sourcing, Quotes, and Fair Selection, and Lesson 04 · Ordering, Receiving, and Paying (the purchase order, goods-receipt, and three-way match this lesson records and tracks). Leads into Lesson 10 · Ethics, Audit, and Stewardship. Connects to LOG 201 · Stores, Equipment, and Accountability (the stores ledger every goods-receipt feeds), PME 210 · Basic Staff Duties and Written Orders (records, referencing, and filing discipline), CIS 220 · Identity, Access, and Records Security (separation of duties), and LDR 420 · Command Responsibility and Ethical Leadership (honest stewardship of the Principality's money).
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia