Revenue Recognition Rules for AI Service Engagements

Your AI agency had what looked like a great month. A client signed a $240,000 contract for a twelve-month model development and deployment project, paying the full amount upfront as required by your contract terms. Your bookkeeper recorded $240,000 in revenue for the month. Your profit and loss statement looks spectacular. You celebrated. Then your accountant called and explained that you cannot recognize $240,000 in revenue just because the client paid it. Under proper accounting standards, you can only recognize revenue as you deliver the service — approximately $20,000 per month over the twelve-month engagement. The $220,000 difference sits on your balance sheet as deferred revenue — a liability, not income.

This is not an edge case. Revenue recognition is one of the most commonly mishandled accounting areas in AI agencies, and getting it wrong has real consequences. Your financial statements misrepresent the business. Your tax obligations may be calculated incorrectly. Lenders and investors who rely on your financials are misled. And if you ever face a financial audit — whether for a transaction, a loan, or a tax examination — improper revenue recognition will be flagged as a material weakness.

Revenue recognition matters because it determines when you can claim you earned money. Receiving cash and earning revenue are different events in accounting, and conflating them paints a misleading picture of your agency's financial health.

The Basics of Revenue Recognition

Revenue recognition is governed by accounting standards that define when and how companies should record revenue in their financial statements.

The core principle is straightforward: Revenue should be recognized when (and as) a company satisfies its performance obligations to the customer. In plain language, you earn revenue by delivering what you promised, not by signing a contract or receiving payment.

For US companies following GAAP, the standard is ASC 606 (Revenue from Contracts with Customers). For companies following IFRS, the standard is IFRS 15. The principles are nearly identical.

The five-step framework under ASC 606:

1. Identify the contract. A contract exists when both parties have committed to the agreement, the rights of each party are identified, payment terms are identified, the contract has commercial substance, and it is probable that you will collect the consideration.

1. Identify the performance obligations. What distinct deliverables have you promised? Each deliverable that could be provided separately is a distinct performance obligation.

1. Determine the transaction price. What is the total amount you expect to receive? This includes fixed fees, variable fees (such as performance bonuses), and any consideration payable to the customer.

1. Allocate the transaction price. If there are multiple performance obligations, allocate the transaction price to each one based on its relative standalone selling price.

1. Recognize revenue. Recognize revenue when (or as) each performance obligation is satisfied — either over time or at a point in time.

How This Applies to AI Agency Engagements

AI agencies have several common engagement types, each with different revenue recognition patterns.

Time-and-Materials Engagements

In a T&M engagement, you bill the client for hours worked at an agreed rate. Revenue recognition is straightforward.

Revenue is recognized as hours are worked. If your team works 160 hours in March at $200 per hour, you recognize $32,000 in revenue in March, regardless of when the client pays. If you invoice in April and the client pays in May, the revenue is still March revenue. April creates an account receivable, and May converts that receivable to cash.

The performance obligation is the delivery of professional services, and it is satisfied continuously as the services are performed. This is "over time" recognition.

Watch for unbilled revenue. If your team works hours in March but you do not invoice until April, the March hours represent revenue that has been earned but not billed. This should appear on your balance sheet as unbilled revenue (or accrued revenue) — it is an asset, not income that should be deferred.

Fixed-Price Project Engagements

Fixed-price projects are more complex because the total price is set but the delivery happens over time.

The key question: Is the performance obligation satisfied over time or at a point in time?

For most AI agency projects, the answer is over time, because the client receives and consumes the benefits of your work as it progresses. You are building something for the client — a model, a pipeline, an analysis — and the client has a right to the work product as it is being created.

When revenue is recognized over time, you need to measure progress. There are two methods:

Input method. Measure progress based on inputs — hours worked relative to total estimated hours, or costs incurred relative to total estimated costs. If you estimate a project will take 800 hours and you have worked 200 hours, you are 25% complete and recognize 25% of the total contract value.

Output method. Measure progress based on outputs — milestones completed, deliverables accepted, or other measures of work done. If a contract has four equal milestones and you have completed two, you are 50% complete and recognize 50% of the total contract value.

The input method is more common for AI agencies because AI project milestones are not always equally sized and output measurement can be subjective.

