SaaS startups, scaleups and the CPAs who serve them

ASC 606 revenue recognition, a cap table with ASC 718 stock comp, and burn and runway on your own books.

For SaaS startups, scaleups and the CPAs who serve them. Connect QuickBooks Online, or run the whole finance stack on Fintra.
Book a demoLog in

Revenue Recognition

Example figures
Acme Corp: annual SaaS: recognized
$10,000
Globex: usage overage: recognized
$3,480
Initech: multi-year + discount: catch-up
$540,000
Umbrella: annual renewal: billed
$96,000
Deferred revenue $1.8M (illustrative)

Your billing tool, your cap table, and your books never agree, and the board finds out at the worst time.

  1. Revenue lives in a spreadsheet

    Stripe invoices say one thing, a rev-rec tab in Excel says another, and the GL says a third, so ASC 606 becomes a quarter-end scramble and deferred revenue is a number nobody can trace back to a contract.

  2. Bookings, billings, and revenue blur

    Sales celebrates a booking, finance billed something else, and revenue recognizes a third number, so the growth numbers get argued about in board meetings instead of trusted.

  3. The cap table cannot see the books

    Carta holds the shares and QuickBooks holds the ledger, so ASC 718 stock-comp expense is hand-journaled every month, the 409A sits in a folder, and dilution math lives in a founder’s spreadsheet.

  4. Runway is a guess

    Burn, the hiring plan, and the forecast live in a model that drifts from actuals the day it is built, so the runway number in the board deck is stale before the meeting starts.

  5. Spend leaks between tools

    Expenses and bill pay run in apps that do not post to the ledger cleanly, so the burn you watch and the burn you booked never quite match.

  6. Enterprise deals stall on security

    The first SOC 2 questionnaire lands, evidence is scattered across screenshots and Notion, and a six-figure deal waits while a founder assembles a binder by hand.

What Fintra does for technology

Fintra runs the finance side of a software company, from the first booking to the audited close. It leads with the loop SaaS bleeds on: booking to billing to ASC 606 revenue to the deferred-revenue waterfall to cash and runway, posting real journal entries on one governed ledger. Your cap table and ASC 718 stock-comp expense live in Fintra too: the cap table, grants and 409A valuations are entered here, and the expense posts to that same ledger rather than being computed in a tool that cannot see the books. Connect QuickBooks Online, or run it all on Fintra.

  • Run it on Fintra, or connect QuickBooks Online
  • ASC 606 revenue & deferred-revenue waterfall
  • Cap table, 409A & ASC 718 expense posted to your ledger
  • FP&A, burn & runway
  • SOC 2 controls & evidence in Fintra Trust

Stock-Comp Expense

Example figures
A. Rivera, ISO, 40,000, 4-yr / 1-yr cliff
$4,200 exp
K. Osei, RSU, 12,000, double-trigger
$0 exp
J. Park, NSO early-exercise, 60,000
$6,900 exp
ASC 718 stock-comp expense computed from each grant’s 409A-based fair value and vesting, and posted to the general ledger. Illustrative grants.

Run it on Fintra, or connect QuickBooks Online.

Lead with running the whole finance stack on Fintra: one governed ledger for revenue, spend and stock-comp expense, so bookings, billings, revenue, and stock comp reconcile by construction. Not ready to move off your tools? Fintra connects to QuickBooks Online and reads the chart of accounts, customers, vendors, invoices and bills, and owns the ASC 606 engine, the cap table, FP&A, and the evidence on top.

Stays in your existing stack

QuickBooks, your billing tool

  • GL history & chart of accounts
  • Customers, invoices & bills
  • Subscription billing & card collection

Fintra connects to QuickBooks Online. It does not read Stripe or other billing-tool data, so contracts are entered in Fintra and revenue schedules are created from the invoices you post. The cap table, grants and 409A valuations are entered in Fintra too.

Fintra runs

Finance, Trust and People, plus the two technology jobs below

  • ASC 606 revenue engine
  • Deferred-revenue waterfall
  • Cap table & ASC 718 stock comp
  • FP&A, burn & runway
  • Expenses & bill pay
  • HRIS & ATS
  • SOC 2 controls (Fintra Trust)
  • Governance & evidence

