Intuit Sequence acquisition: Build a Deferred Revenue Roll-Forward Before Revenue Management Moves Into QuickBooks

The Intuit Sequence acquisition, announced October 15, 2026, promises an integrated revenue management offering for Intuit Enterprise Suite and QuickBooks Online Advanced in the coming months. Whatever you decide about tools, prepare the same way: a deferred revenue roll-forward by contract that ties to the general ledger, so any new system starts from proven balances.

Why this matters now

Intuit's press release of 2026-10-15 says it has signed an agreement to acquire Sequence, a revenue management company that "automates the end-to-end quote-to-revenue process for businesses." The release names the products the deal is meant to strengthen, Intuit Enterprise Suite and QuickBooks Online Advanced, and describes the goal as "a single platform to price, bill, and collect on revenue tied to consumption, usage, seats, and milestones." Financial terms were not disclosed. Intuit says it "will develop an integrated offering in the coming months" and will continue to support Sequence customers after the acquisition closes.

Sequence's own announcement, also dated 2026-10-15, describes the product as covering deal configuration, pricing, billing, invoicing, collections, and revenue recognition, with AI agents handling daily tasks alongside finance teams. Its co-founder and CEO, Riya Grover, will join Intuit's mid-market product organization. CFO Dive's report of 2026-10-15 adds that Sequence was founded in 2021, raised a $20 million Series A last December, and serves finance teams at high-growth software and services companies. CPA Practice Advisor's coverage, published 2026-10-15, notes that the Sequence team is joining Intuit and that the offering is aimed at mid-market businesses and the accounting firms who advise them.

What none of that gives you is a date, a price, a feature list, or a migration path. The coverage reports the deal. It does not tell a CFO on QuickBooks Online Advanced, or a controller already running a separate billing tool, what to prepare before an integrated offering appears. That preparation is the same whichever way the product lands, and the deliverable is a deferred revenue roll-forward by contract that ties to the general ledger. October is a good month to build it. The September quarter just closed, 2027 budgets are being set, and most mid-market teams have a renewal or a contract change in the pipeline that will test the schedule anyway.

What the deal says, and what it does not say yet

Three facts are on the record. The agreement is signed and not closed. The target products are Intuit Enterprise Suite and QuickBooks Online Advanced. The billing models called out are consumption, usage, seats, and milestones. Everything else, including timing, pricing, which plan tiers get what, and how an integrated offering would treat existing schedules, is unstated. Planning around a guess is how migrations go wrong.

Those three facts still matter, because the billing models named are exactly the ones that break a spreadsheet schedule. A straight annual subscription recognized in twelve equal pieces is easy. Usage billed in arrears, seats added mid-term, and milestones billed ahead of or behind the work are where billings and revenue diverge, and the divergence is the deferred revenue balance. If a new system is going to take over those schedules, it will need an opening balance per contract on the cutover date. If you stay where you are, you still need the same number every month end. Either way the baseline comes first.

There is a second reason to act now rather than after a product announcement. A tool migration is the moment when prior-period errors surface, because the new system forces a contract-level opening balance that the old spreadsheet never had to produce. Finding those errors in a quiet month is a correcting journal entry. Finding them during a cutover, with an auditor watching, is a restatement conversation. The ASC 606 in QuickBooks Online guide explains why the ledger alone cannot carry the schedule. This article is about proving the schedule you already have.

Build the deferred revenue roll-forward by contract

A deferred revenue roll-forward lists, for every contract, the opening contract balance, billings during the period, revenue recognized during the period, and the closing balance. Opening plus billings less revenue equals closing. Billings are a flow: an invoice debits accounts receivable and credits deferred revenue. Revenue is a flow: recognition debits deferred revenue and credits the revenue account as performance obligations are satisfied. The opening and closing figures are points in time, and the closing figure is what the balance sheet reports.

