NetSuite Expense Amortization Controls and Tie-Out

Executive Summary

NetSuite Expense Amortization is appropriate when a purchased good or service creates a prepaid or deferred cost that should be released to expense over specified accounting periods. NetSuite first routes the covered amount to a Deferred Expense account, then uses a non-posting amortization schedule as the instruction set for later journals. The schedule itself does not affect the general ledger, so the close is incomplete until an authorized user generates the amortization journal entries ^[1]. For bill-based schedules, those journals normally debit expense and credit deferred expense.

The key decision is not simply whether a payment spans several months. Management needs an approved policy covering eligible cost, service-start evidence, period convention, residuals, dimensions, currency, ownership, and materiality. FASB describes an asset as a present right to an economic benefit and expenses as including the using up of assets ^{[2] [3]}. That principle supports prepaid-expense recognition, but it does not create a universal capitalization threshold. Both quantitative and qualitative factors belong in the policy decision ^[4].

The recommended control chain is classify, select, approve, create, generate, modify, reconcile, certify. Standard templates cover time-based schedules; Variable templates are specifically for project service items and depend on project completion. With vendor-bill approval routing, the schedule is not created until bill approval ^[5]. After creation, only unrecognized amounts may be changed when schedule modification is enabled ^[6]. Posted history should be corrected through supported credits or separately approved journals, not by silently rewriting the schedule.

At month-end, the controller should tie opening deferred expense plus new deferrals minus recognition minus credits or write-offs, plus or minus reclasses and foreign-exchange effects, to ending deferred expense. Oracle's Deferred Expense Rollforward is designed to reconcile balance-sheet movement to the income statement ^[7]. Inquiry alone is not sufficient evidence of control operation, so the close package should retain the report, general-ledger tie-out, exception log, approvals, and evidence of follow-up ^[8].

Introduction and Background

This report examines NetSuite expense amortization as a controlled prepaid-expense process, not as a generic synonym for depreciation or lease amortization. The practical problem begins when Accounts Payable records a bill before the company has consumed the related service. A one-year software subscription, insurance premium, support contract, or similar cost may create a prepaid asset at payment or billing, followed by periodic expense recognition as benefits are received. FASB's conceptual framework explicitly notes that many assets deliver benefits across several periods and identifies amortization as a form of systematic allocation ^{[9] [10]}. Comparable official guidance describes recognizing expense as the entity receives the prepaid service ^[11].

In NetSuite, Expense Amortization automates the link among a source transaction, a schedule, and generated journal entries. The Accounting Periods feature must be active before Amortization can be enabled, and NetSuite adds a default Deferred Expense account when the feature is turned on ^[12]. A line needs an amortization template and a deferral account. The template supplies the recognition logic; the schedule applies it to the transaction amount and dates; journal generation produces the posting.

That automation narrows clerical risk but does not replace judgment. Management remains responsible for internal control over financial reporting, including outsourced activities ^{[13] [14]}. Control evaluation should address both design and operating effectiveness ^[15]. Accordingly, the design objective is not merely to produce twelve equal entries. It is to show why a cost qualified, why a template was selected, when recognition started, who approved any change, what posted, and how the ending balance tied to the general ledger.

The guide therefore addresses NetSuite amortization templates, NetSuite amortization schedule changes, NetSuite prepaid expense amortization, NetSuite amortization controls, and the NetSuite month-end amortization tie-out as parts of one lifecycle.

Definition, Scope, and Decision Taxonomy

What native Expense Amortization is

Expense Amortization is NetSuite's transaction-linked mechanism for moving a purchase or expense amount from a deferred expense balance into expense over time. NetSuite uses one Deferred Expense account type for prepaid and deferred expense. The accounting policy may still distinguish current from noncurrent presentation or separate categories by account, subsidiary, department, class, or custom segment. Federal accounting guidance provides the same core classification logic: advances and prepayments are initially assets and are reduced as goods or services are received ^{[16] [17]}.

Native amortization is strongest when the source transaction is the audit trail. The bill or credit carries the schedule selection, the schedule preserves future recognition, and the generated journal links recognition to the scheduled line. A recurring journal repeats a predesigned posting, but it does not inherently preserve the same one-to-one relationship with each vendor bill. Recurring-journal generation can still be separated from review, approval, and posting ^[18].