Run it all on Fintra. Fintra can run the general ledger, ASC 606 revenue, the cap table and stock-comp accounting, FP&A, and spend itself, so a startup tired of stitching QuickBooks to a billing tool to Carta to a spreadsheet, or a fractional CFO running twenty client books, can consolidate onto one platform. A company with several entities consolidates them into one P&L and balance sheet. Fintra Payroll is coming soon.

ASC 606 revenue you can defend, and the cap table on the same books.

Every startup has a bookkeeper somewhere. ASC 606 revenue and the cap table are where a SaaS back office is won or lost, and where a fundraise or an audit turns painful, so Fintra builds them in rather than bolting them on.

SaaS Revenue Recognition

ASC 606, on a governed ledger

Every contract’s transaction price is allocated to its performance obligations by standalone selling price, and revenue recognizes on its schedule: ratably for a subscription, at a point in time for setup, at a milestone for services, and as consumed for usage that is reported. When an invoice for a rev-rec product posts, its schedule is created and the deferral posted, and each month’s recognition posts a real journal entry. The deferred-revenue waterfall shows what releases when, a contract change catches up cumulatively instead of being overwritten, and the revenue dashboards put booked, billed and collected side by side.

  • ASC 606 allocation by standalone selling price
  • Deferred-revenue waterfall from real journal entries
  • Usage recognized as it is reported
  • Booked, billed & collected side by side

Cap Table and Stock Comp

Equity accounting on your own books

The cap table holds security classes, stakeholders, holdings, the option pool, and SAFEs and notes counted as converted in the fully diluted view. ASC 718 stock-comp expense computes from each grant’s 409A-based fair value and vesting, with forfeitures reversed, and posts to your general ledger by cumulative catch-up, so a re-run posts nothing twice. 409A valuations price the grants they cover, and a priced round with a new option pool is modeled against the real table. The equity story and the accounting become one source of truth, not a cap-table tool and a GL arguing at audit.

  • Cap table, option pool, SAFEs & notes
  • ASC 718 expense posted to your ledger
  • 409A valuations attached to grants
  • Round & option-pool dilution modeling

Deferred-Revenue Waterfall

Example figures
Billed up front
$120,000
one annual contract
Recognized each month
$10,000
ratably over the year
Deferred after month one
$110,000
Deferred revenue releases month by month as the obligation is satisfied, and each release posts a journal entry from deferred revenue to revenue. Illustrative.

Everything else your business runs on

Accounting, budgeting, HR and security run on the same books, approvals and evidence as everything above, so nothing is copied between systems.

Accounting and the month-end close

Transactions are recorded, categorized and reconciled, and the close entries are drafted for a named person to approve. Double-entry, ASC 606 and multi-currency, with statements from the posted books.

See accounting and the close

Budgets, forecasts and budget vs. actuals

Budgets, scenario forecasts and driver models that read the posted books directly, so there is no export to keep in step.

See budgeting and forecasting

HR and people

Onboarding, time off, cases and an HR help desk that answers routine questions, with hiring and headcount plans kept against the finance budget.

See HR and people

Security with SentriAI

A bill payment a person records, a change to a vendor's bank details and a change to a person's role, whether a person or an AI agent asks for it, are each allowed, held for approval or blocked before they happen, with the reason written down. Every decision is sealed into a hash-chained record an auditor can recompute.

See how SentriAI checks actions

Payroll

Coming soon

Payroll on the same books as your accounting, budgets and HR is coming soon.

Read about payroll

The same books, approvals and controls, set up for technology

Finance

Recognize revenue, watch the runway, on one governed ledger.

ASC 606 revenue recognition with the deferred-revenue waterfall, and FP&A built for a startup: budgeting, budget against actuals, driver-based plans, a 13-week cash roll-forward, and runway and burn from the books, all posting to or reading from real journal entries. Expenses and bills post to the same ledger so booked burn matches real burn, each payment in a pay run is checked before release, and stock-comp expense posts from the cap table. A company with several entities consolidates them into one P&L and balance sheet.

Explore SaaS finance
  • ASC 606 revenue & deferred-revenue waterfall
  • Budget, BvA, driver plans, 13-week cash & runway
  • Expenses & bills on the same ledger
  • ASC 718 expense posted; multi-entity consolidation

