Most organisations treat end of month as something that happens inside the finance function. Reconciliations, journal entries, management accounts — finance closes the books, and everyone else moves on to the next thing. It's a reasonable assumption. It's also incomplete.
A lot of what makes month-end accurate never touches the finance team first.
Finance doesn't generate the numbers alone
Program managers hold the delivery data behind funded outcomes. Asset managers hold the additions, disposals and changes behind the asset register. HR holds the employee changes behind the payroll numbers. None of these teams think of themselves as part of the finance process. All three feed it directly.
When end-of-month procedures are designed as though finance operates in isolation, they miss the departments actually generating the underlying activity. The result isn't a finance problem. It's an organisational one that shows up in the finance function.
Why completeness of data matters
An accurate financial picture relies on completeness of data, not just accuracy within finance's own records. Three examples show why.
Revenue recognition depends on delivery. Under AASB 15 Revenue from Contracts with Customers, funding is recognised as the organisation satisfies its performance obligations — as the service is actually delivered — rather than simply when the cash arrives. Finance cannot correctly recognise revenue for a program without knowing what was actually delivered that month. If program managers aren't tracking delivery against the funding agreement, finance is left estimating, or assuming delivery is on track when it isn't.
Asset costs need to sit against the right program. When an organisation buys, disposes of, or moves equipment between programs, that change affects the depreciation and cost allocation used in program-level reporting. If the asset register isn't updated promptly, program costs are understated or overstated, and any funder requiring a true cost-per-program breakdown is working from an inaccurate figure. This matters more in organisations running several funded programs from a shared pool of assets.
Payroll allocation depends on accurate employee data. Staff move between programs, change hours, or start and leave partway through a month. Each change affects how labour cost is allocated across cost centres. If HR doesn't flag a change until well after it happens, the management accounts carry a stale allocation — often for months — before anyone notices the numbers no longer reflect where people are actually working.
None of these are finance failures. They are gaps in a process that assumes finance can produce accurate numbers without timely input from the departments that actually hold the underlying activity.
What this looks like when it goes wrong
A pattern worth sharing (details changed to protect confidentiality).
A program was funded to deliver a set number of hours over the year. The program manager's job was to deliver the service — not to think about revenue recognition or funding compliance — so actual delivery hours weren't tracked closely month to month. It felt like paperwork, disconnected from the real work.
But those hours were exactly what finance needed each month to recognise revenue correctly, and to know whether the program was on track to meet its funding obligations. By year end, the shortfall was clear. The program hadn't delivered the contracted hours, which triggered a refund obligation for underperformance. The program had operated at a loss for the entire year, and nobody had seen it coming, because nobody was watching the number that mattered until it was too late to change course.
Had those hours been reported monthly, the underperformance would have surfaced early enough to do something about it.
Building cross-departmental input into month-end
Fixing this doesn't require a systems overhaul. It requires making the connection between each department's numbers and the financial picture visible, and building it into the existing month-end rhythm rather than treating it as a separate ask.
A few things that help in practice:
- Tell each contributing team specifically what's needed and why. A request for actual delivery hours lands differently once someone understands it drives revenue recognition and funding compliance, not just an internal finance deadline.
- Set contributor deadlines ahead of finance's own close date, not on it. If program, asset and payroll data are due the same day finance needs to close, there's no buffer to chase missing information.
- Give each area a single point of ownership for their month-end input, so it isn't unclear who's responsible when something is missing.
- Keep a simple running checklist of what's outstanding before close, so gaps are visible days in advance rather than discovered at the reporting deadline.
- Revisit the process as the organisation changes. New programs, new funding agreements and new asset categories all shift what finance actually needs from other departments.
In summary
End of month has always been seen as finance's responsibility. There are real benefits to involving the rest of the organisation in it: earlier warning signs, a more accurate financial position throughout the year, and fewer surprises when the numbers are finalised. Good end-of-month process is designed around where the information actually comes from — not just who's expected to produce the report.
Is your month-end process missing the departments that generate your numbers?
De Valore can help build a process that reflects how your organisation actually works, not just how finance is set up to run. The first step is understanding where the gap sits.
Start a conversation