A subscription business does not have hard books because of volume. It has hard books because a handful of numbers on the face of the statements are the output of an accounting policy, and the policy is the part that stays with you. Deferred revenue, capitalized commissions, capitalized software and the tax method behind that software all sit in that group, and in 2025 the tax method moved while the capitalization standard was rewritten to take effect later.
So outsourced accounting for SaaS works when the split is written down before the first close: the outside team produces the schedules, and a named person on your side owns the policy each schedule applies.
What Outsourced Accounting for SaaS Actually Covers
Most of the scope is ordinary and moves without argument.
Transaction coding, bank and merchant reconciliations, accounts payable, billing support, payroll processing, the close calendar and the reporting pack are all preparation work. They have a right answer, they can be checked against a source document, and a reviewer can grade them from anywhere. That is the same body of work as any other client accounting services engagement, and the sorting question for each task is worked through in which accounting tasks to outsource.
What does not move is the layer underneath. Somebody has to decide when a performance obligation is satisfied, whether a commission is recoverable, when a software project has cleared the threshold for capitalization, and which tax method the company is on. Those are positions, not calculations. An outside team can draft the memo and run every number that follows from it, but the position belongs to the company, and every schedule below is only as good as the position above it.
Revenue Timing Is the First Policy Call
Everything distinctive about SaaS accounting starts with when the revenue is earned, and that question has one authoritative framework.
The Financial Accounting Standards Board created Topic 606, Revenue from Contracts with Customers, in Accounting Standards Update 2014-09. Its core principle is that an entity "should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services."
The same document sets out the five steps an entity applies to reach that principle, and each one is a place where a subscription contract can go wrong.
- Identify the contract with a customer. An order form, an auto-renewal and a signed master agreement can be one contract or several.
- Identify the performance obligations in the contract. A performance obligation is a promise to transfer a distinct good or service, so implementation, training and premium support may or may not be separate from the subscription itself.
- Determine the transaction price. Usage tiers, credits, service level penalties and rebates are variable consideration, and the standard constrains how much of an estimate can be included.
- Allocate the transaction price to the performance obligations. Discounts on a bundle have to land somewhere, and where they land changes the timing.
- Recognize revenue when, or as, the entity satisfies a performance obligation. A hosted subscription is generally satisfied over the term rather than at invoice.
Deferred revenue is the consequence of that timing, and the standard gives it a different name. Under paragraph 606-10-45-2 of the same update, if a customer pays, or an unconditional right to payment exists, before the entity transfers the good or service, the entity "shall present the contract as a contract liability when the payment is made or the payment is due (whichever is earlier)." A contract liability is defined there as an obligation to transfer goods or services for consideration the entity has already received or is already owed.
That is why an annual prepaid plan makes a growing company's reported revenue lag the cash it has already collected. The cash arrives once, the obligation sits on the balance sheet, and the revenue is released as the service is delivered. An outside team can build and roll that schedule forward every month. The contract-level judgment that feeds it, on what is distinct and how long the term runs, cannot be delegated to whoever is doing the keying.
Sales Commissions Are an Asset Before They Are an Expense
The second policy call is the one that surprises founders, because it moves part of the sales team's pay off the income statement and onto the balance sheet.
Update 2014-09 also created Subtopic 340-40 for contract costs. An entity "should recognize as an asset the incremental costs of obtaining a contract that the entity expects to recover", where incremental costs are the ones the entity "would not have incurred if the contract had not been obtained". Paragraph 340-40-25-2 of that update names the example outright: "for example, a sales commission". As a practical expedient, the update allows those costs to be expensed as incurred "if the amortization period is one year or less".
Once the asset exists, it has to unwind on a defined pattern. Paragraph 340-40-35-1 requires the asset to be "amortized on a systematic basis that is consistent with the transfer to the customer of the goods or services to which the asset relates", per that update.
The judgment hiding in that sentence is which goods or services the commission relates to, because that is what sets the amortization period, and it is not automatically the term printed on the order form. A commission paid once on a subscription the customer is expected to keep renewing may relate to a longer period of benefit than that first term. Take the position once, write down the reasoning, and the amortization run becomes preparation work an outside team can own. Leave it unset and every month produces a number nobody can defend.
Your Own Software Build Has a New Capitalization Test
The standard for capitalizing internal development was rewritten in September 2025, and its required start date is still ahead. The change lands hardest on companies that deliver their software as a subscription.
Accounting Standards Update 2025-06 removes every reference to prescriptive and sequential development stages from Subtopic 350-40, the internal-use software guidance. In their place, an entity starts capitalizing 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". The update also tells entities to consider whether significant development uncertainty exists, and it names two factors to weigh in that judgment: whether the uncertainty around any novel or unproven functions has been resolved through coding and testing, and whether the entity has settled what it needs the software to do rather than continuing to substantially revise the software's significant performance requirements.
The consequence for a SaaS company is stated in the update itself. For software provided through a cloud computing arrangement, the Board expects the amendments "could result in a decrease in software capitalization", bringing the outcome closer to how software sold under an on-premises license is treated.
Timing is workable rather than urgent. The amendments in that update are effective for all entities for annual reporting periods beginning after December 15, 2027, and interim periods within them, with early adoption permitted as of the beginning of an annual reporting period. What matters now is that the capitalization threshold is about to become a judgment about funding and uncertainty rather than a project-stage checklist, and somebody inside the company has to make it. Whether a novel feature has been proven out is something the engineering team can answer and an outside preparer cannot.
The Tax Method Changed in 2025, and Software Is Named in It
Book capitalization is one question. The tax deduction is a separate one, and it moved first.
Revenue Procedure 2025-28 sets out the procedures behind section 70302 of Public Law 119-21, enacted July 4, 2025. That section added section 174A to the Internal Revenue Code, which provides that "a deduction is allowed for any domestic research or experimental expenditures which are paid or incurred by the taxpayer during the taxable year". The change applies to amounts paid or incurred in taxable years beginning after December 31, 2024.
Software is named directly. Section 174A(d)(3) provides that any amount paid or incurred in connection with the development of any software is treated as a research or experimental expenditure, per the same revenue procedure. For a company whose main cost is engineers building the product, that single subsection decides how much tax it pays this year.
The old treatment is what makes the change worth acting on. Under section 174 as amended by the Tax Cuts and Jobs Act, described in Revenue Procedure 2025-28, these expenditures had to be charged to capital account and amortized ratably over a 5-year period where they were attributable to domestic research, or a 15-year period where they were attributable to foreign research. The foreign 15-year period survives, so where development work is performed is now a tax fact rather than an operating preference. A company can also elect under section 174A(c)(1) to capitalize and amortize domestic amounts "ratably over a period of not less than 60 months" instead of deducting them.
There is also a catch-up election. For amounts paid or incurred in taxable years beginning after December 31, 2021, and before January 1, 2025, that were capitalized under the old rule, the remaining unamortized amount can be taken in full in the first taxable year beginning after December 31, 2024, or ratably over a 2-taxable year period beginning with that year, under the same procedure.
One window has already shut. A separate retroactive election applied section 174A back to taxable years beginning after December 31, 2021, and it had to be made by Monday, July 6, 2026, as Revenue Procedure 2025-28 explains. It was open only to a taxpayer that met the section 448(c) gross receipts test for its first taxable year beginning after December 31, 2024, which for a taxable year beginning in 2025 means average annual gross receipts for the three prior taxable years of $31,000,000 or less. A method election on a filed return is not a monthly schedule, and it is invisible to a provider who was only asked to keep the books. If nobody with a view of the tax position was in the room, nobody raised it.
Sales Tax Follows the Classification, Not the Label
The last policy call is the one that turns into a liability quietly, because nothing in the ledger flags it.
Physical presence stopped being a requirement in South Dakota v. Wayfair, Inc., decided June 21, 2018, where the Supreme Court held the physical presence rule of Quill Corp. v. North Dakota unsound and overruled it. The South Dakota law behind that case reached sellers that, on an annual basis, deliver more than $100,000 of goods or services into the state or engage in 200 or more separate transactions for delivery into it. Economic nexus, meaning a collection obligation created by sales volume alone, is what states adopted once physical presence was no longer required, and a self-serve product can cross a state's threshold without the company ever having an employee there.
Whether the subscription is taxable once nexus exists is a separate question, and it is answered by how each state classifies what is being sold. Texas has already answered it inside its own borders. The Comptroller's taxable services list says data processing services providers "include sellers of software as a service and application service providers", so a Texas subscription is not a close call.
The mechanics follow from that classification. The Comptroller's guidance on data processing services says entering, storing, manipulating or retrieving a customer's data is taxable, while "merely using the computer as a tool to help perform a professional service is not taxable", and the state rate on the taxable side is 6.25 percent plus local taxes. That rate does not run on the full price, because the taxable services list is explicit: "Twenty percent of the charge for data processing services is exempt from tax." Tax is due on the rest. The same data processing bulletin carries a mixed-contract rule: where a taxable service is 5 percent or less of the contract price and is not separately identified, no tax is collected on it.
Elsewhere the line still has to be read, and reading it is narrow work. A subscription whose function is holding and manipulating a customer's data sits on a different side of that line than one that delivers a professional judgment, and separately stating the components on the invoice is what preserves the distinction. Registration, filing and reconciliation are all preparation work. Deciding what the product is, state by state, is not.
What the Handoff Looks Like When Policy Stays With You
The workable arrangement is boring and specific, and it is mostly documentation.
Write four short memos before the first close: the revenue recognition policy, the commission amortization period and the reasoning behind it, the software capitalization threshold, and the tax method the company is on. Each one names the person who owns it. Everything the outside team produces then points back at one of them, and review stops being an argument about principles and becomes a check that the schedule follows the memo.
Then fix the sequence. The month-end close checklist settles what is due when, and the same discipline applied to a subscription ledger means the deferred revenue rollforward, the commission schedule and the capitalized software register close in a known order with a named reviewer on each. Where the work sits inside a larger reporting chain, the boundaries are laid out in record to report services.
Two boundaries are worth naming out loud. An outside accounting team is not a finance chief, and the line between producing numbers and committing the company on the strength of them is drawn in what an outsourced CFO does. And if the choice itself is still open, the honest trade-offs are set out in in-house versus outsourced accounting.
Questions About Outsourced Accounting for SaaS
How Much Does It Cost to Outsource Accounting?
The answer tracks scope, not hours. A subscription ledger with one plan, monthly billing and one state of registration carries a fraction of the work of one with usage tiers, annual prepays, multi-element contracts and filing obligations in a dozen states. Review depth is the other driver, because a schedule somebody senior signs off costs more to produce than one that lands in an inbox unchecked. The pricing structures behind those differences are broken down in what outsourced bookkeeping costs.
Will Investors and Auditors Accept Financials an Outside Team Prepared?
They accept financials that can be traced, and who keyed them is not the test. What gets examined is whether the revenue policy is documented and applied consistently, whether the deferred revenue rollforward ties to the billing system, whether the commission asset agrees to the underlying plans, and whether someone with authority reviewed the result. A first audit or a diligence request will ask for the memo before it asks for the schedule. Where a provider's own controls come up, the difference between the two common reports is explained in SOC 1 versus SOC 2.
Start With One Closed Month
Take a month you have already closed. Ask for the deferred revenue rollforward, the commission amortization schedule and the capitalized software register to be rebuilt from the contracts and the billing export, without your existing workpapers as a guide.
Set the result beside what you produced and work down the differences. Each one resolves into either a missing input, which is fixable, or a policy that was never written down, which is the real finding. That test tells you which parts of the work can move and which parts were always a decision wearing the costume of a task.
If your firm carries SaaS clients, the same split decides which of their work can be prepared somewhere else and which stays with your reviewer. Accountably places trained offshore accountants and tax preparers inside US CPA and EA firms, ramped on your software and your procedures in about 3 to 4 weeks, and the signature, the opinion and the final judgment stay with your firm. Since 2022 we have worked with 20+ US firms across 30+ placements. Don't trust us. Test us. The Free 40-Hour Proof Pilot puts a fixed block of your own representative work through full multi-layer review, on your setup, so your reviewer grades real output before a client file depends on it, and if a placement is not the right fit in the first 30 days we replace them free.