Revenue Recognition

Revenue Recognition answers a different question from the rest of the workspace. Everywhere else, Revenue tells you when money moved. Here it tells you when revenue may be recognized — spread across the periods it was earned in, under ASC 606, rather than booked when the invoice was issued.


Overview

Open Revenue → Revenue Recognition, under Operations in the sidebar. From top to bottom the page has:

  • four summary cards for the selected accounting period;
  • a period summary that rolls the deferred-revenue balance forward, channel by channel;
  • Revenue trends and a 12-month recognition forecast;
  • the Revenue recognition schedule table;
  • the Unscheduled revenue records queue;
  • Close Period and Lock Period, for the periods you are ready to finalize.

All amounts are in USD, as the header notes beside the Recognition period selector. That selector defaults to the current month’s accounting period — or, if there is none, the latest one — and scopes the summary cards, the period summary, the schedule table, and the unscheduled queue; the trends and forecast always count from the current month. An accounting period exists for each month that has at least one schedule line, so a month without one is not offered.

The Channel filter in this page’s title row narrows the whole page: the summary cards, the period summary and its export, the trends and forecast, the schedule table, the unscheduled queue, and both table exports. Changing it takes both tables back to their first page. The Recognition period selector still lists every accounting period your organization has, whichever channel you choose.

The method each record is recognized by is not set here. Recognition policies live on the Revenue Settings page, which is also where the four available methods are documented.

Summary cards

CardMeaning
Recognized this periodRevenue recognized on the period’s schedule lines. The line beneath counts the schedule lines behind it. Lines stay Pending until their period is closed, so a period that is still open usually reads $0.00.
Deferred revenue balanceThe period summary’s Closing balance for the selected period and channel — see Period summary. Labelled Balance sheet liability.
Partially recognizedThe amount already recognized on lines that are part-way through — some, but not all, of their scheduled amount. Labelled In-flight and adjusted lines.
Unscheduled recordsA count of revenue records in the period that have no schedule line yet, with the revenue they carry beneath it as pending schedule. See Unscheduled revenue records.

Every card follows the period and the Channel filter. Recognized this period and Partially recognized also follow the schedule table’s search, status, and method filters: narrow the table, and those two cards narrow with it. Unscheduled records follows the queue’s search and reason filters the same way. A card’s value shows — when its data could not be loaded.

Deferred revenue balance is the same figure as the period summary’s Closing, so it reads — whenever the period summary cannot load — for example, before the first schedule line exists.

Period summary

The period summary panel — titled with the month it covers, such as Jun 2026 summary — bridges the deferred-revenue balance from the start of a month to its end. It always covers the month chosen in the Recognition period selector, so changing that selector moves the summary, its export, and the cards together.

The waterfall reads left to right:

  • Opening — the deferred balance carried in from every earlier month.
  • New payment — the cash your revenue records brought in during the month, in USD, less the refunds confirmed during the month. How the cash is measured differs by channel — see New payment.
  • Recognized — everything recognized on the schedule lines of the month’s accounting period.
  • Write-offs — for written-off records, the cash they brought in, less refunds, that was never recognized. A written-off record that was never paid adds nothing.
  • Closing — Opening + New payment − Recognized − Write-offs, which becomes the next month’s Opening.

Below the waterfall, three sections break the month down by channel:

SectionWhat it listsTotal label
Recognized revenueEach channel’s Recognized amount for the month.Net recognized
Deferred revenueEach channel’s Closing balance.Ending balance
Future contracted revenueWhat is still to be recognized on pending schedule lines in later accounting periods.Ending balance

A channel with nothing to report in a section is left out of it, and with a channel chosen in the Channel filter each section lists only that channel. Select Export CSV, then Download CSV in its dialog, to export the three sections — one row per listed channel in each section, plus a total row for each — in the columns Period, Section, Line item, and Amount. The file is recognition_summary_<date>.csv.

The summary needs at least one accounting period. Until the first schedule line has been generated there is none, and the panel reads Failed to load the rollforward. Try refreshing the page. It reads the same when a Stripe payment settled in a currency other than USD and Fours cannot get the exchange rate for its settlement date (see New payment). Then the Deferred revenue balance card reads — and the Deferred trend does not load either, while the schedule table, the Recognized and Booked trends, the forecast, and the unscheduled queue still load.

