Navigating Financial Year End 💲🏗️📊📚

A Practical Guide for Council Infrastructure Asset Managers

Australian councils operate on a 1 July - 30 June financial year. That means the countdown to 30 June is a very real pressure felt across every department from Roads and Stormwater through to Finance and Governance. This guide is designed to help council asset management teams navigate that pressure with confidence.

Welcome to the Iamdata Solutions Asset Management Newsletter – June 2026

Jill Singleton

Director - Asset Management Specialist & Data Analyst

Why Financial Year End Matters More Than You Think

For infrastructure asset managers, Financial Year End (FYE) isn't just a Finance department problem. The data your team provides, condition assessments, maintenance costs, renewal expenditure, and new assets constructed, feeds directly into the council's financial statements, asset registers, and long-term financial plans.

Get it right, and your council presents credible, audit-ready financials. Get it wrong, and you're looking at valuation adjustments, write-offs, or worse: qualified audit opinions that erode public trust.

Tip 1: Start Early

The single biggest mistake councils make is treating FYE as a June problem. By the time June arrives, it is too late to correct data errors, chase missing inspection records, or reconcile capital works expenditure. A structured four-month lead-up transforms year end from a crisis into a routine.

March	Audit asset register for completeness. Identify assets constructed, acquired, or disposed of during the year. Begin reviewing WIP.
April	Reconcile capital works expenditure. Confirm capitalisation vs. maintenance splits with Finance. Identify projects ready for capitalisation.
May	Finalise condition assessments and unit rates. Validate depreciation parameters. Prepare draft asset additions/disposals schedule.
June	Final data submission to Finance. Review and sign off on asset register. Support external auditors with documentation.

Real-world example: A regional Queensland council discovered in late May that $2.3 million in stormwater infrastructure completed in February had never been added to the asset register. The scramble to value, inspect, and record those assets in time for the audit created enormous pressure and a near-miss with their external auditors. Starting reconciliation in March would have caught this months earlier.

Tip 2: Know What Each Department Needs to Deliver

FYE is a whole-of-council exercise. Each department within your Infrastructure Asset Management function has a specific role to play and Finance and Governance can only do their jobs if departments deliver accurate, complete data on time.

Here is an example summary of what each area is expected to provide:

Department	Key FYE Deliverables
Transportation & Traffic	Status of roadworks, new infrastructure to capitalise, project cost data Condition data, maintenance vs. capital expenditure split Inspection records, condition ratings, renewal works costs Asset additions, renewals completed, performance data Regulatory compliance data, infrastructure renewals, WIP status New assets installed, renewals completed, condition assessments Condition inspections, capital works, depreciation data Vehicle acquisitions, disposals, written-down values
Road Maintenance
Bridge Maintenance
Stormwater Management
Water & Wastewater
Parks & Recreation
Buildings & Structures
Fleet Management
Finance	Consolidate all data into financial statements, ensure compliance
Governance	Authorise expenditure, oversee asset management plans and policy compliance

Tip 3: Get Clear on Capitalisation vs. Maintenance

One of the most common sources of confusion, (and audit findings) at FYE is the misclassification of expenditure. The distinction matters enormously for your financial statements:

Maintenance: Maintenance expenditure keeps an asset functioning at its current standard. It flows to the Profit & Loss as operating expenditure.

Capital: Capital expenditure improves, extends the life of, or creates a new asset. It is recorded on the Balance Sheet and depreciated over time.

Misclassifying capital works as maintenance understates your asset base and overstates operating costs. Misclassifying maintenance as capital inflates your asset register and hides the true cost of running your infrastructure. Either way, the auditors will find it.

https://www.iamdata.solutions/post/how-to-distinguish-between-capital-and-maintenance-projects-in-infrastructure-planning

Tip 4: Keep Records That Tell the Story

Auditors don't just want numbers, they want evidence. Good record-keeping throughout the year is what separates a smooth audit from a painful one. For each asset addition, renewal, or disposal, you should be able to produce:

•       Works completion certificates or project handover documentation

•       Engineer or condition inspection reports

•       Cost data from your financial system

•       Spatial data confirming asset location (GIS)

•       Before-and-after photographs for major renewals

Build a habit of capturing this information at the time of works completion not retrospectively at year end. Many councils now ask project managers (internal and external) to complete a standard asset data collection form as part of the works sign-off process.

Tip 5: Communicate Early and Often

• FYE requires cross-department collaboration under time pressure, and I’m sorry to say that this can be a recipe for miscommunication if not managed proactively. I’ve included some communication practices that make a difference:

• Issue a FYE calendar to all departments in February or March, clearly showing data submission deadlines.

• Hold a cross-departmental FYE briefing in April to confirm expectations and answer questions.

• Assign a point of contact in each department to own the data submission process.

