California’s new SB 122 makes most SaaS and digital prewritten software subject to California sales and use tax starting January 1, 2027. That’s a big deal for both software vendors and venture-funded startups that sell into or buy from customers in California.

For startups based in California, this means your software stack is likely to get more expensive. For startups based in other states that sell software in California, your billing and tax processes may need changes to keep up with the new rules.

Below is an overview of what SB 122 does, why it matters to startups, and how Kruze can help you get ahead of it.

What SB 122 Actually Does

SB 122 is part of California’s 2026-27 budget package and was signed into law on June 29, 2026. The law expands California’s sales and use tax base to include certain “digital products,” specifically prewritten computer software, starting January 1, 2027.

In practical terms, California now treats software‑as‑a‑service (SaaS) and other cloud-delivered prewritten software as taxable “tangible personal property,” whether it’s delivered on a physical medium, downloaded, or accessed remotely via the cloud. This is California’s first move to tax SaaS and other cloud‑delivered prewritten software at the statewide base rate plus any applicable local district rates.

What Counts as “Digital Prewritten Software”

Effective January 1, 2027, SB 122 defines a “digital product” as prewritten computer software transferred on tangible storage media, transferred electronically, or accessed remotely. “Prewritten” (or “canned”) software generally means software held or existing for general or repeated sale or lease, including software initially developed on a custom basis if later offered for repeated sale. As a result, many SaaS platforms will be taxable when they provide remote access to prewritten software, subject to the statute’s exclusions.

By contrast, custom software built specifically for a particular client is generally excluded from the tax base under the new framework. The law also focuses on transfers of rights to access, download, copy, update, store, or otherwise use prewritten software, regardless of the technical delivery method.

Effective Date and Tax Rates

The sales and use tax provisions of SB 122 apply to transactions occurring on or after January 1, 2027. California’s statewide sales and use tax rate is 7.25%, and SB 122 applies that base rate plus any applicable local district taxes to taxable digital prewritten software.

Because local district taxes stack on top of the state rate, the effective tax rate on software purchases can exceed 10% in some jurisdictions. Vendors and buyers will also need to consider existing nexus rules, which are the obligation to collect and remit taxes generally when sellers meet California’s economic or physical presence thresholds.

Companies that establish nexus in California under SB 122 or existing economic and physical presence standards may also have a California tax filing obligation. In addition to collecting and remitting sales tax, this can include registering with the state and filing appropriate California tax returns, depending on the nature and extent of their in-state activity.

How This Hits Venture‑Backed Startups As Software Buyers

If your startup is headquartered in California or has significant operations in the state, your existing SaaS stack is likely to become more expensive after January 1, 2027, due to the newly applied sales tax. That includes software like customer relationship management (CRM), applicant tracking systems (ATS), human resources information systems (HRIS), developer tools, analytics, and finance apps.

Vendors with a California sales tax obligation will generally be required to charge, collect, and remit tax on your startup’s subscriptions if they meet the nexus thresholds.

This change doesn’t mean you suddenly owe back taxes on prior‑year SaaS purchases, but it does mean your forward‑looking budget and burn projections should assume higher gross costs for taxable software. For many venture‑funded startups, software is a major line item, so even a mid‑single‑digit to low‑double‑digit effective tax rate can materially affect runway and cash‑flow planning.

How This Hits Startups That Are Software Vendors

If you sell prewritten software or SaaS to customers in California, SB 122 is effectively pulling you into the sales tax world for those transactions starting in 2027. The law amends definitions of “sale” and “purchase” to cover permanent or temporary transfers of rights to access or use prewritten software, including cloud‑based offerings.

For startups, this means you may need to register for California sales tax (Kruze can help you with this), update invoicing systems to add sales tax on California‑sourced transactions, and build processes to collect exemption certificates where applicable. It also increases the importance of classifying your offerings correctly – for example, distinguishing taxable prewritten software from potentially non‑taxable professional services, implementation, or custom development.

It’s also important to note that triggering nexus in California doesn’t just create a sales tax obligation. Depending on your footprint, it may also require your company to file California state tax returns, such as income or franchise tax filings, even if you are headquartered outside the state.

Custom vs. SaaS and Bundled Offerings

SB 122 and related guidance draw a line between prewritten software and custom software, with custom software generally remaining outside the expanded sales and use tax base. However, many startup offerings are bundles: A subscription to a core SaaS platform plus onboarding, consulting, and custom integrations.

How those bundles are structured and invoiced can influence the amount of tax owed! Separately stated, non‑software services may be treated differently from core prewritten software components.

Startups will need to review their contracts and billing practices to avoid accidentally subjecting non‑taxable services to tax simply because they are bundled into a single charge.

Why California Is Doing This

SB 122 is part of a broader effort to stabilize California’s revenue base and align its tax treatment of digital products with how many other jurisdictions already treat software and SaaS. For years, California taxed prewritten software delivered on tangible media. However, the state did not clearly tax software delivered electronically or via the cloud, which created both revenue loss and competitive differences compared to other states.

By redefining digital products as taxable tangible personal property, California closes that gap and broadens its tax base to a rapidly growing portion of the economy. The legislation also pairs the expansion with other revenue‑related provisions, such as extending limits on certain business tax credits and making adjustments to minimum taxes for some entities.

What Other States Tax SaaS?

California’s move to tax SaaS puts additional pressure on other states to update their rules on digital products and SaaS, especially as more of the economy shifts to subscription-based software. You can expect more states to consider this type of legislation or regulatory changes.

Here’s a quick overview:

• Big states that tax SaaS: New York, Texas, Pennsylvania, Massachusetts, Washington, Ohio, South Dakota, Tennessee, and California starting in 2027. We’ve got a comprehensive guide for SaaS taxability you can review for more details.
• Florida, Georgia, and several other states still tend to be more SaaS-friendly, but this could change over time.
• Some home-rule cities, like Denver, can tax SaaS locally even if the state rules are more favorable.

In general, if your startup sells or buys SaaS across multiple states, you should expect the rules to continue to tighten. Because definitions, rates, and guidance change frequently, treat this as a high‑level snapshot, and contact us for specific information.

Planning Tips for Startup Software Buyers

For founders and finance leaders, SB 122 is a good excuse to revisit your software stack and budget before 2027 hits. Consider building a simple inventory of your major SaaS and software vendors, and flag which software is likely to be subject to California sales tax based on your nexus and billing footprint.

Then, model the impact of a 7.25%-10%+ tax on those recurring costs to understand how your burn and runway change under the new rules. This is also a natural time to negotiate contracts, re‑tier licenses, or consolidate tools so that you’re not paying tax on redundant or underused software.

Planning Tips for Startup Software Vendors

If you’re a SaaS or software startup selling into California, you’ll want to work with your tax advisor well before January 1, 2027, to get your compliance house in order. This typically includes confirming whether you have nexus in California, registering for sales and use tax if required, and configuring your billing systems to apply the correct rates based on customer location.

As part of this process, confirm whether your nexus exposure also creates a broader California tax filing requirement. Many startups focus on sales tax compliance first, but California may expect qualifying businesses to file state tax returns once nexus is established.

Documentation will matter: Clearly describing what you sell (prewritten software vs. custom dev vs. services) and how you price it can support your tax treatment if California ever asks questions. You may also want to update your customer communications to explain that sales tax is being added due to a law change rather than a pure price increase.

How Kruze Can Help

SB 122 touches both sides of the startup world: Founders buying software to run their companies and founders selling software to fund their companies. Because the law doesn’t kick in until January 1, 2027, there is still time to get your systems, chart of accounts, and budgeting processes aligned with the new rules.

At Kruze, we’re already tracking how California and other states are approaching digital products so that our venture‑backed clients can stay compliant without drowning in sales tax complexity. If you want help modeling the impact of SB 122 on your runway, or building a workable sales tax strategy for your SaaS startup, we’re happy to help.

SB 122 FAQ for Startups

• When does SB 122 start applying to SaaS and digital software?
• If I had $10,000 in California SaaS sales, how much should I collect in California SaaS Sales Tax?
• Does my startup have to eat this new tax/cost?
• What should I tell my clients?
• Does SB 122 tax all digital products?
• I run a SaaS startup outside California. Do I still need to worry about this?
• Will my startup owe back taxes on prior SaaS purchases because of SB 122?
• How should I classify my product if it’s part software, part services?

When does SB 122 start applying to SaaS and digital software?

SB 122’s expansion of sales and use tax to digital prewritten software, including SaaS, applies to transactions on or after January 1, 2027.

If I had $10,000 in California SaaS sales, how much should I collect in California SaaS Sales Tax?

Approximately $800.

Does my startup have to eat this new tax/cost?

No, not necessarily. However, if you’re a startup selling SaaS to California clients, you should notify your client base NOW that you will be charging CA Sales Tax starting Jan. 1, 2027. You should also amend your sales contracts to include a disclaimer that SaaS Tax might be applicable in CA, starting Jan. 1, 2027.

What should I tell my clients?

Send them a notification email NOW. Explain that a new state law (SB 122) will require sales taxes on many software subscriptions beginning Jan. 1, 2027, and they’ll see a new tax line item on their invoices once the rules take effect.

Does SB 122 tax all digital products?

No. SB 122 focuses on prewritten computer software, including software delivered on physical media, downloaded, or accessed remotely, and does not automatically tax every digital good. Many purely digital content products and certain custom software arrangements may fall outside the scope, depending on how they are structured.

I run a SaaS startup outside California. Do I still need to worry about this?