Table 1 summarizes the decision boundary. It is a classification aid, not an accounting conclusion for every contract.

The table shows why classification precedes configuration. A contract labelled “annual” is not automatically a prepaid expense, and a payment schedule does not by itself prove a lease. Finance should route ambiguous arrangements to the company's accountant before choosing a NetSuite feature. The Houseblend row is included because the firm directly provides NetSuite implementation and administration, but it is intentionally separated from the accounting mechanisms.

Accounting-policy inputs

A usable policy turns judgment into explicit inputs:

• Eligible cost: Define which types of purchased benefits may be deferred and which are expensed immediately.

• Start trigger: Require evidence of service availability, coverage commencement, receipt, or another policy-approved event. Canada's accrual-method guidance expresses the timing concept as assigning the prepaid expense to the year or years receiving the related benefit ^[25].

• Period convention: Specify equal periods, exact days, a first-period convention, or an approved custom pattern.

• Residual treatment: Define when any amount may remain deferred and who approves it.

• Materiality: Use company-specific quantitative and qualitative factors. ICAEW likewise describes materiality in terms of the size and nature of a misstatement ^[26].

• Dimensions: Identify the department, class, location, project, custom segment, subsidiary, and accounting book that must remain consistent.

• Currency: State whether recognition is based on base currency or a supported foreign-currency schedule, and how remeasurement differences are reconciled.

• Ownership: Separate requester, AP preparer, schedule approver, journal poster, and reconciler where practical.

The policy should not borrow a universal dollar threshold from another company. SEC staff has described a percentage as only a possible starting point and emphasizes both quantitative and qualitative factors ^{[27] [28]}.

Template Governance and Feature Configuration

Standard and Variable templates

NetSuite provides Standard and Variable template types. Standard templates require a recognition method and term source. Variable templates are intended for percent-complete expense recognition on project service items ^{[29] [30]}. A controller should not use Variable merely because a calendar pattern is uneven. Variable schedules depend on project behavior and approved time entries.

For Standard templates, the main design fields have distinct control consequences:

• Recognition method: Choose the supported straight-line method or a custom method that matches policy. Exact-days recognition may differ by period because days differ; even-period recognition does not prorate by day.

• Term source: Decide whether terms come from a fixed period, transaction dates, receipt date, or another supported basis. If no transaction-level start date exists, the configured fallback should be understood and tested.

• Offsets: A Period Offset moves the schedule while preserving its period count. A Start Offset delays recognition but preserves the end date, reducing recognized periods.

• Initial amount: Define any fixed amount or percentage recognized in the first period.

• Residual: Define the amount or percentage intentionally left in Deferred Expense rather than amortized.

• Accounts: Confirm the deferral and target expense accounts. A template account can override the transaction's expense account.

Because all amortization templates are public in the account, naming and change control matter. A small group should maintain templates, while AP selects from approved choices. Transactions should be authorized and executed only by people acting within their authority ^[31].

Table 2 is a model template register. Its example rows are hypothetical and should be replaced with company-approved settings.

The register makes template reuse auditable. It also prevents an edit from silently changing the accounting result for future bills. Rather than overwrite a live template's meaning, a controlled design normally inactivates the prior version after open transactions are assessed, then introduces a newly named version. Policies should document what is expected and procedures should document the implementing actions ^[32].

Roles, permissions, and setup controls

Configuration should be tested before production use. Periods must cover the entire expected schedule horizon. Accounts should include the correct Deferred Expense type and target expense accounts by subsidiary and book. Forms should expose schedule, date, residual, and project fields only where needed. Permissions should separate template administration, schedule access, journal creation, journal approval, and report access. Access reviews should be documented and preserve segregation of duties wherever possible (Source: finance.gov.au). The modification preference should be enabled only after change approval and monitoring are designed. Finally, reports should be validated against known UAT cases.

Segregation should separate authority, custody, and accounting where practical; if that is impossible, management should design alternative controls ^{[33] [34]}. For a lean finance team, the compensating control might be a controller review of all new schedules, template changes, manual reclasses, and users with schedule permissions.

Transaction, Schedule, and Journal Lifecycle

From classification to posting

A controlled transaction follows a visible sequence:

1. Classify the purchase. AP confirms that the cost meets the company's prepaid policy and is not a fixed asset, lease, ordinary period expense, or project percent-complete item.

