Choosing lease accounting software is not the same as understanding ASC 842. Most US finance teams and CPA firms reach this point already knowing the standard: leases sit on the balance sheet, right-of-use assets and lease liabilities have to be recognized and measured, and disclosures have grown. The harder question is which system will actually carry those workflows month after month, through modifications, remeasurements and audits, without pushing you back into spreadsheets.
This guide covers how to choose ASC 842 lease accounting software from the perspective of the people who have to run it: US finance teams and CPA firms. It assumes you already know roughly what ASC 842 requires and want a practical way to evaluate software against your real lease portfolio and your close process. Readers who want a broader starting point can begin with our lease accounting overview, but the focus here is selection: what to test, what to ask, and where cheaper or narrower tools tend to fall short.
The current lease model was introduced through Accounting Standards Update 2016-02, which created Topic 842. If you also need context on how the requirements changed, our guide to the differences between ASC 840 and ASC 842 covers that transition so this article does not have to repeat it.
What ASC 842 lease accounting software should actually do
Before comparing vendors, it helps to fix the baseline. A lease accounting system built for ASC 842 should manage the full lifecycle of a lease as an accounting object, not just produce a one-time calculation. At a minimum that means capturing lease data, classifying each lease, measuring the right-of-use asset and lease liability, generating schedules, producing journals, supporting disclosures, and handling changes over time.
Under FASB Topic 842, lessees generally recognize the assets and liabilities created by leases longer than twelve months on the balance sheet, while expense presentation continues to depend primarily on whether a lease is classified as operating or finance. That single sentence sets the bar for software. A system that only tracks payments, or only calculates a schedule for one lease type, is not enough. It has to distinguish the two classifications and carry each through the correct measurement and expense pattern.
This is also where the case for dedicated software is strongest. FASB’s post-implementation review of Topic 842 reported that the standard largely met its transparency objective, but that the cost of applying it, particularly for lessees, ran higher than the Board expected, in part because many existing systems and processes were not equipped to bring operating leases onto the balance sheet. That is the practical problem a good tool solves: not the theory of the standard, but the ongoing administration of it.
Start with your lease portfolio and close process
The right software depends on what you are actually managing, so start by describing your own situation honestly.
Count your leases and the entities they sit across. A company with a dozen equipment leases in one entity has very different needs from a group running real estate, vehicles and equipment across multiple subsidiaries. Note the mix of asset types, because real estate leases tend to carry more options, escalations and modifications than a straightforward equipment lease.
Look at who does the work. An in-house finance team closing monthly has different priorities from a CPA firm managing lease accounting on behalf of many clients, where separation between entities and the ability to move between client files quickly matter as much as the calculations.
Map your reporting requirements. Are you US-only under ASC 842, or do you also report under another framework? Organizations operating across multiple jurisdictions should consider how their software handles ASC 842 and IFRS 16, since a system that supports both can avoid duplicate tooling. Finally, be specific about your monthly close: how many days you have, where the bottlenecks are, and how lease journals currently reach the general ledger.
Evaluate the full ASC 842 lease lifecycle
Once you know your portfolio, test the software against the lifecycle rather than a single calculation. Vendors demo well on a clean new lease. The difference shows up in everything that happens after.
Initial recognition and lease setup
Check how a lease is set up from commencement: payment structure, lease term including reasonably certain options, and the discount rate. Discount rate handling is worth a specific look. ASC 842 requires the rate implicit in the lease where it is readily determinable, and otherwise the lessee’s incremental borrowing rate. Private companies have an additional option, since FASB provides discount rate guidance for private-company lessees that allows a risk-free-rate practical expedient to be elected by class of underlying asset. If you are a private company, confirm the software supports the rate approach you have actually chosen, not just a single hard-coded method.
From those inputs the system should calculate and maintain the right-of-use asset and lease liability from commencement through the end of the lease, and it should apply the operating or finance classification you have determined rather than leaving it ambiguous.
Ongoing schedules and journals
The heart of the system is the schedule it produces and keeps current. Test the right-of-use asset and lease liability schedules, interest calculations, payment allocation, current and non-current liability balances, and the different expense treatment required for operating and finance leases. These are the numbers your close and disclosures depend on, so they should be reproducible, traceable and straightforward to reconcile.
Modifications, remeasurements and terminations
This is where the evaluation should become more rigorous. Leases rarely stay exactly as signed. Terms change, payments are renegotiated, options are exercised, and leases may end early. A capable system should recalculate schedules when terms change, remeasure the liability and adjust the right-of-use asset where applicable, and handle terminations cleanly. Ask the vendor to walk through a modification live, using a lease that already has history, rather than a fresh example.
Check operating and finance lease treatment separately
This is the point that most distinguishes a US evaluation from any other, and it deserves its own step.
Under ASC 842, both operating and finance leases appear on the balance sheet as a right-of-use asset and a lease liability. What differs is how they hit the income statement. An operating lease produces a single, straight-line total lease cost over the term. A finance lease is split into amortization of the right-of-use asset and interest on the liability, which front-loads total expense in the earlier years. Same balance sheet treatment, different expense pattern.
The implication for software is direct. A tool cannot simply claim to “support ASC 842.” It has to support the classification determined under the organization’s accounting policies and then carry operating and finance leases through their respective measurement, expense and reporting models. When you test a system, put at least one operating lease and one finance lease through it and confirm that the resulting expense patterns differ as required under ASC 842. If a vendor treats both types identically, that is a problem, not a simplification.
Look beyond calculations to reporting and disclosures
Correct schedules are necessary but not sufficient. ASC 842 disclosure has grown, and your software should make the reporting side manageable rather than a manual reassembly at quarter end.
Look for lease liability roll-forwards, right-of-use asset movement reporting, maturity analysis of lease liabilities, and a clear split of current and non-current balances. Confirm that operating and finance lease outputs can be produced separately, that journals are reviewable before anything is posted, and that the system retains structured, traceable source material behind each number. Exports matter too, both for review and for any downstream system that needs the data.
A note on language as you read vendor material: be skeptical of absolute claims. No software makes an organization automatically compliant or removes audit risk, and the sensible test is whether a system supports your review and audit preparation, not whether it promises a guaranteed outcome. Treat “audit-ready” as marketing shorthand and evaluate the actual reports and audit trail instead.
Test integrations and journal workflows
For most teams the value of lease software is realized when its output reaches the general ledger with minimal rekeying, so integrations deserve careful testing rather than a checkbox.
Check how journals are posted: whether they go directly to your accounting system, how chart-of-account mappings are configured, whether journals can be reviewed before posting, and how mappings work at the entity level. For any system you do not integrate with directly, confirm that journals can be exported in a usable format.
One caution applies to every vendor, including strong ones. Available import, posting and synchronization workflows vary by integration, so do not assume that a connection to one accounting platform behaves identically to a connection to another. If a vendor lists several integrations, ask specifically about the one you use, whether that is QuickBooks Online, Sage Intacct, Xero or a Microsoft Dynamics 365 environment, and test that path with your own data rather than trusting a general claim of parity.
Decide whether leases and fixed assets should be managed together
For many US organizations, leases are only part of the balance sheet story. Owned fixed assets run through the same close, the same reconciliations and the same reporting, and it is worth understanding how lease accounting and fixed asset accounting overlap before you decide how many systems you want to maintain.
Right-of-use assets and owned assets both affect the balance sheet and both feed period-end reporting. When they live in separate systems, someone has to reconcile between them, and that reconciliation is recurring work. A single platform that manages fixed assets and leases together can reduce that duplication and give you one consistent set of movements and reports. Whether that consolidation is right for you depends on the size and shape of your asset base, but it is a legitimate selection criterion, not just a convenience.
Assess controls, review history and user access
Software that produces good numbers can still fail an evaluation if it cannot be controlled and reviewed. This matters more the larger your team and the more entities you manage.
Look at user permissions, the review workflow before journals are posted, and the change history the system retains as leases are modified over time. Check whether supporting documentation can be attached to a lease, how user access is managed, how entities are kept separate, and, for CPA firms, how a firm-and-client structure is supported across multiple users. Ask what the system records when something changes, since a clear change history and audit trail is far more useful during an audit than a promise that nothing is ever lost. Confirm these capabilities against your own requirements rather than assuming they are present.
Plan migration away from spreadsheets
Most teams arrive at dedicated software from Excel or from a limited module, so the migration itself is part of the evaluation. This is exactly the friction FASB’s review pointed to when it noted that existing systems and processes were often not built for the standard.
Test how existing leases move in. Look for bulk import, the ability to enter opening balances and historical schedules for leases already part-way through their life, validation of the data as it loads, and a clear way to handle rows that fail so you can correct and re-upload them rather than starting over. Where you can, run a parallel period and reconcile the software’s output back to your general ledger before you commit, and confirm that supporting records are retained after migration. A clean migration is often the difference between a system that sticks and one that quietly gets abandoned.
Questions to ask during an ASC 842 software demo
Bring a short, pointed list to any demo. These twelve questions surface most of what a polished sales walkthrough tends to skip:
- How does the software distinguish operating and finance leases, and how does the expense pattern differ between them?
- How are modifications and early terminations handled on a lease that already has history?
- Can it recalculate schedules automatically when terms change?
- What lease liability and right-of-use asset reports are available out of the box?
- How are current and non-current balances presented?
- Can journals be reviewed before they are posted?
- Which posting, import and synchronization workflows are available for our specific accounting integration?
- Can our existing spreadsheet leases be imported in bulk, including opening balances?
- What change history and audit trail does the system retain?
- Can multiple entities or clients be managed and reported on separately under one login?
- Does it support both ASC 842 and IFRS 16 where we need them?
- Can we test the system with our own lease data before committing?
The last question is the most revealing. Where available, testing the system with your own lease data is more informative than relying only on a scripted demonstration. A trial, sandbox or structured product test can show how the software handles the terms, history and accounting workflows that actually exist in your portfolio.
ASC 842 lease accounting software evaluation checklist
Use this as a working checklist during evaluations. Keep the focus on what to test rather than what a vendor claims.
| Requirement | Why it matters | What to test |
|---|---|---|
| Operating and finance classification | Different expense patterns under ASC 842 | Run one lease of each type and confirm the income-statement behavior differs |
| ROU asset and lease liability measurement | Core balance-sheet recognition | Check schedules from commencement, including current and non-current split |
| Discount rate handling | Drives measurement; options differ for private companies | Confirm implicit rate, IBR, or risk-free-rate election by asset class as applicable |
| Modifications and remeasurement | Where most tools weaken | Modify a lease with existing history and review the recalculation |
| Terminations | Common and error-prone | Process an early termination and review the resulting schedules and balances |
| Journals and posting | Determines close effort | Review journals before posting; test your actual integration path |
| Reporting and disclosures | Needed every reporting period | Produce roll-forwards, maturity analysis and movement reports |
| Migration from spreadsheets | Determines whether adoption sticks | Bulk import with opening balances; reconcile to the GL in parallel |
| Multi-entity and user access | Matters for groups and CPA firms | Separate entities, permissions, review workflow, change history |
| Dual-standard support | Relevant for cross-border reporting | Confirm ASC 842 and IFRS 16 where required |
How AssetAccountant supports US lease accounting workflows
If you are evaluating options, ASC 842 lease accounting software for US businesses and CPA firms is the category AssetAccountant is built for. The platform manages leases as accounting objects across their lifecycle: right-of-use assets and lease liabilities, payment schedules, the interest and expense that flow from them, and lease journals with current and non-current movements separated for reconciliation.
AssetAccountant supports the ongoing changes that make leases difficult to maintain over time, including modifications, remeasurement, refinancing and terminations. CPI- or index-linked adjustments can be processed once the updated index or rate is known, without implying that the system forecasts future movements. Existing leases can be imported in bulk, including opening information for leases brought in part-way through their life, while available reports provide structured outputs for lease review and disclosure preparation.
AssetAccountant is built for ASC 842, with IFRS 16 also supported for organizations that report across markets, and it manages fixed assets and leases in one system so owned assets and right-of-use assets run through the same close and reporting. It offers native integrations with Xero, QuickBooks Online, Sage Intacct and Microsoft Dynamics 365, with journal posting to supported systems, and, consistent with the caution above, the available workflows vary by integration rather than being identical across all of them.
Final decision
The clearest signal in any evaluation is not a claim of ASC 842 compliance on a feature list. It is how the software behaves when you push your own leases through it: setup, schedules, a modification, a termination, the journals, the reports, and the path into your general ledger. Test the operating and finance treatment separately, confirm the migration works against real data, and use a trial or structured demo rather than deciding from a slide.
If a single system for both leases and owned assets fits your situation, explore AssetAccountant’s US lease accounting software to see how leases, right-of-use assets, liabilities, schedules and fixed assets can be managed together.