Under ASC 606 the sign of the closing balance tells you what it is. When billings run ahead of revenue, the contract has a liability, which is deferred revenue. When revenue runs ahead of billings, the contract has an asset, an unbilled receivable or contract asset. The standard requires that position to be determined and presented contract by contract, not netted across the customer base. That is the first thing a contract-level roll-forward exposes and a single ledger account hides.

A worked example for the September quarter

Take a software company with three contracts in the quarter ended September 30, 2026. Contract A is an annual seat subscription, $120,000 billed on July 1 for twelve months, recognized at $10,000 per month. Contract B is usage based and billed monthly in arrears: June usage of $7,000 was billed July 1, July usage of $8,000 was billed August 1, August usage of $9,500 was billed September 1, and September usage of $11,000 will be billed October 1. Revenue for Contract B is recognized in the month the usage occurs. Contract C is a $60,000 fixed-fee implementation billed 50 percent at signing on July 15 and 50 percent at acceptance, expected in November, with revenue recognized over time on hours incurred and the work 40 percent complete at September 30.

Three things to notice. First, the total closing balance of $85,000 is not what the balance sheet should show. It should show a contract liability of $96,000 and a contract asset of $11,000, because Contract B's unbilled September usage cannot offset Contracts A and C. Second, Contract B's billings and revenue differ by $4,000 in the quarter even though the contract is billed as you go, because billing lags usage by a month. Third, Contract C carries $6,000 of deferred revenue on a milestone billed at signing, and that balance will swing to an unbilled asset in October as hours continue and no invoice goes out until acceptance.

The three tie-outs

The roll-forward is only a baseline once each column ties to the ledger. The billings column ties to the period's invoice total in accounts receivable, after sales tax and after credit memos, filtered to the revenue items in scope. The revenue column ties to the period's revenue accounts on the P&L for the same items. The closing column, split into liability and asset, ties to the deferred revenue and contract asset balances on the balance sheet at the period end. Each tie-out produces a difference, and each difference gets a named cause: a contract with billings but no schedule, a schedule with no contract, a credit memo booked to revenue instead of to deferred revenue, or a manual journal entry nobody carried into the worksheet.

Run the same roll-forward for each entity if you have more than one, and keep the entity column. Consolidated deferred revenue is a separate problem, and the balance sheet by dimension pilot covers the opening-balance checks that apply when balances are reported by entity or dimension. When contract terms change mid-period, the contract modification guide explains whether the change is a new contract or a modification of the old one, which decides which row of the roll-forward it belongs to.

Accounting controls for the deferred revenue baseline

Source data: signed contracts and order forms with price, term, billing model, and milestone definitions; the invoice register from accounts receivable for the period with sales tax and credit memos identified; usage reports from the metering system for consumption contracts; milestone acceptance evidence; the trial balance at both period ends; and the two press releases dated 2026-10-15, saved with the date they were read, because what Intuit has said will change as the integrated offering is defined. Every export carries the date it was pulled, since invoices get voided and usage gets restated.

Calculation: one worksheet per period with formula cells only. One tab lists contracts and their recognition method. One tab builds billings per contract from the invoice register. One tab computes revenue per contract from the method: straight-line by day or month for term subscriptions, usage times rate for consumption, and inputs to date over total expected inputs for over-time milestones. The roll-forward tab applies opening plus billings less revenue, then classifies each closing balance as a liability if positive or an asset if negative. The entries behind the columns are fixed. An invoice debits accounts receivable and credits deferred revenue. Recognition debits deferred revenue and credits revenue. An unbilled amount debits contract asset and credits revenue, and the later invoice debits accounts receivable and credits contract asset. Nothing is typed over a formula.

Review: someone other than the preparer ties the billings column to the accounts receivable invoice total, the revenue column to the P&L, and the split closing balances to the balance sheet; re-performs the revenue calculation for three contracts, one per billing model; confirms no netting across contracts; lists contracts with billings and no schedule, and schedules with no contract; and reads every manual journal entry posted to the deferred revenue account during the period with its support. Differences are listed by contract with a cause, and the sum of the differences explains the whole gap to the ledger.

