NetSuite lease accounting means carrying right-of-use assets and lease liabilities under ASC 842 through lease records, schedules and journals in Fixed Assets Management, a Built for NetSuite subledger, or an external system. Reconciling it means proving, lease by lease, that the population is complete, schedules and GL agree, and the accounting is right.

A lease subledger carries a good share of the month by itself. It computes the schedules, generates the monthly journals, reclasses the current portion of the liability and, in the better cases, reports its balances against the GL lease by lease.

What it leaves behind is the reconciliation. The preparer pulls the roll-forward, the liability split and the local-currency amortization history, then refreshes the pivots by hand. This month's closing rate is keyed in for the liabilities. The commencement rate is looked up for each right-of-use asset; under this team's policy, a contractual modification moves the ROU asset to the modification-date rate, while a data correction does not. The totals are tied to GL balances that show no lease, and the difference is chased to a lease. The adjusting entry is booked. Every report is saved before and after, because the subledger's reports are live and will not show last month's state once the entry posts.

Key takeaways:

• Lease accounting in NetSuite runs on one of three architectures, and each posts differently. Which one is in use decides how much of the reconciliation the system does for you, not what has to be proved.

• A lease subledger's reconciliation reports prove that what it computed reached the GL. They do not test the accounting it applied, and they surface activity posted around them without explaining it.

• Lease reconciliation failures fall into five families: population, FX rate, event classification, timing and attribution. FX rate and event classification are where accounting policy and fact-specific judgment sit with the controller.

• Two failures can produce no difference at all: a wrong discount rate baked into the schedule, and a lease missing from both sides. Both are found outside the tie, by re-performing the schedule and reviewing the lease register.

  
  

How lease accounting works in NetSuite

There is no single NetSuite lease module. A lease reaches the GL in one of three ways, and the reconciliation depends on which is in use.

1. The Fixed Assets Management lease feature. Oracle's Fixed Assets Management SuiteApp, an optional module sold separately, includes a Lease Accounting feature covering ASC 842 and IFRS 16. The preparer creates a lease record, adds the payments and generates the lease amortization schedule; the SuiteApp computes net present value, interest and principal from the rate entered. Create Lease Journal generates the commencement entry, which is the right-of-use asset journal entry itself: ROU asset debited, lease liability credited, and the journal linked from the lease record. An ROU asset is then proposed and created from that journal, and runs through the ordinary asset life cycle, depreciation included.

The periodic entry is the part to understand before reconciling it. Record Lease Interest creates the periodic journal. For a finance lease that is a debit to interest expense and a credit to the lease liability; for an operating lease, a debit to accumulated depreciation on the ROU asset and a credit to the lease liability. Depending on the approval setup, that journal can sit pending approval rather than posted, which is one more reason the schedule and the ledger are not the same thing. Taken together with the asset's depreciation, those entries mean the net ROU balance falls each period by depreciation less the interest accreted, while the liability rises by that interest before the payment reduces it.

ASC 842-20-25-6 requires one straight-line lease cost for an operating lease, with the ROU asset falling by that cost less the interest. Oracle gets there through the asset record: the generated ROU asset's residual value is set to the lease's total interest as a negative number, so straight-line depreciation runs over cost plus interest, which is the total of the payments, and the periodic charge comes out at the straight-line lease cost. On a modification that residual value is recalculated, and Oracle recommends the Straight Line Remaining method. The setup check is to leave both as generated: change the residual value and the interest stops reaching expense; change the method and the remaining charge is spread differently. And a preparer expecting the ROU balance to fall by the depreciation charge alone will find a difference every month, and that one is not an error.

Two limits are stated in Oracle's own pages. The lease record carries the subsidiary's base currency, and multi-currency is not supported for it. A lease in another currency therefore needs a subledger that supports it, or, as some teams do, a base-currency entry with the remeasurement handled in a workbook; Oracle documents the limit, not the workaround. And modifications require the Allow Lease Modifications preference and create a Lease Contract record each time. Reporting is four lease saved searches, for lease liability detail, the ROU asset listing, and the current and non-current liability splits, alongside the asset register. What Oracle does not document is a lease-by-lease comparison of those balances to the GL. The tie is therefore built the way the fixed-asset tie in the NetSuite account reconciliation guide is built: saved-search totals against the ROU, accumulated depreciation and liability accounts, with the lease journal reachable from each lease record.

