Software Company Chart of Accounts: A Reconciled Design

A software company chart of accounts should explain how contracts, subscriptions, usage, services, development, payroll, commissions, payments, tax, funding, and cash affect the financial statements. It should provide control without creating a general-ledger account for every product, customer, or metric.

This is an educational design framework, not a prescribed sample chart of accounts for every software development company. U.S. GAAP and federal tax treatment can differ, especially for revenue, internal-use or marketed software costs, and research expenditures. Current IRS guidance includes changes under section 174A for domestic research expenditures beginning after 2024. Obtain qualified accounting and tax advice.

Use accounts, dimensions, and subledgers for different jobs

Use general-ledger accounts for financial-statement categories and control balances. Use dimensions for department, product, location, project, channel, or entity. Use subledgers for customers, contracts, invoices, revenue schedules, vendors, fixed assets, payroll, stock compensation, and payment settlements.

This separation keeps the ledger readable while preserving detail. A customer-specific deferred-revenue schedule belongs in a revenue subledger, not 500 separate liability accounts.

Start with balance-sheet controls

Section	Possible accounts	Primary support
Cash	Operating bank, payroll bank, savings, restricted cash	Bank reconciliations
Payment assets	Stripe or other processor clearing, funds in transit	Settlement reports
Receivables	Trade A/R, unbilled receivable, allowance	Aging and contract schedules
Prepaids	Insurance, hosting commitments, software, deposits	Amortization schedules
Fixed and intangible assets	Equipment, leasehold improvements, capitalized software when applicable, accumulated amortization	Asset and project schedules
Liabilities	A/P, cards, accrued expenses, payroll, tax, deferred revenue, debt	Subledgers and statements
Equity	Capital, additional paid-in capital, retained earnings, distributions or draws	Legal and equity records

Separate receivables, cash, and revenue

An invoice can create receivables before cash. Cash can arrive before service and create deferred revenue. Service can occur before billing and create unbilled receivables under an approved policy. These balances require separate accounts and schedules.

Use customer and contract IDs to connect billing and revenue. Reconcile beginning A/R plus billings and other debits, less payments, credits, write-offs, and other reductions to ending A/R. Reconcile the deferred-revenue rollforward separately.

Design revenue accounts around decision needs

Possible revenue groupings include recurring subscription, usage, implementation, professional services, support, hardware, marketplace, and other material streams. Use product or channel dimensions when they provide flexible reporting without multiplying accounts.

Keep discounts, credits, refunds, and other contra-revenue categories visible where policy and reporting require. Do not post collected sales tax to revenue. Do not use MRR or bookings as ledger revenue.

Create deferred and unbilled revenue controls

Deferred revenue should tie to customer-level schedules by contract, performance obligation, service period, invoice, currency, and recognized amount. Unbilled receivables should tie to delivered service not yet invoiced and reverse or settle without duplication when billing occurs.

Stripe and Chargebee documentation illustrate how revenue tools use service periods, rules, schedules, and mappings. Tool output remains subject to the company’s accounting policy and review.

Control payment processors

Create separate clearing accounts for material gateways and currencies. Record gross customer payments in clearing, then record refunds, chargebacks, fees, reserves, foreign exchange, and bank payouts. The ending balance should equal identified unsettled transactions.

Do not post net payouts directly to sales. Reconcile billing to payment activity, payment activity to settlements, and settlements to bank.

Structure operating expenses by function

Common functions include cost of revenue, research and development, sales and marketing, and general and administrative. The proper presentation depends on reporting framework and policy. Departments can carry function while natural accounts carry payroll, hosting, contractor, advertising, travel, rent, insurance, legal, and other expense types.

Define which hosting, support, payment, and operations costs belong in cost of revenue. Apply the policy consistently. Avoid using one “software expense” account for cloud infrastructure, internal tools, customer delivery, and capitalizable projects.

Track software development with projects and policy

Create project codes for material development initiatives and collect employee time, contractor invoices, cloud costs, and other eligible inputs. Keep research, maintenance, customer implementation, internal-use projects, and software to be sold or licensed distinguishable.

Financial-statement capitalization and tax treatment are separate analyses. IRS section 174 and new section 174A rules have changed recently, including procedures for domestic research or experimental expenditures. Do not build tax entries from an old blog or assume book and tax match.

Separate payroll and equity accounts

Use accounts for wages by function, employer payroll taxes, bonuses, commissions, benefits, payroll liabilities, reimbursements, and stock-based compensation when applicable. Reconcile registers, filings, liabilities, and cash.

For equity, preserve legal classes, issuances, exercises, repurchases, distributions, contributed capital, and retained earnings through a separate equity administration record. Do not use the accounting ledger as the only capitalization table.

Build tax and compliance accounts

Separate sales or indirect tax liabilities, payroll taxes, income-tax balances when applicable, franchise taxes, withholding, and other material jurisdictions. Maintain return and payment schedules.

Marketplace-collected tax and customer tax should be distinguished from company revenue. Reconcile liabilities to filed returns and agency accounts.

Sample numbering framework

• 1000s: cash, clearing, receivables, prepaids, and other current assets.
• 1500s: fixed assets, capitalized software where approved, and accumulated depreciation or amortization.
• 2000s: payables, accrued expenses, payroll, tax, deferred revenue, and debt.
• 3000s: equity.
• 4000s: revenue and contra revenue.
• 5000s: cost of revenue.
• 6000s: research and development.
• 7000s: sales and marketing.
• 8000s: general and administrative.
• 9000s: other income, expense, tax, or carefully controlled clearing.

Number ranges are optional. Meaning, consistency, ownership, and reconciliation matter more than numbering.

Worked example

A customer prepays $12,000 for a one-year subscription. Under the approved simple policy, cash is debited and deferred revenue credited for $12,000. Each month, $1,000 moves from deferred revenue to subscription revenue. Processor fees are recorded separately through clearing.

At the first month-end, the bank ties to cash, the processor report ties to clearing, the customer contract and schedule support $11,000 of deferred revenue, and the revenue subledger supports $1,000 of revenue. MRR is calculated in an operating report, not posted as another journal.

Common mistakes

• Creating accounts for every customer and product.
• Combining cash, receivables, deferred revenue, and sales.
• Recording payment payouts as new revenue.
• Posting taxes collected to income.
• Using MRR, bookings, and billings interchangeably with GAAP revenue.
• Mixing research, maintenance, implementation, and capital projects.
• Assuming book and tax software-development treatment are identical.
• Keeping no owner or reconciliation schedule for control accounts.

Decision rule

Approve a chart of accounts for software development company use when it supports financial statements without unnecessary detail, uses dimensions and subledgers appropriately, distinguishes billing, cash, and revenue, separates development categories, reconciles every control balance, and has documented owners and book-versus-tax policies.

Continue at the Accounting Software and Tools hub. Use the software selection framework, compare company accounting software, or review a QuickBooks Desktop comparison chart.

Educational information only. Tax, payroll, and compliance rules change and may vary by jurisdiction. Confirm the current requirements for your facts with the appropriate agency or a qualified professional.

For chart design, cleanup, and reconciled bookkeeping, review Steady’s QuickBooks services.