Operations
Revenue recognition (ASC 606 / IFRS 15) inside Sage Intacct for SA SaaS
If you sell software on a subscription, you have a revenue recognition problem long before you have an accounting team big enough to handle it manually. This is how Sage Intacct's Contract & Revenue Management module handles ASC 606 / IFRS 15 for SA SaaS companies.
Bo Gartner Team
Sage Intacct Implementation Specialists
For South African SaaS companies — whether selling locally, internationally, or both — revenue recognition under IFRS 15 (or ASC 606 if reporting to US investors) is one of the most common reasons to move off Xero or QuickBooks. Neither system handles subscription revenue at scale; both force the finance team into Excel for any revenue model more complex than 'invoice the customer monthly'.
Sage Intacct's Contract & Revenue Management module is built for this. This is what it does and how it lands for an SA SaaS company.
The five-step model — same under ASC 606 and IFRS 15
Both standards follow the same logical flow:
- Identify the contract.
- Identify the performance obligations in the contract.
- Determine the transaction price.
- Allocate the transaction price to the performance obligations.
- Recognise revenue as performance obligations are satisfied.
The work is in the modelling. Once the contract is configured correctly, the recognition is automatic.
Performance obligations — the unit of recognition
A typical SaaS contract has multiple performance obligations: software access (recognised over time, ratably across the term), implementation services (recognised on completion or over time as service is delivered), training (point-in-time), support and maintenance (over time). Sage Intacct models each as a distinct performance obligation with its own recognition rule.
Transaction price and allocation
Where a contract is sold at a bundled price, the transaction price has to be allocated across the performance obligations based on the standalone selling prices (SSP) of each component. Sage Intacct maintains the SSP catalog and applies the allocation. If the customer received a discount, the discount is applied across the obligations proportionally.
Ramps, renewals, and changes
SaaS contracts ramp — month 1–3 at a discounted price, month 4–12 at the full rate. Renewals add periods. Customers expand (more users, more modules) and contract (downgrades). Each change is a contract modification under ASC 606 / IFRS 15. Sage Intacct handles each:
- Ramps: configured as billing schedules; revenue recognises ratably regardless of the billing cadence.
- Renewals: handled as a new performance obligation period.
- Expansions and downgrades: contract modifications — Sage Intacct re-allocates the remaining transaction price as required by the standards.
The deferred revenue waterfall
At any reporting date, Sage Intacct produces a deferred revenue waterfall: how much deferred revenue is sitting on the balance sheet, when it will recognise, and which customer contracts it belongs to. The waterfall ties to the balance sheet, which ties to the underlying contracts. Auditors love this; it is the disclosure they would otherwise spend hours deriving.
The integration with Salesforce / HubSpot
For SaaS companies running Salesforce or HubSpot as the CRM, the integration to Sage Intacct closes the quote-to-cash loop. The opportunity in CRM becomes an invoice in Sage Intacct, which becomes a contract with its performance obligations, which become recognised revenue over the term. Bo Gartner builds this integration as part of SaaS engagements.
For SA SaaS companies — the IFRS 15 specifics
IFRS 15 in South Africa is identical in substance to ASC 606. SARS does not have a different revenue recognition standard; IFRS is the accepted framework for audit and statutory purposes. Where the work gets interesting is in the contract terms common to SA SaaS: ZAR-denominated for local customers, USD or GBP for international; multi-year terms with embedded ramps; bundled implementation + subscription deals. Sage Intacct handles all of this in the same module.
When you don't need this
If your contracts are simple — 'pay us R X per month for as long as you use the product, cancel any time' — you may not need full ASC 606 / IFRS 15 modelling. A monthly billing model with no upfront payments and no multi-year commitments can be handled with simpler recurring revenue tools. The decision to move to Contract & Revenue Management is usually made when the sales motion starts producing multi-year contracts, upfront payments, ramps, or bundled deals.
If that is where you are, book a consult. We'll model your typical contract and show you the recognition schedule it produces.
Frequently asked
Related questions on this topic
South Africa follows IFRS 15 for revenue recognition; IFRS is the standard adopted by the JSE and recognised by SARS for audit and statutory purposes. ASC 606 is the equivalent US GAAP standard, substantively aligned with IFRS 15. If you report to US investors as well as your South African auditor, Sage Intacct handles both within the same configuration.
Yes. Sage Intacct's Contract & Revenue Management module models multi-year contracts with billing schedules that ramp (month 1–3 discounted, month 4–12 full rate, for example). Revenue recognises ratably across the term regardless of when the customer is billed, and any deferred revenue is tracked on the balance sheet.
Bo Gartner builds integrations from Salesforce or HubSpot into Sage Intacct that pass closed-won opportunities through to contracts and invoices, with the contract terms, billing schedule, and performance obligations carried through. Sage Intacct then handles the recognition; reporting feeds back to the CRM for visibility. The full quote-to-cash loop is closed.
If every contract is month-to-month, paid in arrears, with no upfront payments or commitments, you may not need full contract management — a simpler recurring revenue setup suffices. The decision typically tips when contracts include multi-year terms, upfront payments, ramps, or bundled implementation + subscription deals.
Yes. At any reporting date, Sage Intacct produces a deferred revenue waterfall showing how much deferred revenue is on the balance sheet, when each portion will recognise, and which customer contracts it belongs to. The waterfall ties back to the underlying contracts and to the balance sheet — the disclosure your auditor expects, without manual derivation.
Tagged
About the author
Bo Gartner Team
Sage Intacct Implementation Specialists
Bo Gartner is South Africa's specialist Sage Intacct Premier Partner — cloud finance implementation, multi-entity consolidation, integrations, and managed support for mid-market organisations across the SADC region.