The EOFY Accounts Payable Guide
A guide to starting the new financial year ahead
The end of the financial year is an opportunity to review what worked, where AP processes fell short and what needs to change. This guide helps you turn those lessons into a practical action plan for a more efficient, controlled and confident start to the new financial year.
Key insights from this guide:
- Review your EOFY performance: Identify AP bottlenecks, recurring issues and areas for improvement.
- Understand what good looks like: Establish best practices for efficient invoice processing, approvals and financial control.
- Build an action plan: Set clear priorities for the new financial year, with practical steps to improve AP processes.
- Identify opportunities for improvement: Explore where technology, automation and better workflows can help your finance team work smarter.
The Accounts Payable Year End 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:
- 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.
- 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 while you're trying to close the books.
- 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.
“We were always worried that our financials didn't include all expenses, and chasing invoices was like constantly chasing our tail.”
Danny Flaskas, Chief Finance Officer at Maroochy RSL
“With around 1,300 invoices a month, you're not scrutinising every single one. That lack of visibility and control exposed the business to fraudulent activity and financial losses.”
Jonathan Rowley, Managing Director at Vanilla Blue
What Good Accounts Payable Year-End Procedures Look Like
Diagnosis is only useful if you know what you should be aiming for. The five benchmarks below describe what a finance team running an automated AP function actually experiences year-round. Each benchmark is followed by a brief note on how modern AP teams actually got there.
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 — 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.
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.
Discover AP automation for EOFY
Post EOFY Accounts Payable: An 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 AP efforts 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 year end accounts payable pressure.
A 4-step action plan that takes you from diagnosis to first move:
Step 1: Run the post-mortem with your team.
Take the five reflective questions from Section 1 to your next finance team meeting. The detail you need isn't in a system, it's in your team's recall of how EOFY actually ran — which fades quickly once the next reporting cycle takes over. Capture it while the period is still recent enough to be specific.
Step 2: Identify your biggest gaps and focus there.
Walk through Section 2's five benchmarks honestly with your team. The benchmarks where the gap to "good" is widest are where the largest workload and risk are sitting in your process. Group your three biggest gaps together, they're almost certainly connected, and a single platform shift will close all three in parallel. Most teams try to fix everything at once and stall; focused action on the largest gaps moves faster.
Step 3: Speak to an AP specialist about how to close the gaps.
A 15-minute conversation with someone who has implemented this shift before is the fastest way to scope what change actually looks like for your business. It should give you:
- A view on implementation time and cost commitments for a team your size
- How the solution maps to your specific approval chains, integrations, and supplier mix
- Real numbers and proof points from Australian finance teams that have already made the shift
- A clear read on whether automation is the right move for your specific situation, or whether your gaps need a different fix
Step 4: Evaluate the platforms that fit your situation.
Lightyear is purpose-built for the three gaps this guide diagnoses — automated invoice capture and coding for visibility, parallel approval workflows with full chain visibility so nothing sits unnoticed, and continuous statement reconciliation that prevents backlogs.
Where to Look Next
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.
The implementation reality: This shift moves faster than most finance leaders realise. Modern accounts payable automation sits alongside your accounting software — it doesn't replace it. And implementation is measured in weeks, not months.
From my point of view, I'd say just do it. Invest the time and effort to do it properly, and take the leap, because it's truly been game-changing.