Features
Prepaid expense automation

Prepaid expense automation on top of QuickBooks

Finlens builds prepaid amortization schedules directly from the bills already in your QuickBooks Online ledger, then prepares each period's journal entry with the source document attached.

ASC 340-10 Schedules built from bills in QuickBooks Online Review, then post
Illustrative data
Scroll sideways to see the whole screen →
Backed by

Schedules from source documents

Service periods are read from the invoice, so amortization begins on the correct date, not on the first of the month the bill was paid.

Controlled schedule updates

Amendments, credit notes and terminations recalculate the remaining periods instead of forcing a rebuild.

Audit trail by default

Every journal entry links back to the bill that generated it, in the period it was posted.

The problem

Manual prepaid amortization does not scale

Prepaid tracking holds at low volume and degrades predictably as contract counts and service periods grow.

  1. 01
    Schedules sit outside the ledger

    One workbook, one owner and no version control over the file supporting a balance sheet account.

  2. 02
    Recurring entries release a fixed amount

    QuickBooks Online's documented method is a recurring journal entry: the same figure each period, for an occurrence count you set when you create the template. That suits a contract beginning on the first of a month and running unchanged, and accommodates nothing else.

  3. 03
    Contract changes force a rebuild

    An amendment or credit note invalidates every remaining period, and the correction is manual in both the schedule and the ledger.

  4. 04
    Journal support is assembled after the fact

    Nothing connects the entry to the invoice until an auditor requests it, at which point the work is reconstruction rather than retrieval.

How it works

Prepaid amortization automated on your existing QuickBooks Online ledger

Finlens operates as a layer above QuickBooks Online. The general ledger, the chart of accounts and the close process stay where they are.

01 · Identification

Finds the bills

Bills with a service period crossing a period end are detected, including prepaid amounts coded to the profit and loss account in error.

02 · Schedule construction

Builds the schedule

Part first period, full periods thereafter, with the service dates read from the invoice and the proration you choose.

03 · Journal preparation

Prepares the entry

One entry per period, each line carrying the originating bill.

04 · Review

Review, then post

Drafted for review. Posts to QuickBooks Online when you approve it, or on schedule if you switch that on. The schedule shows what has posted and what is due.

Compared

Prepaid expense automation compared

The two ways this is done today on QuickBooks Online, against the one that keeps the schedule and the entry together.

RequirementSpreadsheetQuickBooks Online recurring entryFinlens on QuickBooks
Schedule built from the source invoiceManual entryManual entryAutomatic
Partial first periodFormula dependentNot calculatedCalculated by days
Mid-term amendmentRebuild requiredDelete and recreateRecalculated
Credit note appliedManual adjustmentNot reflectedAutomatic
Early terminationManualContinues postingStopped and trued up
Remaining balance by vendorSeparate worksheetAccount register onlyStanding report
Entry linked to source documentNoNoEvery line
General ledger remains in QuickBooksYesYesYes

Recurring-entry behavior as documented by Intuit for QuickBooks Online. Finlens does not replace QuickBooks; the entry posts to your existing company file.

Worked example

Schedules that recalculate when the contract changes

A $24,000 general liability policy incepting March 18 on a twelve-month term, with coverage increased by $6,000 in July. Struck figures are where a fixed recurring entry is wrong.

PeriodEventExpensePrepaid balanceFixed recurring entry
Mar 18, 2026Inception, $24,000 bill0.0024,000.000.00
Mar 2026Part period, 14 of 365 days920.5523,079.452,000.00
Apr–Jul 2026Four full periods, by days1,972.60 to 2,038.3615,057.532,000.00 each
Jul 4, 2026Amendment, +$6,000 coverage, applied from Aug0.0021,057.53 at Jul 31no change
Aug 2026–Feb 2027Seven recalculated periods, by days2,574.72 to 2,850.581,563.232,000.00 each
Mar 1–17, 2027Term ends1,563.230.00stopped; 6,000.00 stranded

The twelve-month term totals $30,000.00, the original $24,000 plus the $6,000 amendment. Every month is prorated by its service days, the product's default; the amendment applies from the month after it is recorded. Illustrative.

Control and audit

Every entry traced to its source document

Schedule calculations stay linked to the underlying bill, so a reviewer opens any period's entry and reaches the invoice, the service period and the basis of apportionment without leaving the record. Amendments and terminations are recorded against the schedule rather than applied silently, so the history of a balance reads in order: what was set up, what changed, and when.

Each month shows what has posted to QuickBooks Online and what is scheduled, with the journal entry number on the row. A roll-forward of opening balance, additions, releases and closing balance is available for any period, by vendor or by account, which is the schedule an auditor asks for first.

Illustrative data
Scroll sideways to see the whole panel →
40to70%
Faster month-end close, as Finlens customers report
80%+
Reduction in manual bookkeeping
12,000+
Bank connections available through Finlens
3+ hrs
Saved per new client engagement on chart of accounts setup

As published on finlens.app.

FAQs

Frequently asked questions

What accounting teams on QuickBooks Online ask before they move prepaids out of the workbook.

Still have a question?
Bring a contract that started mid-month to a 30-minute call.
Book a demo

Not on its own. Intuit's documented approach is a recurring journal entry that releases the same amount each period; the recurring template runs for a number of occurrences you set by hand. That suits an unchanged twelve-month contract starting on the first of a month. It does not handle a partial first period, a mid-term amendment, a credit note or an early termination, and it produces no amortization schedule.

No. Finlens works on top of QuickBooks Online rather than instead of it. Your existing QuickBooks Online setup stays as it is, and Finlens adds an automation layer that builds prepaid amortization schedules and drafts each period's journal entry, which posts back into QuickBooks once you approve it or on schedule if you switch that on. There is no migration and no second general ledger.

Finlens reads the bills already in your QuickBooks Online ledger, identifies those with a service period that crosses a period end, and builds a GAAP amortization schedule from the invoice dates. Each period's journal entry is then prepared with the originating bill attached, so there is no separate workbook and no manual keying.

Prepaid insurance, prepaid rent, prepaid software subscriptions, maintenance and support agreements, professional retainers and annual licenses. Any bill with a service period can be spread across its months.

Finlens customers report month-end close times 40 to 70 percent faster overall. Prepaid schedule maintenance and journal entry preparation are among the most repetitive tasks in a close, so a meaningful share of that reduction comes from this process.

No. Finlens works with your existing QuickBooks Online chart of accounts and requires no remapping. For a new client engagement that needs a chart built from scratch, Finlens can automate that setup, saving about three hours per engagement.

The schedule recalculates across the remaining periods. An amendment spreads the unreleased balance over the term that is left, and an early termination stops the release and trues up the residual balance in the period of cancellation. A fixed recurring entry does neither, which is where most prepaid balances drift.

Multi-year contracts need the portion releasing beyond twelve months to sit in non-current assets. Whether Finlens applies that split automatically is being confirmed by the product team.