2. Capture the service facts. The requester supplies coverage dates, service-start evidence, contract amount, cancellation terms, department, class, project, and owner.

3. Select the template. AP selects only an approved template and enters transaction-specific start or end dates where policy permits.

4. Approve the bill. When vendor-bill approval routing applies, schedule creation waits for approval. This means an unapproved bill will not yet appear as a created amortization schedule.

5. Review the schedule. The preparer compares schedule total, periods, account, and dimensions to the source. The reviewer investigates residuals, unusual offsets, and first-period amounts.

6. Generate journals. The close owner filters the Create Amortization Journal Entries page by posting period and, in OneWorld, subsidiary. With Multi-Book Accounting, the relevant accounting book also belongs in the selection and review.

7. Approve and post. The journal follows the configured approval route. The control owner verifies that no due schedule was omitted and no journal remained rejected or on hold.

8. Reconcile. The reconciler ties the roll-forward, general ledger, schedule detail, and source activity, then records and ages exceptions.

This sequence distinguishes schedule creation from general-ledger recognition. The journal-entry control should identify who initiates, authorizes, records, and processes period-end entries ^[35]. UK government guidance similarly states that direct journals should require authorization with appropriate segregation of duties ^[36].

Transaction eligibility and exceptions

Templates can be used with vendor bills, vendor credits, and manual journals. For an expense line, a deferral account must be present on the expense account or template. However, NetSuite disables amortization settings on a vendor-bill line derived from a purchase-order line with an accrual ^[37]. That constraint belongs in UAT if purchase orders use accruals.

The operational exception queue should flag:

• Approved bills without expected schedules. Likely causes include missing templates, missing deferral accounts, unsupported PO accrual lines, or dates outside configured periods.

• Schedules with residual balances. Confirm whether the residual was intentional and approved.

• Due lines without journals. The schedule may exist even though no posting has been generated.

• Unexpected accounts or dimensions. Compare source, schedule, and journal classifications.

• Rejected or unposted journals. These should be investigated promptly ^[38].

• Closed-period catch-up. NetSuite moves a closed-period schedule amount to the oldest open period. The resulting concentration needs review and clear cutoff support.

Schedule Changes, Credits, and Global Considerations

How to edit an amortization schedule in NetSuite

An administrator first decides whether direct schedule modification is permitted at all. When the Allow Users to Modify Amortization Schedules preference is enabled, an authorized user can edit the name and existing lines' account, posting period, and amount. New lines cannot be added, other values cannot be changed, and the edited line amounts must still equal the schedule total ^[39].

The safe procedure is:

1. Open a change request with the source transaction, schedule ID, old and new dates or amounts, reason, and accounting analysis. The accounting position paper should preserve the matters considered in reaching the decision (Source: finance.gov.au).

2. Assess posted periods. Direct edits apply only to unrecognized amounts. Determine whether a separate correction or reclassification is required for posted history.

3. Obtain approval from someone independent of the editor, based on the company's materiality and close policy.

4. Edit in the appropriate book. Multi-Book secondary schedules have a separate Update Amortization process, so a primary-book edit should never be assumed to update every book.

5. Reperform the math and compare future lines, total, account, dimensions, and residual to the approved request.

6. Retain evidence of requester, editor, approver, timestamp, before-and-after values, and resulting journal impact.

NIST's general change-control model is useful here: a change should be formally requested, impact-evaluated, tested, approved, and then verified after implementation ^{[40] [41]}.

Credits, cancellations, refunds, and reclasses

For a vendor cancellation or partial refund, use the underlying commercial and accounting evidence to determine the correct transaction. The supported pattern is a vendor credit rather than silently changing the original amortized purchase transaction. A bill-derived vendor credit inherits the bill's expense-line amortization information. The correction must remain supported; Treasury guidance explicitly rejects unsupported reconciliation entries ^[42].

Do not assume that editing an amortization journal changes the schedule. Key system-generated fields are restricted, and journal edits do not rewrite the generating schedule. Where classification must change, a separately approved month-end reclassification may be clearer than attempting to mutate the system-generated journal. Period-end procedures should include review of material adjustments made while preparing the financial statements ^[43].

The change log should include the request and business reason, old and new values, posted-period assessment, approval evidence, editor identity, journal impact by period and book, and reconciliation status with a close-package reference.

OneWorld, dimensions, currency, and projects

