Corviniti/Industries/Accounting for Tech Startups

Industries / Tech Startups

Accounting for Tech Startups

Scalable accounting for high-growth technology companies, from first institutional capital through public-company readiness.

Or call (347) 472-1115

Ro Sokhi, CPA, founder of Corviniti, advising on tech startup accounting
Ro Sokhi Founder and CEO, Corviniti
In the press
Overview

The accounting a venture-backed company has to get right

Key takeaways
  • What it is. The technical accounting behind a venture-backed company: revenue recognized under ASC 606, SAFEs and convertible notes classified correctly, stock compensation measured off a current 409A valuation, engineering costs capitalized or expensed under a written policy, and metrics an investor can rebuild and get the same answer.
  • Where it breaks. Revenue recognized loosely in the seed years becomes a restatement risk at Series C. SAFEs booked as equity that were liabilities become an audit finding. ARR defined casually falls apart when a lead investor rebuilds it in diligence.
  • How we help. We set the policies before they become findings: revenue, cap table instruments, stock comp, and cost capitalization, documented at the standard your next auditor and your next investor will apply.

Startup accounting problems compound. Revenue recognized loosely in the seed years becomes a restatement risk at Series C. SAFEs and convertible notes booked incorrectly become an audit finding. Metrics defined casually become a diligence problem when a lead investor rebuilds them.

Corviniti works with venture-backed software, AI, and AI-adjacent companies at the standard their future investors and auditors will apply. We set up ASC 606 revenue policies that match how your product actually sells, account for the instruments on your cap table correctly, set the software cost capitalization policy, and build reporting that scales from board deck to data room. For the deep technical treatment of software and SaaS revenue itself, see our software revenue recognition page; for AI-specific questions, our AI companies practice.

When the exit path is an IPO or acquisition, the same team carries you through readiness and diligence.

SaaS revenue mechanics

Bookings, billings, cash, and revenue are four different events

The most common startup accounting confusion in one example: a customer signs a one-year, $120K contract and pays the full amount up front. Cash arrives on day one; revenue arrives at $10K a month over the year, and until it is earned the balance sits in deferred revenue as a liability. Signing does not earn revenue, invoicing does not, and collecting does not. Only delivery does. It is also why ARR and bookings are operating metrics, not GAAP revenue, and why diligence teams rebuild the bridge between them.

Bookings versus revenue for a SaaS startup: a $120K annual prepay moving through booking, billing, cash collection, and monthly delivery, with revenue at zero until the service is provided and deferred revenue unwinding to zero over twelve months.
One $120K annual prepay, from signature to earned revenue. Illustrative and not exhaustive.
SAFE note accounting

SAFE note accounting: liability or equity

A SAFE looks simple, but the accounting comes down to one question: is it a liability or is it equity? If the terms oblige the company to pay cash in some exits, or to issue a variable number of shares worth a mostly fixed dollar amount, it is a liability under ASC 480, remeasured at fair value every reporting period with the changes running through earnings. That leads to a result founders should see coming: as the company's value rises, the SAFE loss on the income statement gets bigger. Equity treatment, recorded once at the amount raised, is only available after the ASC 480 and ASC 815-40 tests are cleared.

SAFE note accounting decision chart: whether a SAFE is a liability under ASC 480 remeasured at fair value each period with changes in earnings, or equity recorded once at proceeds, with the classification tests run in sequence.
The classification fork that decides whether your P&L swings with every valuation. Illustrative and not exhaustive.
Engineering costs

Software development costs: capitalize or expense?

Where an engineering dollar lands depends on what is being built and how customers will get it. Genuinely uncertain research is R&D expense under ASC 730. Hosted SaaS code the customer never possesses is internal-use software under ASC 350-40: the application development stage capitalizes, the planning before and the maintenance after expense. Software shipped to run on customer infrastructure follows ASC 985-20, where only the short window between technological feasibility and release capitalizes. The same feature team can hit every outcome in a single quarter, which is why time tracking by project and stage is what makes the position defensible.

Software development cost capitalization decision tree: research expensed as incurred under ASC 730, hosted SaaS code capitalized during the application development stage under ASC 350-40, and shipped software capitalized only between technological feasibility and release under ASC 985-20.
The decision tree for engineering spend. Illustrative and not exhaustive.

This is for you if

  • You are raising a priced round and the SAFEs on the cap table have never been classified.
  • Your first audit is coming and the books are still cash-basis or invoice-driven.
  • An investor rebuilt your ARR in diligence and got a different number.
  • Engineering costs have no written capitalize-or-expense policy and burn is being questioned.