Recognized vs Deferred by Channel and Period

Recognized and deferred revenue by channel is in the period summary: its Recognized revenue and Deferred revenue sections list each channel, and stepping the Recognition period selector moves it from one accounting period to the next. For the individual schedule lines behind those totals — each with its channel, billing period, and status — use the Revenue recognition schedule.

Revenue trends charts one series at a time over the Last 3 months, Last 6 months, Last 12 months (the default), or Last 24 months — the current month and the months before it. Switch series with the buttons above the chart. The trends and the forecast follow the Channel filter.

ViewEach month showsTotal beneath the chart
RecognizedRevenue recognized on that month’s schedule lines.Cumulative recognized — the sum across the range.
DeferredThe deferred balance at month end — the same Closing balance the period summary computes.Closing deferred balance — the last month’s balance.
BookedRevenue invoiced that month: each revenue record’s USD base amount, by invoice date — before refunds, and including voided or written-off records.New bookings — the sum across the range.

Booked is not the Overview’s Bookings. Bookings on the Overview is contract value from entitlement terms; Booked here is invoiced revenue from revenue records, so the two will not match.

The 12-month recognition forecast charts what is still to be recognized on Pending schedule lines in the current month and each of the next eleven, with the Forecast total beneath. Alongside, up to six upcoming accounting periods are listed with their amount and a status chip: Pending for the first period listed when it is open, Forecast for later open periods, and otherwise the period’s own status.

Revenue recognition schedule

The Revenue recognition schedule table lists the schedule lines behind the cards, one row per line: Revenue record, Channel, Method, Billing period, Scheduled, Recognized, and Status. Select a column heading to sort by it; the table starts sorted by billing period, oldest first.

Narrow it with:

  • Search — matches the revenue record ID or the channel. It does not search customer or buyer names.
  • Status — Pending, Recognized, Adjustment, or Cancelled.
  • Method — Straight-Line, Point-in-Time, Usage based, or Milestone.

The table has no channel filter of its own: it follows the Channel filter in the page’s title row. Search, status, and method also narrow Recognized this period and Partially recognized.

Columns shows and hides the table’s columns, and you can drag a column header to move it; the first column stays first, and your choice is remembered in this browser. Export CSV downloads every schedule line that matches the Recognition period, the Channel filter, and the table’s filters — from all pages, not just the rows on screen — with the columns you show, as recognition_schedules_<date>.csv. Saved views describes the dialog.

When AWS credits an invoice, Fours lowers the record’s recognition basis to its original invoice amount less the credit, in USD at the record’s stored rate, and takes the reduction out of the record’s schedule lines that are still Pending, have nothing recognized yet, and sit in an OPEN period: their Scheduled amount drops, and a line left with nothing becomes Cancelled. Lines already recognized, or in a period that has been closed or locked, are not changed. If the credit later fails or is canceled, those lines are restored. Closing a period applies the same correction to its lines before recognizing them. A credited AWS record that has not synced since Fours began recording AWS credits keeps its stored basis.

Unscheduled revenue records

The Unscheduled revenue records queue lists revenue records that have no recognition schedule line yet — records whose recognition status is empty or Unrecognized and whose invoice date falls in the selected period. The chip at its top reads N records · $X at risk: the count, and the amount those records carry — each record’s USD base amount, before refunds.

Work the queue with:

  • Search — record ID, channel, buyer ID, product ID, or the channel’s own record ID.
  • Reason — why a record has no schedule yet (see the table below).
  • Sort — Amt (high to low), the default, Amt (low to high), Date (newest first), or Date (oldest first).

Each row shows the Revenue record, Channel, Buyer (the buyer ID), Amt, and Date (the invoice date). The reason is a filter rather than a column: pick a reason to see the records it applies to.

The queue has its own Columns control and draggable headers, like the schedule table. Like the rest of the page, it follows the Channel filter. Its Export CSV downloads every record that matches the Recognition period, the Channel filter, and the queue’s search and reason, with the columns you show, as unscheduled_revenue_<date>.csv.

