How Softrax works

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 high-growth SaaS company replacing hand-built spreadsheet trails, Softrax RMS delivers audit traceability through a layered set of mechanisms built into its revenue subledger. At the contract level, <cite index="1-3">the system maintains in-depth information about contract details and related records, as well as a full audit trail and history of changes and amendments to a contract's key elements.</cite> The per-contract analytics engine goes further: <cite index="3-8,3-9">Softrax RMS provides analytics on a contract that include state and history as well as all events, bills, modifications, reallocations, fulfillment events, and more that have occurred since inception.</cite> This dir …

Limitations: Public documentation does not describe a dedicated, named read-only auditor login or a purpose-built external auditor portal with distinct SOC-1 access controls; the evidence shows reports can be shared with stakeholders and exported in multiple formats, but the specific access-control mechanism for external auditors ( …

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 moving off spreadsheet-based SSP allocation, Softrax RMS organizes the buyer's contracts around performance obligations (called elements within revenue arrangements) and governs SSP values through per-item price books. <cite index="19-2,19-3">Administrators configure how to calculate the SSP for each revenue item using price books, and fully automated policies then determine how allocations are performed for different products, customers, and contracts.</cite> <cite index="19-4,19-5">Allocation methods include relative, residual, and multi-step approaches, and specific performance obligations can be excluded from the allocation pool.</cite> <cite index="14-5">The syste …

Limitations: The allocation method framework documents relative, residual, and multi-step options but does not explicitly expose adjusted market assessment or expected cost plus margin as labeled system-level method selectors, which can create an audit documentation gap for professional services bundles priced on a cost-plus basis. …

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 B2B SaaS company handling mid-term upgrades, downgrades, and bundled professional services modifications, Softrax RMS addresses this requirement through its Policy Engine and automated contract combination and modification policies. When a contract change event is ingested, the system executes pre-configured modification policies that route the accounting treatment: <cite index="29-3,29-4">the RMS automated contract combination and modification policies enable prospective and retrospective reallocations of revenue as well as cumulative catch-ups (or downs) …

Limitations: The buyer's requirement for a system-generated modification memo containing the accounting rationale and ASC 606/IFRS 15 paragraph citations, attached to the affected contract record and ready for auditor review, is not documented in any Softrax source; the audit trail covers policy changes and manual interventions but …

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 high-growth SaaS company replacing hand-built spreadsheet trails, Softrax RMS delivers audit traceability through a layered set of mechanisms built into its revenue subledger. At the contract level, <cite index="1-3">the system maintains in-depth information about contract details and related records, as well as a full audit trail and history of changes and amendments to a contract's key elements.</cite> The per-contract analytics engine goes further: <cite index="3-8,3-9">Softrax RMS provides analytics on a contract that include state and history as well as all events, bills, modifications, reallocations, fulfillment events, and more that have occurred since inception.</cite> This dir …

Limitations: Public documentation does not describe a dedicated, named read-only auditor login or a purpose-built external auditor portal with distinct SOC-1 access controls; the evidence shows reports can be shared with stakeholders and exported in multiple formats, but the specific access-control mechanism for external auditors ( …

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 moving off spreadsheets and a NetSuite GL, Softrax RMS positions itself as a revenue subledger with bidirectional ERP integration: it ingests contract and billing data, runs ASC 606 / IFRS 15 recognition, generates journal entries, and targets 'GL accounting systems' including NetSuite as an output destination. The integration and workflow module is described as 'API-first' and supports both source (ERP, CRM, billing) and target (GL accounting systems) connections. …

Limitations: The documented primary inbound integration path uses scheduled file extraction to an SFTP server rather than near-real-time API sync from NetSuite, which leaves a latency and control gap for the buyer's close process. …

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 doing manual spreadsheet carve-outs before each close, Softrax RMS replaces that process end-to-end. On ingestion, <cite index="19-3,19-5,19-6">the RMS offers a Workflow Engine that acts as a pre-processor: files are extracted from upstream systems (including your NetSuite ERP) on a scheduled basis, sent to the Softrax SFTP server, and the engine handles data validation, error notification, and API calls into RMS automatically.</cite> Direct API calls into RMS are also available as an alternative. …

Limitations: Softrax does not document a named, certified NetSuite point-and-click connector; the integration runs via a configurable Workflow Engine (scheduled SFTP batch extraction plus API calls) …

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 moving off spreadsheets and a NetSuite GL, Softrax RMS positions itself as a revenue subledger with bidirectional ERP integration: it ingests contract and billing data, runs ASC 606 / IFRS 15 recognition, generates journal entries, and targets 'GL accounting systems' including NetSuite as an output destination. The integration and workflow module is described as 'API-first' and supports both source (ERP, CRM, billing) and target (GL accounting systems) connections. …

Limitations: The documented primary inbound integration path uses scheduled file extraction to an SFTP server rather than near-real-time API sync from NetSuite, which leaves a latency and control gap for the buyer's close process. …

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 doing manual spreadsheet carve-outs before each close, Softrax RMS replaces that process end-to-end. On ingestion, <cite index="19-3,19-5,19-6">the RMS offers a Workflow Engine that acts as a pre-processor: files are extracted from upstream systems (including your NetSuite ERP) on a scheduled basis, sent to the Softrax SFTP server, and the engine handles data validation, error notification, and API calls into RMS automatically.</cite> Direct API calls into RMS are also available as an alternative. …

Limitations: Softrax does not document a named, certified NetSuite point-and-click connector; the integration runs via a configurable Workflow Engine (scheduled SFTP batch extraction plus API calls) …

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 SaaS company like yours recognizing usage-based overages under ASC 606, Softrax RMS handles the full chain from data ingestion to period recognition without manual quantity import or offline calculation. Usage records flow into RMS automatically via the Softrax Workflow Engine, which ingests transactional data — including usage records — from your NetSuite GL, billing system, or any upstream CRM/ERP, eliminating the need for manual CSV imports or hand-calculation. …

Limitations: The initial variable consideration estimate and constraint threshold at contract inception require a human judgment call; Softrax documents the setup and automates all subsequent re-evaluations, but your team must configure the opening constraint, which is an ASC 606 requirement rather than a product gap. …

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 SaaS company like yours recognizing usage-based overages under ASC 606, Softrax RMS handles the full chain from data ingestion to period recognition without manual quantity import or offline calculation. Usage records flow into RMS automatically via the Softrax Workflow Engine, which ingests transactional data — including usage records — from your NetSuite GL, billing system, or any upstream CRM/ERP, eliminating the need for manual CSV imports or hand-calculation. …

Limitations: The initial variable consideration estimate and constraint threshold at contract inception require a human judgment call; Softrax documents the setup and automates all subsequent re-evaluations, but your team must configure the opening constraint, which is an ASC 606 requirement rather than a product gap. …

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 close under both ASC 606 and IFRS 15 simultaneously, Softrax RMS uses a multi-policy 'books' architecture built into its proprietary Policy Engine. The product page documents that RMS can 'automatically enforce two or more revenue policies, including ASC-605, IAS-08, ASC-606/IFRS 15, non-GAAP, management, reporting, and what-if books' against the same contract data set in parallel (rms.softrax.com/products/revenue-recognition-software/). This means a single contract record can carry recognition schedules under multiple policy books simultaneously, satisfying the structural need for parallel closes without re-entering contract data. …

Limitations: The parallel-book engine is documented, but Softrax's public materials do not confirm that the two policy books can apply independent variable consideration constraint thresholds or contract combination rules where ASC 606 and IFRS 15 diverge -- which is the buyer's stated requirement. …

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 close under both ASC 606 and IFRS 15 simultaneously, Softrax RMS uses a multi-policy 'books' architecture built into its proprietary Policy Engine. The product page documents that RMS can 'automatically enforce two or more revenue policies, including ASC-605, IAS-08, ASC-606/IFRS 15, non-GAAP, management, reporting, and what-if books' against the same contract data set in parallel (rms.softrax.com/products/revenue-recognition-software/). This means a single contract record can carry recognition schedules under multiple policy books simultaneously, satisfying the structural need for parallel closes without re-entering contract data. …

Limitations: The parallel-book engine is documented, but Softrax's public materials do not confirm that the two policy books can apply independent variable consideration constraint thresholds or contract combination rules where ASC 606 and IFRS 15 diverge -- which is the buyer's stated requirement. …

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, Softrax RMS operates as a revenue subledger sitting between the buyer's CRM/CPQ and the NetSuite GL. The system builds per-performance-obligation recognition schedules: <cite index="31-1,31-2">contract changes are managed through RMS automated contract combination and modification policies, enabling prospective and retrospective reallocations of revenue as well as cumulative catch-ups for any non-distinct performance obligations.</cite> When contract data changes mid-period, <cite index="31-9">because Softrax RMS is linked to and imports transactional data, revenue forecasts can always be adjusted and recalculat …

Limitations: The product documentation uses the phrase 'you can then import the RMS journal entries into your revenue recognition journal' (Softrax revenue recognition product page), which leaves open whether the NetSuite GL push on close cadence is fully automated and zero-touch or requires a user-initiated trigger via the Workflo …

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, Softrax RMS operates as a revenue subledger sitting between the buyer's CRM/CPQ and the NetSuite GL. The system builds per-performance-obligation recognition schedules: <cite index="31-1,31-2">contract changes are managed through RMS automated contract combination and modification policies, enabling prospective and retrospective reallocations of revenue as well as cumulative catch-ups for any non-distinct performance obligations.</cite> When contract data changes mid-period, <cite index="31-9">because Softrax RMS is linked to and imports transactional data, revenue forecasts can always be adjusted and recalculat …

Limitations: The product documentation uses the phrase 'you can then import the RMS journal entries into your revenue recognition journal' (Softrax revenue recognition product page), which leaves open whether the NetSuite GL push on close cadence is fully automated and zero-touch or requires a user-initiated trigger via the Workflo …