Example: Your agency signs a $200,000 fixed-price contract to build a recommendation engine over five months. You estimate the project will require 1,000 hours of work. In month one, your team works 180 hours. Using the input method, you are 18% complete and recognize $36,000 in revenue, regardless of the payment schedule or milestone structure.

The risk with fixed-price revenue recognition is that your estimate of total effort drives the recognition. If you estimate 1,000 hours but the project actually takes 1,400 hours, your early revenue recognition was too aggressive. You need to regularly reassess your estimates and adjust revenue recognition accordingly. If the project is going to cost more than expected, you may need to recognize a loss provision.

Milestone-Based Engagements

Some AI projects are structured around milestones with payments tied to milestone completion.

If milestones represent distinct performance obligations — each milestone produces a standalone deliverable that the client can use independently — then revenue is recognized at each milestone upon delivery and acceptance.

If milestones are progress payments for a single integrated project — the client cannot use the output of one milestone without the others — then the milestones are not distinct performance obligations. Revenue should be recognized over time using a progress measure, not at milestone payment dates.

Example: A three-phase engagement where Phase 1 is data assessment, Phase 2 is model development, and Phase 3 is deployment. If each phase produces a standalone deliverable (an assessment report, a trained model, a deployed system) that the client can use independently, each phase is a separate performance obligation. Revenue is recognized as each phase is completed.

But if the assessment, model, and deployment are interdependent — the assessment only matters because it informs the model, and the model only matters because it will be deployed — then the three phases are a single performance obligation, and revenue should be recognized over time based on progress.

Retainer Engagements

Retainer arrangements — a fixed monthly fee for ongoing AI services — have predictable revenue recognition.

Revenue is recognized monthly as the services are provided. A $15,000 monthly retainer creates $15,000 in revenue each month, assuming the services covered by the retainer are being delivered.

Watch for unused retainer hours. If your retainer includes a specific number of hours per month and the client does not use all of them, the treatment depends on the contract terms. If unused hours expire, revenue is recognized regardless of usage. If unused hours roll over, the unused portion may need to be deferred.

Prepaid retainers require deferral. If a client pays six months of retainer upfront ($90,000), you recognize $15,000 per month over six months. The remaining balance is deferred revenue on your balance sheet.

Success-Based or Performance-Based Fees

Some AI engagements include variable compensation tied to outcomes — a bonus if the model achieves a certain accuracy target, or revenue sharing based on the business impact of the AI solution.

Variable consideration adds complexity. Under ASC 606, you include variable consideration in the transaction price only to the extent that it is probable that a significant reversal of revenue will not occur. In practice, this means you should not recognize success fees until the success criteria are met or you are highly confident they will be met.

For AI agencies, the conservative approach is typically correct. AI project outcomes are inherently uncertain. Recognizing a performance bonus before the model has demonstrated it meets the target accuracy is premature and risky. Wait until the condition is satisfied.

Licensing and Productized Service Revenue

If your agency licenses software, pre-trained models, or productized tools, revenue recognition follows different patterns.

Right-to-access licenses (where the customer accesses the IP over time, and you continue to support and update it) — revenue is recognized over the license term.

Right-to-use licenses (where the customer receives the IP and can use it without ongoing updates from you) — revenue is recognized at the point in time when the license is delivered.

If you sell a model to a client with no ongoing obligations, revenue is recognized upon delivery. If you license a model with ongoing maintenance, retraining, and support, the license revenue may need to be separated from the service revenue, with each component recognized differently.

Practical Revenue Recognition for AI Agencies

Setting Up Your Accounting System

Your accounting system needs to support proper revenue recognition. This means tracking:

Deferred revenue. Cash received but not yet earned. This appears as a liability on your balance sheet because you owe the client future services.

Unbilled revenue (accrued revenue). Revenue earned but not yet invoiced. This appears as an asset on your balance sheet because the client owes you for work already performed.

Revenue by engagement. You need to track revenue at the engagement level to measure profitability and to recognize revenue correctly for each contract.

Most accounting platforms for small businesses (QuickBooks, Xero) can handle basic deferred revenue with journal entries. For more complex revenue recognition, you may need to supplement your accounting system with a revenue recognition module or a dedicated tool.