Potentially, yes. If you sell prewritten software or SaaS to customers in California and meet the state’s economic or physical nexus thresholds, you may be required to collect and remit California sales tax under SB 122. Location of your HQ alone doesn’t shield you if your sales into California cross those thresholds.

Will my startup owe back taxes on prior SaaS purchases because of SB 122?

Current guidance and commentary indicate that SB 122 applies to transactions occurring on or after January 1, 2027, rather than retroactively taxing prior SaaS purchases. That said, it’s still important to monitor any future administrative guidance for nuances in implementation, and we’ll post any updates when new guidance is issued.

How should I classify my product if it’s part software, part services?

Under SB 122, prewritten software components are generally taxable, while certain custom development and professional services may not be. Because classification can be fact‑specific and heavily influenced by contracts and invoicing, most startups will want to work with a tax advisor to structure offerings and documentation appropriately.

How much do startup CEOs, CTOs, and COOs actually make in 2026?

Startup CEOs, CTOs, and COOs all earn roughly $165,000 to $167,000 in average cash salary in 2026, based on real, anonymized payroll data from hundreds of venture-backed companies. The more useful finding sits underneath that average: no single role is the highest paid at every stage. CTOs lead at Seed, and COOs out-earn everyone by Series A and Series B. The common assumption that the CEO always tops the pay scale does not survive contact with the data.

Kruze Consulting pulls these benchmarks straight from client payroll systems, not surveys or recruiter estimates. That distinction matters more than it sounds. Survey data lags reality and over-represents the best-funded outliers, which is exactly the wrong bias when you are trying to set responsible cash comp in a capital-efficient market.

Key findings:

• Average cash pay converges tightly. CEOs, CTOs, and COOs each land near $165,000 to $167,000 overall.
• The highest-paid role changes by stage. CTOs lead at Seed ($155,000). COOs lead at Series A ($227,000) and Series B ($246,000).
• Medians sit below averages for all three roles, so a small group of late-stage, well-funded executives pulls each average up.
• CTO pay is the most consistent benchmark, with average and median under $1,000 apart.
• COO pay is the most stage-dependent: Lowest at Seed, fastest-rising, highest by growth stage.

For a deeper analysis focused specifically on founder pay, see our Startup CEO Salary Report, which includes historical trends, year-over-year data, and benchmarking tools. This guide expands that lens to cover the rest of the C-suite.

Where this data comes from (and why it beats salary surveys)

This dataset comes directly from the payroll systems of Kruze’s VC-backed startup clients, US-based companies that have collectively raised billions from leading venture funds. It is actual payroll, not self-reported survey responses, and all client data is fully anonymized and aggregated before analysis, so no companies or individuals can be identified.

That difference is the whole point. Most published startup salary data is built from surveys, which carry two problems. They lag the market, often by a year or more, and they skew toward the companies most willing to respond, which tend to be the best-funded.

In a market defined by runway preservation and milestone-driven pay, both biases push reported numbers higher than what most founders should actually budget. Real payroll records show how venture-backed startups are responding to the current climate, not how they responded two boom years ago.

That climate still reflects the post-correction era of venture funding. After the 2022 to 2023 reset in valuations and deal volume, startups recalibrated executive pay to balance market competitiveness against investor expectations for efficient growth. With late-stage IPO and M&A windows still choppy, companies lean less on high salaries and more on structured equity and variable comp to attract and retain C-suite talent.

The C-suite at a glance: Average salary by role and stage

Two things stand out. First, average pay across all three roles converges to nearly the same overall figure, right around $165,000 to $167,000. Second, the stage ranking is not a simple “later stage pays more for everyone.” COOs at Series A out-earn both CEOs and CTOs, and CTOs pull ahead at Series B.

This tight band is not an accident. It reflects how disciplined cash compensation has become since the reset. Seed and Series A rounds today are smaller and more milestone-driven than they were in 2021, which anchors early-stage cash pay in a narrow range.

By Series B, companies with proven product-market fit and efficient growth raise larger rounds, and that shows up as higher CTO and COO averages when boards fund the leadership needed to scale.

Average vs. median: A quick reality check

Averages get skewed by a handful of high earners at well-funded, later-stage companies. Medians correct for that. Across all three roles, the overall median sits below the overall average, which confirms that a smaller group of higher-paid executives is pulling each average upward.

The CTO’s average and median are the closest of the three, under $900 apart. That tight spread makes CTO pay the most reliable single benchmark to hire against. COO pay shows the widest gap, which means a small group of highly paid, later-stage COOs is lifting that average.

Those outliers usually sit at companies that raised unusually large rounds or are preparing for a liquidity event. When pre-IPO financing is available, boards sometimes boost COO and CEO cash comp to pull seasoned operators out of mature companies. In today’s more selective late-stage market, those outsized packages are rarer, which keeps medians grounded even as a few high earners raise the averages.

How much do startup CEOs make?

CEO pay is the most closely watched benchmark, because it sets the tone for the rest of the leadership team and feeds directly into burn and runway. The average startup CEO salary has climbed to $165,000 in the latest data, up from $161,000 the prior year, continuing a rebound that started after two years of fundraising pressure and valuation resets.

The median tells a slightly different story. At $159,000, it sits just below the average, which means most CEO salaries cluster in a fairly tight range while a group of higher-paid CEOs pulls the average up. Those higher earners tend to run companies that raised larger Series B or later rounds, often in capital-intensive sectors like AI infrastructure, climate and energy, or deep tech, where investors expect experienced leadership and fund higher cash comp alongside significant equity.

For the full breakdown of CEO pay trends over time, average-vs-median analysis, founder self-check tools, and board review templates, see the complete Startup CEO Salary Report.

How much do startup CTOs make?

CTOs have historically out-earned CEOs at the earliest stages, because technical talent is scarce and startups compete with Big Tech pay to land strong engineering leaders. The data confirms it. CTOs remain one of the highest-paid roles in the early-stage C-suite, with an overall average of $167,000 and a median of $166,000, the tightest average-to-median gap of any role Kruze tracks.

That floor has held even through repeated Big Tech layoff cycles. More engineers are on the market, but top-tier technical leaders who have scaled teams and shipped complex products stay scarce. The surge in AI and data-heavy startups has only raised demand for senior technical leadership, which keeps CTO cash comp firm even in a cautious funding environment.

CTO pay rises steadily at each milestone, reflecting both the growing complexity of engineering organizations and the deeper capital and de-risked models of later-stage companies. The near-identical average and median mean there is no small cluster of extreme outliers distorting the picture. It is a genuinely consistent benchmark to hire against.

How much do startup COOs make?

COO pay follows a distinct pattern: lower at Seed, but rising the fastest and landing the highest by Series A and Series B. At the growth stage, COOs post the highest average pay of the three roles.

The overall median COO salary is $150,000, well below the $167,000 average and a wider gap than either the CEO or CTO roles show. That points to a cluster of COOs paid at or below the median, with a smaller group of highly paid, later-stage COOs pulling the average up sharply.

Why do COOs out-earn CEOs after Seed?

At Seed, many startups do not have a dedicated COO at all. The role gets folded into the CEO’s responsibilities or handled part-time by an early operations hire, which keeps Seed-stage COO pay the lowest of the three roles.

That changes fast at Series A and B. Operational complexity across team, process, and go-to-market execution rises sharply, and boards pay a premium for an experienced operator who can run the day-to-day while the CEO focuses on strategy and fundraising. That premium is why COO comp overtakes both CEO and CTO pay by Series A and stays highest through Series B.

What this means for founders and boards

The clearest takeaway is that no single role is universally the highest paid across every stage. At Seed, CTOs command the top average, reflecting the scarcity of technical talent willing to join an unproven company. By Series A and B, COOs move to the top as boards pay up for operators who can scale the business.

For founders building a leadership team, that means compensation planning should be stage-specific and role-specific, not a flat rule applied across the org. For boards and investors reviewing burn and runway, benchmarking each hire against the right stage-specific range, and checking both average and median, gives a far more accurate read on whether a package is in line with the market.

If you’re building a budget, Kruze can help

This data reflects real, anonymized payroll information from Kruze’s client base of VC-backed startups. If you need help thinking through your own executive compensation plan, building a hiring budget, or modeling how new leadership hires affect your runway, contact Kruze Consulting. Our team of experienced startup accountants can help you build a financial model that reflects the true cost of hiring a leadership team.

California’s new law taxing SaaS (SB 122) is part of a much bigger trend: More and more states are steadily expanding sales tax rules to cover SaaS, cloud software, and other forms of digital prewritten software.

For startups, that means California is no longer an outlier to watch from a distance – it’s joining a long and growing list of states that already tax software delivered electronically or accessed remotely.

Why this matters

SB 122 applies California sales and use tax to digital prewritten software, including SaaS, beginning January 1, 2027. That change brings California closer to the approach already used in many other jurisdictions, where cloud software is taxable even if the customer never downloads or physically receives the product.

For founders, the practical takeaway is simple: If a startup buys SaaS in multiple states or sells SaaS across state lines, California is now part of a broader multi-state compliance tapestry rather than a one-off rule change.

Quick overview for founders

If you’re a startup founder or CFO just trying to understand the big picture, here’s the TL;DR on SaaS sales tax in the U.S. and where California’s SB 122 fits in. The details vary by state, but the pattern is clear enough to inform your planning:

• Many states already tax SaaS or remotely accessed prewritten software in some form, and California joins that group in 2027 under SB 122.
• Big startup-market states where SaaS is commonly taxed include New York, Texas, Massachusetts, Pennsylvania, Washington, and now California.
• Some states use partial or nuanced rules, such as Colorado local jurisdictions and Connecticut’s reduced rate for certain business use cases.
• Some states still do not tax SaaS at the state level, but that list has been shrinking as lawmakers modernize tax codes around digital products.
• The broader direction is clear: States are moving toward taxing software based on what it does, not how it is delivered.

