Key Takeaways
- A software-as-a-service accounting ledger needs separate accounts for subscription revenue, deferred revenue, and cost of revenue, since one revenue line cannot support SaaS reporting.
- The tech stack has distinct layers spanning billing through reporting, and each layer should feed the ledger through a defined, reconcilable connection.
- Subscription revenue is recognized over time under ASC 606, so the ledger carries unearned amounts as a liability until the service is delivered.
- Companies buying software-as-a-service follow different rules, since implementation costs in a cloud arrangement can be capitalized under ASU 2018-15.
- Most SaaS companies should build integrations and reporting on top of a proven ledger instead of building their own accounting software.
A SaaS founder at about $1.5M in ARR gets a simple question from her board: what is MRR by customer cohort?
Her team needs two weeks to answer. The billing system has the data, the bank feed has the cash, and the general ledger lumps subscriptions, implementation fees, and usage into one revenue account. Nothing is wrong with the bookkeeping. The ledger was built for year one, and the company is now in year three.
Building a software-as-a-service accounting ledger and tech stack means structuring the chart of accounts around recurring revenue, deferred revenue, and SaaS cost of revenue, then connecting billing, payments, and expense tools to that ledger so the numbers flow in automatically and reconcile every month.
This blog covers how to structure the ledger, which layers belong in the stack, how to connect them, and when the setup needs to change.
What Should Your SaaS General Ledger Track?
A general ledger is the record from which every financial statement is built. A software-as-a-service accounting ledger has four jobs a standard ledger setup often misses:
Revenue recognition: Recognize subscription revenue as the service is delivered.
Deferred revenue: Track prepaid amounts as a liability until they’re earned.
Cost classification: Separate hosting, support, and product delivery costs from operating expenses like sales and marketing.
Financial metrics: Generate reliable MRR, ARR, retention, and gross margin figures directly from your accounting records.
For the definition and the revenue mechanics behind these jobs, see What Is SaaS Accounting?
1116 Perspective | Build for the Questions You Will Be Asked
A ledger is easy to set up for today’s questions. The harder discipline is structuring it for the questions a board, lender, or acquirer will ask in eighteen months, because retrofitting a chart of accounts means restating history.
How Do You Account for Software-as-a-Service?
The accounting treatment depends on whether your business sells SaaS or pays for it.
If You Sell SaaS
Subscription revenue is recognized as the service is delivered, rather than when payment is received. Under ASC 606, companies follow a five-step process:
Identify the customer contract.
Identify the performance obligations.
Determine the transaction price.
Allocate the price across the performance obligations.
Recognize revenue as each obligation is satisfied.
The FASB’s ASU 2014-09 outlines this model. In practice, an annual subscription paid upfront is initially recorded as deferred revenue, then recognized over the subscription term as the service is delivered.
If You Buy SaaS
For businesses purchasing SaaS, the arrangement is generally treated as a service contract. However, some implementation costs may qualify for capitalization rather than immediate expense.
Under FASB’s ASU 2018-15, customers apply the internal-use software guidance in Subtopic 350-40 to determine which implementation costs qualify for capitalization. Eligible costs are then expensed over the hosting arrangement’s term, in the same line item as the hosting fees.
This blog focuses on the first case: software-as-a-service accounting for SaaS companies that sell subscriptions and need a ledger and tech stack built around their revenue model.
How To Structure the Chart of Accounts?
The chart of accounts is where software-as-a-service accounting either works or fails. A SaaS-ready structure separates the things a general setup combines.
| Account Group | What Goes There | Significance |
|---|---|---|
| Subscription Revenue | Recurring plan fees, split by product or plan where useful | Source for MRR and ARR |
| Usage & Overage Revenue | Variable, consumption-based charges | Shows revenue that is not contractually recurring |
| Implementation & Services Revenue | Onboarding, training, and professional services | Keeps one-time work out of recurring metrics |
| Deferred Revenue (Current & Long-Term) | Unearned amounts from prepaid contracts | Liability that releases to revenue as service is delivered |
| Unbilled Revenue | Revenue earned before invoicing | Prevents understating a period |
| Cost of Revenue | Hosting, customer support, and third-party software used to deliver the product | Drives gross margin |
| Sales & Marketing | Acquisition spend, including salaries and tools | Drives CAC and payback |
| Research & Development | Product and engineering costs | Keeps product spend separate from delivery cost |
| General & Administrative | Finance, legal, and overhead | Completes the operating expense view |
Two design choices pay off later:
Use classes or dimensions, not more accounts: Product line, customer segment, and entity can be tagged on transactions, so the chart of accounts stays short while reports stay detailed.
Decide the cost of revenue boundary early: A customer success hire might sit in cost of revenue or in sales and marketing depending on the role. Document the rule and apply it every period, since gross margin and CAC both depend on it.
Capitalized costs, such as certain contract acquisition costs and software development costs, need their own accounts and a documented policy. The treatment depends on the applicable standard and the facts, so confirm it with your accountant before setting it up.
What Belongs in a SaaS Tech Stack?
A SaaS accounting stack is a set of layers, each with a job the ledger depends on. Think in functions before products.
| Layer | What It Does | What the Ledger Needs From It |
|---|---|---|
| Billing & subscriptions | Creates invoices, plans, upgrades, and renewals | Invoice and plan-change data tied to customers |
| Payments | Collects cash and handles refunds and failed charges | Payout detail that reconciles to the bank |
| General Ledger | The system of record for all transactions | Period locks, an audit trail, and GAAP reporting |
| Revenue Schedules | Spreads contract value over the service period | Monthly entries that tie to deferred revenue |
| Expense & AP | Handles bills, approvals, and spend | Coded, approved transactions |
| Payroll | Pays employees and contractors | Summarized journal entries by department |
| Reporting and FP&A | Produces dashboards, forecasts, and board packs | Reliable, consistently defined ledger data |
| Document Storage | Holds contracts and support | Retrievable records for audits and diligence |
Billing and payments platforms such as Stripe and Chargebee are common examples of the first two layers. The point is the function, not the brand: each layer should hold one kind of truth, and the ledger should sit at the center.
The general ledger is the layer everything else feeds, so it is the one decision worth examining closely.
Which Accounting Software Do U.S. SaaS Companies Use?
No neutral, authoritative census exists, so treat any “most used” claim with caution. The choice tracks company size and complexity:
- Early stage: Entry-level cloud ledgers such as QuickBooks Online or Xero, often paired with a separate tool for deferred revenue schedules.
- Growing: Companies adding multiple entities or usage-based billing often move to mid-market platforms such as Sage Intacct.
- Later stage: Larger organizations often use ERP-class systems such as NetSuite.
You may have outgrown your ledger if the close takes more than a few days, deferred revenue lives in a spreadsheet no one else can audit, or board reports need manual reconciliation first.
Should You Build Your Own Accounting Software?
For almost every SaaS company, no. Build the integrations and reporting layer, but not the ledger itself. A ledger must keep double-entry records balanced, lock closed periods, preserve an audit trail, and support reconciliation. Auditors and investors look for each of those controls, and each is hard to get right.
A custom ledger also adds diligence risk, since a buyer has to trust a system no one outside the company has tested. Choose a proven ledger and spend engineering time on integrations and reporting that reflect your own metrics.
What Should the Month-End Close Look Like?
A software-as-a-service accounting close should follow the same steps each month, in the same order:
Confirm billing, payment, and payroll data have synced.
Reconcile bank and payout accounts.
Run the revenue schedule and post the deferred revenue release.
Review accruals, unbilled revenue, and prepaid expenses.
Review cost of revenue classification against the documented rule.
Lock the period and produce statements and metrics.
A repeatable process is what makes the numbers comparable month to month. Our Month-End Close Services are built around a checklist like this, and reliable Financial Reporting Services turn closed books into statements leadership can use.
1116 Perspective | The Close Is the Control
A strong stack still produces weak numbers if no one reviews them. The close turns a reconciled ledger into trusted statements, and teams most often skip it when they’re busy.
Common Mistakes in SaaS Accounting Setups
Small accounting setup mistakes can lead to inaccurate financial reports, unreliable SaaS metrics, and extra work during audits or fundraising. Here are the common issues to watch for and how they affect your books.
Combining all revenue types: Mixing subscriptions, usage-based revenue, and services makes MRR harder to calculate accurately.
Misclassifying hosting costs: Recording delivery costs as operating expenses can overstate gross margin.
Tracking deferred revenue separately: Relying on personal spreadsheets makes the schedule harder to audit and hand over.
Skipping monthly reconciliations: Differences between billing systems, payment records, and the general ledger can go unnoticed.
Delaying chart of accounts changes: Restructuring the ledger after a funding round or audit request can create extra work and pressure to correct prior-period reporting.
These mistakes are easier to prevent than repair, and most trace back to decisions you make when you first set up the ledger and stack.
When Does the Setup Need to Change?
A software-as-a-service accounting setup that works at one stage often strains at the next. Revisit the ledger and stack when:
Pricing becomes more complex, such as usage-based charges, multiple products, or custom contracts.
The company adds entities or currencies, requiring entity-level reporting and consolidation.
An audit, raise, or sale is on the horizon, where documentation and traceability matter.
As the finance team grows, manual workarounds known to only one person become a risk.
Reporting needs outgrow the ledger, and metrics require monthly manual work.
For how a remote team supports this day-to-day, see Remote Accounting Services for Growing SaaS Businesses.
Build a Ledger and Tech Stack That Scales With 1116 Partners
A well-structured ledger and a connected stack turn software-as-a-service accounting from a monthly scramble into a repeatable process. The structure decisions you make now determine how quickly you can answer the next question from a board, lender, or investor.
1116 Partners works as an extension of your leadership team, with Controllers and Senior Accountants who design and run the accounting foundation for growing SaaS companies. That includes SaaS Accounting Services, SaaS Bookkeeping Services, and Fractional Controller Services, built for companies that need their reporting to keep pace with their growth.
FAQs
-
Early on, yes, if it has a documented method and a reviewer. As contracts, plan changes, and customers multiply, spreadsheets become hard to audit and easy to break, which usually signals it’s time to move schedules into a system tied to the ledger.
-
Daily or weekly syncs keep reconciliation manageable, and the data should be complete before every month-end close. The right cadence depends on volume, but the key is a consistent, reviewed process.
-
A billing system manages customers, plans, and invoices. The general ledger is the official accounting record that produces financial statements. Billing data feeds the ledger, but billing reports alone don’t replace it.
-
Costs of delivering the product, such as hosting, customer support, and third-party software used in the service, are typically treated as cost of revenue. Whatever the rule, document it and apply it consistently, since it determines gross margin.
-
When it operates through more than one legal entity, sells in multiple currencies, or has a parent-subsidiary structure that requires consolidation. Planning for it before the first additional entity is added avoids restructuring the chart of accounts later.
