Your balance sheet on ASC 842 and IFRS 16: ROU assets, lease liabilities, and the splits that matter

ASC 842, IFRS 16, and FRS 102 changed how most companies account for leases. Almost every lease now lands on the balance sheet - as a right-of-use (ROU) asset and a lease liability. More transparency for investors. More work for finance teams.

Here’s how it actually fits together, and how to present it without losing sleep before audit season.

ROU assets and lease liabilities, in plain English

Strip away the standard-speak:

• The ROU asset = what you get to use (the office, the equipment, the vehicle).
• The lease liability = what you owe for using it.

Together, they show the full picture - the resource and the obligation. No more hiding leases in the footnotes.

A quick example. You sign a 5-year lease on office equipment. On day one, you record the ROU asset based on the lease liability (plus any direct costs or prepayments), and the lease liability as the present value of future payments. Month by month, the ROU asset gets depreciated and the liability shrinks as you pay it down.

Sounds clean. The catch: you have to split that liability into current and noncurrent - and keep it accurate as time moves on. Payments due in the next 12 months are current. Everything beyond is noncurrent. Get this wrong and your liquidity ratios, debt metrics, and audit story all take a hit.

The splits that matter: how to present everything

ASC 842, IFRS 16, and FRS 102 all expect leases to look a lot like owned assets - so the presentation needs to reflect that.

ROU assets: where they live

Usually under property, plant & equipment (PP&E), as their own line item. Most teams group them by lease type:

• ROU assets - operating leases (ASC 842)
• ROU assets - finance leases (ASC 842)
• ROU assets - leases (IFRS 16 and FRS 102, single lessee model)

Lease liabilities: the current/noncurrent split

In the liabilities section, clearly separated:

• Lease liabilities - current portion
• Lease liabilities - noncurrent portion

That split isn’t optional. It tells investors, auditors, and your CFO what’s hitting cash in the next 12 months versus what’s further out - and it drives your liquidity ratios across the board.

Where finance teams usually trip up

Most reporting errors don’t come from bad intentions. They come from spreadsheets, manual workflows, and data scattered across teams. The usual suspects:

• Wrong current vs. noncurrent split
• Outdated discount rates or stale assumptions
• ROU asset not updated after a modification or renewal
• Missing renewal options or variable payments
• Incomplete maturity analyses
• Thin documentation when auditors come knocking

Any one of these can land you with misstatements, audit findings, or - worst case - restatements.

The fix isn’t more discipline. It’s better tools.

How Onederful handles all of this 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 external tools. No middleware. No re-keying.

When a lease is set up or changes, Onederful automatically splits the liability into current and noncurrent, tracks the ROU asset through its full lifecycle (including modifications and terminations), and posts the journal entries straight to your BC general ledger. Disclosures for ASC 842, IFRS 16, and FRS 102 - amortization schedules, maturity analyses, roll-forwards - generate in a few clicks, auditor-ready.

Multiple entities? Multi-currency leases? Handled in the same environment, with FX calculations built in.

Every change, every calculation, every entry - logged in a full audit trail.

The bottom line

Lease accounting under ASC 842, IFRS 16, and FRS 102 isn’t going anywhere. Neither is the pressure to get it right.