How do other states tax SaaS and cloud software?

While every state uses its own definitions, many jurisdictions already have rules that look broadly similar to SB 122 because they tax SaaS, electronically delivered prewritten software, or cloud-accessed software.

Generally taxable states

These states are widely cited in current SaaS taxability guides as taxing SaaS or remotely accessed prewritten software in some form:

• Alabama.
• Arizona.
• Connecticut.
• District of Columbia.
• Hawaii, through its general excise tax structure.
• Kentucky.
• Louisiana.
• Maryland, in at least some digital or SaaS contexts.
• Massachusetts.
• Nebraska, often with product-specific treatment.
• New Mexico.
• New York.
• Ohio, particularly in business-use contexts.
• Pennsylvania.
• Rhode Island.
• South Carolina.
• South Dakota.
• Tennessee.
• Texas, often under data-processing rules with partial exclusions.
• Utah.
• Vermont.
• Washington.
• West Virginia.

Partial or nuanced states

Some states do not fit neatly into a yes-or-no box because SaaS can be taxable only in certain situations, at reduced rates, or at the local level.

• Alaska, which has no statewide sales tax, but many local jurisdictions tax SaaS and other digital services.
• Colorado, where some home-rule cities can tax SaaS or digital products even when the statewide treatment is more favorable.
• Connecticut, where SaaS for business use may be taxed at a reduced rate rather than the full rate.
• Iowa, where personal-use SaaS is commonly taxed and business-use treatment can differ.
• Illinois, where statewide treatment may be more favorable but local taxes can still apply in some jurisdictions.
• Nebraska, where treatment can depend on the type of software product being sold.

States that do not fully tax SaaS

Several states are still commonly described as more SaaS-friendly because they do not broadly tax SaaS at the state level, although local rules, digital product rules, or future law changes can complicate that picture.

• Arkansas.
• Delaware.
• Florida.
• Georgia.
• Idaho.
• Indiana.
• Kansas, though treatment should be checked carefully because guidance evolves.
• Maine.
• Michigan.
• Minnesota.
• Mississippi.
• Missouri.
• Montana.
• Nevada.
• New Hampshire.
• New Jersey.
• North Carolina.
• North Dakota.
• Oklahoma.
• Oregon.
• Virginia.
• Wisconsin.
• Wyoming.

States considering similar legislation

Identifying states that are considering bills like SB 122 can be difficult, because most states revisit SaaS taxation through a mix of legislation, budget bills, digital product definitions, and tax department guidance.

Even so, there is a clear trend. Many states are periodically evaluating whether to explicitly include cloud software, remotely accessed software, or digital products in their sales tax base:

• States with older software tax rules are increasingly revisiting whether those rules should also cover cloud-delivered products.
• Some states are updating “digital product” definitions rather than passing a SaaS-specific law.
• Others are expanding taxability through administrative guidance instead of headline legislation.
• California’s enactment of SB 122 is likely to add momentum for similar proposals elsewhere, especially in states already taxing some digital goods but not clearly taxing SaaS.

What founders should do next

If you’re looking at this list of SaaS‑taxing states and thinking, “We do business in half of these,” you’re not alone – and you shouldn’t try to untangle it on your own.

Kruze Consulting works with hundreds of venture‑backed startups that sell and buy SaaS across multiple states, so we’re already helping founders map where their software is taxable, how SB 122 fits into that picture, and what it means for runway and compliance. Whether you’re a heavy SaaS buyer, a SaaS vendor, or both, we can:

• Analyze your multi‑state SaaS tax exposure.
• Help you set up billing and revenue ops that handle California and other SaaS‑tax states correctly.
• Model the impact of new sales tax rules on your burn and cash runway so there aren’t any surprises at board meetings.

If you want to make sure your SaaS business is ready for California and the other states on this list, contact Kruze – we handle tax and compliance work so you don’t have to.

Common equity accounting issues for startups include mismatches between the cap table and the general ledger, misclassified SAFEs and convertible notes, and incorrect stock‑based compensation expense. These problems are exactly what auditors flag first, and fixing them before audit fieldwork is how VC‑backed founders keep their startup accounting clean, avoid delays, and get through the audit without painful surprises.

Audit fieldwork is the phase of the audit when auditors come onsite (or into your systems), test your transactions, and review documentation to evaluate whether your financial statements are accurate. For startups, this is when any equity accounting issues around SAFEs, convertible notes, stock options, and cap table reconciliations will surface, so cleaning them up in advance makes the entire audit smoother.

Why equity accounting is a hotspot in startup audits

Equity is where your company’s story, legal agreements, and numbers converge – and it’s also where mistakes compound fastest.

Auditors focus on equity accounting because:

• Funding and ownership are central to valuation and investor trust.
• Complex instruments, like SAFEs, convertibles, preferred stock, options, and restricted stock units (RSUs), are easy to misclassify.
• Errors here can ripple through your balance sheet, profit & loss statement (P&L) via stock comp, and disclosures.

If your legal team, finance team, and cap table tool aren’t perfectly aligned, auditors will find inconsistencies, and those can delay the audit or trigger restatements.

Issue 1: Cap table vs. general ledger mismatches

One of the most frequent equity accounting issues is simple mismatch: The number and type of shares in your cap table don’t line up with what’s in your general ledger (GL) and financial statements.

Typical problems:

• New rounds recorded in legal docs and the cap table but not properly booked in the GL.
• Option exercises, cancellations, or RSU vesting reflected in the cap table but missing or incorrectly coded in accounting.
• Par value and additional paid‑in capital (APIC) not reconciled to actual share issuances.

Steps to fix before the audit:

• Reconcile every equity event (round closings, option grants/exercises, RSU vesting) from legal docs to the cap table and then to the GL.
• Make sure share counts, classes, and par values tie out across all systems.
• Prepare a rollforward schedule showing opening equity, changes during the year, and ending balances.

Auditors want to see that your equity accounting accurately reflects your true ownership structure.

Issue 2: Misclassification of SAFEs and convertible notes

SAFEs and convertible notes are standard in startups, but they’re often booked incorrectly.

Common missteps:

• Recording SAFEs as revenue or generic “liability” without considering whether they should be treated as equity‑like instruments.
• Treating all convertible notes as simple debt without evaluating embedded conversion features and their impact.
• Ignoring modifications (extensions, rate changes, cap changes) in accounting treatment.

Before fieldwork:

• Inventory all SAFEs and convertible notes, including terms (cap, discount, interest, maturity, conversion triggers).
• Confirm accounting treatment is consistent with your framework (e.g., US GAAP) and your auditors’ expectations.
• Make sure disclosures clearly describe the instruments and their potential impact on equity.

Getting SAFEs and notes right is a core part of accurate startup accounting for audits.

Issue 3: Stock‑based compensation (options and RSUs) not accounted for correctly

Auditors spend a lot of time onstock‑based compensation because it affects both your P&L and equity.

Common issues:

• Option and RSU grants booked inconsistently, or not at all.
• Expense recognition based on incorrect fair value or vesting schedules.
• Modifications (repricing, changing vesting, extending terms) not reflected in updated expense calculations.
• Poor documentation of 409A valuations and assumptions.

Pre‑audit fixes:

• Make sure you have a complete list of grants, including grant dates, vesting, and any modifications.
• Tie stock‑based compensation expense to underlying grants and 409A valuations.
• Prepare reconciliation schedules showing how you calculated the expense and how it flows into the GL.

This is one of the most technical parts of equity accounting, and auditors will expect detailed support.

Issue 4: Incomplete or inconsistent disclosures

Even if the numbers are right, equity can still cause issues if disclosures are thin or inconsistent.

Auditors commonly flag:

• Missing or unclear descriptions of equity classes and rights (liquidation preferences, dividends, conversion rights).
• No clear explanation of option plans, share‑based payment arrangements, and key terms.
• Lack of disclosure around significant events (new rounds, large grants, changes to plans).

To clean up:

• Draft clear narrative disclosures that match your legal documents and cap table.
• Make sure all significant equity events during the year are documented and explained.
• Align terminology across your financial statements, notes, and board materials.

Well‑written disclosures make it easier for auditors to trust your startup accounting and equity story.

Issue 5: Equity rollforwards and retained earnings not tying out

Auditors will test your “movement” schedules – how equity and retained earnings change over time.

Common problems:

• Beginning balances that don’t match prior‑year audited numbers.
• Missing entries for share issuances, option exercises, and equity‑settled transactions.
• Retained earnings not reflecting cumulative P&L, dividends, and other changes.

Pre‑audit steps:

• Build year‑over‑year rollforward schedules for each equity account (common, preferred, APIC, treasury stock, retained earnings).
• Tie beginning balances to prior‑year audited financials.
• Reconcile all changes to supporting documentation (board minutes, stock plan reports, legal agreements).

These schedules give auditors confidence that your equity accounting is complete and internally consistent.

How to prepare your startup for an equity‑focused audit

To reduce equity issues before audit fieldwork:

1. Centralize equity data
   • Make sure legal docs, cap table, and accounting system share a single source of truth.
   • Limit manual “side spreadsheets” that can drift out of sync.
2. Run a pre‑audit equity review
   • Work through each known equity issue with your internal finance team or external startup accounting specialists.
   • Fix misclassifications and reconciliation issues proactively.
3. Document everything
   • Keep organized folders for equity: cap table exports, grant agreements, option plan documents, 409A reports, board minutes approving changes.
   • Link each GL entry to its underlying support.
