Where Hours and Money Finally Meet: Reading the Project Billing Report

A project billing report puts each project’s hours next to its money on a single row. You see the hours estimated and used. You also see what the client agreed to pay, what you have invoiced, what has arrived, and what is left to bill. Read together, those numbers tell you whether effort is turning into cash or quietly piling up as unbilled work.

This guide walks through every column, the patterns worth acting on, and a weekly routine that keeps delivery and finance reading the same page.

 What Is a Project Billing Report?

A project billing report is a one-row-per-project view that places delivery data beside financial data. On the delivery side, it shows estimated hours and hours used so far. On the financial side, it shows the order value and the amounts invoiced and collected. It also shows what is left to invoice and what is invoiced but unpaid.

Most service firms already track these numbers. The trouble is that they live in different places. Timesheets hold the hours, while orders, invoices, and payments hold the money. As a result, a project manager may see a project using hours fast while finance sees little billing on it. Often, nobody connects the two until month-end.

The project billing report is the meeting point. For firms that bill by the hour or by milestone, it quickly answers a simple question. Are we getting paid for the work we do?

Why Hours and Money Drift Apart

In a typical professional services automation setup, hours and money are counted independently, and for good reason. Hours come from timesheets and drive delivery decisions such as staffing, estimates, and burn. Money comes from orders, invoices, and payments, and it drives cash flow.

Because the two streams move on different clocks, they drift. A team can log 200 hours this month while the invoice for that work waits for a milestone sign-off. Similarly, a client can pay an advance before a single hour is logged. Neither situation is wrong on its own. Each simply needs to be seen.

Utilization pressure makes this visibility more urgent. According to the SPI Research Professional Services Maturity Benchmark, average billable utilization fell to 66.4% in 2025, the lowest in the survey’s history and below the 70% level SPI treats as a healthy floor. When fewer hours are billable to begin with, every billable hour that fails to reach an invoice costs more.

The Columns in a Project Billing Report, Explained

The exact labels vary by tool, but a well-built project billing report usually carries these seven columns.

Column	What It Measures	Where It Comes From	Question It Answers
Estimated hours	The effort planned for the project	Project setup	How big did we expect this to be?
Used hours	Hours logged against the project so far	Approved timesheets	How much effort have we spent?
Order total	The value of the client’s purchase order	Received PO	How much did the client agree to pay?
Billed	Total invoiced against that order	Invoices	How much have we asked for?
Received	Payments recorded against those invoices	Receivables	How much has arrived?
Remaining	Order total minus billed	Calculated	How much is left to invoice?
Due	Billed minus received	Calculated	How much is invoiced but unpaid?

Two derived ratios make the report far easier to scan:

• Hours burn is used hours divided by estimated hours. It shows how far through the effort budget the project is.
• Billing progress is billed divided by order total. It shows how far through the contract value you have invoiced.

When those two percentages sit close together, the project is billing in step with delivery. When they pull apart, something needs attention. If any term here is new, the Juntrax glossary entry on work in progress and the one on billable vs non-billable time are good quick references.

How to Read a Project Billing Report in Five Steps

A consistent reading order stops you from reacting to whichever number looks scariest first. Work through each row in this sequence.

Step 1: Check the Hours Burn

Start with delivery. Divide used hours by estimated hours. A project at 30% burn is early, while one at 90% burn is close to its effort budget. On fixed-fee or milestone work, high burn is an early warning, because extra hours rarely come with extra fees.

Step 2: Compare Burn With Billing Progress

Next, divide billed by order total and set it beside the burn figure. For example, a project at 75% burn and 40% billing progress has done far more work than it has invoiced. That gap usually represents unbilled work, which accountants often call work in progress.

Step 3: Look at What Is Due

Then move to collections. The due column shows money you have already asked for but have not yet received. A large due figure on an otherwise healthy project is a collections task. The delivery team did its part, so the follow-up now sits with finance or the account owner.

Step 4: Look at What Is Remaining

After that, check the remaining column. This figure caps what you can still invoice under the current order. If remaining is small but hours burn is well short of 100%, the team may finish the work after the contract value runs out. That calls for a scope conversation or a change request before the next hour is logged.

