Most finance leaders are not surprised by ASC-842 anymore. The standard has been in effect long enough that organisations have had years to get their houses in order. And yet, audit friction around lease accounting remains stubbornly common. The problem has shifted. It is no longer about understanding the standard. It is about the quality of the data sitting underneath it.
What CFOs often discover during audit season is that the compliance framework is in place but the data feeding it is incomplete, inconsistent, or simply old. That gap is where audit findings come from.
The Assumption That Creates the Problem
When ASC-842 was first adopted, the priority was getting leases onto the balance sheet correctly. Right-of-use assets were calculated, lease liabilities were recognised, and disclosures were drafted. For many organisations, that initial implementation was treated as a one-time project.
The difficulty is that lease portfolios are not static. Leases get amended. Terms get extended. Options get exercised. New locations open and old ones close. Every one of those events requires a remeasurement, and every remeasurement requires accurate source data.
When organisations treat ASC-842 compliance as an implementation exercise rather than an ongoing process, the data begins to drift. Amendments do not get recorded promptly. Lease abstracts reflect terms that have since changed. The system carries information that was accurate three years ago but is not accurate today.
By the time auditors arrive, the work is not a review. It is a reconstruction.
What CFOs Actually Need From Their Lease Data
Three things determine whether a finance team will move through an audit cleanly or spend weeks producing evidence on demand.
The first is completeness. Every lease in the portfolio should be captured in the system, including amendments and modifications as they happen rather than at year-end. Gaps in the lease population create gaps in the balance sheet.
The second is traceability. For every right-of-use asset and lease liability on the balance sheet, there should be a clear line back to the source document. Which clause governs the lease term? What supports the discount rate selected? When was the most recent remeasurement and what triggered it? Auditors ask these questions. The time spent finding the answers during fieldwork is time that could have been avoided with organised, accessible documentation throughout the year.
The third is currency. Lease data needs to reflect the current state of the portfolio, not the state it was in when the system was last updated. This is where spreadsheet-based approaches tend to fail. A spreadsheet updated twice a year cannot keep pace with a portfolio where lease events occur continuously.
Where Audit Friction Actually Comes From
In conversations with finance teams, the most common sources of audit friction are not complex accounting judgements. They are administrative. Schedules that cannot be reconciled because data changed without the system being updated. Discount rate support that was documented in an email thread that has since been archived. Lease modifications that were agreed months ago but never formally recorded.
These are not failures of expertise. They are failures of process. And they are expensive, because audit time billed to investigating administrative gaps drives up fees and delays sign-off.
A well-structured lease accounting environment reduces this friction not by doing anything complicated but by keeping accurate data in one place, updated in real time, with documentation attached to each record.
The Role of Software in Reducing Audit Fatigue
Dedicated lease accounting software does not eliminate the need for good processes, but it does make good processes easier to maintain. When lease events trigger automatic remeasurements, when documents are stored against the relevant records, and when audit reports can be generated on demand rather than assembled manually, the friction at audit time drops considerably.
The key capability to look for is not the breadth of features but the fit with how the organisation actually operates. A system that supports the fiscal calendar structures a business uses, that integrates with the ERP already in place, and that can handle multi-entity portfolios without requiring manual consolidation is one that reduces workload rather than adding to it.
Property Works supports a range of fiscal year structures, including the retail calendars common in the restaurant and QSR sectors. A lease accounting system that cannot correctly handle a 52/53-week fiscal year will generate timing discrepancies in amortisation schedules that require manual correction at every close. That is the kind of detail that compounds over time.
The Practical Question for Finance Leaders
The question worth asking before the next audit cycle begins is not whether the team is technically compliant. It is whether the evidence of compliance is organised, accessible, and current.
If the answer involves caveats about data that needs to be pulled together, systems that need to be reconciled, or documentation that is stored in multiple places, that is the area to address now. Audit season does not create the problem. It reveals it.
A lease accounting review conducted well before fieldwork begins gives finance teams the opportunity to identify and correct gaps on their own terms, rather than under the time pressure of an open audit.
To schedule a lease accounting review with the Property Works team, visit propertyworks.com/contact.