4. Talk to your auditors early
   • Ask what they typically focus on for companies at your stage.
   • Confirm expectations for SAFEs, converts, stock compensation, and disclosures.

Good equity accounting turns the audit into a validation of your processes, not a discovery of hidden problems. Get ahead of your next audit by fixing equity issues now. Contact Kruze Consulting to review your cap table, SAFEs, and stock‑based compensation so your startup accounting is audit‑ready and investor‑friendly.

Equity Accounting Issues for Startups

• Why do auditors focus so much on equity accounting for startups?
• How can I make sure my cap table matches my accounting records?
• What are the biggest equity accounting problems with SAFEs and convertible notes?
• How do auditors test stock‑based compensation expense?
• What should I do before fieldwork to reduce equity‑related audit issues?

Why do auditors focus so much on equity accounting for startups?

Equity reflects ownership, funding, and compensation, and mistakes here can distort the balance sheet, P&L, and disclosures. Complex instruments like SAFEs, convertibles, and stock options make equity a high‑risk area that auditors have to scrutinize carefully.

How can I make sure my cap table matches my accounting records?

Reconcile each equity event from legal documents to the cap table and then to GL entries. Build rollforward schedules for share counts and equity accounts, and confirm that beginning and ending balances tie to prior‑year statements and current cap table data.

What are the biggest equity accounting problems with SAFEs and convertible notes?

Common issues include misclassifying SAFEs as revenue, treating convertible notes as simple debt without considering conversion features, and failing to update accounting when terms change. Each instrument needs clear documentation and consistent treatment in your startup accounting.

How do auditors test stock‑based compensation expense?

They review your option and RSU grant data, 409A valuations, vesting schedules, and any modifications, then check that expense recognition follows the applicable accounting rules. They’ll expect reconciliation between the detailed grant data and the expense recorded in your GL.

What should I do before fieldwork to reduce equity‑related audit issues?

Run an internal equity review: reconcile the cap table and GL, clean up stock comp accounting, prepare detailed schedules (AR/AP, equity rollforwards), and draft clear disclosures. Address known issues with your finance and legal teams ahead of fieldwork so auditors encounter a stable, well‑supported equity picture.

August sits in the middle of Q3 and does not bring major corporate income tax filing dates for calendar‑year C‑corps, but it still includes recurring payroll, sales, and state compliance obligations that matter for growing startups. Founders can use August to stay ahead on employment and transactional taxes, and to keep their compliance up to date heading into the September estimated tax deadline.

Federal: August in the 2026 tax calendar

For most venture‑backed C‑corps, there is no standard federal corporate income tax payment due in August. The third federal estimated corporate income tax installment, covering income earned from June through August, is due on September 15, 2026.

That said, founders should keep an eye on:

• Monthlypayroll tax deposits for income tax withholding, Social Security, and Medicare (FICA), which are typically due by the 15th of the following month.
• Routine information and employment reporting that falls throughout Q3, even though the formal “quarterly” federal payroll return (Form 941) is not filed until after Q3 ends.

For startups that are ramping headcount, August is a good time to confirm that payroll systems are correctly handling federal deposits and that those liabilities reconcile to the general ledger.

State-level August obligations: Payroll, sales, and transactional taxes

At the state level, August is mostly a “steady state” month for:

• State payroll and unemployment tax deposits for July wages.
• State sales and use tax filings for monthly filers covering July activity.
• Industry-specific transactional taxes for businesses with monthly reporting cycles.

For example, many states require monthly sales or use tax returns by the 20th or 23rd of the following month, which puts July sales/use activity on an August due date for monthly filers. Quarterly filers, by contrast, will have filed their Q2 returns in July, so August is mainly about staying current on monthly obligations.

Early‑stage startups that rely on payroll providers and sales tax automation often see these filings handled behind the scenes, but founders should still confirm that July and August state deposits match their expectations and that notices are monitored.

City-specific deadlines in August

Across major startup hubs like Austin, Boston, New York City, Palo Alto, San Francisco, Santa Monica, Seattle, Washington DC, Atlanta, Salt Lake City, Mountain View, Chicago, Dallas, Miami, San Jose, Boulder/Denver, and San Diego, there is generally no single, widely‑applicable city corporate income or franchise tax deadline that hits in August for all startups.

Instead, August compliance for these cities is driven by:

• Federal monthly payroll deposits.
• State monthly payroll/unemployment and sales/use tax filings.
• Ongoing local business license or tax obligations that follow annual or quarter‑end cycles earlier in the year.

A few examples of requirements that may affect specific founders, depending on their situations:

• Palo Alto and other California cities. City business taxes and California corporate estimates are concentrated earlier (and again in September); August tends not to add a new city‑specific corporate tax date, but monthly state sales/use or payroll obligations can still apply.
• Austin, Texas. Texas quarterly reports were due in July for Q2; in August, Austin startups mainly handle July payroll and sales tax deposits, plus any ongoing property tax matters if bills are still delinquent.
• New York City and Boston. Complex corporate and business taxes have main return and estimate dates outside August; August is again about monthly state sales/use and payroll deposits for companies with July activity.

How August fits into the 2026 startup tax year

Looking at the full 2026 startup C‑corp tax calendar, August serves as the bridge between mid‑year compliance and the next major corporate estimate:

• Q1 and Q2. Heavy filing months with federal and state income tax returns, Delaware franchise tax, and Q1/Q2 estimates.
• July. Q2 payroll filings and state quarterly returns, plus local business tax items for certain cities.
• August. Steady state, including monthly payroll and sales/use deposits, but no standard corporate income tax due date for calendar‑year C‑corps.
• September 15. Third federal and state corporate income tax estimates for profitable C‑corps.

For founders, this means August is an ideal month to make sure payroll, sales tax, and state compliance are up to date; to review whether profitability trends will trigger larger September estimates; and to clean up any notices or small issues before the fall deadlines arrive.

August 2026 checklist for startup founders

In August, founders should:

• Confirm that July federal payroll deposits (income tax withholding, Social Security, Medicare) were made correctly and reconcile to your books.
• File and pay any state monthly sales/use tax returns due in August for July activity, especially if your startup has nexus in multiple states.
• Check that state unemployment and withholding deposits for July are current and that your payroll provider is aligned with each state’s rules.
• Review Q3 projections to see whether your September 15 estimated corporate income and franchise tax payments need to be adjusted, based on updated burn and revenue trends.
• Use August as a light‑touch compliance month to resolve any IRS or state notices from earlier in the year, rather than letting them pile up ahead of September and October deadlines.

Make August your tax maintenance month

August is the perfect time to clean up payroll, sales tax, and state filings before the next round of estimates hits in September. If you’re not sure which obligations apply to your startup, or want a second set of eyes on your 2026 tax calendar, Kruze’s startup tax CPAs can help you stay compliant without slowing down growth.

Section 280G – the golden parachute tax rule – is a hidden trap that can reduce founder payouts in a startup acquisition. For venture‑backed startup founders and executives, understanding the 280G trap is essential to protecting exit proceeds.

Section 280G applies when change‑in‑control compensation (cash bonuses, severance, and equity acceleration) for founders and executives exceeds a specific amount, triggering a 20% excise tax on “excess parachute payments” and denying the company a tax deduction on that same compensation.

Many founders only hear about Section 280G when it’s almost too late, usually when an acquisition is on the table, and the deal team is deep into diligence. That’s exactly why it feels like a trap: The rule only shows up when your startup is winning, and then threatens to claw back a meaningful piece of the upside.

What Section 280G Actually Does

The 280G trap happens when parachute payments to executives slightly exceed a strict IRS threshold, and suddenly become heavily penalized.

Under Section 280G, a parachute payment is broadly defined as compensation that is contingent on a change in control of the corporation and paid to a “disqualified individual” (certain officers, highly compensated employees, and significant shareholders). That almost always includes founders.

A change in control generally means a significant shift in who owns or controls a company, usually when a person or group acquires more than 50% of the voting power or equity, or when the company is merged, sold, or transfers substantially all of its assets to another entity. In the context of startup exits and 280G, it’s the transaction (stock sale, merger, or asset sale) that hands effective control of the company to a new owner and therefore triggers any compensation that’s contingent on that event.

When those contingent change‑in‑control payments reach or exceed three times a disqualified individual’s average W-2 compensation over five years (the “base amount”), they can trigger the 280G excise tax and loss of deduction.

Under Section 280G:

• The IRS evaluates “parachute payments” tied to an acquisition or change in control.
• These payments are compared to an executive’s base amount.
• If total payments exceed 3 times the base amount, penalties apply.

The most founder‑unfriendly feature of 280G is its “cliff.” It’s not a gradual phase‑in – it’s a hard line. Crossing the threshold by even one dollar triggers:

• A 20% excise tax on the executive.
• Loss of the company’s tax deduction on the excess compensation.

That means less cash to the founder and worse deal economics for the buyer.

Why the Cliff Is So Dangerous

The structure of 280G creates a disproportionately serious outcome. A minimal overage can create a massive tax impact.

Let’s look at an example of an executive:

• Base executive average salary over 5 years: $300,000
• Threshold: 3 x $300,000 = $900,000
• Unvested equity: $500,000
• Change of control bonus: $300,000
• Consulting agreement for services after closing: $100,001
• Total parachute payments: $900,001

That single extra dollar triggers the rule.

Now the “excess parachute” becomes:
$900,001−$300,000 = $600,001

What happens as a consequence?

• The executive pays 20% tax on $600,001, totalling $120,000.20.
• The company loses the deduction on $600,001.

