How Aptitude RevStream works

Requirement evaluated: The system must handle contract modifications, specifically mid-term upgrades and downgrades, and correctly apply either prospective treatment or cumulative catch-up treatment under ASC 606 and IFRS 15 based on the modification's classification (new distinct goods or services vs. not distinct). The buyer currently hand-calculates these determinations at close; the system must automate the classification logic and produce a modification memo with the accounting rationale attached to the affected contract record, ready for auditor review.

For a high-growth B2B SaaS company currently hand-calculating modification treatment at close, RevStream does provide meaningful automation around the execution of contract modifications and SSP reallocation. <cite index="36-5">The platform is documented as able to retrospectively and prospectively adjust 'in-flight' arrangements with an interactive SSP engine that allows rules to be easily adjusted and fair values recalculated.</cite> <cite index="d0ac4f9b-fcdb-4cad-a719-6c81409f3e5e">Business users can modify contracts and transactions, with a complete audit trail capturing those changes.</cite> <cite index="51-3">The solution explicitly handles frequent modifications and the need to repor …

Limitations: The material gap for this buyer is that the treatment selection (prospective vs. cumulative catch-up) appears to remain a manual accountant judgment, which replicates the current spreadsheet-era risk inside a more structured system. …

Requirement evaluated: The system must produce audit-ready, auditor-facing revenue recognition schedules that provide full traceability from recognized revenue in the NetSuite GL back to the originating contract, performance obligation, SSP allocation, and any modification event. Given that the buyer's external auditors currently follow hand-built spreadsheet trails, the system must support auditor access or exportable workpapers that replicate the logical chain at the transaction level, not just at the summary level.

For a B2B SaaS company replacing hand-built spreadsheet trails with an auditable sub-ledger, RevStream provides a centralized repository that stores all contract, billing, and accounting data at the contract line level, which powers roll-forward reporting and deferred revenue schedules directly traceable to the originating contract. The platform documents a 'drill down from reported results to underlying transactions and business logic' mechanism, meaning finance users can navigate from a reported revenue figure back through the calculation chain to the source transaction. …

Limitations: The buyer's external auditors require transaction-level workpapers that replicate the logical chain from GL line to originating contract, SSP allocation inputs, and modification event — not just a dashboard they can navigate. …

Requirement evaluated: The system must automatically allocate the transaction price across all performance obligations at standalone selling price (SSP) using the residual, adjusted market assessment, or expected-cost-plus-margin methods as appropriate, and must support SSP range inputs and VSOE-equivalent SSP libraries for the buyer's professional services bundles. Because the buyer currently hand-calculates these allocations in spreadsheets, the system must produce a fully machine-generated allocation schedule that is auditable line by line by external auditors.

For a B2B SaaS company currently hand-calculating SSP allocations in spreadsheets, Aptitude RevStream addresses this requirement through a dedicated SSP Engine module that plugs into the core Revenue Recognition Manager. The SSP Engine was originally built to compute VSOE and BESP fair values under SOP 97-2 and EITF 08-01/ASU 2009-13 — the direct predecessor to ASC 606 SSP governance — and was carried forward to support the three ASC 606/IFRS 15 estimation methods. …

Limitations: The SSP Engine is a separately licensed module that extends the Transaction Hub; buyers must confirm in scoping that it is included in their contract, and the depth of configuration required for per-PO-class method selection (residual vs. adjusted market assessment vs. expected-cost-plus-margin) …

Requirement evaluated: The system must handle contract modifications, specifically mid-term upgrades and downgrades, and correctly apply either prospective treatment or cumulative catch-up treatment under ASC 606 and IFRS 15 based on the modification's classification (new distinct goods or services vs. not distinct). The buyer currently hand-calculates these determinations at close; the system must automate the classification logic and produce a modification memo with the accounting rationale attached to the affected contract record, ready for auditor review.