• Use a shared tracking tool (see Power BI below) so everyone can see progress in real time.

• Schedule a mid-May checkpoint to identify and resolve issues before the final rush.

Communication is free. Audit findings are not. A 30-minute cross-department meeting in April can prevent weeks of remediation work in June.

Tip 6: Harness the Power of Customised Power BI Reports

If there is one investment that pays dividends at every Financial Year End, it is a well-designed, council-specific Power BI reporting suite. Unlike generic reports generated from your asset management or finance system, a customised Power BI solution can bring together data from multiple sources, your asset register, financial ledger, GIS, and works management system into a single, live, decision-ready view.

What Power BI Can Do for Your FYE Process

Here are six report types that make a real difference at year end:

Capital Works Report

Tracks WIP expenditure against budget in real time, highlighting projects approaching completion that need to be capitalised before 30 June.

Asset Register Completeness Report

Identifies gaps in your asset register, missing condition ratings, unknown acquisition dates, zero-value assets, so you can fix them before audit.

Depreciation & Valuation Report

Summarises depreciation charges by asset class, with drill-through capability to individual assets for audit queries.

https://video.wixstatic.com/video/85e758_fb0337cb78f5409c903db4c837970d65/720p/mp4/file.mp4

Maintenance vs. Capital Spend Analysis

Visualises the split between maintenance and capital expenditure, flagging potential misclassifications for Finance review.

https://video.wixstatic.com/video/85e758_c79bb05a12f743a7a2cdc0aec95dfc89/1080p/mp4/file.mp4

Condition Profile Report

Shows the condition distribution of your asset portfolio, supporting long-term financial planning and renewal forecasting.

Year End Checklist Tracker

A live progress report showing which departments have submitted their FYE data, and what's still outstanding.

Beyond Year End: Power BI for Year-Round Asset Intelligence

The councils that sail through FYE are the ones that use Power BI throughout the year, not just at year end. When your reports are live and your data is current, year end becomes a validation exercise rather than a data collection exercise.

I have developed and built many Power BI reporting solutions for councils spanning:

• Financial reporting (budgeting, valuations, depreciation, and capital expenditure tracking)

• Asset management performance (condition profiles, renewal forecasting, and maintenance analysis)

• Planning and development (DA tracking, compliance monitoring, and land use reporting)

• Licensing and compliance (permit status, fee collection, and renewal tracking)

• Environmental health (inspection scheduling, outcome monitoring, and risk reporting)

• Customer request management (request volumes, response times, and resolution rates)

• Parking permits (permit issuance, revenue, and infringement tracking)

• Water management (consumption data, infrastructure performance, and billing reporting)

Every council is different. The most effective Power BI solutions are built around your data structures, your workflows, and your reporting obligations, not a generic template.

Tip 7: Use Year End as a Springboard for Improvement

Financial Year End can also offer up improvement opportunities. When it’s all done and dusted, it’s good to step back and ask: how well is our asset management function working?

As you work through the FYE process, take note of:

•       Data gaps that caused delays or required manual workarounds

•       Processes that relied on a single person's knowledge or effort

•       Expenditure that was difficult to classify or verify

•       Assets that could not be located, valued, or substantiated

•       Reporting requests that your current tools couldn't easily answer

Each of these is a signal and an opportunity to improve your data quality, your systems, or your processes before next year's FYE arrives.

The councils that continuously improve their asset data quality are the ones that can answer their auditors' questions in minutes, not days. That confidence comes from year-round discipline and the right tools to support it.

Financial Year End does not have to be a stressful scramble.

With the right planning, clear communication, good record-keeping, and the right technology tools in place, your council can close the year with confidence and set a stronger foundation for the year ahead.

I work alongside councils and public authorities to build the data quality, reporting capability, and asset management processes that make FYE, and every other time of year for that matter, easier to manage.

I have worked on many different projects with my Local Government clients, from designing and developing Power BI Reports, to building SQL Server databases for spatial data, to managing and maintaining GIS and the Asset Management systems. If you'd like to discuss how we might work together, then please email Jill at ➡️ jill.singleton@iamdata.solutions

If you would like to receive the latest Newsletter Blog straight to your inbox, please subscribe here: ➡️ https://www.iamdata.solutions/subscribe

You can read all our Newsletters and Blogs here:➡️ https://www.iamdata.solutions/blog

You may also be interested in our Projects Page:➡️ https://www.iamdata.solutions/past-projects

Check out what our clients say about us here:➡️ https://www.iamdata.solutions/reviews

If you would like to see a particular topic covered in these newsletters, then please let me know about it. The chances are other people will be interested and would like to hear about it too! Please email me at: ➡️ jill.singleton@iamdata.solutions with your suggestions.  

er BI Report                                      What It Helps You Do