This is the essence of the 280G trap: A small oversight leads to a six-figure tax hit. And this example only covers the federal excise tax. The executive will also owe ordinary income tax, plus state, local, and Medicare taxes on certain amounts, which pushes the effective tax rate even higher.

In this situation, there’s an easy fix. Simply reduce the consulting agreement, or the change-of-control bonus. But what happens if the “disqualified individual” has significant unvested equity in the company, like a founder? Let’s look at another example:

• Founder/CEO average salary over 5 years: $165,000 (from our Startup CEO Salary Report)
• Threshold: 3 x $165,000 = $495,000
• Unvested equity: $8,000,000
• Change of control bonus: $500,000
• Total parachute payments: $8,500,000

Now our founder’s “excess parachute” is:

8,500,000 - $495,000 = $8,005,000

And the result is:

• The founder pays 20% tax on $8,005,000, totalling $1,601,000, plus ordinary income tax, state, local, and Medicare taxes on certain amounts.
• The company loses the deduction on $8,005,000.

That’s a big tax bill!

What Counts as a Parachute Payment?

Many founders underestimate how much compensation gets swept into 280G calculations. Generally speaking, if the payment is contingent on a change of control, it counts as a parachute payment. From a startup accounting perspective, the following commonly qualify:

• Accelerated vesting of stock options or restricted stock units (RSUs). This is how most founders fall into the 280G trap. When unvested stock options or RSUs accelerate because of a sale or merger, they become parachute payments.
  • There’s one qualification that can reduce the tax burden: If the payment was virtually certain to be made anyway, special rules apply. The value of the payment is set at the net present value (NPV) minus the present value of the payment on the date it would have naturally vested. Also, an amount of 1% of the full accelerated payment multiplied by the number of full months of acceleration is added.
• Change-of-control bonuses. This includes any bonus that’s promised to become payable or paid upon a change of control.
• Retention bonuses. Any bonuses paid to employees and founders to make sure they stay with the company through closing, contingent on the change of control occurring.
• Salary continuation. Any commitment that allows the employee to continue to receive salary for any period after the closing.
• Non-compete payments. Any payment for not competing with the company if the payment is contingent on the change of control.
• Non-solicitation payments. Any fees paid as part of an agreement for not soliciting customers or employees after the acquisition.
• Consulting agreements. Any agreement to provide consulting services after the change in control, if the engagement is contingent upon the acquisition closing.

Because these elements are often defined years earlier in employment agreements and equity plans, the trap is usually set long before the exit. And without strong startup accounting and close coordination with legal and tax advisors, it’s easy to underestimate how much parachute compensation is actually baked into your cap table and comp plans.

How Startups Accidentally Fall Into the 280G Trap

In practice, the trap usually emerges in one of a few patterns:

• Founders with low historical cash comp but large equity stakes see big option acceleration and a deal bonus push them over the 3X threshold.
• Companies add large change‑in‑control severance or retention packages late in the life of the startup without modeling 280G, inadvertently creating excess parachute payments.
• Inadequate records and incomplete modeling lead teams to misjudge whether they’re above or below the line until diligence forces a re‑calculation.

These surprises are particularly painful because they show up after expectations have been set.

Strategies Startups Can Use to Manage the 280G Trap

There’s no one‑size answer, because every deal and cap table is different. But common strategies, implemented with tax and legal counsel, include:

• Adjusting bonus amounts or timing so key individuals stay under the 3X safe harbor where that makes economic sense.
• Re‑designing vesting and acceleration mechanics, like shifting from full single‑trigger acceleration to more nuanced double‑trigger structures. Single‑trigger acceleration (everything vesting at closing) can dramatically increase parachute payments because all remaining equity is treated as deal‑contingent compensation. Double‑trigger acceleration – where vesting requires both a change in control and a qualifying termination – often reduces 280G exposure while still protecting founders if they are let go after the acquisition.
• Using cutback or gross‑up provisions, depending on the negotiating leverage and tax priorities of the parties. A cutback provision automatically reduces parachute payments to stay just below the 3X threshold, trading a slightly smaller headline payout for avoiding the excise tax and deduction disallowance. A gross‑up provision does the opposite: The buyer agrees to cover some or all of the excise tax, increasing the total cost of the package but preserving the founder’s intended net payout when the parties decide the tax hit is worth absorbing.
• Obtaining disinterested shareholder approval in certain private company situations, which can “cleanse” some parachute payments and avoid excess treatment when structured properly (more on this below).

The critical point is timing. These decisions should be made before terms are fully baked into the deal – ideally well before any letter of intent (LOI).

Managing 280G Using Shareholder Approval

Founders sometimes hear that they can “fix” 280G with shareholder approval, but the mechanism is highly technical. In certain cases, however, it can turn otherwise penalized parachute payments into non‑penalized compensation if it’s used correctly.

For non‑public companies (no readily tradeable stock), Section 280G offers a special exception often called a “280G cleansing vote.” If you meet the requirements, the excess parachute payments are not treated as excess under 280G, so:

• The 20% excise tax is eliminated.
• The company (or buyer) keeps its tax deduction for the payments.

The core elements are:

• The company is privately held (stock not readily tradeable).
• Disinterested shareholders – those not receiving parachute payments and not constructively treated as disqualified individuals – owning more than 75% of the voting power approve the payments.
• All voting shareholders receive adequate disclosure of all material facts about the parachute payments and 280G implications.
• Each affected founder/executive signs a binding waiver of their right to the excess parachute payments if shareholder approval is not obtained (the right is restored only if the vote passes).

In practice, the process looks like this:

1. Tax and legal advisors perform a detailed 280G analysis, including base amounts, parachute payments, present value, and potential excess.
2. Founders and other disqualified individuals agree in writing to waive any excess parachute amounts if shareholders don’t approve.
3. The company prepares a disclosure package describing the transaction, the change‑in‑control payments, the excess parachute exposure, and the consequences.
4. Disinterested shareholders – excluding anyone receiving parachute payments – are asked to vote specifically on approval of the excess parachute payments.
5. If more than 75% of the disinterested voting power approves, the waived payments are restored and treated as non‑excess, avoiding the excise tax and deduction disallowance.

Because this exception is not available to public companies and has strict procedural rules, it’s a planning tool for private, venture‑backed startups that want to address 280G before closing.

Why This Matters Before an Exit

280G is often treated as a last-mile tax issue, but it is actually a problem rooted in early decisions. The strategies outlined above work best if you understand the mechanics of Section 280G and start planning early. Here’s a timeline founders can use to address 280G.

Years before exit (ongoing)

• Set a reasonable salary using market data. Use Kruze’s Startup CEO Salary Report and Startup Compensation Guide benchmarks to keep founder/CEO pay within a rational range for your stage, instead of underpaying yourself.
• Design comp plans with 280G in mind. Avoid casually adding rich single‑trigger acceleration or outsized change‑in‑control severance without modeling parachute payments. Coordinate with your tax and legal advisors when updating offer letters, equity plans, and retention packages.
• Keep your finances and cap table updated and accurate. Accurate W‑2 histories, option grants, vesting schedules, and ownership records are essential for any future 280G analysis.

6-12 months before a likely exit (or as soon as you see a path to sale)

• Calculate your base amount. For each founder/executive who might be a disqualified individual, compute the five‑year average W‑2 compensation. This is the base amount in the 280G formula.
• Model parachute payments. Estimate transaction bonuses, severance, and the present value of accelerated equity and other deal‑contingent compensation.
• Run the 3X test. Determine whether projected parachute payments are likely to reach or exceed three times each person’s base amount, and quantify any excess.
• Explore planning options early. If you’re on track to trigger 280G, talk to your advisors about:
  • Adjusting bonus amounts or timing.
  • Tweaking vesting and acceleration mechanics.
  • Allocating some payments to well‑documented noncompete or consulting arrangements.
  • Whether a disinterested shareholder approval vote is available given your cap table and investor base.

This is the window where you still have meaningful flexibility.

During acquisition negotiations (LOI through signing/closing)

• Flag 280G early with the buyer. Make sure the acquirer’s deal team understands the potential excise tax and deduction loss. 280G is their problem too, so they usually care about getting it right.
• Decide whether to pursue a 280G vote. If your company qualifies as private and your ownership structure supports it, work with your legal counsel to:
  • Identify disinterested shareholders and confirm you can reach the 75% voting‑power threshold.
  • Obtain waivers from founders/executives.
  • Prepare the disclosure materials and coordinate the vote timing before closing.
• Negotiate alternative protections if a vote isn’t feasible. Consider cutback provisions (reducing payments to stay under 3X) or gross‑ups (buyer covering some of the excise tax), as well as deal structuring that minimizes contingent parachute treatment.
• Document it clearly. Ensure your proxy/consent materials and transaction documents describe the parachute payments, the 280G analysis, and who bears the risk if a vote fails or the IRS disagrees.

Plan for the 280G Trap Before It Costs You

The best time to address 280G is long before an acquisition is imminent. Kruze Consulting works with founders, finance leaders, and boards to keep books accurate, equity records organized, and compensation data ready for detailed 280G analysis. That means fewer surprises during diligence, better coordination with legal and tax advisors, and more confidence when a change in control is on the table.

Section 280G and the 280G Trap

• In simple terms, what is Section 280G?
• Why is 280G considered a trap for founders?
• Are all change‑in‑control payments parachute payments?
• How does startup accounting help with 280G?
• What should founders do now to reduce 280G risk?

In simple terms, what is Section 280G?

Section 280G is a tax rule that penalizes certain “golden parachute” payments – deal‑contingent bonuses, severance, and equity acceleration – when they reach or exceed three times an executive’s five‑year average W‑2 compensation.