Step 5: Assign an Action to Every Flagged Row

Finally, turn each observation into a decision. Every flagged row should leave the review with one owner and one next step, such as raising an invoice, chasing a payment, or reopening scope. Otherwise, the same rows tend to reappear in next week’s review.

Six Patterns and What Each One Tells You

Once you read the report in this order, most rows fall into a small set of recognizable patterns.

Pattern	What It Usually Means	What to Do
Hours burn well ahead of billing progress	Work is being delivered faster than it is invoiced	Raise the next invoice or push the milestone sign-off
Billing progress well ahead of hours burn	You invoiced in advance, such as a deposit or retainer	Track delivery closely so the work catches up with the billing
Hours burn near 100% with remaining still high	The effort budget is nearly spent on a fixed-fee job	Review scope and estimate before the overrun grows
Remaining near zero with hours burn well below 100%	Contract value is used up before the work is done	Open a scope or change request conversation now
High due relative to billed	Invoices are going out but payment is slow	Follow up on collections and check the payment terms
Used hours logged with no order total	Work has started without a purchase order in place	Confirm the commercial agreement before more time is logged

The first two patterns have an accounting parallel worth knowing. Under IFRS 15, work performed but not yet invoiced typically sits as a contract asset, while billing ahead of the work creates a contract liability. The ACCA’s plain-language explainer covers both. India’s Ind AS 115 follows the same model, so confirm the treatment for your own books with your accountant. The project billing report does not replace that accounting. It shows operations teams the same gap early enough to act.

A Worked Example: Three Projects, Three Stories

Here is how a short report might look for a consulting firm with three active projects. The figures are illustrative.

Project	Est. Hours	Used Hours	Order Total	Billed	Received	Remaining	Due
Apollo Redesign	320	250	$45,000	$22,500	$18,000	$22,500	$4,500
Helios Migration	180	164	$42,000	$42,000	$28,000	$0	$14,000
Orion Support	90	73	$0	$0	$0	$0	$0

Apollo Redesign is at 78% hours burn but only 50% billing progress. The team has delivered well past what the invoices reflect, so the action is to raise the next invoice. The $4,500 due is modest and worth a routine reminder.

Helios Migration is fully billed, with 91% of its hours used and nothing left to invoice. Delivery looks healthy. However, $14,000 is still due, which makes this a collections row. The account owner should follow up before the project closes and attention moves elsewhere.

Orion Support has 73 hours logged and no order behind them. That could be internal work, a missing purchase order, or a deal that was never formally closed. Either way, someone needs to confirm the commercial terms, because those hours cannot turn into an invoice as things stand.

Each row ends the review with a clear owner and a clear next step, which is exactly what the report is for.

How Often to Review the Project Billing Report

The right rhythm depends on who is reading.

• Project managers, weekly. A short weekly pass catches billing gaps while the work is fresh, which makes invoices easier to raise and easier for clients to approve.
• Finance, at each billing cycle. Before invoices go out, finance can use the remaining column to confirm that nothing is being billed beyond the order value.
• Leadership, monthly. A monthly portfolio view shows where cash is stuck in due balances. It also shows which projects use hours faster than they generate billing.

Consistency matters more than frequency. A report reviewed every week at the same time builds a habit, whereas an occasional deep dive tends to surface problems after they are expensive.

What Makes the Report Trustworthy

A project billing report is only as reliable as the data feeding it. Before you trust the rows, check these five habits.

1. Timesheets are approved on time. Late or missing entries make hours burn look lower than reality. The Juntrax guide to timesheet management covers the basics.
2. Billable status is set at entry. Marking time as billable when it is logged avoids a month-end sorting exercise.
3. Rates follow the date of the work. If a consultant’s rate changes in June, March’s hours should still bill at March’s rate. See the difference between billing rate and cost rate.
4. Orders exist before work starts. Without a received purchase order, the report has no order total to measure against.
5. Issued documents stay as issued. Changing a catalog price later should never rewrite an invoice you have already sent.

Reading the Project Billing Report in Juntrax