Decision: the CFO owns two decisions. The first is what to do with each listed difference: a correcting entry this period, a prior-period adjustment, or a policy clarification. The second is the tool question, and it does not have to be made today. Staying with the current setup, adopting a standalone billing platform, or waiting for Intuit's integrated offering all start from the same contract-level opening balances, so the baseline is the deliverable regardless of the choice. Each decision gets an owner, a date, and a re-test at the next quarter end.

Limits and common mistakes

First, the deal is not closed and the integrated product does not exist yet. Nothing above describes how that offering will work, and your recognition policy is set by ASC 606 and your contracts, not by whichever tool holds the schedule. A tool change is never a reason to change a policy.

Second, billed as you go is not the same as recognized as you go. The right-to-invoice shortcut applies only when the amount you can invoice corresponds directly to the value transferred to date. Minimum commitments, tiered pricing that resets, and credits for overages break that match, and then the variable consideration has to be estimated and constrained rather than copied from the invoice.

Third, mid-term seat additions are contract modifications. Added seats priced at their standalone selling price are treated as a separate contract and get their own row. Added seats at a discount that reflects the existing relationship are accounted for prospectively with the remaining consideration, which changes the monthly revenue on the original row from the modification date forward.

Fourth, the billings column is net of sales tax and credit memos. Gross invoice totals that include tax overstate billings and create a closing balance that will never clear. A credit memo coded to revenue rather than deferred revenue produces the same symptom in the other direction.

Fifth, with more than one entity, never net a contract asset in one entity against deferred revenue in another, and convert foreign currency balances at the period-end rate while revenue flows use the rates in effect when recognized. The two rates differ, and the difference belongs in the currency adjustment, not in the roll-forward.

Finally, this article covers the arithmetic and the control design, not legal or tax matters. Presentation questions on contract assets, and any prior-period adjustment the review surfaces, should be discussed with your auditor before the entries are posted.

Frequently Asked Questions

What is a deferred revenue roll-forward?

A deferred revenue roll-forward lists, for each contract, the opening contract balance, billings during the period, revenue recognized during the period, and the closing balance, where opening plus billings less revenue equals closing. Billings and revenue are flows for the period, and the opening and closing balances are point-in-time figures that tie to the balance sheet.

Does the Intuit Sequence acquisition change how QuickBooks Online handles revenue recognition today?

Not yet. As of the October 15, 2026 announcement, the agreement is signed but not closed, financial terms were not disclosed, and Intuit has said only that it will develop an integrated offering for Intuit Enterprise Suite and QuickBooks Online Advanced in the coming months. Your recognition policy is set by ASC 606 and your contracts, not by the tool.

Why can't I net contract assets against deferred revenue?

ASC 606 requires the contract asset or contract liability position to be determined for each contract, so an unbilled balance on one customer cannot offset a prepaid balance on another. A single net deferred revenue account understates both the liability and the asset, which is why the roll-forward classifies each contract's closing balance separately.

How do usage-based contracts show up in the roll-forward?

Usage-based revenue is recognized in the period the usage occurs, while the invoice usually follows in the next period, so the contract carries a contract asset at each period end equal to the unbilled usage. In the roll-forward, billings lag revenue by one period and the closing balance is negative, which the balance sheet presents as an asset rather than as deferred revenue.

What should I prepare before migrating billing or revenue schedules to a new tool?

Prepare a contract-level roll-forward for the cutover period whose billings tie to accounts receivable, whose revenue ties to the profit and loss statement, and whose closing balances, split into liabilities and assets, tie to the balance sheet. Every difference should have a named cause and a decision, because the new system will need a proven opening balance for every open contract.

FinBoard reads each entity's QuickBooks Online file into one reporting layer, so the billings, revenue, and balance sheet figures the roll-forward ties to come from the same ledger data, across entities, with drill-down to the invoices and journal entries behind every number. See how FinBoard supports finance teams on QuickBooks.