ASC 842, made manageable: a finance team’s guide to getting it right

ASC 842 changed the rules for lease accounting in the US - most leases now sit on the balance sheet as a right-of-use (ROU) asset and a lease liability. Good for transparency. Tough on finance teams that are still doing it in spreadsheets.

Whether you’re rolling it out for the first time or cleaning up after a rushed adoption, here’s how to handle ASC 842 without the chaos - plus a few notes for teams also reporting under IFRS 16 or FRS 102.

What ASC 842 really asks of you

The short version: every lease (with a few exceptions) needs to show up on your balance sheet, classified, calculated, and disclosed correctly.

The longer version comes down to four things:

• Recognition - record an ROU asset and a lease liability for each lease.
• Classification - operating or finance (yes, ASC 842 still keeps both, unlike IFRS 16).
• Measurement - calculate liability as the present value of future payments; ROU asset measured accordingly.
• Disclosure - maturity analyses, weighted-average rates, reconciliations, and more.

Miss any of these and your auditor will find them. Get them right and ASC 842 becomes routine.

Rolling out ASC 842 in 6 steps

1. Pull every lease into one place

Lease data tends to live everywhere - procurement, real estate, IT, HR. Start with a complete inventory:

• Real estate (offices, warehouses, retail)
• Equipment (machinery, IT, office)
• Vehicles
• Embedded leases - the easiest to miss. Service contracts often hide them (think dedicated servers in an IT outsourcing deal).

If you skip one, your balance sheet is wrong. That’s how transitions stall before they start.

2. Classify each lease

ASC 842 uses five criteria - ownership transfer, purchase option, lease term vs. economic life, present value vs. fair value, specialized asset. If any is met, it’s a finance lease. Otherwise, operating.

Tricky cases (renewal options, variable terms) are where misclassification usually creeps in. Document your judgment for every borderline call.

3. Choose your transition method

Two options:

• Effective date method - apply ASC 842 from the adoption date. Simpler, no restatement.
• Comparative method - restate prior periods. More work, but cleaner comparability.

Most teams pick the effective date method. Run simulations either way so leadership sees the balance sheet impact before go-live.

4. Plan for modifications and remeasurements

Leases change. Every change - extension, early termination, scope shift, CPI bump - needs to trigger a remeasurement. Build a process for catching modifications early, not at year-end.

5. Wire it into your accounting system

If lease data lives outside your ERP, you’ll be reconciling forever. Lease liabilities, interest, depreciation, and journal entries all need to flow into the GL - automatically. Manual postings are where errors compound.

6. Build out your disclosures

ASC 842 requires:

• Lease liability maturity analysis
• Weighted-average remaining lease term
• Weighted-average discount rate
• Reconciliation of lease liabilities
• Cash outflow disclosures

Auditors will compare these to your underlying schedules. They need to match.

Where ASC 842 rollouts usually stall

Most failed (or painful) ASC 842 transitions trace back to the same handful of issues:

• Missing leases. Embedded leases, branch-office contracts, equipment hidden in service deals.
• Spreadsheet fatigue. Works for 10 leases. Breaks at 50.
• Misclassification. Renewal options and variable terms misjudged.
• No modification tracking. Changes happen, nobody updates the schedule.
• Disconnected systems. Lease data lives apart from the GL.
• Thin documentation. Discount rate assumptions undocumented, classification calls unjustified.

Each of these is fixable. None of them are about working harder - they’re about working with the right setup.

Reporting under more than one standard?

Plenty of US companies don’t just deal with ASC 842. If you have EU subsidiaries, IFRS 16 is in play. If you have UK or Irish entities, FRS 102 comes in too. Each handles leases a little differently:

• IFRS 16 - single lessee model, all leases on the balance sheet.
• ASC 842 - operating vs. finance split, both on the balance sheet.
• FRS 102 - operating leases generally stay off the balance sheet (closer to the old IAS 17).

If you’re running all three, you don’t want three systems. You want one platform that applies the right rules per entity.

How Onederful handles ASC 842 inside Business Central

Onederful is built natively into Microsoft Dynamics 365 Business Central - so your lease accounting lives where your finance data already does. No middleware. No re-keying.

For ASC 842 specifically, that means:

• Every lease centralized - active, archived, or in negotiation - alongside contracts and amendments.
• Automatic classification based on ASC 842 criteria.
• Lease liability and ROU asset calculations done automatically, including remeasurements when terms change.
• Disclosures generated on demand - maturity analyses, weighted-average rates, reconciliations - all ASC 842-compliant.
• Journal entries posted directly to your BC general ledger. Full audit trail.
• Multi-entity, multi-currency support for global rollouts.
• One platform for ASC 842, IFRS 16, and FRS 102 - apply the right rules per entity automatically.

When the auditor asks, “How did you arrive at this number?” - the answer is visible in 30 seconds.

The bottom line

ASC 842 isn’t going anywhere. Neither is the work it generates. The teams who handle it well aren’t the ones with the most spreadsheets - they’re the ones with the right tools, where the lease data already lives.