Trust

Every revenue schedule, equity grant, and dollar out: checked and recorded.

Fintra checks the places money leaks at a startup. A grant struck below the current 409A is refused before it is saved. A contract modification re-cuts revenue with a cumulative catch-up rather than a quiet edit, and every change to a contract or schedule is written to the revenue audit log. Each payment in a pay run is checked for a new vendor, a changed bank account and an unusual amount, and held or blocked before release, and a possible duplicate bill is held. An AI agent or an app asks the Control Tower before a sensitive financial action, and each decision is kept in a hash chain that can be recomputed.

See how actions are checked
  • A grant below the current 409A is refused
  • Contract changes caught up, not overwritten
  • Pay-run checks & possible duplicate bills held
  • Control Tower decisions in a recomputable hash chain

People

Engineers, GTM, contractors, and AI agents on one org chart.

Headcount is most of the burn, and hiring is the constraint on the plan. The budget costs headcount by month from salary, benefits and taxes, and Fintra HR puts every employee, contractor, and AI agent on one workforce graph with a trust score, with an ATS and AI interviewer, onboarding, merit cycles, and comp recommendations. The AI recruiter and interviewer stay advisory, and a named human always approves.

See people and HR
  • HRIS, ATS & AI interviewer
  • Equity offer scenarios before the offer goes out
  • Headcount cost by month in the plan
  • Comp recommendations; humans + AI agents trust-scored

Customer success

Customer health and at-risk accounts.

Support and success work from the same accounts and invoices as the books. A billing question is answered from the customer’s own open invoices, and a request is assigned to the person who owns the follow-up.

  • Billing answers from the customer's own open invoices
  • Requests assigned to an owner
  • Service policies and response times
  • Customer satisfaction kept with each case

One contract becomes a revenue schedule and a deferred-revenue waterfall.

The moat is one governed ledger from the signed order to recognized revenue. A contract allocates to its performance obligations, revenue recognizes on the right pattern, and deferred revenue rolls forward on a waterfall, every release a posted journal entry rather than a spreadsheet rebuilt every quarter.

Allocation & automatic recognition

Each contract allocates its transaction price across performance obligations at their standalone selling price, then recognizes ratably for a subscription, at a point in time for setup, at a milestone for services, and as consumed for usage. When an invoice for a rev-rec product posts, its schedule is created and the deferral posted automatically. On a $120K annual contract billed upfront, $10K recognizes each month and $110K remains deferred after the first month (illustrative), every entry traceable to the contract that justifies it.

Deferred-revenue waterfall

Deferred revenue rolls forward on a month-by-month waterfall that shows what releases when and the backlog still to recognize, drawn down as each obligation is satisfied. Billed against recognized shows the contract asset (unbilled) or the contract liability (deferred), so the balance an auditor asks about is the balance the ledger already proves.

Bookings, billings, revenue side by side

The revenue dashboards put booked (deals marked won), billed (posted invoices) and collected side by side by deal, rep and account, with revenue growth read from the general ledger, so sales, finance, and the board look at the same picture and each figure says where it came from.

Usage, retention & contract changes

Metered, usage-based lines recognize as usage is reported rather than as billed. Variable consideration (discounts, credits, expected refunds) and contract modifications change the transaction price with a cumulative catch-up on what was already recognized. Gross and net revenue retention come from billed revenue by customer.

Know the runway before the board asks.

Burn is the number that decides whether the plan survives, so FP&A is built on the same ledger as the actuals, not in a model that drifts the day it is created. Budgets, plans, the 13-week cash roll-forward, and runway all read real journal entries and open invoices and bills.

Budgeting & budget-vs-actuals

Build a budget once and watch budget against actuals update off the posted ledger, filtered by cost center, so an overspend surfaces in the month it happens, not at the quarterly review. Every variance drills down to the journal lines behind it, and a month with no actuals says so instead of showing a variance of minus 100%.

Driver-based plans

Plan revenue from drivers such as starting MRR, net new and churn, or price and volume; plan headcount cost by month from salary, benefits and taxes; and roll it into a three-statement plan whose balance sheet must balance every month, with cash derived from the cash flow. A plan can also start from a year’s posted actuals.

