top of page

ASC 606 and Subscription Businesses: What Your ERP Needs to Get Right

  • Writer: Michael Basone
    Michael Basone
  • Apr 17
  • 2 min read

Overview

Subscription revenue may look simple — but once you introduce tiered pricing, bundled services, and contract changes, complexity increases بسرعة.ASC 606 fundamentally changes how and when revenue is recognized, and your ERP must be configured to handle it accurately.


The Core Principle: Performance Obligations

ASC 606 is built on a five-step model, with performance obligations at its core — the distinct promises to deliver goods or services.

For simple SaaS:

  • One obligation → revenue recognized over time

For complex subscription models:

  • Multiple obligations may include:

    • Software + onboarding services

    • Hardware + recurring service (IoT)

    • Tiered or bundled pricing

    • Usage-based + fixed subscriptions

Each requires:

  • Proper allocation

  • Accurate recognition schedule

👉 Missteps here can lead to material financial errors and restatement risk


Where ERP Configurations Typically Break Down

Deferred Revenue Tracking

Revenue collected before delivery must be deferred. Incorrect setup leads to overstated revenue and compliance risk.

Contract Modifications

Mid-term upgrades, downgrades, or changes require:

  • Reallocation of revenue

  • Correct accounting treatment per ASC 606

Standalone Selling Price (SSP) Allocation

Revenue must be allocated based on relative SSP, not list price. Improper allocation = inaccurate financial reporting.

Usage-Based Revenue

Variable consideration requires:

  • Estimation (with constraints), or

  • Recognition as usage occurs


What Acumatica Does Well — and Where to Be Careful

What Works Well

  • Native deferred revenue scheduling

  • Strong support for straight-line recognition

Where Extra Attention Is Needed

  • Multi-element arrangements → require careful configuration

  • Contract changes → need defined workflows

  • Reporting → often requires custom build or external tools

The Billing Platform Question

For complex subscription businesses, using a billing platform like:

  • Chargebee

  • Zuora

…can significantly improve accuracy.

Best Practice Setup

  • Billing platform handles:

    • Proration

    • Upgrades/downgrades

    • Usage tracking

  • ERP (Acumatica) handles:

    • Financial posting

    • General ledger

👉 The integration layer is critical — poor mapping leads to reconciliation issues over time.


A Practical ASC 606 Checklist

Before moving forward, ensure you can answer yes to all:

  • Have you identified all performance obligations?

  • Do you have defined SSP for each element?

  • Is revenue recognized based on delivery (not billing)?

  • Can you generate a deferred revenue rollforward?

  • Do you handle contract modifications correctly?

  • Are policies documented and consistently applied?

👉 If not, gaps exist that need immediate attention.


We’ve Been Here Before

High Ground Consulting has worked with:

  • SaaS companies

  • IoT subscription businesses

  • Service-based organizations

…to implement and fix ASC 606-compliant systems.

If you're building or optimizing your subscription financial architecture, we’re available for a direct, practical conversation.


About High Ground Consulting

High Ground Consulting specializes in designing financial systems for subscription and IoT businesses, ensuring accurate and audit-ready revenue recognition.

We work with:

  • Acumatica

  • Leading billing platforms like Chargebee

 
 
 

Comments


bottom of page