The close is a downstream symptom
Close cycle days are usually blamed on the close process. In a bank they are more often the interest on a debt taken out earlier: items left open in operations, suspense balances with no owner, and differences that were explained verbally and never written down.
Fixing the close therefore means fixing the daily control. When every difference is classified, owned and aged from the day it appears, the month end has nothing left to discover.
What finance gets out of the same engine
- A daily position on every reconciled account, rather than a monthly snapshot.
- Suspense and clearing accounts with an owner per item and an age, which is what makes them shrink.
- Certification with preparer and reviewer separation enforced by the system.
- An evidence pack per account and period, with rule versions, approvals and attachments included.
- A single classification vocabulary shared with operations, so the two teams stop arguing about what a difference is.
Close metrics worth tracking
| Metric | Why it matters | Where it comes from |
|---|---|---|
| Open items at close | The real size of the close problem | Break population by account |
| Aged items over threshold | Where an audit finding is most likely | Break age at period end |
| Value inside tolerance | What automation is absorbing without review | Tolerance pass matches |
| Manual journals raised | How much of the close is still hand made | Actions taken on items |
| Evidence assembly time | The cost of proving the control worked | Time to export the pack |
Two audiences, one set of records
The daily control and the close serve different audiences and the same data. Operations needs to know what did not match today and who is fixing it. Finance needs to assert that a balance is supported, that open items are known, and that the assertion can be evidenced later. When those two live in separate systems, the close begins with a reconciliation of the reconciliations, which is a genuinely absurd amount of work to perform every month.
| Question | Operations view | Finance view |
|---|---|---|
| What is open? | Items to work today, by owner and age | Items supporting a balance, by classification and value |
| Is it under control? | Match rate and break age | Certification status and reviewer sign-off |
| What changed? | New breaks since yesterday | Movement in the open item population since last close |
| Prove it | The item history | The period pack, with approvals and rule versions |
Close cycle days, and the number underneath them
Close cycle days is the metric finance functions are measured on and it is a poor diagnostic on its own, because it aggregates several unrelated constraints into one figure. A close that takes eight days because three accounts are reconciled at the end has a different problem from a close that takes eight days because every account is reconciled on time and the review layer is the bottleneck.
The more useful number is when each account reaches a reconciled and reviewed state relative to period end, tracked per account rather than in aggregate. That immediately separates the accounts that are genuinely difficult from the accounts that are simply scheduled late, and the second group is usually larger. Sequencing work by exposure rather than by habit tends to remove more days from a close than any amount of additional effort applied uniformly.
Close cycle days, and where they actually go
Ask a controller where the close time goes and the answer is rarely the accounting. It is waiting for a reconciliation to be finished, chasing an explanation for a difference somebody else owns, and assembling support for accounts that were reconciled but not evidenced. All three are consequences of the control happening somewhere the finance team cannot see.
- 01Waiting. Removed when the daily reconciliation completes daily and its status is visible without asking.
- 02Chasing. Removed when every open item already has a classification and a named owner, so the explanation exists before the question.
- 03Assembling. Removed when evidence is a by-product of the work, so support is a filtered export rather than a collection exercise.
None of those three is an accounting improvement. They are all operational, which is why a close acceleration project that begins in the general ledger usually disappoints and one that begins in the daily reconciliation usually does not.
Materiality and tolerance are not the same idea
Finance teams reason in materiality: a difference below a threshold does not change the financial statements. Operations teams reason in tolerance: a difference below a threshold does not require an item to be worked. These sound similar and behave very differently, because materiality is about a balance and tolerance is about an item.
A hundred immaterial differences of the same kind are a control failure even when their sum is immaterial, because they indicate something systematically wrong that will not stay small. The practical rule is to set tolerances on the operational question, which is whether the class of difference is understood, and to report by classification so that a growing population of small differences is visible as a pattern rather than hidden under a threshold.
Multi-entity, multi-currency, and the intercompany problem
A banking group reconciles the same relationship from two sides, and the two sides use different ledgers, sometimes different currencies and occasionally different accounting dates. Intercompany differences that survive to consolidation are expensive to explain and are usually caused by one of three things: a timing difference that neither side recorded as such, an FX translation applied on different dates, or a posting made in one entity and not the other. Reconciling intercompany balances on the same cadence and with the same classification vocabulary as everything else turns those into daily items with owners rather than into a quarterly argument between two finance teams.
Where to start if finance is sponsoring the project
Start with the account that produces the most manual journals at close, not with the largest account. That is usually a suspense or clearing account, and it is where the shared classification vocabulary pays for itself in the first month. Then extend to general ledger reconciliation and to balance sheet certification.
Questions about financial reconciliation software
Is this a replacement for our close management tool?
It is the reconciliation and exception layer underneath it. Some banks run both, with certification here and task management in the close tool. What matters is that the differences are worked in one place with one vocabulary.
Can auditors be given read access?
Access is role based, and a read only role scoped to accounts and periods is a normal configuration for internal audit or an external reviewer.
How far back does the evidence go?
Retention is configurable to your record keeping policy. The evidence for a period is exportable at any point while it is retained, and the export contains the rule versions in force at the time rather than today.
Does it post journals?
No. It produces the classified difference, the suggested action and the approval trail. Postings are made in your systems by your people, which is where they should stay.