13-week cash flow & runway

A 13-week cash roll-forward projects collections from open invoices, shifted by each customer’s real payment history, and payments of open bills, week by week. Runway is cash on the books over net burn averaged across the last three complete months, and every screen that shows runway uses that one definition.

Scenario planning

Copy a plan with separate revenue and cost adjustments, compare scenarios side by side, and mark one as the official budget for the year, with a second approver if the company requires one. Every scenario runs against the real books, so the trade-off you present is grounded, not hand-waved.

The cap table that posts to the books.

Most startups run a cap-table tool that holds the shares and an accounting system that holds the ledger, and reconcile them by hand. Fintra keeps the cap table beside the ledger it posts to, so equity and accounting are one governed source of truth.

Cap table, pool & SAFEs

Founders, employees, investors, the option pool, and outstanding SAFEs and notes live in one table, with a fully diluted view as of any date and each grant’s vesting. A new grant drives its own ASC 718 expense, and an exercise is refused if it would take more shares than have vested or were granted.

ASC 718 stock-comp expense, posted

Stock-comp expense computes from each grant’s 409A-based fair value, its vesting schedule and forfeitures under ASC 718, and posts to the general ledger by cumulative catch-up: a late grant catches up in one period, a re-run posts nothing twice, and a forfeiture before vesting reverses. The monthly hand-journal disappears.

409A support, attached to grants

Support

A 409A valuation you obtain is recorded and prices the grants it covers, feeding the fair-value inputs to ASC 718, and a grant struck below the current 409A is refused before it is saved. Fintra accounts for and governs the valuation; it does not issue the 409A itself, and we say so plainly.

Dilution & round modeling

Model a priced round and a new option pool against the real fully diluted table and see the dilution before you sign the term sheet. The scenario runs on the same table that drives the stock-comp accounting, so the ownership math and the accounting agree.

Every tech client on one platform, each with its own books.

A firm or fractional CFO serving SaaS companies works each client on a different mix of QuickBooks, a billing tool and a cap-table tool. Fintra gives every client its own governed books, its own revenue schedules, and its own evidence trail, worked from one console instead of a folder of logins.

Per-client books, one login

Each client is its own entity with its own ledger, chart of accounts, and access, and the firm works across all of them from one console once each client accepts the firm’s request. A new client is set up from its name in one step, with a chart of accounts from its industry’s template and a draft engagement.

Standardized ASC 606 across the book

Every client on Fintra’s ASC 606 engine reads the same way: the same schedules and the same deferred-revenue waterfall, so a reviewer reads the twentieth client’s revenue the same way as the first. Consistency is built in, not enforced by a checklist and hope.

Evidence trail per client for review & audit

Every report the firm issues for a client is kept as a version with its hash, each figure in it can be traced to the records behind it, and a client report needs a manager’s and a partner’s approval from two different people. The firm proves its work as a by-product of doing it.

Multi-entity roll-up

A client with several entities consolidates into one P&L and balance sheet, with elimination rules, adjustments, subsidiaries fed by trial-balance imports, and an ASC 830 currency policy with period-end revaluation. Across the firm’s clients, the practice command center rolls up WIP, realization and the state of every close.

SOC 2 readiness that closes the enterprise deal.

The security questionnaire that stalls your first enterprise contract becomes evidence you can hand a prospect, an auditor, or a customer’s security team, not a binder you assemble by hand the week the deal is due.

SOC 2, GDPR & ISO 27001

SOC 2, GDPR, and a starter set of ISO 27001 Annex A controls are control packs in Fintra Trust, each control with its policies and evidence, and tests where a control can be tested automatically. This is evidence mapped to the framework, not a certificate.

Controls, evidence & audits

Each control carries its policies and its evidence, with test results where the control can be tested automatically, and an auditor reviews them through access that expires. A formal SOC 2 attestation is issued by an independent auditor, never by Fintra; Fintra hands that auditor the evidence instead of a scramble.

Governed actions

An AI agent or an app asks the Control Tower before it moves money or changes a financial record, and gets allow, deny or review, with the reasons and the approvers the action needs. Each payment in a pay run is checked before release, and a held or blocked payment drops out of the run with its reason.

Recomputable evidence

