Module 01 · Control Foundations and Segregation of Duties

Handling Emergency Spending Without Losing Control

Every approval rule meets a Saturday breakdown eventually. Write the exception down, and it stays an exception instead of quietly becoming the process.

6 min readLesson 5 of 5 in this moduleUpdated 2026-09-22

Key takeaways

  • Define in writing what qualifies as an emergency — usually safety, an outage that stops trading, or a legal deadline.
  • Urgency caused by poor planning is not an emergency; naming that difference is most of the control.
  • Set an emergency ceiling: a value above which even a genuine emergency needs a call to the owner, not just a later note.
  • Require retroactive sign-off within 24 hours, with a short written reason — that is what keeps the exception reviewable.
  • Log emergency purchases in one place and review the log monthly; a pattern means a planning problem, not bad luck.
  • If more than a small fraction of spending goes through the emergency route, the normal limits are set wrong.

The compressor fails at 8pm on a Saturday. The van needs a tyre before a delivery run that leaves at six tomorrow morning. The only approver is on a flight. Every approval matrix meets this situation, and how a business handles it decides whether the matrix survives the year.

The failure mode is not the purchase itself — it is what happens next. An unwritten exception is made, nothing goes wrong, and it is made again the following month for a slightly weaker reason. Within a quarter, "emergency" has quietly become the normal route for anything inconvenient, and the approval rule applies only to purchases nobody minded waiting for.

An emergency spending rule fixes this in three parts: a written definition of what qualifies, a ceiling above which someone must be reached anyway, and a retroactive sign-off within 24 hours. The exception stays available and stays visible.

Define the word before you need it

Write the definition while nothing is on fire. Most small businesses can use some version of this list:

Qualifies as an emergency

  • A safety risk to staff, customers, or the public.
  • A failure that stops the business from trading — power, refrigeration, a vehicle needed for today's deliveries.
  • A situation where waiting causes physical loss: stock that will spoil, damage that will spread.
  • A legal or regulatory deadline that falls before the next approval cycle.

Does not qualify

  • A price that expires tonight. A discount is not an emergency; it is a negotiation.
  • Something that was foreseeable and simply was not ordered in time.
  • A purchase that could wait until Monday morning without any real consequence.
  • A request that is urgent for the supplier rather than for you.

That second list does most of the work. The distinction is not between calm and urgent — it is between could not have been planned and was not planned.

The most common abuse is poor planning, not dishonesty

Somebody forgets to reorder, notices on Friday, and calls it an emergency because that is the only route that moves fast enough. Nothing dishonest happened, but the control was bypassed and the underlying planning problem stays invisible. This is exactly what the monthly log is for.

Set a ceiling, not just a process

An emergency justifies bypassing the waiting, not the amount. So the rule needs two bands:

ValueWhat happens
Below the emergency ceilingBuy it, keep the receipt, log it, get retroactive sign-off within 24 hours
Above the emergency ceilingReach the owner by phone first, whatever the hour — approval may be verbal, but it happens before the commitment

Pick the ceiling deliberately. A useful rule of thumb: set it at the point where the cost of being woken up is clearly smaller than the cost of the wrong decision. Write down both the number and the phone route, so nobody has to decide at 2am whether calling is appropriate.

The 24-hour retroactive sign-off

Within one working day, the person who made the purchase submits: what was bought, from whom, the amount, the receipt, and one line on why it could not wait. The approver signs it — or does not.

The window matters. A same-day review is a genuine review: the facts are fresh, the alternative options are still obvious, and a "this could have waited" response lands while it can change behaviour. The same conversation three weeks later, attached to an invoice, is a formality nobody learns anything from.

A rejected retroactive approval is not a punishment

It is a signal that the decision was outside the rule — logged, discussed once, and used to fix either the planning or the limit. If a retroactive approval is never refused, it has become a rubber stamp and stopped being a control.

Keep one log, and read it monthly

Emergency purchases need to be visible together, not scattered through the ledger. One simple log — date, item, supplier, amount, who authorised it, reason — reviewed monthly, answers three questions your normal reports will not:

  • Is the same emergency recurring? A part that fails quarterly is a maintenance decision, not an emergency.
  • Is one person using the route more than everyone else? Usually a planning or workload problem in their area.
  • Are the normal limits too low? If routine purchases keep arriving through the emergency door, the door is being used as a shortcut around a limit that does not fit the business.

A reasonable target is that emergency spending stays a small fraction of total purchases — a handful of transactions a quarter for most small businesses. There is no universal number, but a route that carries a meaningful share of your spending is no longer an exception route.

Doing this in Reyuko

Reyuko does not have a separate "emergency purchase" workflow — no accounting package can decide whether your Saturday breakdown qualified. What it can do is make the review possible: every purchase and payment lands in the same ledger with its date, supplier and amount, so pulling the month's unusual purchases for your log review is a filtered list rather than a reconstruction from receipts in a drawer.

Keep the emergency log itself outside the ledger — a shared sheet is fine. The ledger tells you what was spent; the log tells you why the normal rule was bypassed, and only the second one teaches you anything.

Write the emergency rule
  1. Define, in writing, what qualifies — and include the list of what does not.
  2. Set an emergency ceiling and the phone route for anything above it.
  3. Require retroactive sign-off within 24 hours, with a one-line reason.
  4. Keep every emergency purchase in a single log with six fields.
  5. Review the log monthly, and fix the planning or the limit when a pattern appears.

With the principles and the approval rules in place, the next module turns them into the three written routines that carry them day to day — starting with petty cash.

Frequently asked questions

What counts as an emergency purchase?

Spending that cannot wait for normal approval without causing harm: a safety risk, an outage that stops the business trading, a failure that will damage stock or equipment, or a legal or regulatory deadline. A supplier's discount expiring tonight and a job someone forgot to order for are not emergencies, however urgent they feel.

Should there be a spending ceiling even for emergencies?

Yes. Set a value above which someone must reach the owner by phone regardless of the hour — the emergency route covers speed, not unlimited value. Below the ceiling, the purchase proceeds and gets signed off retroactively; above it, a conversation happens first, even a short one.

How quickly should an emergency purchase be approved after the fact?

Within 24 hours, or the next working day where the emergency falls over a weekend. The point of a short window is that the details are still fresh and the decision can genuinely be reviewed rather than rubber-stamped weeks later alongside an invoice.

What should the emergency log record?

Date, what was bought, from whom, the amount, who authorised it, and one line on why it could not wait. Six fields on one row is enough — the log exists so patterns become visible, not to create paperwork.

What does it mean if we use the emergency route often?

Almost always that something upstream is wrong: approval limits set too low, an approver who is unreachable too often, or stock reordering that runs too late. Frequent emergencies are a symptom to investigate, not a category of spending to accept.

Keep the exceptions where you can see them

Reyuko records every purchase and payment in one ledger, so an after-the-fact review of unusual spending is a filtered list rather than a hunt.

Download Reyuko freeSee what's included