For a high-growth B2B SaaS company currently hand-calculating modification treatment at close, RevStream does provide meaningful automation around the execution of contract modifications and SSP reallocation. <cite index="36-5">The platform is documented as able to retrospectively and prospectively adjust 'in-flight' arrangements with an interactive SSP engine that allows rules to be easily adjusted and fair values recalculated.</cite> <cite index="d0ac4f9b-fcdb-4cad-a719-6c81409f3e5e">Business users can modify contracts and transactions, with a complete audit trail capturing those changes.</cite> <cite index="51-3">The solution explicitly handles frequent modifications and the need to repor …

Limitations: The material gap for this buyer is that the treatment selection (prospective vs. cumulative catch-up) appears to remain a manual accountant judgment, which replicates the current spreadsheet-era risk inside a more structured system. …

Requirement evaluated: The system must maintain a bidirectional, field-level integration with the buyer's existing NetSuite GL, writing recognized revenue, deferred revenue, and contract asset or liability journal entries back to NetSuite with the correct account, subsidiary, class, and department dimensions already populated, so that no manual journal entry re-keying or spreadsheet-to-GL upload step remains in the close process. The integration must also pull contract and billing source data from NetSuite in near-real-time rather than requiring manual exports.

For a B2B SaaS company closing revenue into NetSuite, RevStream's documented mechanism splits into two directions with materially different maturity levels. On the outbound side, RevStream holds a 'Built for NetSuite' certified SuiteApp called the RevStream GL Connector for NetSuite, built on the NetSuite SuiteCloud platform. This connector posts period-end revenue recognition and deferred revenue journal entries into the NetSuite GL and can be scheduled automatically or run on demand. …

Limitations: The inbound data pipeline is documented as flat-file and CSV-based rather than an event-driven or scheduled API pull, meaning the buyer's requirement to pull contract and billing source data from NetSuite in near-real-time without manual exports is not evidenced as supported. …

Requirement evaluated: The system must ingest contract and billing data from NetSuite and decompose each contract into discrete performance obligations, supporting the full complexity the buyer described: multi-year subscriptions, bundled professional services, usage-based overages, and ramped pricing tiers. Ingestion must be automated and traceable so that every performance obligation created maps back to a source contract line, eliminating the manual carve-out work currently done in spreadsheets before each close.

For a B2B SaaS company currently managing revenue in NetSuite-fed spreadsheets, RevStream's core decomposition engine is its Transaction Hub module, which centralizes bookings and arrangement information and provides automated tools to decompose multi-element arrangements into discrete performance obligations, eliminating the manual carve-out process. <cite index="27-1,27-2">The Transaction Hub "allows management of complex multi-element arrangements without relying on complicated spreadsheets and manual processes" and centralizes bookings and arrangement information with automated tools to identify and process each element.</cite> Once data is loaded, the Revenue Arrangement Manager (RAM) …

Limitations: The decomposition engine, SSP allocation, arrangement grouping, and audit trail are well-documented; however, no certified native NetSuite connector is evidenced for RevStream, meaning the NetSuite ingestion layer relies on flat-file or API pipelines that require configuration and ongoing maintenance. …

Requirement evaluated: The system must maintain a bidirectional, field-level integration with the buyer's existing NetSuite GL, writing recognized revenue, deferred revenue, and contract asset or liability journal entries back to NetSuite with the correct account, subsidiary, class, and department dimensions already populated, so that no manual journal entry re-keying or spreadsheet-to-GL upload step remains in the close process. The integration must also pull contract and billing source data from NetSuite in near-real-time rather than requiring manual exports.

For a B2B SaaS company closing revenue into NetSuite, RevStream's documented mechanism splits into two directions with materially different maturity levels. On the outbound side, RevStream holds a 'Built for NetSuite' certified SuiteApp called the RevStream GL Connector for NetSuite, built on the NetSuite SuiteCloud platform. This connector posts period-end revenue recognition and deferred revenue journal entries into the NetSuite GL and can be scheduled automatically or run on demand. …

