The date and the evidence
When a management team asks for accounts sooner, finance should take the request seriously. An earlier view can change a decision while there is still time to act. But the request becomes dangerous when the completion date is allowed to stand for the quality of the account. I have seen a reporting timetable improve while the explanation of unresolved balances became less visible. My argument is that a faster close should carry a clearer exception record, because speed makes the boundary between established evidence and pending work more consequential.
At Lurenshan Commercial Bank, our monthly management close took twelve working days. The executive team wanted seven. The existing process contained 4,800 reconciliation items older than our internal review window. They were not all equally material or equally difficult, and counting them did not tell us their combined financial significance. It did tell us that a deadline announcement alone would not repair the process. We needed to understand why the work had accumulated before deciding how much of it could safely move earlier.
I began by asking what the earlier account was supposed to help executives decide. Some information could be available sooner through better source records and clearer ownership. Other figures depended on estimates that required review. Still other matters would remain unresolved at the management reporting date and needed an explicit treatment. This classification mattered more than a general demand for urgency. It gave colleagues a way to discuss the quality of a specific balance rather than defend their department's reputation for meeting deadlines.
The distinction also changed the technology discussion. A workflow could route an exception and record its age, but it could not supply a missing explanation simply by moving the item to a different status. We asked system colleagues to support the evidence trail and the responsible person's review. We did not ask them to make the dashboard look complete. A closed task without a satisfactory accounting explanation would have been a presentational improvement with little value to the executive reading the result.
Make unfinished work legible
An exception register is useful only if it supports judgement. A long list can become a hiding place of its own. We grouped items by cause, age and significance, identified an accountable owner and recorded the next action. Where a balance required a management estimate, the paper distinguished that estimate from a completed reconciliation. The reader could then understand what had been determined and what still depended on further work. I wanted the register to make uncertainty discussable without implying that every unresolved item had the same consequence.
The team also needed a route for raising matters that did not fit the expected timetable. A junior accountant should not have to choose between missing a deadline and describing a problem too confidently. We made it possible to bring a significant concern to the controller with the evidence available, the unanswered question and the proposed treatment. This did not remove accountability for preparation. It made escalation part of a controlled close rather than a personal admission of failure after the deadline had passed.
There was resistance from branches asked to correct source records while handling their normal work. Some managers saw the programme as a central finance project and wanted central finance to carry all of its cost. I accepted responsibility for the reporting process, but I could not accept responsibility for facts that only the originating team could establish. We agreed specific work allocations and retained overdue actions in executive reviews. That made the resource consequence visible instead of allowing a central instruction to become an unacknowledged local burden.
After twelve months, we were producing the management close in seven working days, and the aged-item count had fallen to 430. Those figures describe a meaningful change, but they do not describe perfection. The remaining items continued to have owners, values and next actions. We reviewed adjustments made after the initial close because a shorter timetable could otherwise have displaced effort into the following period. I would be concerned by an account that celebrated five days gained while declining to examine what happened on day eight.
Resource the explanation
The programme cost CNY6.8 million, including workflow work and temporary specialist support. We also delayed a proposed reduction in support capacity. This was uncomfortable because the earlier reporting date had initially been associated with efficiency. I explained that removing avoidable work and removing experienced reviewers are different decisions. A team can complete routine processing more quickly while still needing capacity to resolve unusual matters. Treating every hour as interchangeable would have weakened the part of the process that required the most judgement.
I now ask for a more detailed account of effort alongside the stock of open items. A small group of recurring causes can consume considerable time even when the visible count is falling. Conversely, several low-value items may be resolved through one correction to a source process. This analysis helps distinguish temporary clean-up capacity from continuing control work. It also gives managers a better basis for deciding whether a proposed automation reduces a cause or merely moves the same investigation to another team with a different budget.
For the audit committee, the useful question is not whether seven days is an impressive number compared with another institution. The useful question is whether management receives a timely account that preserves the qualifications needed for oversight. I would show the timetable, significant unresolved matters, later adjustments and the resources required to sustain the process. Directors should be able to challenge the relationship between those measures. A reporting date without that context invites an easy comparison and a weak understanding of the institution's actual control position.
There is a cultural consequence as well. If the only celebrated result is completion, people learn to describe incomplete work in completed language. If the organisation values an accurate explanation of what remains, colleagues can raise a concern while it is still manageable. I do not mean that every close should become an unlimited investigation. Deadlines matter, and materiality matters. I mean that a deadline should govern a decision about the account, with the unresolved position documented, rather than erase the distinction between a decision and certainty.
The next close programme I lead will begin with two questions together: when do executives need the account, and what must accompany it for them to use it responsibly? That pairing keeps speed connected to purpose. It also makes the cost of achieving an earlier date easier to discuss before commitments are made. I would be pleased to shorten a timetable again. I would be more pleased if the people reading the result could explain its remaining uncertainties as clearly as they could state the day on which it arrived.