2. A Built for NetSuite lease subledger. NetLease by Netgain and LeaseQuery for NetSuite are lease engines installed inside the NetSuite instance, holding the lease records and schedules as NetSuite records and generating the journals from there. FinQuery describes LeaseQuery as built entirely inside the SuiteCloud platform and integrated with the chart of accounts, currencies, departments, classes and locations. NetLease's documentation shows each journal line carrying the lease it belongs to, and its reconciliation reports key on that tag. Where the tag exists, lease-level reconciliation is possible without leaving NetSuite.

NetLease's documentation describes the mechanics. The commencement entry debits the ROU asset, credits a long-term lease liability account, and routes prepayments, incentives and initial direct costs through an ROU clearing account. The monthly operating lease journal entry charges the straight-line cost to lease expense, reduces the liability, builds ROU accumulated amortization by the asset reduction, and accrues the payment to a lease payable clearing account. A separate reclass journal moves the current portion of the liability.

Its nine-step month-end procedure runs from confirming pending leases through to disclosure reports. It includes reconciliations of both clearing accounts and, lease by lease, of the liability and of the gross, accumulated and net ROU asset between subledger and GL. A foreign-currency add-on books the historical-rate adjustment to accumulated amortization on each amortization run.

3. An external lease system. FinQuery's cloud LeaseQuery platform (as distinct from its SuiteCloud app above), Visual Lease, CoStar and similar external systems calculate outside NetSuite and post or import journals into it. The GL carries no lease reference unless the import adds one. Where it does not, the lease-level bridge has to sit outside the GL, usually in a workbook. The most useful improvement available is a lease identifier on every journal line, in the memo field or a custom segment, so the GL detail can be grouped the way the subledger is.

What the subledger's reconciliation reports prove, and what is left

NetLease's reconciliation reports exist, in its documentation's own terms, to confirm that the transactions and balances the subledger expected have been reflected in the GL, by lease. When a lease does not tie, the documented checks are whether every journal for the period was run, whether the report is pointed at the right accounts, and whether each entry carries the lease tag. That is a posting-completeness test. It runs one way, subledger to ledger, and it catches a skipped journal, a commenced lease with no postings, and a manual entry that dropped the lease reference. Where there is no such report, as with Fixed Assets Management, the same test is built in the workbook. Either way, four things remain after it passes.

Whether the subledger's number is right. The report compares the GL to the schedule. If the schedule carries the wrong discount rate, classification, term, or exchange rate on the ROU asset after a modification, the report ties, and the schedule it tied to is wrong. The schedule is the thing the report trusts.

What posted around the subledger. The roll-forward report's filter for tagged impacts, left off, surfaces activity on the lease accounts with no lease tag. NetLease's documentation says such activity is mostly manual journals, and names it as the commonest source of a variance. The same report excludes the short-term reclass and currency revaluation journals by default, and names that exclusion as a common reason its total differs from the trial balance. The report finds the untagged amount. Explaining it is the preparer's job.

A state as of a date. The reports are live. Once a lease is modified, terminated or transferred, NetLease's guidance is that a report cannot be exported as of the period before the change. The pre-adjustment state has to be saved before the adjusting entry posts, or it is gone.

The evidence. A tie is a screenshot. A reconciliation is the tie, the explained items, the entries proposed and approved, the post-adjustment state, and a reviewer's sign-off, in that sequence. The disclosure evidence has a version of the same problem. NetLease's weighted-average rate and term figures come from different reports depending on the release: the older single-currency searches are now deprecated, and the current reports consolidate across the portfolio. The workpaper records which one the disclosure was built from.

Why a lease reconciliation can fail even when the subledger ties to the GL

Lease reconciliation failures sort into five families. Naming the family first tells the preparer what kind of response it needs: an entry, a timing explanation, a classification decision or a completeness action.