In OneWorld, schedules and generated journals are subsidiary specific, and users see only subsidiaries to which their roles have access. The transaction's subsidiary constrains available departments and items. Reconciliation should therefore occur by subsidiary and base currency before consolidation.

With Multi-Book Accounting, schedules are book-specific, journal generation requires an Accounting Book filter, and report filters must be validated by book. Secondary books can also have different subsidiary base currencies. A primary-book tie-out does not prove that secondary-book recognition is complete.

Foreign-currency amortization requires special caution. Oracle documents the feature as available only in UK editions, using historical transaction exchange rates; related reports exclude revaluation of the source transactions and journals ^[44]. Other editions and account configurations require account-specific testing rather than inference.

For projects, Variable schedules require Project Management and calculate completion from entered and approved time. They do not provide forecast amounts ^[45]. That is a separate recognition basis from a conventional prepaid subscription.

Month-End Reconciliation and Control Evidence

The roll-forward equation

The central month-end test is:

Opening deferred balance + new deferrals - recognized expense - credits or write-offs + or - foreign-exchange and reclassification effects = ending deferred balance.

Each term should map to a report or controlled journal population. Oracle's roll-forward columns include new vendor bills and credits, system-generated amortization journals, beginning balance, and ending balance. The beginning balance should tie to the prior period's balance sheet, while the ending balance should tie to the same period's balance sheet ^[46].

The close owner should perform the following sequence:

• Generate due journals for every subsidiary and accounting book in scope. Reconciliations, journal processing, and suspense clearing are recognized period-end activities (Source: finance.gov.au).

• Review generation exceptions, including due schedule lines absent from a journal and journals awaiting approval.

• Run the roll-forward by subsidiary and base currency before consolidated review.

• Tie opening balance to the prior certified ending balance.

• Tie new activity to vendor bills, credits, and approved manual journals posted to Deferred Expense.

• Tie recognition to system-generated amortization journals and identify manual entries to the same accounts.

• Review ending schedules for negative balances, stale residuals, elapsed end dates, and missing source evidence.

• Investigate variance rather than forcing an unsupported plug. Treasury reconciliation guidance advises keeping causes of differences and analyzing them monthly for recurrence ^[47].

• Certify and retain the report parameters, general-ledger extract, exception disposition, approvals, and reviewer sign-off. Documentation should identify who performed and reviewed the work ^[48].

Reconciliation is a detective control, while template restrictions, permissions, and approvals are preventive controls. Effective internal control commonly combines both ^[49]. COSO describes monitoring as periodic or ongoing evaluation, which supports recurring review of template access, modifications, and aged exceptions ^[50].

Exception aging and evidence quality

An exception register should record owner, age, amount, root cause, financial-statement effect, correction, due date, and reviewer. Useful categories include missing schedules, unposted journals, unauthorized template use, unexpected residuals, closed-period catch-up, manual entries to deferred accounts, credit mismatches, dimension differences, and foreign-currency variances.

Age alone does not determine materiality, but age reveals process weakness. A small recurring exception can indicate a broken interface, form, or training step. Australia's Department of Finance recommends regular review of correcting journals to identify processing patterns (Source: finance.gov.au).

Evidence should be reproducible. If a report is used as control evidence, retain its parameters and test its completeness and accuracy. PCAOB guidance requires company-produced information used as audit evidence to be tested for accuracy and completeness or supported by controls, and to be sufficiently precise and detailed ^{[51] [52]}. The close file should identify who prepared and reviewed the reconciliation and when.

Data Analysis and Evidence

This section converts the control design into measurable schedule and reconciliation tests. The figures are hypothetical examples, not recommended thresholds or representations of a specific NetSuite account.

Assume a fictional software subscription costs $24,000 for service from January through December, with an approved equal-period method, no residual, and no initial amount. The allocable cost is $24,000, the eligible period count is 12, and the monthly amount is $2,000. NetSuite's even-period method does not prorate currency amounts by days in a period ^[53].

Assume separately a fictional $18,250 insurance premium covering 365 days with an approved exact-days method. The daily allocation is $50. A 31-day month would recognize $1,550, while a 30-day month would recognize $1,500. This pattern follows the principle that each day in the term receives an equal amount under the exact-days method ^[54].

