The Post-EOFY Accounts Payable Playbook
If June was your most stressful month, you're not alone.
For Australian finance teams running manual AP, EOFY is when it all piles up. Invoices arrive faster than you can process them. Approvals stall, and chasing them eats time you don't have. Statement reconciliation backs up while you're chasing accruals. By June 30th, you've spent three weeks firefighting and audit prep hasn't started.
EOFY doesn't just expose these problems. It amplifies them. The bottlenecks exist all year round; they just don't show until manual processes meet a non-negotiable deadline.
The upside: this isn't a once-a-year event to brace for. The problem isn't EOFY — it's a process that was never built for this kind of volume, and the right tools make the fix more achievable than most finance leaders assume. Now, before another financial year runs on the same process, is the time to address it.
The EOFY Post-Mortem
Diagnose where your AP process leaked time this EOFY
Answer these as a self-reflection, not a checklist. The questions you can't answer with confidence are usually the ones pointing at the biggest gaps in your process.
- At any point in June, could you say with confidence how many invoices were outstanding, and why they were being held up?
If you answered no, that's a visibility gap. Confident visibility means the answer is in the system, not in someone's head or inbox.
- How long did the average invoice sit waiting for approval in the final two weeks of June?
If approval times in those final two weeks were noticeably longer than the rest of the year — say, days instead of hours — that's an approval bottleneck. Manual approval chains depend on the approver having time. In June, no one has time, and the longer invoices wait, the higher the risk of late payments, supplier friction, and missed cut-offs.
- How often do you reconcile supplier statements?
If reconciliation gets pushed when you're busy, and especially if it got skipped entirely in the June rush, that's a reconciliation backlog. Every unreconciled statement becomes a question you'll have to answer in August, when you have less time and the information is colder.
- How many hours did your team spend on manual data entry, chasing approvals, or matching invoices to POs in June?
Estimate it honestly across the whole team. The number itself matters less than how it compares to a normal month. If June ran 50% or 100% above your usual hours, that's the cost of the three gaps above stacking up under EOFY pressure. It's also the number you'll need when building the case for change.
- If next financial year ran on exactly the same process as this one, would next June look any different?
If the honest answer is no, that's the most important question in this guide. The process didn't get worse over the year, the demands on it did. And those demands aren't going down in the next financial year.
The three gaps these questions expose
Your answers to the questions above are likely pointing to three specific gaps:
Gap 1: Invoice visibility
You can't see in real time what's outstanding, what's been approved, and what's stuck. Invoices live in inboxes and spreadsheets. The information exists, but it’s siloed and disjointed.
Gap 2: Approval bottlenecks during close
Approvals are the part of the AP process you have the least control over — they sit with people outside your team, and when EOFY pressure hits, those approvals slow down. Volume doesn't slow with them. The result is a queue that builds on your desk: invoices waiting for sign-off, suppliers chasing you for updates, and a process that grinds while you're trying to close the books.
Gap 3: Statement reconciliation backlogs
Statement rec gets deprioritised under pressure because it feels less urgent than closing the books. It isn't less urgent, it's just less visible, until audit season arrives and every unreconciled statement becomes a question you have to answer with colder information.
Five benchmarks for a modern AP process
The five benchmarks below describe what a finance team running an automated AP function actually experiences year-round.
Real-time visibility on every outstanding invoice
What it looks like: Every invoice in the system shows where it is in the approval chain, who's holding it up, and what's blocking it from moving.
How modern AP teams got there: They consolidated documents into a single inbox. Every supplier sends to a single capture point — typically a dedicated email address or supplier portal — where invoices land, get extracted automatically, and are immediately visible to the whole finance team.
Approvals that keep moving even during close
What it looks like: Approval workflows route automatically based on rules you set once, so the queue doesn't depend on any one person's availability. Even when approvers get pulled into close, BAS, or audit prep, you can see exactly where every invoice sits and nudge approvers directly without leaving the system.
How modern AP teams got there: They moved approval rules out of email and into a system that routes and tracks every invoice. Finance can see at a glance who's holding what, what stage each invoice is at, and notify approvers in one click — turning "chasing approvals" from a manual job into a system action.
Statement reconciliation is handled continuously, not in a backlog
What it looks like: Supplier statements get reconciled as they come in, not in a frantic sweep at year-end. Discrepancies are flagged instantly, so you're resolving them while they're still fresh. Audit prep becomes a straightforward export rather than a month of detective work.
How modern AP teams got there: They stopped treating reconciliation as a periodic task. Statements get matched against invoices the moment they arrive, and discrepancies surface immediately for resolution — turning a monthly project into background work.
A complete audit trail, available on demand
What it looks like: Every invoice has a complete record attached to it — the invoice itself, who approved it, when, with what supporting documentation, and how it was coded. When auditors ask for evidence, it comes out of the system in seconds.
How modern AP teams got there: They consolidated invoice records into a single system that captures the full lifecycle automatically. Nothing has to be reconstructed from emails, spreadsheets, or memory. Every action is logged from the moment it happens.
A finance team that's not firefighting AP at EOFY
What it looks like: Modern AP teams handle June at the same pace as any other month, because the process did the heavy lifting throughout the year.
How modern AP teams got there: This isn't a benchmark you reach by trying harder. It's the cumulative result of the four benchmarks above. Once visibility, approvals, reconciliation, and audit trails are running automatically, June stops being a different month.
The New Financial Year Action Plan
The three gaps aren't independent problems with separate fixes. They're symptoms of the same shift modern AP teams have already made, moving from manual effort to a purpose-built AP platform. Lightyear is built specifically for this: it sits alongside your accounting software and handles the parts of AP that buckle under EOFY pressure.
Here's a 4-step action plan that takes you from diagnosis to first move:
Why now?
EOFY didn't create the chaos of June, it amplified what was already there. That's why the months following EOFY are the right window to act. The pain is still fresh enough to drive decisions, capacity is back as close work winds down, and audit prep is about to surface the same reconciliation gaps all over again,making the case for change easier to build, not harder.
Leave it too long, though, and the urgency fades. By the time the new financial year is in full swing, "we need to fix this" turns into "we'll look at it again before May." And then it's June again.
Where to look next
AP Provider Comparison Guide
See how the leading AU Accounts Payable platforms compare on workflow, integration, pricing, and implementation.
15-minute call with an AP Specialist
Get a quick read on whether automation is the right move for your situation.