What you get

  • The revenue policy ASC 606 applied to how your product actually sells, with the bookings-to-GAAP bridge reconciled.
  • The instrument memos SAFEs and convertible notes classified through the ASC 480 and 815-40 sequence, with fair value marks.
  • Stock comp accounting ASC 718 grant accounting tied to a 409A cadence that keeps up with the round pace.
  • The capitalization policy Engineering costs mapped to ASC 730, 350-40, or 985-20 with time tracking that survives audit.
  • The diligence pack Metrics defined in writing, reconciled to GAAP, and a data room that stays ready between rounds.
How We Help

What we deliver

The core accounting a venture-backed company needs, documented at the standard your next auditor and next investor will apply.

The revenue policyASC 606 applied to how your product actually sells, with the bookings-to-GAAP bridge reconciled.
The instrument memosSAFEs and convertible notes classified through the ASC 480 and 815-40 sequence, with fair value marks.
Stock comp accountingASC 718 grant accounting tied to a 409A cadence that keeps up with the round pace.
The capitalization policyEngineering costs mapped to ASC 730, 350-40, or 985-20 with time tracking that survives audit.
The diligence packMetrics defined in writing, reconciled to GAAP, and a data room that stays ready between rounds.

When companies bring us in

  • You are raising a priced round and the SAFEs on the cap table have never been classified.
  • Your first audit is coming and the books are still cash-basis or invoice-driven.
  • An investor rebuilt your ARR in diligence and got a different number.
  • Engineering costs have no written capitalize-or-expense policy and burn is being questioned.
Our Experience

Where we have done this work

Engagement Notes

A Series B SaaS company heading into its first audit

The books were cash-basis with revenue booked at invoicing, and the cap table carried two years of post-money SAFEs recorded as equity. We converted to accrual, built the ASC 606 policy around the actual contract types, reclassified the SAFEs as liabilities with the fair value marks documented, and had the position memos finished before the auditors started fieldwork. The audit closed without a single restatement conversation.

Engagement Notes

A usage-priced platform whose ARR did not survive diligence

A lead investor rebuilt the company's ARR from the ledger during a Series C and got a materially lower number, because the metric had quietly absorbed one-time services and annualized usage spikes. We rebuilt the definition, reconciled it to GAAP revenue month by month, and restated the metric history so the figures the company reported matched the ledger. The round closed on the rebuilt numbers.

The Detail

The gaps, and how we close each one

Issue 01

SaaS revenue recognition that matches how you sellASC 606

Subscriptions, usage pricing, and multi-element deals each recognize differently, and early-stage teams often book to the invoice or to the cash instead. The error is invisible while the company is small and compounding by the time an auditor or an investor finds it.

The treatment

A subscription is a stand-ready obligation recognized over the term, usually ratably. Usage and overage fees are variable consideration, and where the monthly bill tracks the value delivered, the right-to-invoice expedient recognizes what you invoice without a full-contract estimate. Implementation and services get tested for whether they are distinct. Cash collected before delivery sits in deferred revenue as a liability, and bookings and ARR reconcile to GAAP revenue through a bridge we keep clean from day one. The full software treatment, license versus SaaS, obligation counting, and ASC 340-40 commissions, lives on our software revenue recognition page.

How we handle it: We build the ASC 606 policy around your actual contract types and keep the bookings-to-GAAP bridge reconciled.

Issue 02

SAFE and convertible note accountingASC 480 / 815

Founders assume SAFEs are equity because the form says so. Many are liabilities under ASC 480, remeasured at fair value every reporting period, and the misclassification is one of the most common first-audit findings for venture-backed companies.

The treatment

We run the classification in sequence: ASC 480 liability characteristics first, including change-of-control cash-outs and variable-share settlement worth a mostly fixed amount, then the ASC 815-40 own-equity tests, with equity as the residual. A liability-classified SAFE is remeasured at fair value each reporting date with changes through earnings, which means good news grows the loss, a result worth explaining to the board before the first mark. Convertible notes run their own gates across ASC 470-20, 480, and 815; that analysis lives on our convertible debt accounting page. Every position is documented before the auditors ask.

How we handle it: We classify every instrument on the cap table through the ASC 480 and 815-40 sequence and document the marks.

Issue 03

Stock compensation and 409A valuationsASC 718

Every option grant needs a grant-date fair value, and that depends on a current 409A valuation. As the company grows, grants get made against stale valuations, which is a problem an auditor flags and the SEC scrutinizes in the pre-IPO cheap-stock review.

The treatment