Table 3 demonstrates a quarter-end tie-out for the fictional software schedule and an additional fictional insurance schedule. All amounts are illustrative.

The numerical control is not complete merely because the combined balance equals $31,750. The reviewer should also test whether the service dates were correct, whether the right template drove the pattern, whether each journal posted in the intended period, and whether manual activity was authorized. Reconciliation confirms complete and accurate processing, but it also helps identify unauthorized transactions and explain differences ^{[55] [56]}.

Three operational metrics make the process more observable. Schedule coverage rate is source transactions expected to amortize that have a valid schedule divided by all source transactions expected to amortize. On-time journal rate is due schedule lines included in approved, posted journals by the close deadline divided by all due lines. Exception aging groups unresolved items by amount and age band, with posted-period effects separately identified.

These are internal process measures, not external benchmarks. Targets should follow the company's close calendar, risk tolerance, and materiality policy. A SuiteAnalytics Amortization Schedule dataset can expose schedule lines and linked journal numbers. That makes it a useful basis for exception analytics after its completeness and permissions are validated. Other enterprise systems likewise provide a deferral report to reconcile recognized and remaining balances as of a specified date, reinforcing the category-level control objective ^[57].

Implementation Readiness, UAT, and Operating Model

Minimum UAT cases

User acceptance testing should cover normal processing and failure paths in a sandbox. At minimum:

• Standard equal-period bill: Verify deferral posting, schedule periods, journal account, and final zero balance.

• Mid-period start: Compare even-period and exact-days outcomes to policy-approved expectations.

• Approval routing: Confirm that an unapproved vendor bill has no created schedule and that approval creates the expected schedule.

• Missing deferral account: Confirm that the configuration error is visible and routed to an owner.

• PO accrual line: Confirm that amortization is unavailable on the documented unsupported line type.

• Vendor credit: Test full and partial credit, prior-period recognition, future schedule effect, and source links.

• Schedule edit: Change an unrecognized period and amount, verify total preservation, approval evidence, and the next journal.

• Posted-period correction: Confirm that prior recognized amounts are not silently changed and that the approved correction path works.

• Closed period: Verify catch-up into the oldest open period and the related exception review.

• OneWorld: Test role visibility, subsidiary filters, dimensions, and subsidiary-base-currency roll-forward.

• Multi-Book: Test primary and secondary schedules, journal generation, and book-filtered reports independently.

• Foreign currency: Where supported, verify historical-rate journals, rounding, and separation from revaluation.

• Variable project schedule: Verify approved time, percent completion, missing forecast behavior, and project selection.

• Report completeness: Trace a sample from source to schedule to journal and from journal back to source. Valid transactions should be recorded completely, accurately, and on time ^[58].

• Permission conflict: Confirm that an unauthorized role cannot maintain templates or schedules.

A walkthrough should combine inquiry, observation, document inspection, and reperformance, rather than relying on user explanations alone ^[59]. Change evidence should show the old result, approved new result, and successful post-implementation verification.

Operating ownership and external support

The steady-state model should name accountable roles. The accounting policy owner decides eligibility, thresholds, methods, and exception treatment with the company's accountant. A prepayment begins as an asset, while a capital-asset decision requires a different useful-life analysis ^{[60] [61]}. The AP preparer captures source facts and selects an approved template. The NetSuite administrator maintains configuration, roles, forms, reports, and controlled changes. The journal approver reviews the generated posting population. The reconciler performs the roll-forward and retains evidence, while the controller reviewer certifies the balance and exception disposition.

Houseblend is a direct provider of NetSuite implementation and managed-administration services, so it is a relevant external-support option when internal teams need help designing or operating this process. Its implementation scope includes modules, roles, permissions, forms, workflows, dashboards, and controls ^[62]. Its managed-support scope includes roles, permissions, forms, saved searches, dashboards, and ongoing requests ^[63]. Those services do not transfer management's accounting or control responsibility.

Consultant support is most warranted when configuration crosses books or subsidiaries, existing schedules do not tie, roles are overbroad, a migration includes partially recognized prepaids, or saved searches and datasets become key controls. In each case, the need is controlled design, evidence, and remediation rather than an unsupported journal plug.

Implications and Future Directions

The most consequential design choice is to treat the amortization schedule as a controlled subledger instruction, not as the accounting entry itself. That framing clarifies ownership: AP establishes transaction facts, the template governs recognition logic, the schedule displays expected future recognition, journal generation posts the current period, and the reconciliation proves completeness.

