How Should Revolving Funds and IOUs Be Controlled Across Remote Operating Sites?

Introduction

Every asset-heavy enterprise has a cash problem it does not talk about: the several million dollars spread across dozens or hundreds of site-level funds at generation plants, substations, depots and remote project camps. Each was opened for a legitimate reason. Few are governed with the rigour applied to a purchase order.

The fund lifecycle spans setup, disbursement, IOU issuance, liquidation, replenishment and closure, and in legacy portals every stage is a form. Forms capture data; they enforce nothing. A fund’s declared purpose is recorded once and never checked again, IOUs with two-day clocks age for months, and closing a fund means typing a treasury acknowledgement receipt number into a field and hoping it matches.

This article covers revolving funds, custodian accountability and IOU governance at remote sites. For the administrative burden of individual employee claims, see our companion piece on manual petty cash management challenges.

Baseline guidance on cash controls and misappropriation risk appears in the ACFE Report to the Nations, the ACFE fraud resource library and AICPA internal control resources.

What Is the Difference Between Petty Cash Funds, Revolving Funds and IOUs?

A petty cash fund is a small imprest float for minor incidentals. A revolving fund is a larger site-level fund spent against a declared corpus of permitted expense types and replenished back to its approved balance. An IOU, or temporary advance, is cash released from either fund to a named individual before the expense occurs, creating an employee receivable that must be liquidated with receipts inside a short window.

What Does a Controlled Revolving Fund Lifecycle Look Like?

A controlled revolving fund lifecycle is a state machine, not a sequence of forms. Each state has mandatory entry and exit conditions, and the fund cannot advance until the current one is complete and evidenced. In legacy portals every state is an independent form that can be submitted regardless of what came before.

How Do You Enforce a Fund’s Declared Corpus at Liquidation?

Enforce corpus by converting the fund’s declared purpose from a free-text sentence into structured, machine-checkable rules at setup, then validating every liquidation line against those rules automatically. In most legacy systems the corpus is captured once and never referenced again, so custodians are checked only if a reviewer remembers to look. This is the highest-value control fix in site fund management: cheap to implement, and it closes a gap internal audit reliably finds.

Instead of a purpose reading “operational expenses for plant maintenance and site logistics”, the fund record carries permitted categories, mapped GL accounts and per-category caps.

Fund: Plant Site Revolving Fund - Entity 042
Approved balance: USD 25,000
Permitted categories:
  - Fuel and lubricants        GL 6210   cap USD 1,500 / txn
  - Local freight and hauling  GL 6240   cap USD 1,000 / txn
  - Permits and statutory fees GL 6810   cap USD   800 / txn
  - Emergency spare parts      GL 6120   cap USD 2,000 / txn
Blocked categories: entertainment, staff welfare, capex
Liquidation rule: reject if category not in permitted list

A line coded to staff entertainment is then rejected at submission with a specific reason, not discovered six months later in a sample-based audit. The logic behind real-time budget validation on expense requests applies directly: the check moves from post-hoc review to point of entry.

How Should Custodian Accountability and IOU Clocks Be Enforced?

Custodian accountability should be a signed, digitally stored undertaking naming one accountable individual per fund, linked to the fund record and visible to HR so resignation or transfer automatically triggers a fund clearance before final pay is released. Many groups already capture such an undertaking — as a paper form filed locally. The weakness is the manual linkage between fund register, custodian record and HR offboarding.

How Do You Replenish, Close and Right-Size Site Funds?

Replenishment should trigger automatically when the fund falls below a defined threshold — commonly 30 to 40 percent of approved balance — batching every liquidated disbursement since the last cycle into one evidenced request. A site that made 47 disbursements in a fortnight submits one replenishment with 47 lines, not 47 requests. That requires receipt capture at the moment of spend, working offline, as covered in our piece on AI OCR expense receipt capture for energy and utilities. Manual routing stretches the cycle to three to six weeks, and sites respond rationally by requesting oversized funds as a buffer.

Model the numbers for your own estate with a savings calculator; the broader financial framing sits in our finance automation ROI guide for CFOs.

How to Automate Revolving Fund and IOU Controls: A Step-by-Step Implementation Guide

Multi-entity groups typically move site funds from form-driven administration to enforced control over 8 to 16 weeks, in this sequence.

1. Inventory every fund across the estate. Build one register of every petty cash and revolving fund at every site and entity, capturing approved balance, custodian, entity, cost centre, declared corpus and last reconciliation date.

2. Codify the corpus as structured rules. Convert each fund’s free-text purpose statement into permitted expense categories, GL accounts and per-transaction caps that a system can validate, rather than a paragraph a reviewer must interpret.

3. Define the fund lifecycle as a state machine. Model setup, disbursement, IOU issuance, liquidation, replenishment and closure as explicit states with mandatory entry and exit conditions, so no fund advances with an incomplete prior state.

4. Digitise custodian accountability undertakings. Capture signed undertakings electronically, attach them to the fund record, and integrate with HR so resignation or transfer raises a fund clearance requirement before final pay is released.

5. Enforce IOU clocks and caps at submission. Configure the liquidation window, countdown reminders, escalation path, per-transaction cap and a block on new IOUs while one is open, enforced at request rather than reviewed after the fact.

6. Enable offline mobile capture at site. Deploy mobile capture with OCR so custodians and field crews photograph receipts and record disbursements without connectivity, syncing with timestamps and geolocation when the device reconnects. Adoption depends on this working on the devices field staff already carry, as covered in our piece on mobile accessibility limitations for field staff.

