Questions? Give us a call at (800) 882-6705
Revenue recognition software turns a signed contract into a recognition schedule that posts itself each period, allocates a multi-element deal across its performance obligations, and keeps deferred and recognised balances tied to the ledger rather than to a spreadsheet.
BCS ProSoft configures Sage Intacct revenue recognition around your contract structures, recognition policies, and reporting bases. The five ASC 606 steps below map to specific setup in the system, which is where compliance actually gets decided.
Starts with a discovery call. We review your contract types, obligations, billing model, and reporting bases, then give you a realistic scope and pricing range.
THE SCHEDULE NOBODY WANTS TO OWN
The revenue schedule lives in one workbook that one person maintains. Every contract modification means reworking it, every auditor question means proving it, and nobody wants to be the one who inherits it.
It is rarely lost at the policy level. It is lost in the gap where the policy gets implemented by hand, which is exactly the gap a configuration closes.
WHERE COMPLIANCE IS DECIDED
ASC 606 is a five-step model. Compliance is decided by how each step is configured in the system that posts the entries, so this is the mapping we build against.
Background on the standard itself lives in our ASC 606 explainer and common revenue recognition errors. This page is about the configuration that implements it.
STILL RUNNING REVENUE IN A WORKBOOK?
Almost every team we work with arrives with a revenue workbook that encodes years of policy decisions: how a bundled deal splits, what happens on an upgrade mid-term, which contracts recognise on milestones. That logic is the asset. The fragility is that it lives in formulas one person maintains and an auditor has to be walked through.
A revenue workbook rebuilt each period. Modifications reworked by hand. Deferred balances proven on request.
Recognition schedules that post from the contract, a deferred rollforward tied to the ledger, and an audit trail behind every entry.
BCS ProSoft translates your existing recognition policy into contract templates and obligation treatments, then migrates in-flight contracts with their remaining schedules so nothing restarts at go-live.
WHAT THE CONFIGURATION DOES
Each one removes a step the finance team currently performs by hand every period.
MULTI-ELEMENT ALLOCATION
A deal that bundles subscription, implementation, and training is three or four performance obligations with different recognition patterns. Each carries its own method and its share of the transaction price based on standalone selling price.
The allocation is calculated from configuration rather than typed into a schedule, so it applies the same way on the hundredth contract as the first.
DEFERRED VS RECOGNISED
Recognised revenue for the period and the remaining deferred balance are both ledger positions, so the rollforward reconciles by construction instead of being proven each close.
Finance and leadership can see what has been earned and what is still to come without waiting for someone to update the workbook.
DUAL REPORTING
A transaction posts to multiple books at once, so a US GAAP or ASC 606 view sits alongside IFRS 15, a management basis, and a tax basis without a second data entry path.
For groups reporting under more than one framework, this removes the reconciliation between bases that otherwise happens every period.
AUTOMATED SCHEDULES
Once obligations and templates are set, the period entry is generated and posted on schedule. Modifications re-derive the remaining periods rather than requiring a manual rebuild.
Professional services firms mixing fixed-fee, milestone, and T&M work get each pattern handled natively. More: revenue recognition for professional services.
WHAT CHANGES AT CLOSE
When the schedule posts from the contract, the revenue portion of close becomes an exception review: modifications, unusual obligations, contracts that need judgement. The routine majority posts without intervention.
The audit conversation changes too. Instead of walking an auditor through formulas, you show the configuration and the transaction trail behind each entry.
BEFORE YOU EVALUATE
The questions that decide whether this is worth your time.
Yes. A transaction posts to multiple books at once, so an ASC 606 or IFRS 15 view and a management or tax basis are produced from the same source rather than reconciled to each other after the fact.
Each performance obligation carries its own recognition method and its share of the transaction price based on standalone selling price, so a contract bundling subscription, implementation, and training recognises on three different patterns.
Modifications, upgrades, and cancellations re-derive the remaining schedule from the contract rather than requiring the schedule to be rebuilt by hand, and the deferred balance adjusts with an audit trail behind it.
Not necessarily. Billing and recognition are separate schedules — you can invoice annually and recognise monthly. Where a billing or CRM system already owns the contract, it can feed the recognition schedule instead of being replaced.
Subscription and SaaS businesses, professional services firms with milestone and T&M work, and multi-entity groups that need the same policy applied consistently across entities. See Sage Intacct for professional services.
The recognition journal and the deferred rollforward stop being prepared manually. What remains is reviewing exceptions such as modifications and unusual obligations, rather than rebuilding the schedule every period.
HOW THE PROCESS WORKS
A practical path, with pricing that reflects the actual scope.
We review your contract types, performance obligations, billing model, recognition policy, and the bases you report on. That produces a realistic scope and pricing range, and an honest answer if the fit is not there.
BCS ProSoft builds the contract templates, obligation treatments, standalone selling prices, and book structure, then migrates in-flight contracts with their remaining schedules so recognition continues uninterrupted.
Your team runs a period in parallel against the existing workbook so the numbers are proven to agree before cutover, then has support through the first live close and the first audit on the new configuration.
Start with a discovery call. We will review your contract structures, obligations, and reporting bases, then walk you through what the configuration would involve. You can also explore Sage Intacct first.
BCS ProSoft is a certified Sage Intacct implementation partner.