Why is 280G considered a trap for founders?

Because it uses a cliff test and a low historical salary can make it very easy to exceed the threshold, turning a seemingly normal exit package into an excess parachute subject to a 20% excise tax and lost deductions.

Are all change‑in‑control payments parachute payments?

No, but many are. Parachute payments are compensation “in the nature of” pay that is contingent on the change in control and made to certain disqualified individuals, including founders, executives, and major shareholders.

How does startup accounting help with 280G?

Accurate startup accounting provides accurate salary history, equity data, and transaction‑related compensation information, which advisors need to calculate the base amount, model parachute payments, and design strategies to reduce or manage excess parachute exposure.

What should founders do now to reduce 280G risk?

Use market data (like Kruze’s CEO Salary Report) to avoid setting low salaries, review change‑in‑control and acceleration terms with counsel, and make sure your books, payroll, and cap table are up-to-date and accurate so advisors can run credible exit and 280G scenarios before you’re in live deal mode.

For a venture-backed founder, the goal isn’t just getting acquired. It’s keeping as much of the purchase price as possible after all the fine print is applied. Strategic buyers will run your numbers through rigorous startup accounting and merger and acquisition (M&A) accounting checks, and the details, like Net Working Capital and Purchase Price Allocation, can quietly shave millions off your payout if you’re not prepared.

Why Net Working Capital can cut your payout at the last minute

In most M&A deals, the headline price you celebrate in the term sheet is not the amount that actually lands in your bank account. One of the biggest reasons is Net Working Capital (NWC) adjustments.

Net Working Capital is usually defined as:

• Current assets (like cash equivalents, accounts receivable, prepaid expenses)
  minus
• Current liabilities (like accounts payable, accrued expenses, short-term obligations)

In many deals, the buyer and seller agree on:

• A target NWC amount at closing.
• A mechanism to adjust the purchase price up or down if actual NWC is above or below that target.

If your actual NWC at closing is lower than the agreed target (perhaps because receivables are slow, payables are high, or you burned through more cash to improve your numbers) your payout drops. Conversely, stronger working capital can increase the effective price.

Strategic acquirers will:

• Rebuild your NWC from your detailed schedules.
• Challenge items they believe are misclassified or under-reserved.
• Push for adjustments when they think they’re inheriting more liabilities than the target assumed.

Founders who treat NWC as a legal/finance “detail” rather than a core part of exit planning often learn about these adjustments at the worst possible time: Right before closing.

The role of startup accounting in Net Working Capital

You can’t manage NWC strategically without clean, timely startup accounting. Buyers don’t accept rough estimates. They want schedules that tie directly to your general ledger and bank accounts.

Key building blocks:

• Accounts receivable (AR) schedule. Detailed listing of customer balances, aging, and any reserves for doubtful accounts.
• Accounts payable (AP) schedule. Clear breakdown of vendor obligations, due dates, and any unusual items.
• Accruals and other current liabilities. Properly booked expenses incurred but not yet paid (bonuses, vendor accruals, taxes).
• Prepaids and other current assets. Items like prepaid SaaS contracts or insurance, booked correctly instead of sitting in generic expense buckets.

When your NWC-related accounts are sloppy, including things like missing reconciliations, inconsistent cutoffs, and vague classifications, acquirers assume more risk and push for lower effective prices or tighter adjustments.

Strategic M&A accounting is about using these schedules proactively:

• Cleaning and reconciling them months before you go to market.
• Modeling how different NWC levels impact your net payout.
• Avoiding last-minute surprises when buyer accountants rebuild your numbers.

Purchase Price Allocation: How buyers “slice” the deal value

Purchase Price Allocation (PPA) is how the buyer allocates the total consideration across different assets and liabilities they’re acquiring. It’s a core concept in M&A accounting, and it impacts:

• How the buyer will recognize goodwill and intangible assets.
• Tax treatment on both sides of the deal.
• How your financials look post-close (if you’re joining a public or large private company).

Typical buckets in a PPA include:

• Tangible assets (cash, equipment, certain working capital items).
• Identifiable intangibles (technology/IP, customer relationships, trademarks).
• Goodwill (the residual value representing synergies, brand, and “over-the-top” economics).

Why founders should care:

• Certain structures and allocations can be more tax-efficient than others.
• The way deferred revenue, contracts, and customer relationships are valued can affect earn-outs and post-close metrics.
• A buyer may argue for conservative valuations on assets, which can influence how they justify price internally.

If your underlying startup accounting doesn’t clearly separate and support these items, you lose leverage. Strategic buyers will default to cautious assumptions, and your ability to push for a higher valuation narrative weakens.

Strategic financial schedules that acquirers expect to see

To run NWC and PPA, buyers need more than a high-level P&L. They expect detailed schedules and support.

Common requests include:

• Historical monthly financials (P&L, balance sheet, cash flow) for several years.
• AR and AP aging reports with clear cutoffs.
• Deferred revenue schedules and contract-level details for subscription businesses.
• Capitalization tables and stock-based compensation schedules.
• Fixed asset and intangible asset listings.
• Tax returns and R&D credit documentation.

Well-prepared startup accounting teams have these schedules:

• Up to date and reconciled.
• Structured in ways that align with how buyers model and review deals.
• Ready to drop into a data room without weeks of rebuilding.

When schedules are missing or obviously patched together, acquirers infer that more risk is lurking – and that they need to protect themselves in the final purchase price mechanics.

How strategic M&A accounting maximizes your exit payout

Maximizing your payout isn’t just about negotiating a headline valuation. It’s about minimizing the downward adjustments and protecting the economics through:

1. Clean, consistent working capital
   • Tight monthly closes with well-supported AR, AP, and accruals.
   • Clear policies around cutoffs and reserves, so buyers see less uncertainty.
2. Proactive NWC planning
   • Understanding the target NWC in your term sheet.
   • Managing collections, payments, and accruals with that target in mind as you approach closing.
3. Thoughtful Purchase Price Allocation support
   • Having clear documentation on your technology, customer base, and other intangibles.
   • Being able to articulate and support the value of each major asset category.
4. Aligned tax and accounting treatment
   • Ensuring your tax posture and GAAP financials tell the same story.
   • Avoiding surprises (like unrecorded liabilities) that buyers can use to justify reductions.

Founders who invest in strategic startup accounting ahead of an exit often find that:

• Negotiations focus on business fundamentals, not cleanup.
• Buyers trust the numbers more and move faster.
• The final payment looks much closer to the headline price they signed.

How a startup-focused firm helps you get exit-ready

Kruze Consulting specializes in venture-backed companies, and approaches exit readiness as a multi-step process, not a last-minute scramble.

That typically includes:

• Tightening your monthly close and working capital reporting.
• Building and maintaining NWC and deferred revenue schedules in a buyer-friendly format.
• Coordinating with legal and tax advisors on deal structure and PPA implications.
• Preparing your financial and tax documentation for the scrutiny of large strategic acquirers.

Instead of discovering NWC and PPA during the negotiation itself, you go into the process already knowing how they work – and how they’ll affect your payout.

Strategic M&A Accounting for Startup Exits

• What is Net Working Capital and why does it matter in an exit?
• How does Purchase Price Allocation affect my exit?
• Why is startup accounting so critical before an acquisition?
• How can a specialized startup accounting firm help maximize my exit payout?

What is Net Working Capital and why does it matter in an exit?

Net Working Capital is current assets minus current liabilities at closing. Buyers often set a target NWC and adjust the purchase price if actual NWC is higher or lower. Poorly managed working capital can reduce your final payout, even if the headline valuation looks strong.

How does Purchase Price Allocation affect my exit?

Purchase Price Allocation determines how the buyer allocates the deal value across assets, liabilities, and goodwill. It influences tax treatment, post-close financial reporting, and sometimes how the buyer internally justifies price and performance. Clear support for your assets gives you more leverage.

Why is startup accounting so critical before an acquisition?

Clean, GAAP-aware startup accounting produces accurate financials and detailed schedules (AR/AP aging, accruals, deferred revenue) that buyers rely on. If your numbers are messy, acquirers see more risk and push harder for price reductions or protective terms.

How can a specialized startup accounting firm help maximize my exit payout?

A startup-focused firm can tighten your monthly close, build buyer-ready financial schedules, coordinate tax and accounting around deal structure, and anticipate the areas where acquirers tend to push for adjustments. That preparation helps keep more of the negotiated purchase price in your final payout.

Venture-backed startups issuing stock options that rely on ultra-cheap, automated 409A providers are taking a real risk. A thin, “check-the-box” valuation can blow up under IRS scrutiny or acquirer due diligence, jeopardizing employee option holders and slowing (or discounting) your exit – exactly what VCs hate.

Audit-proofing your startup for acquisition

Think of your 409A valuation as part of your startup accounting infrastructure for an eventual exit. The point isn’t just to set a strike price, it’s to document a defensible fair market value (FMV) for your common stock.

Cheap, lightly reviewed valuations create problems because:

• They may rely on generic templates instead of your actual cap table, round terms, and forecasts.
• They often don’t adequately consider recent financing events or changing market comps.
• They produce reports with minimal narrative or support, giving auditors and acquirers little to trust.

When a future acquirer or their advisors see this, they don’t just shrug. They start asking: “Were options priced correctly? Are there hidden tax exposures for employees or the company? Do we need to fix this before closing?”

A strong, well-supported 409A valuation makes those questions much easier to answer, and far less likely to derail a deal.

Why are 409As so important to startups?