ReasonWhat it means
Missing service datesA straight-line record has no service start or end date — on the record or on its entitlement.
Invalid service datesA straight-line record’s service end date is before its start date.
Missing trigger dateA point-in-time record has no trigger date, service start date, or invoice date.
Missing measurement windowA usage-based record has no dates to measure over — no service or entitlement period, and no invoice date.
Invalid measurement windowA usage-based record’s measurement window ends before it starts.
Missing milestone inputsA milestone record lacks a trigger date, an external trigger reference, or milestone amounts. An unscheduled milestone record currently shows this reason even when its milestone amounts are set.
Unsupported methodThe policy that applies names a method Fours cannot schedule.
Policy resolution failedNo recognition method could be resolved for the record.
Schedule pendingThe inputs look complete; the schedule has not been generated yet.
Service date lookup failedStill offered as a filter, but no record is currently given this reason: if Fours cannot look up service dates, the queue does not load.

The accounting period lifecycle

An accounting period moves through three states, and it only moves forward:

StatusWhat it means
OPENThe default. Schedules for the period can still be generated and changed, and their lines stay Pending.
SOFT_CLOSEDClose Period has run the recognition workflow for that period and recognized its pending schedule lines. An Admin can close it again, with a reason, to re-run the workflow. This is the state a period must be in before it can be locked.
LOCKEDThe period is final. Nothing can reopen it, and a further close or lock attempt is rejected.

Closing needs revenue write access, and locking — or closing a SOFT_CLOSED period again — also needs the Admin role. In the Insulin Revenue app, the Close Period card appears only if your role has revenue write access; the console shows it to every role and rejects the action for a role without it.

Close a period

  1. Enter the period — either a month such as 2026-06, or a period ID.
  2. Add a reason — optional for an OPEN period, required to close a SOFT_CLOSED period again.
  3. Select Close Period.

Closing starts the recognition workflow for that period: every pending schedule line in it is recognized at its scheduled amount, and the period moves to SOFT_CLOSED.

Lock a period

  1. Enter the period.
  2. Enter a reason — locking will not proceed without one.
  3. Select Lock Period.

Saved view

The page’s views are listed in the rail under Saved views · Revenue Recognition — see Saved views for saving, sharing, and who can change a view. A view here keeps the Channel filter, the Recognition period (which also sets the period summary’s month), the Revenue trends series and range, the schedule table’s search, status, and method filters and its columns, and the unscheduled queue’s search and reason and its columns. It does not keep the schedule table’s sort or the queue’s Sort choice, and the Close Period fields are never part of a view.

Without a view, only the two tables’ columns are remembered between visits; everything else resets when you leave the page.

KPI calculation formulas

All amounts are in USD: recognition schedules are generated in USD, and the page reports in USD only — except that a record with no USD base amount counts at its own-currency amount in Booked and the pending-schedule figure. Every figure follows the Channel filter. Each formula is the same for every channel that generates schedule lines — AWS, Azure, GCP, and Stripe — except New payment, whose cash rules differ by channel; Opening, Closing, Write-offs, the Deferred revenue balance card, and the Deferred trend are built on it. See New payment below, and Period summary for channels on the Net reporting basis.

