Add ASC 606 explained for startups: a question to check first

2026-10-22 15:41:25 +00:00
parent fd06e19cb2
commit 455b105035
1 changed files with 148 additions and 0 deletions
@@ -0,0 +1,148 @@
 <br>Here is the core of ASC 606 explained for startups: revenue belongs in the period when your company delivers what the customer contracted for, not when the invoice goes out. For a startup selling subscriptions, pilots, or setup work, that gap changes monthly results and what investors, lenders, or buyers see later. The first thing to check is whether any agreement promises more than one thing.<br>
 When revenue timing starts to matter for a startup
 <br>Most early founders first meet revenue recognition through a bookkeeper's question rather than a formal policy. Someone asks why the deal you closed in March shows up in April, or why the annual payment isn't in revenue yet. That moment is usually the first sign that cash and earned revenue have started to separate. Nothing is wrong yet, but the gap is now visible, and it will keep growing as the company signs more customers.<br>
 <br>In practice, the gap widens when customers pay in advance, when work spans several months, or when a contract includes more than one deliverable. A simple monthly plan rarely raises questions. An annual contract with onboarding, training, and a support tier does. Each piece may be recognized differently, and the books have to show which piece was delivered and when.<br>
 <br>That is where ASC 606 comes in. It is the revenue recognition standard under U.S. GAAP, and it gives a company a method for deciding when and how much revenue to record from a customer contract. You don't need to memorize its wording to use it well. You need to know which questions it asks, because those are the same questions an investor, lender, or buyer will ask later.<br>
 <br>Timing matters outside the accounting team, too. A founder deciding whether to hire, or a board reviewing a plan, reads revenue as a sign of demand. If recognized revenue runs ahead of the work done, the picture looks stronger than the business underneath it. If it trails the work, the company may look weaker than it is. Neither outcome is a crime, but both can lead to worse decisions.<br>
 <br>This also matters before a fundraise or a loan application. Reviewers often rebuild revenue from contracts when they want to test whether the reported numbers hold up. A founder who can explain the logic in advance usually spends less time in that conversation. The point is not perfection. It is being able to say why the numbers look the way they do.<br>
 What the standard asks you to look at in each contract
 <br>Start with the contract itself, not the accounting entry. ASC 606 treats a contract as an agreement with enforceable rights and payment terms, and it asks what the company promised to transfer. Those promises are the unit of analysis. Writing down every promise, including the ones that appear only in an order form or a side email, is the first useful habit.<br>
 <br>The standard calls each distinct promise a performance obligation. A promise is distinct when the customer can benefit from it on its own and it can be separated from the other promises in the contract. Software access, implementation, and training are often separate in substance, even when they sit on one invoice. Whether they are separate is a judgment, and that judgment should be written down with the reasons behind it.<br>
 <br>Next comes the transaction price, which is the amount the company expects to be entitled to for those promises. Discounts, credits, variable fees, and refund rights can change it. A founder who offered a first-year discount in exchange for a longer commitment should know whether that discount reduces the total price or shows up somewhere else. The answer depends on the written terms, not on how the sales team describes the deal.<br>
 <br>Then the company allocates that price across the promises and decides when each one is satisfied. Some are satisfied over time, such as access to a platform during a subscription period. Others are satisfied at a point in time, such as a one-time delivery or a completed setup. The timing rule follows from that classification, which is why the classification deserves more care than it usually gets.<br>
 <br>Keep the answer tied to documents. A short contract memo, with the terms, the list of promises, and the reasoning for each judgment, is often enough for a small company to explain its treatment. Store it with the contract. When a deal changes, update the memo rather than relying on memory, because memory is usually the first thing to drift.<br>
 Where subscription, pilot, and implementation deals usually get tangled
 <br>Subscriptions look simple until they aren't. A monthly software plan usually delivers access over time, so revenue follows the months of service. The complication starts when the plan bundles a setup fee, a premium support tier, or a commitment to build a custom integration. Each addition may create a separate promise, or it may not, depending on whether the customer can use it without the rest.<br>
 <br>Pilots deserve special attention. Many startups run a paid pilot that turns into a larger agreement if the trial goes well. The pilot may be a separate contract, or it may be an early phase of a bigger one. If the terms are unclear, the company can treat a conditional payment as earned too early, or delay revenue that should have been recognized. The question to ask is whether the pilot creates enforceable rights that stand on their own.<br>
 <br>Implementation work is often where founders get surprised. A setup fee paid upfront may be treated differently from the ongoing service it supports. Whether the setup is a distinct promise, and whether it is recognized at completion or across the service period, affects how the first months look. A founder might expect the setup fee to appear immediately, then find it spread across the subscription term.<br>
 <br>Contract modifications are the other common trap. A customer adds seats, extends the term, or swaps one product for another in the middle of the year. Some changes are treated as a new contract, and others change the existing one. The answer depends on whether the added promises are distinct and priced at their standalone value. A founder who handles every change as a simple add-on may be doing the accounting wrong without knowing it.<br>
 <br>None of this means the answer is always complicated. A plain, monthly, cancelable plan with no add-ons may need very little judgment. The value of checking first is that you learn quickly which contracts need a closer look, rather than discovering the issue during a month-end close or a diligence request.<br>
 A hypothetical Boston software startup, from the first signed contract
 <br>Here is an example that is entirely hypothetical. Picture a small software startup in [Boston](https://Venturegrowthpartners.com/locations/massachusetts-boston-interim-cfo-services/) that sells a scheduling tool to clinics across Massachusetts. Its founder, Maya, signs a first annual contract with a regional clinic group. The agreement includes platform access for the year, a setup project in the first weeks, and a training session for front-desk staff. Suppose the annual price is $48,000, invoiced and paid at signing.<br>
 <br>Maya's first instinct is to record the full amount as revenue when the cash arrives. Her bookkeeper pauses. The setup project and the training look like distinct promises, and the platform access runs for the full year. So the bookkeeper suggests reading the contract line by line before entering anything. Nothing has been filed yet, and the question is cheap to ask now, while it would be expensive to answer after the books are closed.<br>
 <br>Reading the terms, they list the platform access, a setup project to be finished within the first month, and a training session. Maya had assumed the setup was included at no separate value. The contract shows that part of the price is tied to it. The bookkeeper flags the setup as a separate promise, and Maya agrees that the setup only helps the customer once the platform is running, which is a point the judgment has to account for.<br>
 <br>The judgment goes into a short memo. Platform access is recognized monthly as the service runs. The setup and training are recognized when each one is completed, and the allocation of the price is written out so anyone can check it. Maya accepts that the first month of revenue will look smaller than the cash received. The difference sits as deferred revenue on the balance sheet, which is an obligation to keep serving the customer.<br>
 <br>Before the next board meeting, Maya asks what changes next. The answer is that the monthly revenue line will reflect service delivered, not the invoice. The cash forecast stays on the cash timing it always followed. Two numbers now need to be reconciled in every report, and a founder who understands why the gap exists is far less likely to panic when it shows up on the page.<br>
 Checking the first reporting cycle for that startup
 Reconciling cash and revenue
 <br>At the first close, the bookkeeper builds a simple bridge from cash received to revenue recognized. Start with the cash from the annual invoice, subtract the deferred portion, and add the amounts earned from completed setup and training. The bridge doesn't need to be elaborate. It needs to tie to the contract memo and to the bank statement, so anyone can follow the path from one to the other without asking for an explanation.<br>
 <br>Working capital becomes the next question. The upfront payment helps the cash position, but the deferred revenue represents service still owed. A finance leader looking at the company would separate the cash that is truly available from the cash that already belongs to future service. Mixing the two is one of the more common ways small companies overstate how much room they have to spend, hire, or absorb a slow month.<br>
 Explaining the gap to the board
 <br>The board deck gets a short note. It shows recognized revenue, cash collected, and the deferred balance, with one sentence explaining the difference. Maya avoids jargon. She says the annual prepayment is earned over the year and the setup is recognized when it is finished. Board members who understand the logic early tend to ask better questions later, such as whether other customers follow the same pattern and whether the setup work is repeatable.<br>
 <br>The clinic example also tests the forecast. If the company sells many annual contracts, the monthly revenue line will lag the cash line during growth and catch up later. A forecast that treats revenue and cash as the same thing will mislead in both directions. The fix is a forecast with separate lines for billings, cash, and recognized revenue, so each line answers a different question and nobody mixes them up in a meeting.<br>
 <br>Over the next few months, Maya notices that the setup pattern repeats across new customers. She asks the bookkeeper to update the contract memo template so each new deal starts with the same checklist: the promises, the price, the timing, and the owner of the judgment. The change is small, but it turns a one-time decision into a routine. That shift from a single answer to a repeatable process is often the real goal of asking the question first.<br>
 <br>The scenario has limits. The clinic contract is hypothetical, and the judgments would differ with other terms, other customers, or a different company structure. The example shows the reasoning, not a ruling on any real case. A real company should confirm its own treatment with the people responsible for its books and, where needed, with its outside auditor.<br>
 How interim, fractional, and permanent finance leaders would approach this question
 <br>Once the question shows up, a founder has to decide who will answer it. Some companies have an in-house controller who can handle the work. Others have a bookkeeper who records entries but does not own the judgments. A third group has no one clearly responsible yet. Three models of finance leadership differ in how they fit that gap, and the choice depends on what is missing.<br>
 <br>An interim finance leader fills a defined period, usually when a role is empty or someone is leaving. The focus is continuity: keeping reporting on track, handling an urgent issue, and handing the work to a permanent hire or a defined team. The engagement ends when the transition does, so the scope should be clear from the start.<br>
 <br>A fractional finance leader works part time on an ongoing basis. The role suits a company that needs regular guidance without a full-time executive. The work often covers planning, cash forecasting, investor reporting, and reviewing accounting judgments like the ones in the clinic example. The scope is agreed in writing and can change as the company grows and its contracts become more varied.<br>
 <br>A permanent finance leader is a full-time hire with a long-term mandate. That fits a company whose finance workload and team are large enough to justify a dedicated executive, and it changes the company's structure and cost base. The decision is harder to reverse, so it usually follows a clear view that the work will continue for a long time.<br>
 Attribute
 Interim
 Fractional
 Permanent
 Typical purpose
 Cover a gap or a transition
 Ongoing guidance without a full-time executive
 Long-term leadership of the finance function
 Time pattern
 Set by the length of the transition
 Part time and ongoing, set in the agreement
 Full time, set by the employment role
 Common focus
 Continuity, urgent fixes, and handover
 Forecasting, reporting, and reviewing judgments
 Strategy, team building, and company-wide planning
 Good fit when
 A role is vacant or changing hands
 Decisions keep coming, but a full hire is not yet justified
 The finance workload is large enough for a dedicated executive
 What changes next
 The work moves to a permanent hire or a defined team
 The scope is revisited as the company grows
 The function is built around the executive
 <br>None of the three is better in general. In practice, the right one depends on how many decisions are piling up and how long they will keep coming. For the ASC 606 question, the choice also shapes who owns the contract memo. An interim leader can review and document the judgments for a transition. A fractional leader can build the template and review each new kind of deal. A permanent leader can make the policy part of the function's routine. Either way, deciding the owner before the question becomes urgent is far better than waiting for a diligence request, when the answer tends to get written under pressure.<br>
 What to check before raising money, refinancing, or preparing for a sale
 <br>Revenue timing is one of the first things a reviewer rebuilds during a fundraise, a loan application, or an exit process. The reviewer wants to see whether reported revenue ties to contracts and to cash. A company that can answer that quickly tends to get through the early questions with fewer surprises, and the conversation can move on to the parts of the business that matter most.<br>
 <br>Positioning a business also depends on the numbers. A buyer or investor reads recognized revenue as a sign of the recurring base, so the treatment of setup fees, pilots, and multi-year deals matters. Presenting revenue in a way the contracts don't support can cause problems later, especially in diligence. The aim is accuracy, not a flattering story, and accurate numbers are easier to defend when someone pushes on them.<br>
 <br>Negotiations get harder when the numbers need explaining in the room. A lender may ask how deferred revenue would be handled if the company stopped serving a customer. A buyer may ask how much of the revenue depends on a pilot that has not yet converted. Having the contract memo and the reconciliation ready lets the discussion stay on the business and off the spreadsheet.<br>
 <br>Closing a transaction usually involves a long list of document requests. Contracts, revenue schedules, and the reasoning behind key judgments are common items. The longer the company takes to assemble them, the more time the process takes and the more room there is for misunderstanding. Organized files shorten that work, although they cannot promise any particular outcome on their own.<br>
 <br>Audit preparation follows the same logic. Auditors test revenue closely because it is easy to misstate, so they often start with contracts and cutoff. A company with a clear list of performance obligations and documented judgments usually has fewer open items when fieldwork begins. Systems matter as well. QuickBooks and NetSuite can both track deferred revenue schedules, but a system only helps if someone set up the rules correctly and keeps them current.<br>
 <br>Be realistic about limits. Not every startup faces an audit this year, and not every fundraise triggers a deep review. The point is to know your answers before anyone asks. If a question about revenue timing would make you pause during a meeting with a lender or an investor, that pause is the signal to do the work now.<br>
 A decision criterion to apply to your own contracts
 <br>The criterion is this: for each type of customer agreement, can you state in one sentence what the company promised, when that promise is delivered, and who on your team owns the judgment? If you can answer all three for every contract type, the first question is in good shape. If one answer is missing, that gap is your next step, and it tells you where outside help would matter most.<br>
 <br>Start with the contract types you actually sign, not the ones described on your website. Many companies rely on three or four templates that cover most deals, plus a few custom agreements that drift away from the template. Checking the custom agreements first usually surfaces the most risk, because those are the ones where nobody has written down the reasoning yet.<br>
 <br>For each type, write down the promises, the price, and the expected timing of delivery. Mark any promise you cannot describe clearly. A promise that is vague to you is probably vague to an auditor, a lender, or a buyer, and they will ask about it. Clarity at this stage costs far less than clarity during a close or a diligence request.<br>
 <br>Then ask whether the answers live in one place. If the reasoning exists only in one person's head, the company depends on that person staying. A simple memo, stored with the contract and updated when terms change, makes the answer portable. It also gives a new bookkeeper, a new controller, or a new finance leader something concrete to start from.<br>
 <br>If the list is long, or the judgments feel uncertain, the choice of support becomes a practical question. An interim, fractional, or permanent finance leader can each take part of that work, depending on how many decisions are open and how long they will keep coming. Match the support to the decisions in front of you, not to a headcount chart. Revisit the criterion when a new kind of deal appears, when a raise or loan is on the calendar, or when someone new takes over the books. What changes next is usually the contract, not the standard, so the list should follow the contract.<br>