WIP accounting for fixed-fee vs T&M projects: how work, revenue, and billing align

In project-based work, work completed, revenue recognized, and invoices issued rarely align at the same time. If you rely only on invoices, your numbers will look wrong. If you rely only on effort, your revenue will be delayed. WIP connects these moving parts into a consistent financial picture.

The key point is simple. WIP logic depends on the project billing model. Fixed-fee and T&M projects follow different rules, and mixing them leads to distorted margins and unreliable reporting.

This article explains WIP logic in practical terms. Actual revenue recognition depends on contract terms, accounting policy, and applicable standards such as ASC 606 or IFRS 15.

What is WIP accounting in project-based services

Work-in-Progress (WIP) accounting tracks the difference between work performed and revenue recognized or billed. It exists because project delivery and financial reporting do not move at the same pace.

In a typical service firm, work happens continuously. Teams log hours daily, complete tasks, and move projects forward. Financial reporting, however, happens in structured intervals and follows accounting rules.

This creates a gap.

For example, your team completes 40 percent of a project in March and invoices only after a milestone in April. Without WIP, March would show low revenue, even though significant work was delivered.

That is why work-in-progress accounting in project management is not optional. When it is applied correctly, revenue reflects actual delivery, margins become reliable, and forecasts are based on real progress.

Without WIP, financial reports become a reflection of billing timing, not business performance.

Why WIP behaves differently across project types

WIP is not a universal calculation. It changes based on how projects are structured and sold.

The reason is straightforward. Different billing models create different timing between work, revenue, and invoicing.

In some projects, revenue is tied directly to work performed. In others, it depends on estimated progress. And in many cases, billing follows its own schedule, separate from both.

This means two projects with identical effort can produce very different financial results.

That is why WIP accounting for fixed-fee vs T&M projects requires different approaches. Using one model for both creates confusion and inaccurate reporting.

Fixed-fee vs T&M projects: the core difference in WIP logic

The difference comes down to how revenue is recognized. In many T&M projects, recognition closely follows work performed. In many fixed-fee projects, revenue is recognized over time using a measure of progress rather than invoice timing alone.

Time and materials (T&M): WIP follows actual work

In T&M projects, revenue is earned when work is performed.

Each approved hour or expense directly translates into revenue. The financial logic is simple and observable.

The flow in T&M projects is straightforward. Work is completed, time is approved, revenue is recognized, and the invoice follows shortly after. Because each step is directly linked to actual activity, financial visibility remains clear and immediate.

Fixed-fee projects: WIP follows progress, not billing

In fixed-fee projects, revenue is not tied to invoices or individual hours. It is tied to how much of the project is complete.

In fixed-fee projects, the sequence is less direct. Work is completed gradually, progress is estimated, and revenue is recognized based on that progress, while billing follows predefined milestones or schedules.

As a result, WIP includes:

• Unbilled revenue, work done but not invoiced
• Deferred revenue, invoiced but not yet earned

This dual structure makes fixed-fee WIP more complex.

Conceptual comparison

Aspect	T&M projects	Fixed-fee projects
Revenue recognition	Based on actual work	Based on progress
Billing trigger	Time and expenses	Milestones or schedule
WIP type	Unbilled revenue	Unbilled and deferred revenue
Financial visibility	Immediate	Dependent on estimation

How WIP accounting works in T&M projects

WIP in T&M projects reflects the gap between work completed and invoicing, not between work and revenue. Because revenue is recognized as time is worked and approved, the financial logic closely follows actual delivery.

Revenue recognition in T&M

In T&M projects, revenue is recognized as work is performed and approved.

Every billable hour contributes directly to revenue. If a consultant logs 6 hours, those hours create revenue once approved. This makes time and materials WIP accounting straightforward.

WIP in T&M: unbilled revenue

The main form of WIP in T&M is unbilled revenue, which includes approved time entries waiting for invoicing and expenses that have been recorded but not yet billed. If billing cycles are short, this WIP remains low and does not accumulate over time.

Common issues in T&M WIP

Problems in T&M projects are usually operational, not conceptual. Delayed time approvals slow down revenue recognition, billing delays push invoices further out, and missing or incorrect time entries lead to lost revenue.

The impact is usually limited to cash flow delays rather than major revenue distortion, but over time, these gaps can still affect overall financial visibility.

How WIP accounting works in fixed-fee projects

Fixed-fee WIP depends on estimation. This introduces more risk and requires stronger controls.

Revenue recognition in fixed-fee

Revenue is recognized using the percentage of completion.

This means you estimate how much of the project is complete and you recognize the percentage of the total contract value.

For example:

• Project value: $100,000
• Completion: 30 percent
• Recognized revenue: $30,000

This method aligns revenue with delivery, not billing

WIP in fixed-fee: unbilled vs deferred revenue

Fixed-fee projects create two WIP directions.

• Unbilled revenue: Work completed but not invoiced yet
• Deferred revenue: Invoices issued before work is completed

Both must be tracked together to understand the real financial position. If you track only one, your reports will be incomplete.

The most common WIP mistakes in service firms

Most WIP issues do not come from complex accounting rules. They come from misalignment between how work is delivered and how it is reported.

Recognizing revenue based on invoices instead of work

This is one of the most frequent mistakes, especially in fixed-fee projects. Teams often treat invoices as the moment revenue is earned, even when delivery is still in progress.