Limitations: The inbound data pipeline is documented as flat-file and CSV-based rather than an event-driven or scheduled API pull, meaning the buyer's requirement to pull contract and billing source data from NetSuite in near-real-time without manual exports is not evidenced as supported. …

Requirement evaluated: The system must ingest contract and billing data from NetSuite and decompose each contract into discrete performance obligations, supporting the full complexity the buyer described: multi-year subscriptions, bundled professional services, usage-based overages, and ramped pricing tiers. Ingestion must be automated and traceable so that every performance obligation created maps back to a source contract line, eliminating the manual carve-out work currently done in spreadsheets before each close.

For a B2B SaaS company currently managing revenue in NetSuite-fed spreadsheets, RevStream's core decomposition engine is its Transaction Hub module, which centralizes bookings and arrangement information and provides automated tools to decompose multi-element arrangements into discrete performance obligations, eliminating the manual carve-out process. <cite index="27-1,27-2">The Transaction Hub "allows management of complex multi-element arrangements without relying on complicated spreadsheets and manual processes" and centralizes bookings and arrangement information with automated tools to identify and process each element.</cite> Once data is loaded, the Revenue Arrangement Manager (RAM) …

Limitations: The decomposition engine, SSP allocation, arrangement grouping, and audit trail are well-documented; however, no certified native NetSuite connector is evidenced for RevStream, meaning the NetSuite ingestion layer relies on flat-file or API pipelines that require configuration and ongoing maintenance. …

Requirement evaluated: The system must recognize usage-based overage revenue in the period in which the usage occurs, consuming metered billing data ingested from the buyer's billing system or NetSuite, and must correctly model overages as variable consideration under ASC 606 (applying the constraint test before recognition). The mechanism must be automatic; the buyer should not need to manually import usage quantities or calculate recognition amounts outside the system.

For a B2B SaaS company needing automated period-of-usage overage recognition, RevStream operates as a revenue subledger whose Transaction Hub layer ingests data from upstream billing and contract systems. <cite index="52-3,52-4">The Transaction Hub is documented as a repository of contract, order, and business events that interfaces with source systems including ERP, CRM, contract, billing, and sales platforms to collect, aggregate, and enable transactions for revenue recognition.</cite> <cite index="15-2,15-7">The datasheet confirms RevStream integrates flat files, CSV files, and upload utilities, connecting automatically with cloud or on-premise ERP or billing applications.</cite> <cite in …

Limitations: The critical gap for this buyer is the absence of any documented automated variable consideration constraint test applied to overage amounts before recognition: no public Aptitude source names this mechanism for RevStream, leaving open whether constraint logic must be manually configured or is not present at all. …

Requirement evaluated: The system must recognize usage-based overage revenue in the period in which the usage occurs, consuming metered billing data ingested from the buyer's billing system or NetSuite, and must correctly model overages as variable consideration under ASC 606 (applying the constraint test before recognition). The mechanism must be automatic; the buyer should not need to manually import usage quantities or calculate recognition amounts outside the system.

For a B2B SaaS company needing automated period-of-usage overage recognition, RevStream operates as a revenue subledger whose Transaction Hub layer ingests data from upstream billing and contract systems. <cite index="52-3,52-4">The Transaction Hub is documented as a repository of contract, order, and business events that interfaces with source systems including ERP, CRM, contract, billing, and sales platforms to collect, aggregate, and enable transactions for revenue recognition.</cite> <cite index="15-2,15-7">The datasheet confirms RevStream integrates flat files, CSV files, and upload utilities, connecting automatically with cloud or on-premise ERP or billing applications.</cite> <cite in …

Limitations: The critical gap for this buyer is the absence of any documented automated variable consideration constraint test applied to overage amounts before recognition: no public Aptitude source names this mechanism for RevStream, leaving open whether constraint logic must be manually configured or is not present at all. …

Requirement evaluated: The system must support dual-standard reporting under both ASC 606 and IFRS 15 simultaneously, given that the buyer explicitly operates under both standards. This means the system must be able to hold parallel recognition schedules or adjustments where the two standards diverge (for example, on variable consideration constraints or contract combination rules) and report each basis independently rather than forcing a single-standard close.