Population. A lease commenced in the register but never posted, a lease terminated in the contract but still amortizing, and a contract that contains a lease and was never abstracted. The third is the auditor's completeness question. Under ASC 842-10-15-3 a contract contains a lease when it conveys the right to control the use of an identified asset for a period in exchange for consideration. Whether the asset is identified turns partly on whether the supplier holds a substantive substitution right, and control turns on who obtains the economic benefits and directs the use. Data-center space written as a subscription, and equipment written as a managed service, can meet the definition while the contract never uses the word. Short-term leases of twelve months or less can be kept off the balance sheet by class of underlying asset under ASC 842-20-25-2. A lease that reached only one side produces a difference and gets found. The dangerous population failure is the lease missing from both sides: nothing in the register, nothing posted, nothing in the GL, and a tie at zero.

FX rate. ASC 842-20-55-10 settles the rule. The lease liability is a monetary liability, remeasured at the closing rate; the right-of-use asset is a non monetary asset, remeasured at the rate on the commencement date. That rate is fixed by the right-of-use asset journal entry at commencement, and the monthly run never revisits it. ASC 830-10-45-18 lists accumulated depreciation and the related expense among items carried at historical rates, so the ROU asset's accumulated amortization stays at the commencement rate too.

Two consequences follow for a foreign-currency lease held in a subledger, since the native record cannot hold one. Monthly amortization posted at the period's rate drifts accumulated amortization away from the historical rate a little every month. When the period's rate is above the commencement rate, the correction debits accumulated amortization; when it is below, the entry reverses. For a finance lease the offset is amortization expense. For an operating lease, NetLease's documented treatment books it to the single lease cost, which the example below follows; some companies use FX gain and loss instead, and Netgain reports audited clients on both.

The second consequence is configuration. NetSuite's currency revaluation can be applied to any non-equity balance sheet account flagged for it, so the lease liability accounts should carry the flag and the ROU asset accounts should not. An ROU account left flagged is remeasured at the closing rate every month, against the standard; and where the subledger books its own FX entries, check the two together so nothing is remeasured twice.

The harder FX question follows a modification. When a modification is not a separate contract, the liability is remeasured from the modified terms at the updated discount rate. The ROU asset is adjusted in full for most modifications, and proportionately, with a gain or loss, where the modification reduces the scope of the lease. For a foreign-currency lease the question is then which rate the ROU asset carries. Deloitte's Roadmap: Leases (Section 8.8.2) sets out two views: apply the modification-date rate to the whole ROU asset, which recognizes an exchange difference on that date, or keep the commencement rate on the pre-modification balance and apply the modification-date rate only to the increase. Deloitte reports that either is acceptable as an accounting policy applied consistently and disclosed where material. The controller's job is to have chosen one, in writing, before the first modified lease reaches the reconciliation.

Event classification. Lease modification accounting under ASC 842-10-25-8 treats a modification as a separate contract only when it grants an additional right of use at a price commensurate with its standalone price. Otherwise ASC 842-10-25-9 has the lessee reassess classification at the effective date and remeasure under ASC 842-10-35-4. A rent escalation entered with the wrong effective date and fixed this month is none of those. It is an error in the original entry, corrected as one, and under either rate view the ROU asset keeps its commencement rate. A material prior-period error also gets the ASC 250 assessment; correcting the lease record is not the whole analysis.

Whether the subledger can tell the two apart depends on the workflow it offers and whether the lease qualifies. NetLease documents a true-up modification for a lease commenced with the wrong information, and notes it is not yet available for FX or multi-book leases; for those, its documented path is to reverse the history back through the affected periods. A standard modification is for an actual modification. Used as a workaround on an FX lease, as L-022 below assumes, the rate reset it creates is a reconciling item, not the accounting conclusion. The accounting decision comes first and the workflow is chosen to implement it. The control is a modification register with a column recording, for each change, whether it was contractual, a remeasurement event or a correction, decided by someone who read the document.

Timing. Order forms arrive after the monthly journals have run. A renewal signed on the 28th and received after that run is accrued directly to the GL and processed in the subledger next month, so for one period the GL holds an entry no subledger report knows about. NetLease's roll-forward can place a transaction by posting period or by transaction date, and a report on one basis against a trial balance on the other differs by every transaction dated in one month and posted in another. The reconciling item is the accrual, the evidence is the document behind it, and the follow-up is its reversal when the subledger catches up.

Attribution. A consolidated GL carries no lease detail. Currency revaluation posts one summary line per account. The short-term reclass posts and reverses. None of these are wrong; all of them are amounts on the ledger side with no counterpart on the schedule side, and the workbook has to name each one.

