Your AWS bill says $0.00 due this month, so your runway spreadsheet says you have 22 months of cash left. But your credits expire in four months — and the same infrastructure that costs you nothing today will cost roughly $8,000 a month starting in January. Your real runway isn't 22 months. It's closer to 12, and no investor will fund the version of the plan that pretends otherwise.
Cloud credits are one of the best deals available to an early-stage startup. AWS Activate hands eligible startups $1,000 on the self-serve Founders path and up to $100,000 through the Portfolio path for startups backed by an affiliated accelerator, incubator, or venture firm. Those credits can cover two years of infrastructure while you find product-market fit. But they create a bookkeeping trap: books that show nearly zero infrastructure cost, margins that look fantastic until they don't, and a cash forecast that falls off a cliff the month the credits run out. Here's how to account for credits correctly from day one.
What Activate Credits Actually Are (and Aren't)
AWS Activate credits are promotional credits applied to your AWS account to offset the cost of eligible services — compute, storage, databases, and more than 200 other services, including third-party models on Amazon Bedrock and eligible support plan charges. They are not cash, not a grant deposit, and not transferable to another account. You can't sell them, move them between companies, or cash them out.
Three facts shape everything about the bookkeeping:
- They expire. Founders-tier credits are typically valid for about a year; larger Portfolio awards commonly run up to two years. The exact expiry lives in your award email and the Activate console — write it down the day you receive the award, because AWS will happily let the date pass quietly.
- They don't cover everything. Upfront reservations, savings-plan prepayments, and some marketplace and third-party charges are typically ineligible. The month you buy a one-year upfront reservation expecting credits to absorb it is the month you learn this the expensive way.
- They arrive in tranches. Portfolio awards often unlock in stages as you hit milestones or consume prior tranches. Each tranche can carry its own clock, so "we have $100,000 in credits" may really mean "$25,000 expiring in March and $75,000 arriving later."
The Core Rule: Credits Are a Discount, Not Income
This is the mistake that corrupts everything downstream. When the credits land, founders are tempted to record them as an asset — or worse, as revenue. Neither is right.
Under U.S. GAAP, cloud hosting arrangements that don't include a software license are accounted for as service contracts: you recognize the service expense as you consume the service. Guidance on implementation costs for these arrangements has been refined over the years, but the treatment of the usage itself never changed — each month's consumption is that month's expense. A promotional credit that offsets the bill is economically a price reduction on that service, not a separate stream of income. The standard practice is to record the gross expense and net the credit against it as a contra-expense, so your books show both what the infrastructure truly costs and what you actually paid.
In plain double-entry terms, a $4,200 AWS month with $4,200 of credits applied looks like this:
2026-09-01 * "AWS August usage"
Expenses:Cloud:AWS 4,200.00 USD
Expenses:Cloud:AWS-Credits -4,200.00 USD
Liabilities:AccountsPayable:AWS(The payable nets to zero because credits settled the bill — no cash moved.) When credits cover only part of the bill, the contra-expense line carries just the credit portion and the remainder flows to cash or card as usual. If you use plain-text accounting, a dedicated Expenses:Cloud:AWS-Credits contra account plus a monthly reconciliation against the AWS bill gives you this structure for free; the Beancount documentation covers how contra-style accounts and monthly balance checks work in practice.
Why does the gross number matter if you paid nothing? Because every metric an investor, lender, or acquirer cares about — gross margin, cost of revenue, burn multiple, unit cost per customer — must be computed on gross cost. A SaaS startup showing 95% gross margins on credit-subsidized infrastructure doesn't have 95% gross margins. It has a temporary subsidy, and diligence will gross it right back up. Keeping the gross expense visible means your unit economics are honest from the start, and the post-credit future holds no surprises.
Set Up Your Books Before the First Bill
Do this once, in an afternoon, and the monthly work drops to minutes.
Create a small, dedicated chart of accounts. At minimum: a gross expense account for cloud infrastructure (split compute, storage, and data transfer if any one of them is material), a contra-expense account for credits applied, and — if you run staging, production, and ML training — cost-center tags or sub-accounts per environment. Credits should be traceable to the environment that consumed them, because "training ate $60,000 of credits" is a budgeting insight you'll want later.
Keep a memo ledger of every credit grant. Credits aren't balance-sheet assets in the formal sense, but you still need a schedule: award date, tranche, dollar amount, expiry date, eligible scope, and which AWS account it landed in. A simple table works. Review it monthly alongside the burn review, and set calendar alerts at 75% consumed and 90 days to expiry. Expired credits are the most common way startups donate money back to their cloud provider.
Reconcile monthly to the AWS bill, not to your bank statement. When credits cover the full bill, nothing hits your bank account — which means bank-feed bookkeeping silently records zero infrastructure cost. Pull the AWS Cost Explorer or the monthly invoice, book gross expense and credits applied from that document, and confirm the contra-expense line ties to the "credits applied" total. Ten minutes a month prevents a year-end reconstruction project.
Model the Credit Cliff, Not Just the Runway
Standard runway math — cash in bank divided by current net burn — lies to credit-funded startups in two directions at once. It understates your true cost structure and overstates how long your cash lasts, because net burn snaps back to gross burn the month credits expire.
Run three numbers instead of one:
- Net burn, as today, with credits applied. This is your actual cash trajectory.
- Gross burn, with credits added back. This is the business you're actually building — the one that has to survive after the subsidy ends.
- The cliff date: the month credits run out at your current consumption growth rate, not at today's flat spend. Cloud spend grows with usage, so project the expiry against a growing number. If credits expire in six months but consumption grows 15% monthly, the effective cliff arrives sooner than a flat-line forecast suggests.
Show investors both burns. Sophisticated seed investors already diligence past the credit subsidy — many will ask for gross-margin figures "before credits" explicitly. Founders who volunteer the grossed-up numbers, with a credible plan for the post-credit cost structure (savings plans, reserved capacity, architectural efficiency, or simply revenue that covers it), look dramatically more fundable than founders whose model implicitly assumes free infrastructure forever.
The same logic applies to pricing. If your per-customer cloud cost is $3 gross and you price as though it's $0.20 net-of-credits, every new customer accelerates the day the math breaks. Price on gross cost; treat the credit period as margin expansion, not as the cost structure.
The Tax Side Is Simpler Than It Looks
Promotional credits that merely reduce what you pay for services are generally treated as a purchase-price adjustment, not as taxable income when received. You don't book $100,000 of income on the award — and correspondingly, you can't deduct the $100,000 of gross expense the credits absorbed. You deduct what you actually paid. The IRS taxes the net effect, which is the economically correct answer: the subsidy shows up as lower deductions, not as phantom income.
Two related points deserve a conversation with your CPA:
- AWS spend itself is deductible. The portion of cloud costs you actually pay is an ordinary and necessary business expense. Keep clean gross-spend records regardless, because the same usage logs feed other analyses.
- Development cloud spend can matter for R&D incentives. Cloud costs for development and testing environments may factor into research-credit calculations and the current rules for expensing versus capitalizing software development costs. Whether credit-offset spend qualifies is a facts-and-circumstances question — which is exactly why you kept the gross numbers. A CPA running an R&D study can only work with spend you actually tracked.
None of this is exotic, but all of it depends on the gross-expense bookkeeping from the previous sections. The founders who scramble at tax time are invariably the ones whose books show $0 of cloud spend for eleven months.
Six Mistakes That Bite Credit-Funded Startups
Booking credits as revenue or a cash asset. This inflates both revenue and assets, misstates every ratio built on them, and creates a deferred-revenue-style liability you'll never actually owe anyone. Credits are a discount. Book them as one.
Building on ineligible services. Architectures centered on upfront commitments or marketplace products that credits can't touch convert a subsidized bill into a real one overnight. Check eligibility before committing to a service, not after the invoice arrives.
Ignoring tranche clocks. Treating a staged $100,000 award as a single pool with a single expiry is how teams discover that $40,000 expired while they were "saving it for scale." Schedule every tranche separately.
Commingling accounts. Running company workloads through a founder's personal AWS account — or mixing two startups' credits in one organization — turns the monthly reconciliation into forensic accounting and can violate program terms. One company, one payer account structure, from the start.
Forgetting support credits. Activate can apply credits to support plans, and early-stage teams routinely pay for Business Support out of pocket while credits sit unused. If your award covers it, use it — architectural guidance during the build phase is worth more than the same credits spent on idle instances later.
Never re-forecasting post-credit pricing. Credits buy you time to earn the right to pay full price — through revenue, efficiency, or committed-use discounts. Twelve months before expiry, start modeling the steady-state bill: savings plans for baseline workloads, lifecycle policies for storage, and rightsizing from the usage data you collected. The cliff should be a budgeted step, not a surprise.
A 15-Minute Monthly Routine
Put a recurring calendar block next to your investor-update day and run the same checklist: pull the AWS invoice and record gross expense plus credits applied; confirm the contra-expense total matches credits consumed; update the memo ledger with remaining balances and days-to-expiry per tranche; recompute net burn, gross burn, and the cliff date; flag any spend on ineligible services; and glance at per-environment trends for anomalies. Visualizing the two burn lines side by side each month — gross and net converging as credits deplete — is one of the highest-value charts a pre-revenue startup can maintain, and a dashboard like Fava renders it directly from your ledger without a spreadsheet.
Credits are runway in disguise: they don't extend your cash, they compress your costs temporarily. Books that show the gross cost, track every tranche's clock, and forecast the cliff month turn a two-year subsidy into what it's supposed to be — a head start, fully measured.
Simplify Your Financial Management
As you scale past the credit period and real infrastructure bills arrive, maintaining clear, auditable financial records becomes essential — investors will ask for them. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data, version-controlled and ready for analysis. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