Juntrax runs the project-to-cash operations layer for services firms, and the Project Billing report is where its two streams meet. Each row shows a project with its estimated hours, used hours, order total, billed, received, remaining, and due. Hours come from timesheets, while money comes from orders, invoices, and payments. The report lines them up so you can compare them without blending them into one figure.

Several rules behind the screens keep those rows honest:

• A sale is tied to a project at the order stage. When a client’s purchase order arrives, you record it as a Received PO against a project. Invoices raised against that order inherit the project, so billing always traces back to the job.
• Billable time becomes invoice lines. When you invoice a project, its billable hours drop in as service lines, priced at hours multiplied by each person’s rate.
• Rates follow the day the work was logged. The system applies the rate that was in effect on that date, not today’s rate.
• Invoices and payments have hard limits. An invoice cannot exceed the order’s remaining balance, and a payment cannot exceed what is still outstanding on an invoice.
• Prices freeze when you bill. Once an invoice is raised, later catalog changes leave it, and the profit on it, exactly as billed.
• Statuses update on their own. An invoice turns Overdue the day after its due date and Paid once nothing is pending.

For a closer look at a single order, the Received PO Manage screen works as a control center. It shows tiles for order total, billed, received, remaining, pending, and overdue, along with a progress bar and tabs for invoices and receivables. You can see the whole flow in our tour of how Juntrax runs its own operations.

Juntrax also works alongside the accounting system you already use, such as Tally, QuickBooks, Xero, or SAP. Your ledger remains the system of record for accounting. Juntrax handles the operational layer between the timesheet and the collected invoice. That setup suits consulting firms, engineering firms, and legal practices that bill against hours and milestones.

Common Mistakes When Reading a Project Billing Report

Even a clean report can mislead if you read it the wrong way. Watch for these traps.

• Treating billed as collected. Billed is a request for payment. Received is the cash, and the due column holds the difference.
• Reading money without hours. A project with a large remaining balance looks healthy until you notice it has already used most of its estimated hours.
• Ignoring rows with zero order total. Hours logged without an order are easy to miss. With no invoice gap, nothing draws attention to them.
• Reviewing only at month-end. By then, the hours are old, the details are fuzzy, and invoices take longer to approve. The Juntrax guide to revenue leakage explains how these small delays add up.
• Skipping the owner. A flagged row without a named owner usually shows up again next week, unchanged.

Make the Project Billing Report a Weekly Habit

The project billing report earns its place because it answers the question every services firm asks at some point: is the work we do turning into money we collect? Read hours burn first, compare it with billing progress, check what is due and what is remaining, and leave every flagged row with an owner. Over a few weeks, that routine pulls billing closer to delivery and makes cash flow far more predictable.

Do your hours and invoices still live in separate tools? Then the fastest way to see the difference is to run the report on your own projects. Juntrax offers a free 14-day trial with no credit card required.

Frequently Asked Questions

What Is a Project Billing Report?

A project billing report is a one-row-per-project view that shows estimated and used hours alongside the order total, amount billed, amount received, amount remaining to bill, and amount due. It helps teams see whether delivered work is being invoiced and collected on time.

What Is the Difference Between Billed and Unbilled Amounts?

Billed amounts are work you have already invoiced. Unbilled amounts are work you have delivered but not yet invoiced. In a project billing report, unbilled work shows up when hours burn runs ahead of billing progress.

How Do You Calculate the Remaining Amount on a Project?

Subtract the total billed from the order total. For example, a $45,000 order with $22,500 billed has $22,500 remaining. That figure is the most you can still invoice under the current order.

What Does the Due Column Mean?

Due is the amount billed minus the amount received. It represents invoices that have been sent but not yet paid in full, so it points to collections work.

How Often Should You Review a Project Billing Report?

Project managers benefit from a weekly review, finance from a review before each billing cycle, and leadership from a monthly portfolio view. A fixed weekly slot tends to catch billing gaps while the work is still fresh.

Does a Project Billing Report Replace Accounting Reports?

No. A project billing report is an operational view for delivery and finance teams. Formal revenue recognition, contract assets, and financial statements still belong in your accounting system and with your accountant.