The Best ASC 606 Software Depends on How You Earn Revenue
What is the best ASC 606 software? It depends on whether your revenue is subscription, contract, or percentage-of-completion — and most buyers pick on the wrong axis.
“What is the best ASC 606 software?” is one of those questions where the honest answer starts by rejecting the question. Not to be difficult — because the category does not exist the way buyers assume it does.
ASC 606 software is three different product categories wearing one label. Which one you need depends entirely on how your business earns revenue, and most evaluations go wrong by comparing across categories on a feature grid.
Key takeaways
- Pick on how you earn revenue, not on a feature comparison. Subscription, contract-based, and percentage-of-completion businesses need structurally different systems.
- Construction and engineering firms almost always need a construction ERP, because over-time recognition depends on job cost data a finance platform does not hold.
- Sage Intacct is the depth leader for subscription and multi-element arrangements among mid-market ERPs.
- Contract modifications are where implementations fail, not initial recognition. Evaluate that, not the happy path.
- Some companies genuinely do not need dedicated software. Simple revenue plus a documented policy passes an audit.
The five-step model, and where software actually helps
ASC 606 recognises revenue through five steps: identify the contract, identify the performance obligations, determine the transaction price, allocate that price to the obligations, and recognise revenue as each obligation is satisfied.
Software is largely irrelevant to steps one through three. Those are judgement and policy. Software earns its keep at steps four and five — allocation across obligations, and the mechanics of recognising revenue over time — and at the disclosure schedules that come afterwards.
That is why feature grids mislead. Every vendor ticks “ASC 606 compliant.” What differs is whether the system models your particular pattern of obligations natively, or expects you to contort it into something else.
Category 1: subscription and multi-element arrangements
If you sell software, services, contracts with bundled hardware, or anything with several deliverables priced as one number, your difficulty is allocation. You have one contract price and several performance obligations, each satisfied on a different schedule, and the standard requires allocating the price across them by standalone selling price.
Doing that manually is where finance teams lose their quarter.
Sage Intacct is the depth leader here among mid-market platforms. It was built as a finance platform first, and its revenue recognition automation for subscription and multi-element arrangements handles schedules, deferrals and reallocations without a spreadsheet layer. NetSuite is the other common answer at this size, and the larger enterprise suites all have capable engines.
Acumatica handles revenue recognition competently, but it is one module inside a broad operational ERP rather than the centre of the product. If finance is your primary ERP user base, that difference matters. If operations staff also live in the ERP, it usually does not outweigh Acumatica’s broader scope — a trade-off we work through in Acumatica vs Sage Intacct for mid-market.
Category 2: construction and percentage-of-completion
This is the category most commonly mis-shopped, and it is worth being blunt about why.
Most construction contracts are a single performance obligation satisfied over time. There is no allocation problem to solve. The entire difficulty sits in the measure of progress — usually cost-to-cost percentage-of-completion, where recognised revenue is a function of costs incurred against estimated total cost.
That calculation needs three things per job, at cost-code level:
- actual costs to date
- committed costs not yet incurred
- a current, defensible estimate of cost to complete
None of that lives in a finance platform. It lives in the job cost ledger.
Which means the requirement is not “revenue recognition software.” It is an ERP where job costing and revenue recognition are the same system: Viewpoint Vista, Viewpoint Spectrum, Sage 300 CRE, or Acumatica Construction Edition.
Bolting a revenue recognition tool onto QuickBooks does not solve this. It gives you a system that can calculate recognition beautifully from data you do not have.
The construction-specific traps
- Unapproved change orders and claims are variable consideration. They have to be estimated and then constrained — recognised only to the extent a significant reversal is not probable. Most systems will happily let you recognise the full amount.
- Estimated cost to complete is an input, not an output. If your ETC is stale, your revenue is wrong, and no software fixes that. The discipline is operational — which is why the ERP-versus-spreadsheet question is really a question about whether project managers update estimates in the system.
- Retainage affects billing and cash, not recognition. Systems that conflate the two produce revenue that tracks invoices rather than performance.
- Loss jobs must be recognised in full immediately. Worth verifying the system does this rather than amortising the loss.
Category 3: you may not need any of this
Some companies recognise revenue at a point in time, on straightforward contracts, with no modifications and no variable consideration. A well-configured general ledger and a documented revenue recognition policy will pass an audit.
If that is you, the best ASC 606 software is the accounting system you already have, plus a written policy your auditor has seen.
The honest trigger for moving is not revenue size. It is when a spreadsheet becomes the system of record for a number in your audited financials — when the recognition schedule lives in Excel, has no audit trail, and one person understands it. That is a real risk, and it is the point at which dedicated capability pays for itself.
What to actually evaluate
Five questions, in priority order. A demo will show you the happy path for all five; ask to see the hard case instead.
| # | Question | Why it matters |
|---|---|---|
| 1 | Does it model performance obligations natively? | Or does it expect you to represent them as invoice lines, which breaks at the first bundle |
| 2 | What happens on a contract modification? | This is where implementations fail. Ask to see one processed, not described |
| 3 | Can variable consideration be estimated and constrained in-system? | Incentives, penalties, claims, unapproved change orders |
| 4 | Where does the measure of progress come from? | Real operational data, or a number somebody types in each month |
| 5 | Does it produce disclosure schedules without an Excel export? | The quarter-end test |
Ask every vendor to demonstrate question two. Initial recognition is easy and every product does it well. Modifications — a change order that alters scope and price mid-contract — are what separate systems that work from systems that generate a quarterly manual adjustment forever.
The short version
| If your revenue is… | Look at | Because |
|---|---|---|
| Subscription, bundled, multi-element | Sage Intacct, NetSuite | Allocation across obligations is the hard part |
| Percentage-of-completion, construction | Viewpoint Vista, Spectrum, Sage 300 CRE, Acumatica Construction | Recognition depends on job cost data |
| Broad operations plus decent finance | Acumatica | Adequate recognition, much wider scope |
| Simple and point-in-time | What you already have | Plus a written policy |
| Genuinely unusual, ERP otherwise fine | A standalone tool | Only if recognition is the only gap |
Where to start
The wrong first step is a vendor shortlist. The right first step is writing down, in a paragraph, how your contracts actually work: what you promise, when the customer gets it, what can change mid-contract, and what is uncertain about the price. That paragraph determines the category, and the category determines the shortlist.
We scope and run ERP selections and migrations for construction and mid-market firms, including the revenue recognition workstream — and we publish platform comparisons rather than steering every conversation toward one product. If the answer for you is that your current system is fine and the real problem is configuration, that is an answer we give regularly.
Talk through your revenue model with us →
Related reading: Acumatica vs Sage Intacct · Viewpoint Spectrum review · Acumatica vs Sage 300 CRE