KPIFormulaCalculation details
Recognized this periodΣ recognized amountOver the schedule lines in the selected period and channel that match the table’s search, status, and method filters — every status counts unless you filter one. The line beneath is the number of those lines.
Deferred revenue balanceClosing of the selected periodThe period summary’s Closing (below) for the selected Recognition period and Channel. The schedule table’s search, status, and method filters do not change it. Reads — when the period summary cannot load.
Partially recognizedΣ recognized amount where 0 < recognized < scheduledOver the same lines as Recognized this period.
Unscheduled recordscount(records with no schedule line)Records whose recognition status is empty or Unrecognized and whose invoice date is in the selected period, in the selected channel, narrowed by the queue’s search and reason filters.
Pending schedule · at riskΣ USD base amount of those recordsThe card’s $X pending schedule line and the queue’s $X at risk chip. A record with no USD base amount counts its invoice amount. Refunds are not subtracted, and voided or written-off records count at full value.
OpeningΣ (New payment − Recognized − Write-offs) over every earlier monthThe previous month’s Closing, carried forward.
New paymentΣ cash brought in during the month − Σ refunds confirmed during the monthCash is measured per channel — see New payment below. Each record counts toward its own channel.
Recognized (period summary)Σ recognized amount of the schedule lines in the month's accounting periodEvery status counts. Each line counts toward its record’s channel.
Write-offsΣ max(0, the record's cash − its confirmed refunds − everything recognized on its schedule lines) over written-off recordsCash and refunds are the record’s New payment amounts across every month, so a written-off record that never brought in cash adds 0. Placed in the month the record was last updated, or failing that its invoice month.
ClosingOpening + New payment − Recognized − Write-offsComputed per channel, then summed. The per-channel values are the Deferred revenue section.
Future contracted revenueΣ max(0, scheduled − recognized) over Pending lines in later accounting periodsLater means accounting periods that start after the selected month.
Recognized trendΣ recognized amount per monthTotal = the sum across the range (Cumulative recognized).
Deferred trendClosing balance at each month endTotal = the last month’s balance (Closing deferred balance). Built on New payment, so it follows the same per-channel cash rules, and it does not load when a Stripe settlement’s exchange rate is unavailable.
Booked trendΣ USD base amount of records per invoice monthTotal = the sum across the range (New bookings). A record with no USD base amount counts its invoice amount; refunds are not subtracted, and voided or written-off records count. Invoiced revenue — not the contract value the Overview’s Bookings counts.
12-month recognition forecastΣ max(0, scheduled − recognized) over Pending lines, per monthThe current month and the next eleven. Forecast total is the sum; each listed upcoming period shows its month’s amount.

New payment

New payment counts the cash each revenue record actually brought in, in the month it arrived, rather than the amount invoiced. Unless its row below says otherwise, a record counts its collected amount on its collected date when it has both, otherwise its disbursed amount on its disburse date. A later payout does not move cash already counted in the month it was collected.

Channel partnerFormulaIncluded/excluded dataDate, currency, and rounding rules
AWSnet amount collected, else disbursed amountNet amount collected = what AWS’s billing-event ledger shows it collected after its fee, or the disbursed amount when that is larger — the same figure Seller amount due uses. A record with no collected date and amount counts its disbursed amount.Collected date, else disburse date. Converted to USD at the record’s stored rate.
Azurecollected amount, else disbursed amountAn Azure payout already has its refunds taken out, so a record counted by its payout has no refund subtracted again.Collected date, else disburse date. Converted at the record’s stored rate.
GCPΣ payout Google reported, per report monthWhen Google reported a charge’s payout month by month — the per-report rows on Cash & Disbursements — each report’s payout counts in its own report month. A GCP record with a payout amount but no payout or collected date counts in the month its billing period starts, else its invoice month. Otherwise the general rule applies. A refund Fours has already applied to its original charge is not counted a second time.Report month (or the dates above). Converted at the record’s stored rate.
StripeΣ net amount settled of each Stripe payment linked to the recordThe net amount Stripe settled after its fee, as on Cash & Disbursements. Only payments that succeeded or settled count; refunds, credits, credit memos, and payments drawn from a credit wallet are left out. When none of the record’s payments carries Stripe’s settlement details, the general rule applies.The date the payment settled, else the record’s collected date, else when the funds became available, else the disburse date, else when the payment was created. A settlement in USD counts as is; one in another currency is converted at the published exchange rate for its settlement date — the most recent rate up to seven days earlier — looked up when you open the page. If that rate can’t be found, the period summary, the Deferred revenue balance card, and the Deferred trend don’t load.
Oracle, SnowflakeThe general rule—Converted at the record’s stored rate.

Refunds. A confirmed refund lowers New payment in the month it was confirmed — the month of its refund disbursement date or, for a refund that succeeded without one, its refund invoice date. The amount is the refund’s disbursed amount; a refund that succeeded with no disbursed amount recorded uses its refund invoice amount. Pending, failed, canceled, and requires-action refunds are not subtracted, and neither is a refund on an Azure record counted by its payout.

Currency. A record in USD counts as is. A record in another currency is converted at its stored USD rate; one with no stored USD rate adds 0 to New payment.

Freshness

Recognition schedules are generated as each channel’s revenue syncs in. A separate recognition recovery job runs hourly, at 17 minutes past the hour, and re-runs schedule generation for any sync that committed its records but ran out of retries before its schedules were built — so a missed generation repairs itself rather than leaving a permanent hole in the schedule.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.