Case Study
North London Waste Authority: A Local Authority Fixed Asset Accounting Case Study
Written by: John de Robeck • Published: January 14, 2025 • Updated: August 17, 2026

Case Study
Written by: John de Robeck • Published: January 14, 2025 • Updated: August 17, 2026

This case study explains how North London Waste Authority and FMIS developed a cloud-based fixed asset accounting environment around evolving classifications, financial periods and reporting requirements. It is intended for local authority finance and asset teams considering how data design, configurable software and implementation support can strengthen financial control, reporting and audit readiness.
Case Study
Challenges
Client Overview: North London Waste Authority is a statutory public authority serving more than two million residents across seven north London boroughs. Its responsibilities include arranging waste disposal and managing waste from the area’s reuse and recycling centres.
North London Waste Authority (NLWA) selected FMIS Fixed Assets to establish a cloud-based fixed asset accounting system capable of supporting detailed financial records, configurable asset classifications and changing reporting requirements.
The project required more than a standard software setup. As NLWA’s source data and Finance Team requirements developed, FMIS worked alongside the organisation to refine the asset structure, support successive imports and provide practical guidance on configuration, reporting and ongoing use. This local authority fixed asset accounting case study shows how configurable software and collaborative implementation can support an evolving public-sector programme.
NLWA’s project involved bringing together asset information from multiple sources while its preferred data structure was still developing. Categories, subcategories, locations, facilities, asset systems and other classifications all needed to be represented consistently.
The system had to retain useful identifiers from source records and provide a clear basis for importing and maintaining asset data. It also needed to support individual asset records and wider views by location, facility and asset grouping.
Financial requirements included monthly accounting periods, year-end processing and different approaches to depreciation. NLWA also needed to manage impairments, revaluations, transfers and disposals. As the Finance Team refined its requirements, the implementation needed to accommodate configuration changes without losing control of the accounting structure.
Local authorities prepare their financial statements under the Accounts and Audit Regulations 2015 and proper accounting practices set out in the CIPFA/LASAAC Code of Practice on Local Authority Accounting. The Code is based on International Financial Reporting Standards, adapted to reflect the public-sector and statutory framework within which local authorities operate.
A local authority fixed asset register may include property, plant and equipment, infrastructure assets, heritage assets and investment properties. Operational land and buildings, specialist infrastructure and assets without an active market can require different approaches to classification and valuation. Finance teams must also maintain accurate information about useful lives, depreciation, impairments, revaluations, component replacements, transfers and disposals.
Regular reconciliation between the fixed asset register, capital expenditure records and the accounting system helps ensure that additions and subsequent changes are reflected in the annual accounts. This depends on consistent identifiers, clear classifications and a traceable history of changes. Incomplete or outdated source information can make both valuation and audit more difficult, which is why NLWA needed a system that could accommodate developing data without losing financial control.

“As our requirements developed, we needed an asset register that could be shaped around categories, subcategories, locations and facilities. FMIS gave us the flexibility to refine that structure and the practical support to work through the changes.”
Liz Lugtendorff
North London Waste Authority
FMIS began by working with NLWA to understand its accounting calendar, asset classifications, depreciation policies, reporting requirements and source data. These discussions formed the basis of a detailed setup document and the initial system configuration.
The configuration was refined as NLWA received further data and involved additional stakeholders. When new subcategories and revised analysis codes were required, FMIS consultants explained the relationship between the main asset profile, accounting defaults, numbering structures and imported records.
FMIS Fixed Assets uses configurable profiles and analysis codes to describe assets according to an organisation’s own requirements. For NLWA, these included category, subcategory, location, facility, asset type, asset system, status and functional location.
This structure supports different views of the fixed asset register while maintaining a consistent accounting record. Saved layouts can present the fields most useful to the Finance Team and retain preferred sorting. Main asset and sub-asset records can also provide detailed and consolidated views of related components within a facility.
Data preparation and import were central to the project. FMIS supported NLWA with import templates, validation and the process for removing and reloading test data when the asset structure changed.
The system was configured around NLWA’s financial year, accounting periods and required depreciation methods. It also provides controlled processes for additions, transfers, disposals, impairments and revaluations, giving NLWA a defined route for maintaining information as its data develops.
Some asset information depended on external data and decisions involving different project stakeholders. FMIS continued to provide workshops, demonstrations and direct support while these dependencies were resolved.
When NLWA revised its classification requirements, FMIS set out the appropriate sequence for changing profiles, exporting existing codes, updating defaults and reimporting revised data. Support also covered layouts, facility groupings, batch processes and presenting useful fields to Finance Team users.
“The ability to tailor the information shown to users and organise records around our facilities has been important in making the asset register practical for the Finance Team. Having direct access to the FMIS consultants has also helped us work through the detailed configuration as the project developed.”
Liz Lugtendorff, North London Waste Authority
NLWA now has a configured cloud-based fixed asset accounting environment designed around its financial periods, asset classifications and reporting requirements.
The project has established a structured basis for maintaining asset information, with configurable fields and layouts that support different views of the register. It has also created defined processes for importing data and recording changes throughout the asset lifecycle.
The configuration has continued to evolve as NLWA’s data and Finance Team requirements have become clearer. FMIS has remained involved through testing, revised imports, system demonstrations and detailed configuration support.
NLWA’s experience provides several practical lessons for other public authorities planning a fixed asset software implementation:
What is the purpose of a local authority fixed asset register?
It provides a structured record of the authority’s non-current assets and the financial information associated with them. It supports depreciation, valuation changes, disposals, financial reporting and the evidence required for review and audit.
Why is asset classification important?
Different asset classes may require different accounting treatments, useful lives, depreciation methods and reporting. Consistent categories and subcategories also help finance teams analyse assets by location, facility, function or asset type.
How can fixed asset accounting software support local authority controls?
A dedicated system can apply consistent accounting profiles, maintain an audit trail and provide controlled processes for additions, imports and lifecycle changes. Configurable layouts and reports can then help users review the register and reconcile it with wider financial records.
This public sector fixed asset accounting case study demonstrates the value of combining configurable software with an implementation approach that can respond to changing information and stakeholder requirements.
FMIS Fixed Assets provides NLWA with a structured fixed asset management platform for financial processing and reporting, supported by continuing consultancy as its asset data is classified, presented and maintained.
For local government and other UK public sector organisations, a reliable fixed asset register is an important foundation for public sector accounting and balance sheet reporting. It records capital assets and other non-current assets in the UK public sector, supports the annual depreciation charge and provides an audit trail for capital expenditure, impairment and valuation changes.
FMIS provides fixed asset accounting software and implementation support for local authorities, central government organisations and other public bodies.
Learn more about FMIS solutions for local and central government, or request a product demonstration to discuss your requirements.



https://www.fmis.co.uk/wp-content/uploads/2026/02/SORP-Lease-Accounting-Changes-2026.webp
1024
1024
John de Robeck
https://www.fmis.co.uk/wp-content/uploads/2026/04/FMISNavyTeal-1-150x80-1.webp
John de Robeck2026-02-23 11:00:512026-03-18 08:50:32Preparing for Charities SORP Lease Accounting Changes 2026FMIS Ltd
167b John Wilson Business Park
Whitstable
Kent
CT5 3RA
United Kingdom
Phone:+44 (0) 1227 773003
Fax:+44 (0) 1227 773005
Sales:sales@fmis.co.uk
Support:support@fmis.co.uk
Protected: FMIS Internal Training – Recap and Quiz| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
| PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gat_UA-48954022-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| Cookie | Duration | Description |
|---|---|---|
| VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
| YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
| yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
