- A control environment is a small number of rules that always operate, not a long document.
- The close calendar is the backbone; without it, close duration is unpredictable.
- Reconcile frequently and the monthly version becomes a formality.
- Exceptions should be routed and resolved, not merely flagged.
- Reporting cadence should match decision cadence, not accounting convenience.
The control environment
A control environment is the set of rules that determine who may commit the company to spending money and how that is evidenced. For most companies below a few hundred people, five controls do almost all the work.
The test of a control is not whether it is documented but whether it operated every time during the period. Auditors ask for evidence of operation; so should you.
- Approval authority defined by amount and cost centre, with named holders.
- Segregation between vendor creation and payment release.
- Verification of bank detail changes through an independent channel.
- Documentation requirements enforced by the system, not by memory.
- Periodic review of access, limits and dormant cards.
The close calendar
The close calendar states what happens on each working day after period end, who owns it, and what it depends on. Writing it down converts close from an event people dread into a sequence that runs itself.
The most valuable column is the dependency: it makes visible which single late input is holding up everything downstream.
- Day 1: cut-off enforced, card and bank feeds confirmed complete.
- Days 2–3: outstanding documentation chased, review queues cleared.
- Days 3–4: reconciliations completed, accruals posted.
- Day 5: review, variance commentary, distribution.
Reconciliation discipline
Reconciliation proves that two independent records agree. Doing it weekly on high-volume accounts keeps each session short and surfaces problems while the context is still fresh in someone's mind.
Unreconciled items should have owners and ages. An item that has been unresolved for three months is not an item — it is a decision nobody has made.
Exception handling
An exception with no owner and no deadline is not being handled.
| Exception | Owner | Target resolution |
|---|---|---|
| Missing documentation | Cardholder, escalating to their manager | Before cut-off |
| Unmatched transaction | Finance operations | Within the weekly reconciliation |
| Policy breach | Cost centre owner | Within the review cycle |
| Suspected duplicate payment | Payables | Before the payment run |
| Dormant card | Finance | Quarterly review |
Reporting cadence
Reporting should match the rhythm at which decisions are actually made. A monthly pack is the wrong instrument for a weekly cash decision, and a daily dashboard is the wrong instrument for a quarterly strategy discussion.
Most operating companies settle on three layers: a weekly cash view, a monthly management pack, and a quarterly review that revisits assumptions rather than just reporting outcomes.
- Weekly: cash position, short-horizon forecast, anything unusual.
- Monthly: results against budget, working capital, commentary on variances.
- Quarterly: assumption review, scenario refresh, structural decisions.
Documentation and retention
Retention periods are set by tax and company law in each jurisdiction, and commonly run to several years. Storage location matters as much as duration: documents that exist only in an individual's inbox are not retained in any meaningful sense.
Decide where documentation lives, make that the only place it lives, and make sure it survives someone leaving the company.
Frequently asked questions
Approval authority by amount, separation of vendor creation from payment, verification of bank detail changes, enforced documentation requirements, and a periodic access review. Five controls that always operate beat twenty that sometimes do.
Weekly for high-volume operating accounts and card programmes, monthly at minimum for everything else. Frequent reconciliation is faster in total than the monthly marathon it replaces.
Usually a controller or finance operations lead. In smaller companies it is often the finance lead directly. The important thing is that it is somebody's named responsibility rather than everybody's assumption.
Improve documentation completeness before period end. In practice that means automatic receipt capture, coding rules for recurring merchants, and clearing review queues weekly rather than at cut-off.
Keep reading
Sources and further reading
Every factual statement on this page is checked against primary documentation. Terms change frequently, so confirm details with the provider before acting on them.
- FASB Accounting Standards Codification Reference point for accrual, expense recognition and close-process statements.
- IRS Publication 463 — travel, gift and car expenses Used for statements about expense substantiation and record keeping in the United States.
- Nacha — ACH Network rules and resources Used for statements about ACH timing and payment rails.
- Brex Support Center Official help documentation, including account access and card administration topics.