The Reason Your NFP Month-End Takes Ten Days Instead of Three
Revenue recognition requires a different approach to every funding agreement, every month. When those methods live in spreadsheets and people's memory, the close drags. The Board sees numbers that depend on decisions made under pressure the night before. The finance team, you, continue to face the eleventh-hour stress of the situation.
The new financial year has just started. New funding agreements are in place. First installments are landing. Acquittals from last year are running in parallel.
And by month-end, your team will work through every one of those funding streams by hand, applying the revenue recognition method, reconciling installments against expenses, making judgements that the board's surplus figure depends on entirely.
If the close ran long last financial year, it will run long again this year. Not because your team lacks knowledge or capability. Because the rules for each agreement live in a spreadsheet, a a shared drive, or someone's memory backlog, and they are applied manually, under pressure, every month.
That is not a people problem. It is an architecture problem.
The start of a new financial year is the right moment to fix it – before the pattern repeats for another twelve months. This article explains why the close is slow, where the days actually go, and what changes when the system carries the rules instead of your team.
What governs NFP revenue recognition
Revenue recognition for not-for-profits sits under two standards: AASB 15 Revenue from Contracts with Customers, and AASB 1058 Income of Not-for-Profit Entities. Most finance teams understand which standard applies to a given funding stream.
The difficulty is not in the theory of it, but in the execution. This is because applying the right method to each agreement, consistently, every month, across an organisation that holds several funding streams at once can be quite the challenge.
Here’s an example to demonstrate what that looks like in practice.
On 1 July 2025, a new charity begins operating. For 2025–26, it is awarded $720,000 in funding. On 1 July it receives its first installment of $250,000. During July it incurs and pays $48,000 in expenses.
How much revenue should it recognise in July?
There are several defensible answers.
Method A (On receipt AASB 1058): The organisation controls the $250,000 received and recognises all of it. Against $48,000 in expenses, July's surplus is $202,000. Net assets are $202,000.
Method B (Over time by period AASB 15): The grant covers 12 months, so the organisation recognises one twelfth — $60,000 — in July. Against $48,000 in expenses, the surplus is $12,000. Prepaid income sits at $190,000.
Method C (Over time by expense AASB 15): Revenue is recognised equal to expenses incurred: $48,000. Surplus is zero. Equity is zero.
Same $250,000. Same $48,000 in expenses. A $202,000 surplus, a $12,000 surplus, or a $0 surplus. Three legitimate outcomes. Each one tells the board a different story.
Now think about the application across every active funding agreement your organisation holds. Eight agreements, twelve, fifteen? Each one carrying its own standard, its own logic, its own outcome. Each one re-worked at every close.
That is where your days are spent. And that is where the board's confidence in the numbers begins to erode, not because of errors but because the method depends on whoever ran the process this month.
The process your team is running every month, and what it costs
There is no shortcut around the approach itself. Revenue recognition requires understanding the contract. But the work of applying and recording that reasoning – consistently, month after month, across every agreement – does not have to rely on your team.
A reliable approach works through four steps:
1. Map every active funding agreement. List each source – donations, grants, government funding, service agreements. Most NFP organisations hold more funding streams than they expect once every source is counted.
2. Identify the applicable standard for each. NDIS funding, Disability Employment Services, single-year grants, multi-year grants, memberships, and subscriptions each carry different treatment. Each one points to AASB 15 or AASB 1058.
3. Apply and document the method per agreement. The reasoning needs to be recorded, not just for audit, but so it stays consistent from one close to the next, regardless of who runs the process.
4. Run the close with the method already set. When the recognition logic lives in the system, the close verifies the outcome rather than calculating it from scratch. That is what takes the days back.
The load compounds at month-end because each funding stream carries its own logic, and most NFP finance teams are carrying that logic in spreadsheets.
That is where the gap lies.
What changes when the system carries the rules
Most NFP finance teams have managed revenue recognition manually for years. Not because they lack skill, but because the systems available to them did not support any other approach. The manual process was the only process.
When the recognition rules for each funding stream are configured into the system: the standard, the method, the acquittal dates, the performance milestones, the journals run automatically at close.
You aren’t required to repeat calculations each month as the outcome is already verified.
1. The audit trail is clean because it is built into the process, not assembled after the fact.
2. The numbers are consistent month to month, because the method is set in the system, not applied by memory.
3. The board sees figures they can trust, not numbers that depended on which method someone applied under pressure the night before month-end.
4. The close runs in days, not weeks, because the team is reviewing, not rebuilding, from scratch.
That is the shift. Finance teams that have made it describe the same outcome: the first close after go-live runs differently. By month three, the difference is significant. By the end of the year, the team that was grinding through ten-day closes is closing in three to four.
Overhead allocation: the second reason the close drags
Revenue recognition is not the only driver of month-end drag. Overhead allocation is the less visible one, and for organisations holding multiple grant contracts, it matters just as much.
Every funding agreement requires a share of overhead costs: administration, IT, facilities, staffing and employment on-costs. The purpose is to establish the true cost of delivering on each grant. Without it, there is no accurate picture of which programs are viable and which are absorbing costs the grant does not cover.
The three common allocation methods are:
By headcount or FTE: Costs are divided by the number of full-time equivalent staff working on each grant. Common for software and shared services.
By percentage of revenue: A fixed share, such as 15 percent of grant revenue, is allocated to cover overhead.
By usage measure: Physical measures like floor area in square metres are used for costs such as rent and facilities.
A system that captures this statistical data automatically and applies the allocation rules without human intervention wins you those days back.
The calculation runs as part of the close rather than holding it up.
Why month-end is slow, and why it does not have to be
Step back and the pattern is clear.
Revenue recognition is a judgement your team re-makes every month, for every funding agreement. Overhead allocation depends on data that is not available until the period closes. Each funding stream carries its own logic. Most organisations hold several at once. None of this is a decision made once — it is the same set of decisions, repeated every close, by hand.
That is why the close is slow. And that is why the board sees numbers they cannot fully rely on when they arrive — not because of errors, but because those numbers were calculated under pressure, on a timeline, by a team that should be reviewing rather than rebuilding.
The fix is not faster spreadsheets or longer hours.
It is moving the rules into the system: the funding streams, the recognition method per agreement, the acquittal dates, the overhead drivers, configured once, so each close verifies the outcome rather than recalculates from scratch.
That is what takes the pressure out of month-end. That is what gives leadership and the board reporting they can act on.
The new financial year is the window. It will not stay open long.
New agreements are in place. The year is clean. July's close has not run yet.
This is the moment to configure the system correctly — before month-end habits calcify for another twelve months, and before the first close runs on the same manual process your team has been absorbing for years.
Once July closes on the old method, the year is running. Changing the setup mid-year is harder, not easier. The window to start clean is now.
The organisations that have made this shift consistently describe the same outcome: the pressure does not ease gradually. It changes with the close. The first month after go-live, the team is verifying instead of calculating. By month three, the close runs in days. By year-end, the board pack is reviewed — not rebuilt at 11pm the night before.
That outcome is available to your organisation. But it requires starting before this financial year gets away from you.
A short diagnostic maps your active funding streams, identifies the recognition method for each, reviews your overhead allocation approach, and shows you exactly where your current close is losing days — and how quickly that changes with the right system in place.
How Healthy is Your Revenue Recognition Process?
Could your current process stand up to audit? Is your month-end close more manual than it needs to be?
Our free Health Check helps you benchmark your revenue recognition process, identify gaps, and determine where improvements can make the biggest impact.
Simply work through the checklist, total your score, and see where your organisation sits—and what to do next.