Crypto Accounting for Startups: From Pre-Seed to Series A

Most Web3 founders treat accounting as a problem for "later". Then they need to fundraise, and "later" arrives at the worst possible time.

It's the week before a term sheet. The lead asks for a treasury statement, a runway model, and a clean cap table including any tokens already issued. The founder opens a folder of CSV exports from three wallets, a Notion page with a list of contractor payments, and a spreadsheet that hasn't been updated since Q3. Two weeks of reconciliation work compress into a weekend. Sometimes the deal survives that weekend. Sometimes it doesn't.

Crypto accounting for startups isn't about producing perfect GAAP statements from day one. It's about building the right thing at each stage so you're never the bottleneck in your own fundraise. Here's what that looks like in practice.

Why crypto startups underbuild accounting (and what it costs them)

Three reasons it gets neglected:

The work feels invisible. Nobody on the team is asking for a balance sheet. Customers don't care. Engineering velocity does not improve because your books are clean. The cost of skipping accounting is zero until it isn't.

The tooling is bad. QuickBooks does not understand a Gnosis Safe. Xero does not categorize an LP position. Most founders try one or two traditional tools, hit a wall, and conclude the problem is unsolvable for now.

There's no accountant on the team. Technical founders ship code, talk to users, and raise money. Bookkeeping sits in nobody's job description, so it sits.

The cost of underbuilding shows up at three predictable moments:

1. Fundraising due diligence. Investors ask for transaction history, treasury composition, burn rate, and cap table. If those aren't ready, your timeline slips and your perceived professionalism drops.
2. Tax filings. Token launches, vesting events, and contractor payments in crypto generate taxable events that compound. Reconstructing two years of activity at filing time is expensive and error-prone.
3. Audits and entity changes. Series A almost always triggers an audit. Setting up a foundation, opening a regulated entity, or applying for a banking partner all require records you can produce in days, not weeks.

The pattern is the same across all three: the work was always going to be done. Doing it later means doing it under deadline pressure with worse data.

Pre-seed: the 4-tool minimum

At pre-seed, you have a small team, one or two wallets, and most of your cash either in a bank or in stablecoins. You don't need an accounting system. You need four things, in this order.

1. A wallet inventory. A single document (Notion page, spreadsheet, anywhere) that lists every wallet associated with the company. Address, network, purpose (treasury, ops, gas), signers, and date created. Update it whenever a wallet is added or rotated. This is the most underrated artifact in startup accounting. Without it, every reconciliation later starts with archaeology.

2. Books that exist. Not GAAP. Not double-entry. Just a record of every meaningful transaction. A spreadsheet works at this stage. Columns: date, amount, asset, USD value at transaction, category (revenue, expense, capital, transfer), counterparty, transaction hash or invoice reference. Update weekly. Twenty minutes a week is enough; let it slide for two months and you've created a project.

3. A payroll record. Even if you have no employees, you almost certainly have contractors. Keep one document per contractor: who they are, what they're paid, in what asset, on what schedule, and what their tax status is in their jurisdiction. If you're paying in crypto, record the USD-equivalent at the date of each payment. This is the document that will make your first 1099 or equivalent filing trivial.

4. A custody log. Where are the keys? Who has access? What's the recovery process? If your founder loses a hardware wallet on a Tuesday, the company needs to know what's recoverable by Wednesday. Write it down. Store it somewhere that survives one person leaving.

That's it. Four documents. Total setup time: a weekend. Total maintenance: an hour a week.

Seed: what changes when you have employees and a treasury

Seed funding changes three things at once. You hire full-time employees, which means real payroll. Your treasury grows past the point where a spreadsheet feels safe. And you start spending on infrastructure that needs categorization (audits, legal, vendor SaaS, sometimes hosting in stablecoins).

Payroll becomes load-bearing. Once you have W-2 or equivalent employees, you need a payroll provider that handles withholding, social contributions, and reporting. If any of those employees are paid partly in tokens, you need that to flow into the same record. Many startups try to run dual systems (fiat through Gusto, tokens off-the-books) and regret it within a year.