For a B2B SaaS company that must simultaneously close under ASC 606 and IFRS 15, RevStream's mechanism rests on a configurable, rules-based engine that holds both standards within a single data foundation rather than forcing a single-standard close. Aptitude's own solution page states the system is 'scalable to address volume fluctuations and can handle complex contracts, frequent modifications, and the need to report under both US and International GAAPs from a single source of trusted data.' The Aptitude Lease Accounting Engine integration page further documents 'multi-basis accounting to support US GAAP, IFRS from a single data foundation,' confirming that parallel recognition schedules a …

Limitations: No publicly available documentation describes how RevStream specifically handles the precise divergence points between ASC 606 and IFRS 15 that are most relevant to this buyer (for example, variable consideration constraint differences or contract combination rules); those configuration choices will need to be verified …

Requirement evaluated: The system must support dual-standard reporting under both ASC 606 and IFRS 15 simultaneously, given that the buyer explicitly operates under both standards. This means the system must be able to hold parallel recognition schedules or adjustments where the two standards diverge (for example, on variable consideration constraints or contract combination rules) and report each basis independently rather than forcing a single-standard close.

For a B2B SaaS company that must simultaneously close under ASC 606 and IFRS 15, RevStream's mechanism rests on a configurable, rules-based engine that holds both standards within a single data foundation rather than forcing a single-standard close. Aptitude's own solution page states the system is 'scalable to address volume fluctuations and can handle complex contracts, frequent modifications, and the need to report under both US and International GAAPs from a single source of trusted data.' The Aptitude Lease Accounting Engine integration page further documents 'multi-basis accounting to support US GAAP, IFRS from a single data foundation,' confirming that parallel recognition schedules a …

Limitations: No publicly available documentation describes how RevStream specifically handles the precise divergence points between ASC 606 and IFRS 15 that are most relevant to this buyer (for example, variable consideration constraint differences or contract combination rules); those configuration choices will need to be verified …

Requirement evaluated: The system must build and continuously re-forecast deferred revenue waterfall schedules for each performance obligation, reflecting the buyer's multi-year subscription terms and ramped pricing, and must push recognized and deferred revenue journal entries directly to the NetSuite GL on close cadence. The schedules must update automatically when contract data changes mid-period, replacing the buyer's manual deferred revenue waterfall spreadsheets that currently drive audit risk.

For a B2B SaaS company replacing manual deferred revenue waterfall spreadsheets, RevStream operates as a dedicated revenue subledger positioned between the buyer's upstream contract and billing systems and the NetSuite GL. The system stores data at the contract line level and generates pre-built forecast waterfall schedules per performance obligation, with roll-forward reporting that continuously reflects the SSP-allocated transaction price rather than invoiced amounts. …

Limitations: Public documentation confirms the NetSuite integration exists as a named, separately documented connector, but the specific posting mechanism (scheduled batch vs. real-time API push) …

Requirement evaluated: The system must build and continuously re-forecast deferred revenue waterfall schedules for each performance obligation, reflecting the buyer's multi-year subscription terms and ramped pricing, and must push recognized and deferred revenue journal entries directly to the NetSuite GL on close cadence. The schedules must update automatically when contract data changes mid-period, replacing the buyer's manual deferred revenue waterfall spreadsheets that currently drive audit risk.

For a B2B SaaS company replacing manual deferred revenue waterfall spreadsheets, RevStream operates as a dedicated revenue subledger positioned between the buyer's upstream contract and billing systems and the NetSuite GL. The system stores data at the contract line level and generates pre-built forecast waterfall schedules per performance obligation, with roll-forward reporting that continuously reflects the SSP-allocated transaction price rather than invoiced amounts. …

Limitations: Public documentation confirms the NetSuite integration exists as a named, separately documented connector, but the specific posting mechanism (scheduled batch vs. real-time API push) …