Automation should next focus on exceptions rather than indiscriminate posting. A validated SuiteAnalytics dataset can identify approved bills without schedules, due schedule lines without journals, schedules ending with residuals, unexpected manual postings to Deferred Expense, or recognition shifted into an open period. Information-processing controls should support completeness, accuracy, and validity of data ^[64].

Governance also needs a change cadence. Template owners should periodically review active versions, role assignments, unused templates, exception trends, and account mappings. COSO's framework identifies five integrated components and 17 principles, emphasizing that control activities sit within a broader system of risk assessment, information, monitoring, and governance ^{[65] [66]}. The practical objective is a repeatable close in which unusual items surface early and every balance has a traceable source.

Frequently Asked Questions (FAQs)

What is a NetSuite amortization template?

It is a reusable record that defines the terms used to build schedules, including template type, recognition method, term source, offsets, initial amount, residual, and account behavior. A Standard template supports time-based recognition; a Variable template supports project percent-complete expense recognition. Template selection should be governed through a register, naming convention, version date, owner, and approver.

When is a NetSuite amortization schedule created?

For an eligible purchase transaction, NetSuite normally creates the schedule when the transaction is saved. If vendor-bill approval routing is enabled, creation waits until the bill is approved. The schedule is non-posting and becomes a posting only when amortization journal entries are generated.

How are NetSuite expense amortization journal entries generated?

An authorized user opens the Create Amortization Journal Entries page, selects the posting period and applicable filters, reviews due schedules, and creates the journal. OneWorld requires a subsidiary filter, while Multi-Book Accounting requires an Accounting Book filter. The resulting bill-based journal normally debits expense and credits deferred expense.

How should NetSuite amortization schedule reconciliation work?

Reconcile opening Deferred Expense to the prior certified ending balance, add new bills and other deferrals, subtract recognition and credits, separately identify write-offs, foreign-exchange effects, and reclasses, then tie the computed ending balance to both schedules and the general ledger. Retain report parameters, source populations, exceptions, corrections, preparer evidence, and reviewer sign-off. Fiscal Service guidance frames reconciliation as supporting accurate and timely transaction data ^[67].

Can a posted amortization schedule be deleted?

Not while associated journal entries exist. Deleting a schedule generally requires removing the source transaction line, and linked journal entries must be dealt with first. Because deletion can affect posted accounting, the action should follow a documented correction and approval path rather than routine administration.

What happens to a NetSuite amortization amount in a closed period?

NetSuite posts the amount to the oldest open period. The close team should treat that shift as an exception, assess cutoff and financial-statement impact, and retain approval for any correction. A memorized transaction dated in a closed period similarly moves to the next open period, but it remains a different mechanism from a source-linked amortization schedule.

Is prepaid expense amortization the same as lease amortization or depreciation?

No. Prepaid expense amortization releases a purchased service or other deferred cost. Fixed-asset depreciation allocates a tangible asset's depreciable amount over its useful life ^[68]. Lease accounting recognizes and measures a right-of-use asset and lease liability. Each requires different records, calculations, and controls.

Does NetSuite set a materiality threshold for prepaid expenses?

No universal threshold is established by the cited product documentation, and this report does not recommend one. Management should approve a threshold and exception policy using the entity's facts, reporting requirements, and both quantitative and qualitative materiality considerations.

Conclusion

NetSuite's native Expense Amortization feature is most useful when a prepaid purchase needs a durable link from source transaction to future recognition. Its value is not simply equal monthly math. It creates a controllable chain among the bill or credit, the selected template, a non-posting schedule, generated journals, and the deferred-expense roll-forward.

A defensible design starts with accounting policy and classification. It then limits templates, roles, and schedule modification; captures service dates and dimensions; separates journal preparation from approval and reconciliation; and treats credits, closed periods, books, currencies, and projects as explicit exceptions. The month-end close should prove opening balance, additions, recognition, corrections, and ending balance, while preserving evidence that another reviewer can reperform.

The implementation test is simple: finance should be able to explain every material ending prepaid balance, trace every current-period recognition entry to an approved source and schedule, and show who approved each change. When that evidence is available by subsidiary and book, Expense Amortization is operating as a controlled subledger process rather than a collection of recurring journals.