We make sure every grant is priced off a current 409A valuation, measure grant-date fair value under ASC 718, set the forfeiture policy, and handle the modifications, repricings, and secondary-sale complications that fast-growing cap tables generate. Heading toward an IPO, we run the cheap stock analysis the SEC staff expects. The deep treatment is on our stock-based compensation page.

How we handle it: We tie the grant cadence to the 409A cadence and run the cheap-stock analysis before the SEC asks.

Raising the next round or heading into a first audit? Talk to us before the findings are written for you.

Talk to an Expert
Issue 04

Software development costs: capitalize or expenseASC 350-40 / 985-20 / 730

The same engineering payroll can be R&D expense, capitalized internal-use software, or capitalized software-to-be-sold, and the difference changes burn, gross margin, and the balance sheet. Most startups have no written policy until an auditor asks for one.

The treatment

The decision tree in the infographic above is the policy: research expenses under ASC 730, hosted SaaS code follows the ASC 350-40 stages with application development capitalizing, and shipped software capitalizes only in the short ASC 985-20 window after technological feasibility. We write the policy, set up the time tracking by project and stage that makes it defensible, and keep the documentation contemporaneous, because a capitalization position reconstructed at year-end rarely survives audit.

How we handle it: We write the capitalization policy and set up the project-and-stage time tracking that makes it defensible.

Issue 05

Metrics investors can rebuildDiligence

ARR, NRR, burn, and runway defined casually fall apart when a lead investor rebuilds them from the ledger and gets different numbers. That gap costs you credibility with the exact person deciding how to price your round.

The treatment

We define each metric once, in writing, and reconcile ARR to GAAP revenue so anyone can trace the operating metrics back to the audited financial statements. Board reporting depends on a monthly close discipline, and the data room stays ready for diligence between rounds instead of being assembled in a hurry during one.

How we handle it: We define the metrics once, reconcile ARR to GAAP revenue, and keep the data room diligence-ready.

Issue 06

From first audit to public-company readinessFirst audit / S-1

A first audit surfaces every deferred policy decision at once: revenue, SAFEs, stock comp, capitalization. An IPO adds PCAOB standards, quarterly discipline, and internal controls on top.

The treatment

We take companies through the pre-audit cleanup on our timeline rather than the auditor’s, with position memos written before fieldwork starts. When the path leads to the public markets, the same team runs the readiness workstream: PCAOB uplift, S-1 financial statements, and the close calendar that survives being public. See IPO readiness and audit support.

How we handle it: We run the pre-audit cleanup on your timeline, with position memos finished before fieldwork starts.

FAQ

Frequently asked questions

When should a startup move from cash to accrual accounting?

By the time you raise institutional capital, and earlier if you have deferred revenue or meaningful receivables. Investors diligence GAAP numbers, and converting later is more expensive than starting right.

How should SAFEs be accounted for?

It depends on the terms, and the analysis matters: many SAFEs are liabilities under ASC 480 rather than equity, which puts a fair value remeasurement through earnings every period. We document the position so your auditors can test it.

What is the difference between bookings, ARR, and revenue?

Bookings are contracts signed, ARR is an annualized operating metric, and revenue is what GAAP says you have earned by delivering. A $120K annual prepay is $120K of bookings on day one and $10K of revenue a month as the service is provided. Diligence teams rebuild the bridge between the three, so keep it reconciled from the start.

Should we capitalize our software development costs?

It depends on what you build and how customers get it. Hosted SaaS development can capitalize during the application development stage under ASC 350-40; shipped software capitalizes only briefly under ASC 985-20; research expenses as incurred. The real requirement is a written policy and time tracking that supports it.

Can you work alongside our existing bookkeeper?

Yes. A common model: your bookkeeper handles transactions, we handle the technical layer, the close review, and investor reporting.

Sources & authorities

Primary sources for this page

  • Research costs, capitalized. IRC Section 174: the required capitalization and amortization of research and experimental costs.
  • Qualified small business stock. IRC Section 1202: the gain exclusion that shapes C-corporation and cap-table decisions.
  • Option pricing. IRC Section 409A: the 409A valuation behind a defensible strike price.
  • Revenue and equity compensation. ASC 606 for subscription and usage revenue, and ASC 718 for stock-based compensation.

This page summarizes federal tax and accounting rules for general information, and is not tax or accounting advice. Rules change; confirm the current text before you rely on it.

Contact Us

Contact Us to Learn More

Call: (347) 472-1115
Email: info@corviniti.com

The best way to get started is to complete the form below. Tell us a bit about your business and we will advise on how best to get started.

We will get back to you within 24 hours.

Ro Sokhi, CPA
Ro Sokhi, CPA
Founder & CEO · Big Four experience · 20+ years

We will get back to you within 24 hours.