A company's journal entry review kept failing on timeliness. When the team pulled the data, most manual entries were being posted in the last two days of the close, and one reviewer was approving several hundred of them in about a day and a half. Nobody was being careless. The review simply had no time to be a review. Moving recurring accruals to standard templates posted earlier in the close cut the end-of-period volume sharply, and the control started passing without anyone working harder.
When the Process Is the Control Problem
Some controls fail because the process around them makes them hard to perform.

The control was well designed. The reviewer knew the work. It still failed three quarters in a row.
When that happens, the usual response is to look at the person. More training, a reminder memo, maybe a second reviewer. Sometimes that is the right call. More often the control is failing because of what surrounds it: the timing, the handoffs, the volume, and the workarounds people have built to get through the week.
The reviewer was never the problem.
The calendar was.
When Good Controls Keep Failing
A control is a step inside a process. If the process gives that step no room, the control will be performed in a hurry, partly, or after the fact, no matter how well it reads on paper.
The same control fails under different people.
Failures cluster around month-end and quarter-end.
Evidence exists, but it is dated after the period closed.
The people doing it call it "something we fit in."
Look for the Queue
In most finance processes, work does not arrive evenly. It comes in waves, and the biggest wave usually lands just before a deadline. Review controls tend to sit at the end of the line, which means they take the full force of it.
Find where work piles up and you will usually find the controls that are failing.

Ports plan for the ships that arrive all at once. Most finance processes do not.
Handoffs, Workarounds and Spreadsheets
Queues
Work arrives in waves, and review controls sit at the end of the line, taking the full force of the deadline.
Handoffs
Every time work moves between teams or systems, each side may assume the other one checked it.
Workarounds
When a system falls short, a spreadsheet fills the gap. Over time it becomes the real process, and the control still points at the old one.
Redesign Before You Retrain
Retraining is the default response to a failed control because it is quick and it feels like action. Before reaching for it, a few questions are worth asking:
The answers often point to a change in timing, templates or system configuration that makes the control easier to perform well. That kind of fix tends to last longer than a training session.
People rarely fail a control on purpose. Usually the process left them no room to do it well.
The Bottom Line
A control that keeps failing is often telling you about the process around it. Find the queue, the handoff or the workaround, and fix that first. The control usually follows.
Ask about the flow
- When does the work actually arrive, and how much of it arrives at once?
- What does the person performing the control need, and when do they get it?
- Where does information change hands, and who checks it on each side?
- Is there a spreadsheet or side process doing the real work?
- Could the control move earlier, or could some of the volume move away from the deadline?
Start a Conversation
Have a Specific Problem to Work Through?
An aging finding, control issue, documentation gap, or workstream short on capacity is enough of a starting point. Tell us what is happening and what you need to be true at the end.
Tell us what is stuck, what changed, or what deadline is driving the need. We can determine whether BPS Advisory Group is the right fit and what a sensible scope would look like.
Or write to info@bpsadvisoryus.com