Monthly Revenue Recognition Process

Build a monthly revenue recognition process into your financial close.

Step one: Identify all active engagements. List every engagement that was active during the month.

Step two: Determine progress. For each engagement, determine the revenue that should be recognized based on the engagement type — hours worked (T&M), percentage complete (fixed-price), or monthly amount (retainer).

Step three: Compare to billings. Calculate the difference between recognized revenue and amounts billed. If you recognized more than you billed, record unbilled revenue. If you billed more than you recognized, record deferred revenue.

Step four: Record journal entries. Make the accounting entries to record revenue correctly. For most agencies, this involves adjusting entries to move amounts between deferred revenue, unbilled revenue, and recognized revenue.

Step five: Reconcile. Verify that total recognized revenue, deferred revenue, and unbilled revenue reconcile to cash received and accounts receivable.

Estimate-to-Complete Reviews

For fixed-price projects, regularly review your estimate of total effort required to complete each project.

Monthly, for each active fixed-price engagement, ask:

• How many hours have been worked to date?
• What is the current estimate of hours remaining?
• Has the total estimated effort changed since last month?
• Is the project on track to be profitable, or will there be a loss?

If the estimate changes, adjust revenue recognition. If a project originally estimated at 1,000 hours is now estimated at 1,200 hours, the completion percentage drops, and you may need to reduce recognized revenue or slow the rate of future recognition.

If a project is expected to result in a loss, recognize the entire expected loss immediately. Do not wait for the loss to materialize — accounting standards require immediate recognition of expected losses on contracts.

Common Revenue Recognition Mistakes

Recognizing revenue on contract signing. Signing a contract creates an obligation, not revenue. Revenue is earned through delivery, not commitment.

Recognizing revenue on invoice issuance. Invoicing is an administrative action, not an economic event. Revenue may be recognized before or after invoicing, depending on when delivery occurs.

Recognizing revenue on cash receipt. Cash-basis revenue recognition is only appropriate for very small businesses. Any agency beyond the earliest stage should use accrual-basis accounting where revenue is recognized when earned, not when cash is received.

Ignoring deferred revenue. Upfront payments that cover future services must be deferred. Recognizing them immediately overstates current revenue and understates future revenue.

Inconsistent methods across engagements. Applying different recognition methods to similar engagement types without justification creates inconsistencies that will be questioned in any financial review.

Not reassessing estimates. Fixed-price project estimates must be reviewed regularly. Recognizing revenue based on original estimates when the project has changed significantly produces inaccurate financial statements.

Recognizing variable consideration prematurely. Performance bonuses, success fees, and other variable amounts should only be recognized when achievement is probable. Premature recognition creates revenue that may need to be reversed.

Why This Matters for Your Agency

Accurate financials drive better decisions. When your revenue is recognized correctly, your P&L reflects the actual economic performance of your agency. You can identify which engagements are profitable, which are at risk, and where your margins are trending. With incorrect revenue recognition, these signals are distorted.

Investors and acquirers require it. If you seek investment or consider an acquisition, the buyer's diligence team will scrutinize your revenue recognition. Inconsistent or incorrect recognition will delay the transaction, reduce your valuation, or kill the deal entirely.

Lenders rely on your financials. If you apply for a line of credit or a loan, the lender evaluates your revenue history. Inflated revenue from incorrect recognition may help you qualify for a larger loan than your actual economics support, creating financial risk.

Tax implications are real. In many jurisdictions, the timing of revenue recognition affects when taxes are owed. Premature revenue recognition may create tax obligations before you have the cash to pay them. Deferred recognition may defer tax obligations, improving cash flow.

Client disputes are easier to resolve. When your financial records accurately reflect the work delivered and the value earned for each engagement, disputes about billing are easier to resolve because your records align with the reality of what was delivered.

Revenue recognition is not glamorous work. It does not win clients or build models. But it is the foundation of financial integrity that enables everything else — informed decision-making, investor confidence, tax compliance, and the operational discipline that distinguishes agencies that scale from those that stumble. Build the processes, train your team, and commit to getting it right from the start.