The discount rate, as opposed to the exchange rate, is an input control rather than a sixth family, because a wrong rate does not surface in a clean subledger-to-GL tie. ASC 842-20-30-3 sets the order: the rate implicit in the lease where it can be readily determined, and the lessee's incremental borrowing rate where it cannot. Lessees that are not public business entities have a further option under ASU 2021-09: a risk-free rate instead of the incremental borrowing rate, elected by class of underlying asset. A wrong rate is baked into the schedule at commencement and posts faithfully every month after. It is found by re-performing the schedule from the lease terms, which is why the workpaper carries that re-performance as its own control rather than relying on the tie.

Operating lease journal entries in NetSuite

At commencement, the right-of-use asset journal entry debits the ROU asset and credits the lease liability for the discounted payments, with the ROU side adjusted for any prepaid rent, initial direct costs and incentives. Each month, lease expense takes the straight-line cost, the liability is credited for interest and debited for the payment, and accumulated amortization is credited for the straight-line cost less the interest. In Fixed Assets Management the same economics come from two runs: Record Lease Interest debits accumulated depreciation and credits the liability, and the ROU asset's depreciation carries the straight-line cost to expense. These are the entries the reconciliation re-performs. The example below runs four leases through them.

ASC 842 journal entries: four leases in one close

The example is built around the families rather than the arithmetic. A US-dollar entity closes August. Two of its operating leases are denominated in euros. The euro closed July at 1.15 and August at 1.17, and averaged 1.16 in August. The entity's policy for modified leases is the first of Deloitte's two views, the modification-date rate applied to the whole ROU asset, and only for contractual modifications.

1. L-014, the clean case. A 36-month lease of EUR 10,000 a month, paid in arrears, discounted at an illustrative 6% nominal annual incremental borrowing rate, applied as 0.5% a month. It commenced 1 January 2025, when the euro stood at 1.08, with an initial liability and ROU asset of EUR 328,710, and no incentives, initial direct costs or prepayments. August is month 20. Interest for the month is EUR 813, so the EUR 10,000 payment reduces the liability by EUR 9,187, and because the straight-line cost equals the payment, the ROU asset falls by the same EUR 9,187. Both close August at EUR 153,399, and they stay equal every month of this lease. In euros, the month's operating lease journal entry and the payment are:

In dollars the two balances do not stay equal:

