A guide to revenue recognition and project management

Your project landed on time and on budget. The client paid the first invoice months ago and the money has been in the bank ever since. So why does the finance director keep reporting a revenue figure that is a fraction of it? Because cash and revenue are two different numbers, and the gap between them is where project organizations quietly lose control of their finances.

Revenue recognition is the process by which a business decides when a transaction counts as revenue. Cash does not count as revenue until you have earned every single penny of it.

That is usually treated as an accounts department problem. In consulting, construction and software it is not. What is the point of bringing a project in on budget and on time if nobody tracks the revenue it adds to the books?

When the money in the bank is not yet yours

With long term or B2B contracts, should the client pay upfront, at the halfway point, or once every deliverable has been signed off? The accounting principle of revenue recognition answers it the same way every time: you count revenue once the money has been earned, not when it arrives. A restaurant makes the three cases easy to see.

Paid on provision of service

A customer tries a fashionable new restaurant, is served a delicious meal, and happily pays up. That is payment immediately on provision of service, and the owner records the revenue that same evening.

Paid before the service, or deferred revenue

She is so delighted that she books the place for her fortieth birthday six months from now: sixty guests, a large section closed off just for her. The restaurant asks for payment before the party. That advance is deferred revenue, and it stays deferred until the candles are blown out, because only then has it been earned.

Paid after the service, or accrued revenue

She then recommends the restaurant as caterer for her employer’s corporate entertaining. The company orders whenever it has guests and settles at month end. That is accrued revenue: the meal served on the 1st counts as earned even though the payment lands on the 30th.

Timing	Accounting name	What the books show
Paid as the service is delivered	Recognized revenue	Cash and revenue move together
Paid before delivery	Deferred revenue	Cash received, delivery still owed to the customer
Paid after delivery	Accrued revenue	Revenue earned, cash still owed by the customer

Cash flow and revenue are different numbers

Money in the bank is not automatically recognizable. If the buyer cancels, or the goods and services are never delivered, it goes back. On a complex project that gap runs for quarters, so what you expect to earn and what you have confirmed as earned need tracking side by side rather than inferred from the invoice trail.

Spreadsheets are where most teams lose the thread, because the plan and the confirmations end up in different files. In ITM Platform every project has its own revenue list, where each entry carries a projected amount and a status, and only the statuses configured as actual values roll into the project’s actual revenue totals. That puts projected against actual in one place. See revenue management for how those entries, recurring revenues and statuses are set up.

The five step model behind every recognition policy

Organizations decide which transactions count as revenue using globally accepted standards. IFRS 15 and its United States counterpart ASC 606 set out the same five steps:

1. Draw up a contract with the customer.
2. Identify the contractual performance obligations, those pesky promises made by the sales team.
3. Determine the transaction price.
4. Link the transaction price to the obligations, defining the point at which the client hands over the cash.
5. Recognize revenue when the performing party satisfies the performance obligation.

In plain terms: a contract, something to deliver, clear pricing, and delivery terms. Meet the terms and the revenue is yours.

Five methods, and how to choose between them

There is no one size fits all. The right method depends on what drives value in your contracts, so start here and read the worked example that matches your case.

Method	Revenue follows	Typical fit
Percentage of completion	Reported progress	Long engineering and construction contracts
Linear distribution by milestones	Milestones reached	Phased delivery with agreed acceptance points
Fixed price per period	The calendar	Subscriptions and retainers
Bill rate per estimated hours	Estimated hours × category rate	Professional services and consulting
Direct revenue recognition	The transaction itself	Licenses, pass through goods and resale

Choosing is the easy part. Applying the method period after period, across a portfolio where project types follow different rules, is what breaks spreadsheets. ITM Platform implements these same five methods and spreads the revenue budget across the project’s periods, forecasting each one as soon as a method, a revenue budget and start and end dates exist, then letting you turn a forecast into an actual recognition when the period closes. See revenue recognition for the prerequisites and for setting the method company wide, per project type or per project.