Traditional small businesses rarely need 409A valuations at all. They might use simple equity or profit-sharing, but not option grants priced off a formal FMV.

For VC-backed startups, it’s different:

• Stock options are a core part of compensation.
• The IRS expects options to be granted at or above a defensible FMV.
• Safe-harbor rules hinge on having a proper 409A valuation from a qualified provider.

That’s why 409A valuations are a part of startup accounting that exists specifically to protect option grants from being treated as underpriced (and therefore taxable) compensation.

If you treat that requirement casually with the cheapest possible provider, you’re taking a risk non-VC companies simply don’t face.

How cheap, automated 409A valuations create red flags

Ultra-low-cost providers often position 409As as quick, automated checkbox tasks. The shortcuts show up later, when someone looks closely.

Common red flags:

• Superficial reports. Short documents, sparse explanations of methods used, and little detail on how inputs were chosen.
• Weak treatment of recent financings. Minimal analysis of how your latest preferred round (or SAFE conversions) should influence common share value.
• Inconsistent assumptions. Forecasts, discount rates, or market comparables that don’t align with your actual performance or investor materials.
• No alignment with your broader finance function. The valuation exists in a vacuum, disconnected from your cap table, board discussions, or internal forecasts.

Acquirers and their auditors notice these gaps quickly. At best, they’ll demand a new valuation before closing. At worst, they’ll worry about option mispricing, potential employee tax issues, or broader governance sloppiness, and adjust their terms accordingly.

Why defensible 409A valuations matter for employees

For most team members, options are part of why they joined your startup. A fragile 409A puts that upside at risk.

If a valuation is later deemed too low or poorly supported:

• Employees may face unexpected ordinary income tax or penalties if options are recharacterized.
• You might need to fix historical grants or adjust future ones, creating confusion and frustration.
• The “promise” of their equity package can become a point of anxiety instead of confidence.

A robust 409A valuation process, coordinated with your accounting and legal teams, shows your employees that:

• Strike prices are grounded in serious analysis, not arbitrary numbers.
• Their option grants are structured to minimize future tax risk.
• Leadership takes equity seriously as part of compensation, not just as a recruiting talking point.

That trust matters when you’re asking people to stay through the ups and downs on the way to an acquisition or IPO.

The role of startup accounting in 409A valuation quality

A good 409A doesn’t live in isolation. It depends on clean, accurate data from your finance function.

Strong startup accounting supports 409As by:

• Maintaining an up-to-date, reconciled cap table.
• Producing reliable financial statements and thoughtful projections.
• Keeping documentation on funding rounds, SAFEs, convertible notes, and major milestones organized and accessible.

With that information, your 409A provider can see and understand:

• The true structure of your capitalization.
• How your revenue and growth trends match (or differ from) market comps.
• The story you’re telling investors about your trajectory.

Then your provider can produce valuations that are much more likely to withstand scrutiny later.

If your accounting is messy, even an excellent valuation firm will have to make assumptions. Cheap providers often lean heavily on those assumptions, and that’s exactly what acquirers will challenge.

Why “audit-proofing” early is cheaper than fixing problems later

The temptation to go cheap on 409A valuations is strongest early, when money is tight and the exits feel far away. That’s exactly when it’s worth thinking ahead.

Getting 409As right from the start:

• Reduces the risk of IRS questions about option pricing and income recognition.
• Avoids expensive, last-minute valuation re-dos under the pressure of a letter of intent (LOI).
• Gives acquirers more confidence that they aren’t inheriting hidden liabilities around equity.

In other words: audit-proofing your startup for acquisition isn’t just about pleasing future buyers. It’s about making sure your option plan is something you and your employees can rely on.

409A Valuations and Startup Accounting

• What is a 409A valuation and why do startups need it?
• Why are cheap 409A valuations risky for future acquirers?
• How does startup accounting affect the quality of a 409A valuation?
• When should a startup update its 409A valuation?

What is a 409A valuation and why do startups need it?

A 409A valuation determines the fair market value of a startup’s common stock for option pricing. Startups need it to set strike prices that comply with IRS safe-harbor rules, minimizing the risk that options are treated as underpriced, taxable compensation.

Why are cheap 409A valuations risky for future acquirers?

Ultra-low-cost, automated valuations often rely on generic assumptions and thin documentation. Acquirers and auditors may question whether options were properly priced, which can create tax concerns, delay closing, or lead to adjustments in deal terms.

How does startup accounting affect the quality of a 409A valuation?

Accurate 409As depend on clean financial statements, an up-to-date cap table, and reliable projections. Strong startup accounting provides the data and context that valuation providers need to produce defensible reports, instead of relying on rough estimates.

When should a startup update its 409A valuation?

Typically, startups refresh their 409A at least annually, and sooner after major events like funding rounds, significant changes in performance, or material shifts in market conditions. Regular updates help keep option pricing aligned with reality and maintain safe-harbor protection.

R&D tax credits are one of the most powerful non-dilutive benefits available to VC-backed startups, but you only capture them fully when your tax and accounting functions work as one system, not as separate silos. For most venture-funded companies, the right move is to use outsourced tax preparation services that are tightly integrated with monthly bookkeeping and financial reporting.

Why siloed tax and accounting miss R&D credits

CapturingR&D tax credits reliably depends on your outsourced tax preparation and accounting functions operating as one integrated system. When the team that codes your books is the same team that runs your credit study, R&D-relevant payroll and project spend is tracked correctly all year, documentation is built as you go, and the credit is calculated from clean, structured data. A siloed model, with a bookkeeper on one side and a once-a-year tax preparer on the other, is what causes startups to underclaim, misclaim, or skip the credit entirely.

Many founders still run with a split model: A bookkeeper or basic accounting firm on one side, and a separate tax preparer who only shows up once a year. That structure almost guarantees you’ll underclaim or misclaim R&D credits.

When tax and accounting are siloed:

• The tax team doesn’t see the full details behind engineering and product spend.
• The accounting team doesn’t know how their coding decisions impact credit eligibility.
• No one owns the year-round tracking and documentation needed for a robust R&D study.

The result? Your startup might qualify for meaningful credits, but your startup R&D tax preparation amounts end up being rough guesses, or you skip credits entirely because the data is too hard to pull together.

That’s a mistake. Since 2016, Kruze has filed over $200 million in R&D credits, averaging $114,787 per client in 2025. That’s a significant contribution to your startup’s runway.

A better approach is to treat R&D credits as a core part of your financial operating system, which is fed by your accounting, processed by your tax team, and reviewed in your monthly and quarterly close.

Integrating R&D credit capture with the monthly close

If you want reliable, defensible credits, R&D work can’t be something you reconstruct once a year from memory. It needs to be baked into your regular processes.

An integrated setup connects R&D credit capture to your monthly close:

• Payroll and general ledger (GL) alignment. Every month, engineering, product, data, and other technical wages are coded correctly in your general ledger and matched to payroll reports. This makes it easy to identify Qualified Research Expenses (QREs) later.
• Project and cost tagging. R&D-related projects and cost centers are tagged consistently in your accounting system, so you can pull R&D-relevant data with a few clicks rather than manual spreadsheet reconstructions.
• Regular review. Your finance team periodically checks that the way you’re booking expenses supports your R&D credit tax integration plan. That way, you catch miscodings early instead of discovering them in Q1 next year.

With this model, when the tax team sits down to run the study, they’re drawing from clean, structured data rather than trying to reverse-engineer a year of activity. That’s the difference between leaving money on the table and making R&D credits part of your standard playbook.

Documentation handoff between accounting and tax teams

Strong R&D credits live or die on documentation. For VC-backed startups, documentation is what investors, auditors, and the IRS will look at, not just the final numbers on the return.

In an integrated outsourced tax and accounting environment, documentation moves smoothly:

• Accounting generates the source data. Monthly close produces reconciled general ledger reports, payroll summaries, contractor spend, and project/cost-center breakdowns.
• Tax translates data into R&D documentation. The tax team uses that data to identify QREs, map them to qualifying activities, and build formal R&D studies and workpapers.
• Both sides coordinate on elections and filing. Accounting understands when and how R&D credits are being used (for example, against payroll taxes vs. income tax) and reflects that in financial statements and cash planning.

That activity is continuous, not a once-a-year scramble. It’s what turns R&D credit capture into a repeatable process rather than a high-stress, one-off project.

How Kruze’s integrated approach works for VC-backed startups

Kruze’s model is built around integration. The same team is responsible for your books, your startup R&D tax preparation, and your corporate returns, which is very different from a traditional “bookkeeper here, tax person over there” setup.

In practice, that means:

• Unified tech stack. Your GL, payroll, spend tools, and other systems are managed together, so the data feeding R&D studies is standardized and reliable.
• Accounting and tax talk constantly. The people closing your books are in direct communication with the people calculating your credits and filing your returns. Coding changes, new hiring, and big projects are all evaluated with R&D and tax impact in mind.
• R&D credits are part of the plan, not an afterthought. Annual planning, mid-year reviews, and cash runway conversations include R&D credit expectations as a standard input, not something bolted on later.

Because accounting is set up from day one to capture R&D-relevant payroll and project data, the tax team can run defensible credit studies from structured information, and both sides coordinate on how credits flow through your financials and cash planning, so nothing gets lost between handoffs.

Why integrated outsourced tax preparation services matter for VC due diligence

VCs and their advisors care about two things on R&D credits:

1. Are you capturing everything you legitimately qualify for?
2. Can you defend it under scrutiny?

When investors are more comfortable underwriting your numbers, and your runway, when they see:

