Outsourced accounting for SaaS works best when the outside team owns the repeatable monthly work: the close, the billing-to-ledger reconciliation, the deferred revenue roll-forward and the tracking of software development costs for both GAAP and tax. Management keeps contract approvals and final sign-off, and the CPA firm reviews judgment calls before anything reaches the board.
This guide sets out what to hand off, what to keep in house and what changed in 2026 for SaaS books. Two rule changes matter most for outsourced accounting for SaaS this year: the One Big Beautiful Bill Act made domestic software development costs deductible again under Section 174A, and FASB's ASU 2025-06 rewrote when internal-use software costs start to be capitalized.
A subscription business collects cash before it delivers the service. A customer who pays $120,000 on January 1 for a 12-month subscription has bought $10,000 of service per month. After the January close, $10,000 sits in revenue and $110,000 sits on the balance sheet as a contract liability. Under ASC 606-10-45-2, the entity presents a contract liability "when the payment is made or the payment is due" (Deloitte DART, ASC 606-10-45-2), whichever comes first.
A general bookkeeper who records invoices as revenue on the invoice date front-loads income and understates the liability. The error flows into every metric built from the ledger, and it usually surfaces during a fundraise or a first audit. The mechanics of why prepaid cash is a liability are covered in our explainer on deferred revenue as a liability.
The rest of the SaaS ledger adds its own layers. Contracts bundle subscriptions with implementation and training. Customers upgrade, add seats and renew early. Engineering payroll may be partly capitalized for the books and fully deducted for tax, or the reverse. Each of these is repeatable once the method is set, which is why it suits an outsourced team working under CPA review.
The table below is a practical split of monthly SaaS accounting work. The outside team prepares, the company supplies inputs and approves, and the CPA firm reviews the areas that need judgment.
| Monthly task | Outsourced team prepares | Company or CPA keeps |
|---|---|---|
| Bank, card and payroll reconciliations | Full reconciliation and accruals | Approval of unusual items |
| Billing system to general ledger | Tie invoices, payments, refunds and AR to the GL | Decisions on write-offs and credits |
| Revenue schedules and deferred revenue | Contract-level schedules and the roll-forward | Review of new contract terms and modifications |
| Software development costs | Time and cost tracking by project, capitalization schedule | Capitalization policy and project approval |
| Section 174A tax workpaper | Domestic and foreign R&E cost split | Tax elections and the return itself |
| Sales tax on subscriptions | Liability reconciliation by state | Nexus and taxability decisions |
| Reporting package | Financial statements, SaaS metrics, variance notes | Board narrative and sign-off |
A SaaS close follows the same sequence as any accrual close for cash, payables and payroll. The SaaS-specific steps come after: posting the revenue schedules, reconciling the billing platform to the ledger and rolling forward deferred revenue. The order matters because the metrics package should only be built once revenue and deferred revenue are final for the month.
Stripe, Chargebee, Recurly and Zuora each hold their own record of subscriptions, invoices and payments. The ledger must agree with them. The outside team should compare total invoiced, total collected, refunds and ending receivables each month and trace every difference. Typical breaks are refunds processed in the billing tool but never booked, failed card payments that the platform retries into the next month, and currency differences on international customers. If your billing platform also calculates tax, the setup choices are covered in our guide to SaaS billing sales tax, and state-by-state taxability is in our page on SaaS sales tax by state.
The outsourced team should keep one revenue schedule per contract. Each schedule records the performance obligations, the allocation of price to each one and the month each portion is recognized. A contract that combines a $120,000 subscription with a $20,000 implementation and $10,000 of training usually has separate obligations recognized on different timelines, with the price allocated on standalone selling prices.
Contract modifications are where SaaS books most often drift. An upgrade that adds distinct services at standalone selling prices is accounted for as a separate contract. A change to the price or scope of existing services needs an ASC 606 assessment to decide between prospective treatment and a cumulative catch-up. The outside team can flag every modification from the billing data each month, while the CPA firm signs off on the treatment. Our SaaS revenue recognition under ASC 606 guide walks through the five steps and the modification rules in detail.
The deliverable each month is a deferred revenue roll-forward: opening balance, plus new billings, less revenue recognized, equals closing balance. That closing figure must tie to the balance sheet before the metrics are calculated.
Most SaaS platforms are internal-use software for GAAP purposes, even though customers use them. ASU 2025-06 confirms that Subtopic 350-40 "applies to both (a) an entity that is incurring costs to develop" "the software that will be provided to an end user in a CCA" (FASB, ASU 2025-06), where a CCA is a cloud computing arrangement. The external-use software rules apply only where the customer can take possession of the software and run it elsewhere.
FASB issued ASU 2025-06 in September 2025. It removes the old preliminary, development and post-implementation project stages. Under the new text, capitalization starts when "Management has authorized and committed to funding the software project" and "It is probable that the project will be completed and the software will be used to perform the function intended" (FASB, ASU 2025-06).
FASB calls the second condition the "probable-to-complete recognition threshold" (FASB, ASU 2025-06), and it carries a new test. Significant development uncertainty exists, and capitalization waits, while "The software being developed has technological innovations or novel, unique, or unproven functions or features" that have "not been resolved through coding and testing" (FASB, ASU 2025-06), or while the significant performance requirements are still unsettled. For a SaaS engineering team, that means the capitalization start date for a new product line may be later than under the old stage model, and the outsourced team needs a project-level record of when uncertainty was resolved.
The amendments "are effective for all entities for annual reporting periods beginning after December 15, 2027," and "Early adoption is permitted as of the beginning of an annual reporting period" (FASB, ASU 2025-06). A calendar-year company must adopt by January 1, 2028. Transition can be prospective, modified based on project status, or retrospective.
As of October 2026, the practical handoff is a monthly cost-tracking file by project: engineer hours, contractor invoices, the date funding was approved and the date development uncertainty was resolved. That file supports the current capitalization schedule and, later, the ASU 2025-06 transition and the tax workpaper below. Implementation costs your company pays for its own cloud tools are a separate question, covered in our guide on cloud computing arrangement costs under ASC 350-40.
For tax, the One Big Beautiful Bill Act added Section 174A. The IRS states that "For taxable years beginning after Dec. 31, 2024," "taxpayers may deduct domestic research or experimental expenditures which are paid or incurred by the taxpayer" during the year (IRS, One Big Beautiful Bill provisions). The statute treats "any amount paid or incurred in connection with the development of any software" as a research or experimental expenditure (26 U.S.C. 174A, Cornell LII), so SaaS engineering costs fall inside it.
Two details matter for SaaS companies with distributed teams. Domestic costs can be deducted in the year paid or incurred, or the company can elect to amortize them over at least 60 months. Foreign costs cannot be deducted currently: the IRS says taxpayers may "capitalize and amortize them ratably over a 15-year period" starting from the midpoint of the year the costs are incurred (IRS, One Big Beautiful Bill provisions). A SaaS company that uses offshore developers therefore needs every development cost tagged as domestic or foreign at the time it is booked.
There is also a carryover from the 2022 to 2024 years, when domestic costs had to be amortized over five years. The OBBBA transition rule, with procedures in Rev. Proc. 2025-28, lets a taxpayer elect to deduct the remaining unamortized domestic amount in full in the first tax year beginning after December 31, 2024 (2025 for a calendar-year company), or "ratably over the 2-taxable year period beginning with the first taxable year beginning after December 31, 2024" (IRS, Internal Revenue Bulletin 2025-38). Calendar-year companies that chose the two-year option will see the second half on their 2026 return. The broader rule history is in our article on Section 174 after the One Big Beautiful Bill Act.
A calendar-year SaaS company spends $1,200,000 on software development in 2026: $900,000 for its US engineers and $300,000 for offshore contract developers. Under its current GAAP policy, $360,000 of that cost relates to a module that met the capitalization criteria and was still in development at year end.
| Line | GAAP books | Federal tax |
|---|---|---|
| Domestic development cost | $900,000 | $900,000 deducted under Section 174A |
| Foreign development cost | $300,000 | $10,000 amortized ($300,000 / 15 years, half-year at midpoint) |
| Capitalized to the balance sheet | $360,000 | $290,000 of foreign cost left to amortize |
| 2026 expense or deduction | $840,000 | $910,000 |
The book figure is $1,200,000 less $360,000 capitalized. The tax figure is $900,000 plus $10,000. If the same company elected the two-year transition for $400,000 of unamortized domestic costs from 2022 to 2024, a further $200,000 is deductible on the 2026 return. The outsourced team prepares this split each month from the cost-tracking file, and the CPA firm uses it for the provision and the return. Credit claims are a separate exercise with their own records.
Once revenue and deferred revenue are final, the outsourced team builds the reporting package: GAAP financial statements, a metrics schedule and variance notes. Recurring revenue figures should exclude one-time implementation and training revenue, and each metric should tie back to ledger data. Formulas and their GAAP ties are covered in our guide to SaaS financial metrics. Where the board needs forward-looking analysis on pricing or burn, that work usually sits with a SaaS fractional CFO.
Clean monthly files also shorten audits and diligence. Auditors of SaaS companies test revenue cut-off, deferred revenue and capitalized software closely, and some audit teams now use technology-assisted analysis, as our article on PCAOB technology-assisted analysis in SaaS audits explains. Contract-level revenue schedules, a monthly deferred revenue roll-forward and a project-level capitalization file are the records they ask for first. Founders preparing for a raise can also use our checklist for investor due diligence on startup finances.
Contract and cost complexity is the usual trigger. Signs that a SaaS company has outgrown cash-basis bookkeeping include annual or multi-year prepayments, bundled implementation fees, a planned priced round or audit, engineering spend large enough to make capitalization and Section 174A material, and customers in several sales tax states. As a rule of thumb, a company showing two or more of these usually needs accrual books with contract-level revenue schedules.
If the company already has a controller, a co-sourced model works well. The controller keeps policy and judgment, and the outside team takes the reconciliations, schedules and tracking files described above.
What does outsourced accounting for SaaS usually include? It typically covers the monthly close, reconciliation of the billing platform to the ledger, contract-level revenue schedules, the deferred revenue roll-forward, software cost tracking and a monthly reporting package. Tax elections, capitalization policy and contract approvals stay with management and the CPA firm.
Does ASU 2025-06 apply to a SaaS company's own platform? In most cases, yes. Software provided to customers through a hosted arrangement falls under Subtopic 350-40 unless the customer can take possession of the software and run it elsewhere. The ASU is effective for annual periods beginning after December 15, 2027, with early adoption permitted.
Can SaaS companies deduct developer salaries in 2026? Domestic software development costs can be deducted in the year paid or incurred under Section 174A for tax years beginning after December 31, 2024. Costs for research performed outside the US must still be amortized over 15 years.
Is deferred revenue the same as unearned revenue? Both terms describe cash received or billed before the service is delivered. ASC 606 calls the balance a contract liability, and it is recognized as revenue as each month of service is provided.
Madras Accountancy supports US CPA firms and their SaaS clients with monthly bookkeeping, close support, revenue and deferred revenue schedules, software cost tracking and reporting packages, all prepared for CPA review. To discuss the monthly work you want to hand off, contact our team.
The section 4960 excise tax is 21% of nonprofit pay over $1M. From 2026 it covers all employees. See the medical carve-outs, Form 4720 and a worked example.
The paid family and medical leave tax credit is permanent from 2026. See the 12.5% to 25% rates, the premium option, the 6-month rule and how Form 8994 works.
Opportunity zones become permanent in 2027 under the One Big Beautiful Bill. See the new deferral, rural bonus, and the 2026 handoff.