Percentage of completion

Revenue recognized = progress during the period × total revenue budget

Complete 10% of the project and you recognize 10% of the revenue. Periods are typically monthly or quarterly.

Silver Railway wins a two year contract to build a 1,300 mile railway. The total budget is $100 million, invoiced in eight equal quarterly payments. The company recognizes revenue on the miles built each month as a share of the total. Progress will not be even: terrain and the occasional station decide how much track goes down in a given month.

Recognized revenue, the vertical blue bars, matches the miles built exactly. Now compare it with what you actually invoice.

In the first quarter Silver Railway builds 4% of the 1,300 miles, so it recognizes $4 million while presenting the client with the agreed $12.5 million invoice. The remaining $8.5 million is deferred.

All of this rests on the progress figure being honest: when reported progress drifts from real progress, recognized revenue drifts with it. Our guide to the difference between estimated and actual percentages is worth reading before you commit to this method.

Linear distribution by milestones

Milestone value = estimated hours for the milestone ÷ total estimated hours × total revenue budget

Here the pace of progress is not the key factor. What matters is hitting the milestones.

You are building a system for the retailer Rain Forest with four modules: Inventory, Orders, Purchasing and Shipping. The revenue budget is $100,000 over six months, paid 30% at the start, 30% once Orders is done in the third month, and 40% at the end. Each module becomes a milestone, and the first two are more labor intensive than the last two.

Because the distribution is linear per milestone, each one recognizes the same amount every month: Inventory $14,400, Orders $16,000, Purchasing $10,400 and Shipping $14,400. On the graph the amounts are accumulated.

Notice the two mismatches. You billed $30,000 before working a single hour, which is deferred revenue. By the second invoice you have completed $75,200 worth of work but billed only $60,000, leaving $15,200 of accrued revenue: money earned and not yet billed.

Fixed price per period

Revenue per period = total revenue budget ÷ number of periods

The simplest of the five. Sales Muscle sells software as a service on a yearly subscription, paid twelve months upfront, so the whole amount starts as deferred revenue sitting in the bank before a single month of service has been delivered. Cancel partway through and the remaining balance funds the refund.

Clients pay $24,000, so Sales Muscle recognizes $2,000 every month until the deferred revenue reaches zero at year end.

Bill rate per estimated hours

Revenue = bill rate per professional category × estimated hours per task × progress in the period

The advantage: you can bill estimated hours rather than actual ones.

Your consultancy, The Fifth Big, has landed a contract to transform a client’s financial processes. You price it by estimating hours per consultant profile, partner, senior and junior, across the timeline. The final price is $100,000 in two payments: half on signature, half at sign off.

Because you billed $50,000 at the start, the accounts carry deferred revenue every month until July, shrinking as recognition progresses. From August to close you work without billing, which generates accrued revenue through to December.

Rebuilding that curve by hand each month means chasing timesheets and rate cards across the team. ITM Platform calculates hourly revenue from the professional category bill rate applied to either estimated or actual hours, excludes non billable hours when working from actual hours, and marks tasks and resources that have already been billed so the same work cannot be billed twice. The mechanics are in hourly revenue management.

Direct revenue recognition

This method recognizes revenue as the transaction happens. SureStart runs value added projects, and some clients prefer to buy their software licenses and small acquisitions through it. Each month the client says what it needs, the goods change hands, and the revenue is recognized there and then.

What the PMO gains from getting this right

You cannot pay salaries, report profits or invest without a firm idea of what is genuinely yours to spend. Applying recognition criteria to projects buys tighter financial control and a project management practice that plugs into business strategy instead of running beside it.

Next steps

• Start a free ITM Platform trial and set a revenue budget and a recognition method on a real project.
• See how costs and revenue work together across a portfolio.
• Keep reading: how to calculate the cost of your projects with man hours.