• A clean, reconciled GL and payroll system.
• Well-documented R&D studies tied directly to your accounting data.
• Clearly explained credit utilization (payroll offset vs. income tax).

When they see a siloed process with rough estimates and weak documentation instead, they worry about future restatements, hidden risks, or missed non-dilutive capital.

Integrated tax outsourcing services and accounting make R&D credits something you can talk about confidently in your data room and board deck, instead of something you hope no one asks about. If you want to make R&D credits a reliable, defensible source of non-dilutive cash, talk to Kruze about building an integrated outsourced tax and accounting model that’s designed for VC-backed startups.

Integrated R&D Credits and Outsourced Tax Prep

• Why do siloed tax and accounting teams miss R&D credits?
• How does integrating R&D credit work with the monthly close?
• What documentation is needed to support startup R&D tax preparation?
• Can I keep my current bookkeeper and just hire an R&D tax specialist?
• How does this help with VC due diligence and future audits?

Why do siloed tax and accounting teams miss R&D credits?

When tax and accounting operate separately, the tax team often lacks detailed, well-coded data on engineering and product spend, and the accounting team doesn’t book costs with R&D rules in mind. That disconnect makes it hard to identify and document all qualifying activities and expenses.

How does integrating R&D credit work with the monthly close?

In an integrated setup, each monthly close ensures payroll and R&D-related expenses are coded consistently in the general ledger. Over time, this creates a clean, structured dataset that the tax team can use to run precise R&D studies, instead of reconstructing a year’s activity from scratch.

What documentation is needed to support startup R&D tax preparation?

You need reconciled payroll and GL reports, project descriptions showing technical uncertainty and experimentation, time or cost allocations by role and activity, and clear workpapers tying Qualified Research Expenses to your financials. An integrated outsourced tax and accounting team builds and maintains this documentation as part of normal operations.

Can I keep my current bookkeeper and just hire an R&D tax specialist?

You can, but you’ll likely face more friction and risk. If your bookkeeper doesn’t code and track expenses in ways that support R&D rules, the specialist has to do extra clean-up and may still miss opportunities. A combined outsourced tax preparation and accounting approach reduces those gaps.

How does this help with VC due diligence and future audits?

Integrated R&D credit tax integration produces credits that are tied directly to your accounting records and backed by clear documentation. When VCs, auditors, or the IRS review your numbers, they see a coherent story: consistent books, defensible studies, and credits used in line with your overall tax strategy.

VC-backed founders cannot separate budgeting and accounting if they want to survive a Q2 board meeting. When investors ask, “Did you hit the Q1 budget?”, they really want to see that you can measure performance, explain variances, and adjust your plan with discipline, not just share a spreadsheet.

Why Q2 boards demand Budget vs. Actuals

Budgeting and accounting connect through a single report: Budget vs. Actuals. Your budget is the plan you set in an FP&A tool or planning file; your accounting system holds what actually happened. A Budget vs. Actuals report places the two side by side, line by line, so you can measure the variance and explain it. For VC-backed founders, this is how investors judge whether you can execute against a plan, not just write one.

By the time you get to your Q2 board meeting, your investors expect more than a high-level update on burn and runway. They want a clear Budget vs. Actuals (BvA) report for Q1 that shows:

• What you planned (the approved budget by month and category).
• What actually happened (your accounting data from the general ledger).
• The variance (dollar and percentage differences) and your explanation.

This is where budgeting and accounting meet. Your budget lives in a planning file or FP&A tool; your actuals live in your accounting system. Budget vs. Actuals is the bridge between the two, and it’s how investors judge whether you can execute against a plan.

If you show up to Q2 without a BvA, or with one that doesn’t tie cleanly to your financial statements, it signals that your finance function is not yet operating at VC-grade.

What does budget mean in accounting?

Founders often think of a budget as “that spreadsheet we put together for the fundraise.” In practice, the meaning of budget in accounting is more specific: It is a structured, time-phased financial plan that uses the same categories and structure as your actual financial statements.

To make Budget vs. Actuals work:

• Your budget must mirror your chart of accounts at a useful level of detail (e.g., revenue lines, COGS, payroll, marketing, G&A).
• It should be broken down monthly, not just annual totals.
• It should align with how you present your P&L to the board.

This is what people mean by budgeting in accounting: Building the budget so it can be compared line-by-line to your actual P&L. If your budget is built in a completely different structure than your accounting system, variance analysis turns into manual guesswork instead of a reliable tool.

How to build a simple Budget vs. Actuals (BvA) report

You don’t need a large finance team to build a useful BvA. You do need clean books and a budget that matches your P&L structure.

At a basic level, your BvA should include, by month and/or quarter:

• Budgeted amount (from your operating plan).
• Actual amount (from your accounting system).
• Variance in dollars (Actual – Budget).
• Variance in percentage (Variance / Budget).

Most startups focus on:

• Top-line revenue (by major stream if relevant).
• Gross margin.
• Payroll and headcount-related costs.
• Marketing and sales spend.
• Key overhead categories (rent, software, professional services, etc.).

The goal is not to explain every $50 variance. It’s to identify meaningful differences that impacted burn, runway, or progress against core milestones – and to show the board that you understand why those differences happened.

Why delayed monthly closes ruin mid-year budget management

Even the best budget is useless if your accounting is always one or two months behind. A late close breaks the connection between budgeting and accounting.

When your books are not closed on time:

• You are making Q2 spending decisions based on old data.
• You cannot produce an accurate BvA before your Q2 board meeting.
• You find out you overspent (or underspent) well after the fact, when it’s much harder to adjust.

For VC-backed startups, a practical target is to close the books within 10-15 business days of month-end. That allows you to:

• Run monthly BvA internally and spot trends early.
• Go into board meetings with fresh numbers that reconcile to your financial statements.
• Adjust hiring or marketing plans in Q2 instead of discovering issues in Q3.

If your accountant can’t deliver a timely close, your ability to manage and explain variances mid-year will always be compromised.

What to say when you miss your Q1 budget

Missing budget is not automatically a failure, but failing to understand and explain the miss is. When your Q1 actuals don’t match your projections, here’s how to talk about it with your board.

1. Start with the headline
   • “We were 15% below revenue plan and 10% above expense plan in Q1, resulting in higher burn and one month less runway than budgeted.”
2. Break down the major drivers. Focus on a small number of meaningful variances, such as:
   • Sales/revenue shortfall (slower pipeline, longer sales cycles, pricing changes).
   • Higher-than-planned payroll (faster hiring, higher salaries, use of contractors).
   • Overspend in specific categories (paid marketing tests, legal fees, one-time costs).
3. Connect back to the budget. Show that you understand the meaning of budget in accounting terms. You’re not defending every line, you are explaining how reality differed from your planned P&L structure.
4. Present your Q2/Q3 adjustments
   • Hiring plan changes (freezes, slow-downs, or re-prioritization).
   • Marketing or operating budget adjustments.
   • Updated forecast incorporating what you learned in Q1.

Boards want to see that you are using budgeting in accounting as a management tool, not just a reporting requirement. A clear Budget vs. Actuals, plus a thoughtful narrative and concrete adjustments, builds credibility, even when you miss.

How to tighten budgeting and accounting before your next board meeting

If your next Q2 or Q3 board meeting is coming up and you’re not where you want to be:

• Ensure your books are fully closed for Q1 (and preferably April and May).
• Map your budget to your chart of accounts so you can generate a clean BvA.
• Identify and quantify the 3-5 biggest variances and write a short explanation for each.
• Update your forecast for the rest of the year based on what actually happened in Q1/Q2.

This is also the moment to consider whether your current finance setup can keep up with your growth. If monthly closes are always late, variance reports are manually cobbled together, or you struggle to explain your numbers, it may be time to upgrade to a startup-specialized accounting partner.

Budgeting and Accounting Variances for VC-Backed Startups

• What is a Budget vs. Actuals report and why do investors care?
• What is the meaning of budget in accounting terms?
• How often should a VC-backed startup run Budget vs. Actuals?
• What if our monthly close is always late – can we still manage variances?
• How should founders explain missing the budget to their board?

What is a Budget vs. Actuals report and why do investors care?

A Budget vs. Actuals (BvA) report compares your planned figures (budget) to your real results (actuals) for a given period, usually by month or quarter. Investors care because it shows how well you execute against a plan, how you respond when reality differs, and whether your finance function is disciplined enough to support scale.

What is the meaning of budget in accounting terms?

In accounting, “budget” means a structured, time-based financial plan that mirrors your P&L layout, with the same categories and same level of detail, broken out by month. That structure lets you directly compare budgeted and actual numbers line-by-line and generate meaningful variance analysis, rather than just comparing high-level totals.

How often should a VC-backed startup run Budget vs. Actuals?

At a minimum, you should run BvA monthly once your books are closed, and then roll those into a quarterly view for board meetings. Monthly BvA helps you catch trends early – like overspending on headcount or marketing – so you can adjust in Q2 or Q3 instead of discovering problems at year-end.

What if our monthly close is always late – can we still manage variances?

You can, but you’ll always be reacting late. If your close happens 30-45 days after month-end, your BvA is backward-looking and less useful for real-time decision-making. Tightening your close to 10-15 business days gives you fresher data, makes variance analysis more actionable, and significantly improves the conversation you have with your board. 

How should founders explain missing the budget to their board?

Be direct and structured: Start with the headline variance (revenue, expenses, burn), then explain the top 3-5 drivers using your BvA (for example, slower sales, faster hiring, or higher-than-planned marketing spend). Finally, outline the concrete changes you’re making to your Q2/Q3 plan. Boards are far more concerned with your understanding and response than with hitting every line item perfectly.