Treasury splits by function. Same logic as a DAO multi-sig: separate wallets for reserves, operations, and any program-specific spend. If your seed round was paid in stablecoins, the treasury wallet should be a multi-sig with at least two non-correlated signers. The ops wallet can be smaller and faster.

You need real bookkeeping, not a spreadsheet. This is the stage where most founders try to make QuickBooks work and then look for crypto-native alternatives. The reason: you now have transactions across fiat (bank), stablecoins (multi-sig), and possibly volatile assets (ETH, native tokens). Reconciling those by hand each month becomes a part-time job.

Monthly close becomes a thing. A close is a recurring discipline: at the end of each month, all transactions are categorized, all wallets reconciled, and a balance sheet plus P&L produced. At seed, this should take a day or two. If it takes a week, your tooling is wrong.

Series A: investor-grade books and audit-readiness

Series A raises the bar in a specific way: someone external is going to look at your books and ask hard questions. That someone might be the lead investor's diligence team, an auditor, a banking partner, or a regulator.

What "investor-grade" means in practice:

• Books are current. Last close was less than 30 days ago. Reconciliation is complete.
• Trail is reproducible. Every line in the P&L can be traced to a source transaction with documentation.
• Treasury composition is explicit. Not just "we have $5M". A breakdown by asset, by wallet, with custody method, signer count, and policy.
• Cap table includes tokens. If you've issued tokens (to team, advisors, investors, or as airdrops), they're recorded with grant date, vesting schedule, and fair market value at grant.
• Tax position is known. Filings are current. If they're not, there's a written plan with a timeline.

This is the stage where fractional or full-time finance hire pays for itself in fundraise speed. A diligence process that takes three weeks instead of three months is worth a lot.

Audit-readiness is a related but separate bar. Most Series A rounds don't trigger an immediate audit, but the bigger U.S. and European leads will require one within 6-12 months of close. Audit-ready means: an independent third party can verify your books against on-chain and bank records using the documentation you've kept. If you've been keeping reasonable records since seed, this is mostly a packaging exercise. If you haven't, it's a six-figure cleanup project.

The token allocation problem: equity vs token cap tables

Most Web3 startups end up with two cap tables: equity and tokens. Sometimes they're meant to be aligned. Often they drift.

Equity is the traditional shareholder structure: founders, employees with options, investors with preferred shares. Standard cap table software (Carta, Pulley, AngelList) handles this.

Tokens are a separate ledger. You may have promised tokens to early advisors, allocated tokens to team via a vesting contract, or sold tokens to investors via a SAFT or token warrant. Each of those is an obligation that needs to be tracked, valued, and reported.

The two structures interact in awkward ways. A SAFE+token-warrant investor has both equity and a token claim. An employee with stock options might also have a token grant. When you raise Series A, the lead will want to see both ledgers and understand the total dilution across them.

What needs to be tracked for each token-side commitment:

• Recipient and counterparty
• Grant date
• Token amount or formula
• Vesting schedule (cliff, duration, acceleration triggers)
• Fair market value at grant (this is where most teams skip work and create future problems)
• Tax treatment in recipient's jurisdiction (often the recipient's responsibility, but the company is sometimes on the hook for reporting)

If you're issuing tokens before the network is live, fair market value is genuinely hard to determine. Get it documented anyway, with the methodology you used. "We thought it was zero" is not an answer that holds up in a tax audit two years later.

Treasury management for stablecoins, ETH, native tokens

Treasury management is a real discipline at seed and beyond. The basics:

Stablecoins are your operational currency. USDC and USDT dominate. The accounting question is which issuer, which network, and what counterparty risk you're carrying. Diversifying across two issuers is reasonable. Keeping everything on one chain is a liquidity choice that should be conscious.