The USD liability before remeasurement was $176,317 (July's EUR 162,586 at 1.15, less the August reduction at 1.16). Remeasured at 1.17 it is $179,477, an exchange loss of $3,160 that lives in the GL and on no schedule: an attribution item. The $735 is an FX rate item. Accumulated amortization posted at the average rate overstates the reduction, and a debit to accumulated amortization with a credit to lease expense brings the net ROU asset back to $165,671. The two August entries for this lease, in dollars:

Finance lease accounting reconciles the same way, except that amortization and interest are separate expense lines; in Fixed Assets Management they come from separate depreciation and interest runs.

2. L-022, the correction. A lease with a EUR 180,000 ROU asset commenced at 1.05. Last quarter a 3% escalation was booked from the wrong effective date. The lease is in euros, so the subledger's true-up workflow did not apply, and the fix went in as a standard modification. Assume, for the example, that the workflow applied August's 1.17 to the whole ROU balance. The register says the contract did not change. Under the entity's policy the asset stays at 1.05: $189,000, not the $210,600 the system now carries. The reconciling item is $21,600, the entry reverses the exchange gain the system recognized, and the register reads "correction, no rate reset" with the document reference.

3. L-031, the late renewal. A renewal signed 28 August reached accounting after the August journals had run. The team remeasured the lease on the renewal terms and booked an approved manual entry of $38,000, ROU asset against lease liability, without a lease tag. The roll-forward, run with untagged activity included, shows $38,000 on both accounts with no lease attached. It is a timing item, supported by the signed renewal; September's task is to process it in the subledger and reverse the manual entry.

4. L-035, the one that ties. A lease that commenced 1 August is still pending in the register. No schedule, no journal, no GL balance. The report ties for it at zero, which is the population failure in one line. It is caught by the register review that precedes the reconciliation, not by the reconciliation.

Four leases, five issues, all five families, and the lease that needed no entry was the one that tied.

Controls that make it a reconciliation rather than a tie

Clearing accounts at zero before the tie begins. Where the subledger uses clearing accounts, as NetLease does, the ROU clearing and lease payable clearing accounts should net to zero once the month's entries have posted. Two exceptions are documented: prepayments sit in lease payable clearing until the period the payment falls due, and initial direct costs, incentives and prepaid rent sit in ROU clearing until the lease commences. A balance with neither explanation usually means a journal has not run or has run twice, and sometimes a mapping or posting problem. Either way it is investigated before the tie, not after.

A lease reference on every GL line. NetLease documents it on every journal line. Fixed Assets Management documents the link from the lease record to its journal; Oracle's pages do not describe a lease tag on each line. An external system carries one only if the import does. Without a line-level reference the tie is total to total, which is where offsetting errors go to hide.

Revaluation flags by account. Lease liability accounts should be flagged for currency revaluation; ROU asset and accumulated amortization accounts should not. Check the setup at implementation and again whenever an account is added.

Pre- and post-adjustment copies. Save the subledger reports, the GL detail and the trial balance before the adjusting entries post and again after, with the approval sitting between the conclusion and the entry.

Adjusting entries tagged to the lease. An entry that corrects a lease balance and carries the lease reference updates the subledger-to-GL report for that lease. One that does not becomes next month's untagged variance.

The reconciled population supports the disclosures. The lease disclosure requirements in ASC 842-20-50-4 ask for lease cost by component, cash paid, ROU assets obtained in exchange for lease liabilities, and the weighted-average remaining term and discount rate. ASC 842-20-50-6 asks for the undiscounted maturity analysis reconciled to the balance sheet liability. Build those schedules from the reconciled lease population, after sign-off, not before.

The wider NetSuite control model, including which reconciliation type fits a native subledger and what happens when a balance moves after sign-off, is in the NetSuite account reconciliation guide. For where lease journals sit in the close calendar, see the NetSuite close automation guide.

The same reconciliation in Sage Intacct

The five families carry over to Sage Intacct unchanged; the implementation differs. Sage Intacct lease accounting runs on the ERP's own Lease Accounting application, an additional subscription. It captures the lease master data, generates the payment, liability and ROU schedules from it under the selected accounting treatment, and posts the initial and periodic entries to the GL, with modifications handled through a change-lease process. Marketplace subledgers post journals in from outside.

The Intacct-specific difference is dimensions. Sage describes the application as syncing with the chart of accounts and Intacct's multi-dimensional reporting, and the lease record carries a lease group and lease class. Where the posted entries also carry a lease-level dimension value, the GL groups by lease from the start and the tie runs at lease level without a memo-field workaround. Where they carry only the group or class, the workbook carries the lease reference, as it does for an external system on NetSuite.

Lease accounting automation

Lease engines and close platforms automate different parts of this chain. The useful lease accounting automation question is which preparation is still done by hand: rebuilding the schedule, classifying the exceptions, drafting the adjusting lease accounting journal entries, and assembling the evidence in sequence. Maxima prepares that remaining work and leaves the accounting conclusion with the accountant. Its Account Reconciliations page lists leases among the accounts it covers. It describes the work in the terms this article has used: pull balances, subledgers and workpapers from the source systems, update the workpaper and roll-forward, run completeness checks, and tie supporting balances back to the GL. It does that in the Excel or Google Sheets workpaper the team already uses. For leases in NetSuite that means three things.

It works from the sources the reconciliation already uses. Maxima integrates natively with NetSuite, reading the GL, subledgers and financial reports directly, and takes the lease subledger's exports, the modification register and the supporting documents alongside them. Where the subledger's own reconciliation reports exist, Maxima starts where they stop: the untagged activity they surface, the completeness check against the lease register they do not run, and the rate question they cannot ask.

It prepares the workpaper with an independent re-performance attached. Max's accounting skills include applying the ASC 842 classification tests, building the ROU asset and lease liability schedule with its monthly entries, and remeasuring the liability and adjusting the ROU asset on a modification or reassessment. A schedule rebuilt from the lease terms and the entity's rate policy is what lets the reconciliation test the subledger rather than assume it. The schedule arithmetic is deterministic and gives identical output on every run. Reading the modification register for why a change was made, or classifying an untagged journal, is interpretation, and it is shown with its evidence. Which rate view the entity applies, and whether a change was a modification or a correction, is judgment, and it stays with the controller.

It drafts the adjusting entries and posts them once approved. Lease journals are already prepared and posted to NetSuite on schedule for Gorgias, a multi-entity, multi-currency team that extended Maxima from flux and cash entries into lease accounting. Nothing posts without a named approver. If a late posting hits after the tie, the GL and workbook balances can be refreshed on demand and the tie rerun straight away, without waiting for the next scheduled sync. That makes a late timing item a routine check rather than a second reconciliation. Every figure keeps its source-to-GL lineage. The security page documents the platform controls around it: Type II reports for SOC 1 and SOC 2, ISO 42001 certification, and customer data kept out of model training.

For the mechanics lease reconciliation shares with every other subledger tie, see how Maxima prepares journal entries, the reconciliations definitive guide, and its sibling for a schedule-driven balance, the prepaid expense reconciliation guide.

Bring one month's lease subledger reports and GL detail to a demo and see the workpaper prepared on your own data.

The calls that stay with the controller

The controller chooses the foreign-currency rate view for modified leases and applies it consistently. Whether each change was contractual, a remeasurement event or a correction is read off the document, not the system. The discount rate and its evidence, the question of whether a subscription agreement contains a lease, and which clearing-account balances are valid this month are the controller's calls too. And the signature on the reconciliation is the controller's, which is what turns a prepared workpaper into a control.

Frequently asked questions

Is the Fixed Assets Management lease feature enough on its own?

Not for a complete lease-to-GL reconciliation. It computes the schedule and creates the commencement and periodic interest journals, which can sit pending approval depending on setup, with the ROU asset depreciated as a fixed asset. Reporting is a handful of lease saved searches plus the asset register, with nothing documented that compares each lease to the GL, and the lease record holds only the subsidiary's base currency. A domestic portfolio can run it with a workbook. The native record cannot hold a foreign-currency lease in its own currency; such a lease goes to a subledger that supports it, or, in practice, is converted on entry with the remeasurement handled outside the record.

How do you reconcile lease liabilities and ROU assets to the GL in NetSuite?

Start from the lease register, not the variance: confirm every commenced, modified and terminated lease is in the subledger before anything is tied. Run the subledger's own GL-to-subledger report where one exists, or tie the saved-search or schedule totals to the ROU, accumulated amortization and liability accounts where it does not. Classify each issue into one of the five families, book the adjusting entries with the lease reference on them, and save the reports before and after. The signature covers the explained items and the evidence, not the fact that the totals agree.

Which exchange rate does a right-of-use asset carry in NetSuite?

The commencement-date rate, because ASC 842-20-55-10 treats the ROU asset as nonmonetary, with accumulated amortization at the same historical rate under ASC 830-10-45-18. In NetSuite that means the ROU and accumulated amortization accounts stay unflagged for currency revaluation and the lease liability accounts are flagged, unless the lease subledger books the remeasurement itself. After a modification that is not a separate contract, the entity's policy decides whether the whole asset moves to the modification-date rate or, under the layered view, only the increase does while the pre-modification balance keeps its historical rate.

How do you reconcile a lease change that was really a correction?

Log it in the modification register as a correction, with the document that proves the contract did not change. Use the subledger's correction workflow if it has one that covers the lease. If it does not, decide the correction from the accounting facts: the ROU asset keeps its commencement rate, and any rate reset the system applied is reversed. The item closes when the register, the reversing journal and the post-adjustment report agree.

Where does a wrong incremental borrowing rate show up?

Not in a clean subledger-to-GL tie. The schedule and the GL both derive from the rate loaded at commencement, so they can agree every month even when that rate is wrong. It surfaces only when someone rebuilds the schedule from the lease terms and the approved rate, which is why the rate and its source are kept as evidence with the lease.

What does the lease reconciliation have to support in the disclosures?

The quantitative items in ASC 842-20-50-4 and 50-6: the lease cost components, cash paid, new ROU assets, the weighted-average term and rate, and the maturity analysis tied to the balance sheet liability. They are built from the same signed-off lease population, which is why the reconciliation is signed first.