Each Control Tower decision is kept in a hash chain, and a verify call recomputes the chain and names any entry that was altered. A separate check goes back to the source records after the action to confirm what actually happened. The decision rules are deterministic and explainable, never a black box.

Build the team without blowing the runway.

Headcount is the burn. Fintra HR runs the HRIS, the ATS with an AI interviewer, onboarding, merit cycles, and comp recommendations; the budget costs headcount by month; and the cap table and its ASC 718 expense sit beside them.

HRIS and headcount in the plan

The people record, comp, and org chart live in Fintra HR, PTO and bonus accruals post from it to the general ledger, and the budget plans each role’s salary, benefits and taxes by month, so the hiring plan and the cash plan sit in one model rather than a tab nobody updates.

ATS + AI interviewer

The applicant tracking system and an AI interviewer speed up filling engineering and GTM roles, screening and structuring candidate signal for the hiring team. The AI stays advisory and a named human always makes the call, so automation supports the decision, never replaces it.

Offer, onboarding & equity

Equity offer scenarios are modeled before an offer goes out, anchored to the company’s own grant history or a midpoint you give. When an offer is accepted, the employee record and the onboarding packet are created from it, and the option grant, once entered, is checked against the current 409A and drives its own ASC 718 expense.

Comp recommendations & merit cycles

A comp recommendation reads the salary, rating, band and market figures you enter for a person and flags pay below the market’s 25th percentile, a strong performer whose suggested pay still trails the market, or a suggestion above the band, for a person to review. Fintra runs no pay-gap analysis, because People records hold no gender or ethnicity data. Merit cycles move from proposals to approval to a finalized cycle, and an offer or pay change above a set amount waits for an approver.

Full-population controls for technology and SaaS companies.

Each run of a control tests the whole population, not a sample; only the items that fail open an exception; each exception carries a sealed record of what was checked; the record is mapped to the SOX 404 control it tests; the record can be recomputed to show it was not changed.

ControlHow it is checkedFrameworkStatus
Revenue recognition cutoffTested each time the control runs, by the revenue-cutoff test: each scheduled revenue row is recognized inside its own period, never pulled forward.SOX-CA-05 · Period cutoffAutomated test
Segregation of dutiesTested each time the control runs, by the preparer-and-approver test: the person who created a payment is never the person who approved it.SOX-CE-03 · SoDAutomated test
Bank-to-ledger reconciliationTested each time the control runs, by the bank-to-ledger test: every bank transaction is matched to a posted journal line by period close.SOX-CA-06 · Bank recAutomated test

The controls marked automated test run against your company's own transactions each time they run. It works beside your GRC tool and your external audit, not instead of them.

How full-population testing works

Fintra for technology today

The SaaS core runs on Fintra: ASC 606 revenue recognition with allocation by standalone selling price, schedules created from posted invoices, usage recognized as it is reported, a deferred-revenue waterfall and contract changes caught up cumulatively; the cap table with 409A valuations and ASC 718 expense posted to the ledger; and FP&A with budgets, budget against actuals, driver-based plans, a 13-week cash roll-forward and runway from trailing net burn. Fintra connects to QuickBooks Online; the cap table, grants and 409A valuations are entered in Fintra. It does not read Stripe billing data, and it does not compute MRR or ARR from your contracts: a budget models subscription revenue from starting MRR, net new and churn, and the revenue dashboards put booked, billed and collected side by side, with gross and net revenue retention from billed revenue. 409A support means Fintra records and accounts for a valuation you obtain; it does not issue one. Fintra does not issue cards or lend money. Fintra Trust holds SOC 2, GDPR and a starter set of ISO 27001 Annex A controls with their policies and evidence; that is evidence, not a certificate, and a formal SOC 2 attestation is issued by an independent auditor, never by Fintra. Fintra Payroll is coming soon.

Pages by role

One set of books runs the whole back office. These pages start from the job you do.

See Fintra recognize your revenue and run your runway.

Bring your QuickBooks history, your cap table, or a set of contracts. We’ll show ASC 606 revenue, the deferred-revenue waterfall, the cap table with ASC 718 stock comp, runway and burn, SOC 2 controls in Fintra Trust, and the evidence trail on your numbers.

Book a demoLog in