ETH (or your treasury's volatile asset) is harder. If you raised in ETH, you're exposed to ETH price. You can hold (which is a bet), convert to stable (which locks in current value), or hedge (which adds complexity and counterparty risk). Each choice is defensible. Not making a choice is not.

Your own native token, if you have one, is the most complicated. It's both a treasury asset and a financial obligation to holders. Spending it dilutes; selling it signals. Most startups overweight their treasury to native tokens and underweight stablecoins, then run into runway problems when their token's price drops. A 12-month operating runway in stablecoins is a reasonable floor.

Track each asset class separately. Mark to market monthly. Note unrealized gain/loss. This gets you most of what an auditor will ask for.

Tax events you'll forget

Crypto-native compensation creates tax events that don't exist in traditional startups. The ones that bite hardest:

Token launches. Distributing tokens to the public is a corporate event with tax consequences in most jurisdictions. The company may have income; recipients almost certainly do.

Team vesting cliffs. When a vesting cliff hits, that's a recognition event. Both for the company (compensation expense) and the employee (income, in many jurisdictions). If your vesting is set up as a smart contract, the on-chain event is the source of truth, but your books need to match.

Airdrops to team or contributors. "We airdropped 1M tokens to early users" sounds free. It's compensation expense at fair market value on the airdrop date. For recipients, it's income.

Token-for-services payments. Paying a contractor in tokens is taxable to them at the USD-equivalent on payment date. Your books need to record the expense at the same value.

Treasury swaps. Swapping ETH for USDC realizes gain or loss. So does a stablecoin-to-stablecoin swap, technically (though the gain or loss is usually negligible).

None of these are exotic. They are routine for crypto startups. They're forgotten because they don't trigger a fiat bank entry, so they don't show up in a traditional accounting workflow. This is the most common source of crypto tax problems for startups.

When to hire (and what to hire)

Three roles, in rough order of when they make sense:

Bookkeeper (fractional, $1-3K/month). Right when monthly close starts taking more than a day of founder time. Usually mid-seed. A bookkeeper who has worked with crypto startups specifically is worth paying more for; one who hasn't will burn cycles learning on your books.

Fractional CFO ($3-8K/month). When you're starting to model fundraise scenarios, manage treasury policy, or prepare investor reporting. Often pre-Series A. A fractional CFO is not a bookkeeper; don't hire one to do bookkeeping.

Full-time CFO or Head of Finance. Usually post-Series A, sometimes at the round. The trigger is the volume and complexity of decisions: multi-entity structure, regulated subsidiaries, audit, tax planning, banking relationships. Below that volume, fractional is cheaper and usually enough.

The order matters. Hiring a CFO before you have books is hiring someone to build the foundation rather than operate on it. That's expensive and often a bad use of a senior hire.

Tooling progression by stage

The progression isn't about adding complexity for its own sake. It's about making the next funding round, the next hire, and the next regulator conversation easier than the last one.

FAQ

At what stage do I need a real accounting system instead of a spreadsheet? When monthly reconciliation starts taking more than half a day, or when you have more than two wallets and any volatile assets in the treasury. For most teams that's mid-seed.

Can I use QuickBooks or Xero for a crypto startup? For the fiat side, yes. For the crypto side, you'll need a crypto-native tool that connects to wallets and produces categorized output that flows into your general ledger. Trying to force on-chain transactions into a traditional accounting system manually is where founders lose weeks per year.

How do I value tokens we've granted to advisors before the network is live? Document a methodology and apply it consistently. Common approaches: last priced round, discounted future expected value, or a third-party valuation. The key is that the methodology is written down and used the same way for every grant in that period.

Do I need an auditor before Series A? Usually no, but you need to be audit-ready. Most Series A rounds require an audit within 6-12 months after close. The leads who care most about this will tell you in diligence.

What's the single highest-leverage thing a pre-seed founder can do? Keep the wallet inventory current. It's the document everything else depends on, and it's the one that's hardest to reconstruct later.

Further reading

• Wag3s Ledger — crypto-native bookkeeping built for startups, connects multi-sig wallets and bank accounts with categorized output.
• Crypto Accounting Revolution — how blockchain analytics changed financial compliance.
• Token Vesting Accounting — how to record vesting events and value team token grants.
• AICPA Crypto Asset Practice Aid — practical guidance for U.S. accountants working with digital assets.
• IFRS Foundation crypto papers — international guidance on classification and measurement of crypto holdings.