The result is predictable. Revenue appears in spikes when invoices are sent, while periods of active work may show little or no revenue. Over time, margins look unstable and difficult to trust.

Lack of real-time WIP visibility

In many firms, WIP is calculated only at the end of the month, which makes it hard to act on the data.

Problems build up quietly during delivery. By the time they appear in reports, teams are already reacting instead of managing. Forecasts rely on outdated information, and adjustments become rushed.

Poor alignment between delivery and finance

WIP breaks down when project managers and finance teams use different definitions of progress.

A project manager may consider a phase complete based on tasks finished. Finance may look at cost or time consumed. When these views do not match, revenue recognition becomes inconsistent, and the same project can appear at different stages depending on the report.

Ignoring scope changes in WIP calculations

Scope changes are common in service work, but they are often excluded from WIP updates.

When additional work is added or timelines shift, revenue assumptions should change as well. If they do not, WIP continues to rely on outdated expectations, and margins stop reflecting the actual effort required to complete the project.

How to track WIP correctly in both models

The goal is always the same: align financial reporting with actual delivery, but the way you achieve that depends on the project type.

In T&M projects, accuracy comes from speed and completeness. Revenue follows actual work, so the priority is to ensure that time is tracked daily, approvals happen without delay, and billing closely follows delivery. When this process works well, WIP remains small and short-lived, and financial visibility stays clear.

In fixed-fee projects, the challenge shifts from speed to consistency. Revenue depends on how progress is measured, not when invoices are sent. That means teams need a clearly defined method for tracking completion and must apply it consistently across reporting periods. Even small inconsistencies in how progress is measured can lead to noticeable shifts in revenue and margins.

Practical comparison

Area	T&M projects	Fixed-fee projects
Primary focus	Speed and completeness of data	Consistency of progress measurement
Key driver of accuracy	Timely time tracking and approvals	Clear and stable completion method
Billing relationship	Closely follows work performed	Independent from progress
WIP behavior	Short-lived, mostly unbilled work	Ongoing, includes unbilled and deferred revenue
Main risk	Delayed billing and cash flow	Misstated revenue and margins

Step-by-step: building a reliable WIP tracking workflow

A reliable WIP workflow is not about complex formulas. It is about consistent rules, clean data, and shared understanding between delivery and finance.

Step 1: Define revenue recognition rules per project type

Start by clearly defining how revenue should be recognized for each project type. T&M projects should follow actual approved work, while fixed-fee projects should follow a defined progress method such as percentage of completion.

This sounds basic, but many firms apply mixed logic across projects. That is where inconsistencies begin. If two similar projects follow different rules, their financials will never align.

Step 2: Connect delivery data to financial tracking

WIP is only as accurate as the data behind it. Your workflow should consistently connect three core inputs:

• Time tracking, what work was done
• Cost tracking, what it actually cost
• Project progress, how much of the project is complete

If any of these are delayed or missing, WIP becomes unreliable. The goal is not perfect data, but a steady and predictable flow of delivery data into financial reporting.

Step 3: Track WIP continuously, not just monthly

WIP should not appear only at month-end. By that point, it is already a reporting exercise, not a management tool.

When teams review WIP weekly, they can spot patterns early. For example, delivery may be ahead of billing, or progress may lag behind cost. Acting on these signals early prevents margin surprises later.

Step 4: Align PMs and finance on the same metrics

WIP breaks when different teams use different definitions.

Project managers may focus on task completion, while finance looks at cost or time consumed. Both perspectives are valid, but they must be aligned into one shared logic.

At a minimum, teams should agree on:

• What “completion” means in each project
• How progress is measured and updated
• How revenue is calculated from that progress

Without this alignment, the same project will produce conflicting numbers depending on who reports it.

Step 5: Integrate WIP into forecasting and margin tracking

WIP should not sit only in financial reports. It should feed directly into planning and decision-making.

When WIP is used in forecasting, teams can estimate future revenue based on actual delivery trends instead of assumptions. It also improves margin tracking, since revenue and cost are evaluated together, not separately.

This is where WIP becomes practical. It moves from being an accounting adjustment to a tool that supports better project decisions.

Final thoughts: WIP connects delivery reality to financial truth

WIP accounting is not just a financial exercise. It is how service firms make sure their numbers reflect what is actually happening in delivery.

The key point is simple: WIP depends on the contract structure and the revenue recognition logic behind it. In many T&M projects, WIP follows work performed more directly, while in fixed-fee projects, it depends more heavily on how progress is measured.

WIP is the bridge between what your team delivers and what your reports show. If that connection is weak, every decision built on top of it becomes less reliable.

FAQ: WIP accounting for service firms

Why does revenue look inconsistent across project types?

Different billing models use different revenue recognition methods. T&M follows actual work, while fixed-fee relies on progress estimates.

What is the difference between unbilled and deferred revenue?

Unbilled revenue is work completed but not invoiced. Deferred revenue is invoiced work that has not yet been delivered.

How often should WIP be reviewed?

Weekly reviews provide better visibility. Monthly reviews alone often miss early warning signs.

What causes incorrect margin reporting in projects?

Misaligned revenue recognition, missing time entries, and inaccurate progress estimates are the most common causes.

Can WIP be accurate without detailed time tracking?

It is difficult. Even in fixed-fee projects, time and cost data improve the accuracy of progress measurement and financial reporting.