7. Automate replenishment and ERP posting. Trigger replenishment at a defined balance threshold, batch liquidated disbursements into one request, and post approved entries to the ERP against the correct entity, cost centre and GL account. Native connectors to platforms such as SAP remove the re-keying step.

8. Instrument closure, ageing and float dashboards. Require a matched treasury acknowledgement receipt for closure, and publish real-time dashboards showing fund balances, IOU ageing, corpus exceptions and idle float by site and entity.

How Peakflo Governs Site Funds and IOUs

Peakflo’s travel and expense module models a site fund as a governed lifecycle object, so setup, disbursement, IOU, replenishment and closure each carry their own enforced controls.

Fund replenishment and returns settle through end-to-end payment automation, with balances posted via your ERP integrations and policy applied through agentic spend management. Review the fund lifecycle on the product tour or request a demo.

Our Verdict: Enforced Fund Lifecycles Beat Better Forms, Every Time

Site cash will not disappear from asset-heavy operations, and the answer is not a better-designed form. The controls that matter — corpus validation, IOU clocks, custodian accountability, treasury-matched closure — are rules a system can enforce deterministically and that humans reliably forget. Moving them from policy documents into an enforced lifecycle is a modest technical change with a disproportionate control and working-capital return. Sector and forensic context is available from Deloitte’s power and utilities outlook and PwC’s forensics practice.

Peakflo’s approach to business travel and expense management treats site funds, advances and reimbursements as one governed lifecycle rather than three disconnected modules, with AI agentic spend management applying corpus, cap and duplicate checks at submission across every entity.

Best for

• Multi-entity energy, utilities and infrastructure groups running funds at 10 or more dispersed sites.
• Organisations where IOUs are material and liquidation discipline is weak.
• Shared-services finance functions needing one fund register across many legal entities.
• Groups facing audit findings on cash controls or unliquidated advances.

Not recommended if

• Your operations are single-site with one small petty cash float and monthly reconciliation already works.
• Card acceptance covers effectively all spend and cash disbursement is negligible.
• You are mid-ERP-migration and cannot commit to a stable chart of accounts for 6 to 9 months.

Our Recommendation: Start with the fund inventory and corpus codification in steps 1 and 2 before selecting any platform. Groups that reach vendor evaluation with a clean register and structured corpus rules configure in weeks; groups that arrive with free-text purpose statements spend the first two months of implementation doing that work anyway, under time pressure.

Conclusion

Revolving funds and IOUs at remote operating sites are not a housekeeping matter. They represent real cash, real employee receivables and a control surface auditors examine closely — governed, in most multi-entity enterprises, by forms that record intent without enforcing anything.

The corrective is structural. Define the fund lifecycle as a state machine with mandatory conditions at each transition. Encode the corpus as rules validated at liquidation instead of a sentence a reviewer might recall. Give IOUs an automated clock and a real escalation path. Tie custodian accountability to HR offboarding. Prove closure with a matched treasury acknowledgement rather than a keyed number.

Groups that make this shift typically release 25 to 40 percent of site float back to working capital, compress replenishment from weeks to days, and eliminate the audit finding that says a control was documented but never operated. To see how this works across a multi-entity estate, request a demo.

Frequently Asked Questions

What is a revolving fund?

A revolving fund is a fixed sum of cash advanced to a site or department custodian, spent against a declared corpus of permitted expense types, then replenished to its original balance after liquidation.

What is the difference between a revolving fund and petty cash?

Petty cash is a small imprest float, typically USD 200 to USD 2,000, for minor incidentals with per-transaction caps of a few hundred dollars.

What is an IOU in expense management?

An IOU, or temporary advance, is cash released from a site fund to a named employee before the expense occurs, against a promise to liquidate with receipts.

Why do remote operating sites still need physical cash?

Remote plants, substations, depots and project sites operate where card acceptance is thin, connectivity is intermittent and many counterparties are cash-only micro-vendors such as boat operators, local haulers, permit offices and informal labour.

What is a fund corpus and why does it matter?

A fund corpus is the declared nature of expenses a fund may be used for, agreed at fund setup.

How long should an IOU liquidation window be?

Leading practice is 2 to 5 working days from the nominated date of use, with automated reminders at 50 and 100 percent of elapsed time and escalation to the custodian and site controller on breach.

Should a custodian sign a fund accountability undertaking?

Yes. It is a signed acknowledgement that the custodian is personally accountable for the fund balance and authorises recovery from final pay if the fund is not returned on resignation or transfer.

How should revolving fund replenishment work?

Replenishment should trigger automatically when the fund falls below a threshold, typically 30 to 40 percent of the approved balance, batching all liquidated disbursements since the last cycle into a single request.

How do you prove a fund has been properly closed?

Closure requires three matched artefacts: a final liquidation covering every open disbursement and IOU, evidence that residual cash was returned to treasury, and a treasury acknowledgement receipt number tying the returned amount to a bank or cashier record.

How much cash sits idle in site funds across a multi-site enterprise?

Multi-entity asset-heavy groups commonly find that 25 to 40 percent of total site fund float is structurally idle because fund sizes were set years earlier and never revisited.

Does petty cash automation work without reliable internet at site?

Yes, if the platform supports offline mobile capture. Custodians and field staff record disbursements and photograph receipts without connectivity, and records sync with full timestamps and geolocation when the device reconnects.

What does revolving fund and petty cash automation typically cost?

Spend management platforms covering site funds, advances and expenses in multi-entity enterprises typically range from USD 8 to USD 25 per active user per month, with a multi-entity rollout spanning 8 to 16 weeks.