When one job bills partly by the hour and partly by a fixed fee, the practical answer to what is project cost accounting is this: it records every cost against that job as it happens, so you can compare what the work consumed with what the client pays. The invoice alone cannot show that. Most of the trouble starts in timekeeping and in how revenue is recognized.

Why a single job can bill two ways at once

Many people assume a job is either billed by the hour or sold for a fixed price. In practice, one engagement often mixes both. A consulting team might bill time and materials for discovery, sell a fixed fee for the build, and add a monthly retainer for support. The contract can read cleanly on paper, but the work underneath does not split as neatly. People move between phases during the same week, and hours tend to land in whichever bucket the contract currently favors.

That matters because each billing method pulls on the books in a different way. Hourly work links effort to the invoice directly, as long as the hours are recorded accurately. A fixed fee works the other way around. The amount is set in advance, so the only way to know whether the work still pays is to track cost against the effort that was expected. When both models sit inside one job, the records have to answer two questions at once: what did we bill, and what did it cost us to deliver?

When I read a board packet, I look first at whether the numbers arrive in time to act on them. A revenue total by client can look healthy while a single fixed-fee job quietly absorbs overruns that the hourly work was supposed to cover. The client line says nothing about which billing type is carrying the loss. That gap is easy to miss, because the totals still add up.

Cash timing adds another layer. Hourly work is often invoiced at the end of a period, while fixed-fee work may be billed in milestones or partly in advance. A job can show strong revenue in one month and very little cash for several weeks. Without job-level cost records, the team cannot tell whether that gap reflects a normal billing rhythm or a job that is losing money. The answer affects whether the next hire or the next purchase order can wait.

Project cost accounting is the discipline that keeps those two questions separate and comparable. It is not a product you buy. It is a set of habits: job numbers, cost codes, timesheets that follow the contract, and a regular comparison of cost with billing for each job. Those habits can live in a general ledger, a spreadsheet, or the job costing module of an ERP system. The tool matters less than whether the habits are applied every period.

Why the invoice does not show whether a job made money

The invoice does not show whether a job made money. It shows what the client agreed to pay on a given date, which is only part of the picture for a job that mixes billing methods. A paid invoice can sit beside a job that is losing ground, and the reverse is also true. The difference lies in cost, timing, and the revenue method, none of which appears on the invoice itself.

Many managers assume that if billings cover the team's time, the job is fine. That holds when every hour is billable at a rate that reflects its real cost. It breaks when some hours are written off, when a fixed fee was priced on optimistic effort, or when a change request was approved without a cost estimate. Each of these leaves the invoice looking normal while margin drains away quietly.

Common beliefWhat usually happensWhat to check

Billings cover the workWritten-off or unrecorded hours lower margin without showing on the invoiceCompare recorded hours with billable hours by job each period A fixed fee means a fixed costCost moves with scope changes and reworkTrack estimated against actual hours by phase Revenue on the income statement is job profitRevenue follows progress toward completion, not the invoice dateConfirm the revenue method for each contract with the CPA or controller One margin per client is enoughMargin differs by billing type inside the same clientReport margin by job and by billing type separately

The table makes the gap visible. The left column is what people tend to say, the middle is what usually follows, and the right is what to check. None of these checks requires new software. They require that someone asks the question at a fixed point in the cycle, and that the answer is written down where the next reviewer can find it.

I read these packets with one habit in mind: who would notice a problem, and when? If the answer is the project lead at quarter end, the report arrives too late for most decisions. A margin problem on a fixed-fee job needs to surface while there is still room to change scope, staffing, or the price of the next phase. Once the build is finished, the options narrow to a difficult conversation with the client.

Revenue charts deserve a closer look for the same reason. A line that climbs each month can hide a job whose cost is climbing faster. Pairing revenue with cost by job, even in a simple two-column schedule, shows when growth is real and when billing is only catching up to work that has already been done at a loss. That pairing is the core of the discipline, and it does not need to be elaborate to be useful.

One more trap is worth naming. Owners sometimes read a strong cash balance as proof that every job is healthy. Cash can come from advances on a different job, from a single large milestone, or from a delayed vendor payment. None of those facts says anything about whether the work is profitable. A job-level view separates the cash story from the margin story, and a board reader needs both before drawing a conclusion.

How project cost accounting assigns each cost to the right job and phase

The mechanics are less mysterious than the vocabulary suggests. Each job gets a unique identifier. Each cost that belongs to that job carries the identifier when it is recorded, whether it comes from payroll, a vendor bill, a subcontractor invoice, or an expense report. That tag is what lets the books answer the job-level question later, without anyone reconstructing the history from email threads.

Cost codes add a second layer. A job might have codes for discovery, build, testing, and support, each with its own budget. The goal is not a chart of accounts with hundreds of lines. The goal is to separate the phases where the billing method changes. If the build phase is fixed fee and the support phase is hourly, those phases need separate codes, or the costs of one will blur into the other.

Most jobs draw on the same few categories of cost. Keep each one tied to a document or a time record:

Direct labor, recorded from timesheets that match the job and the phase Materials and third-party services, coded when the vendor bill is approved Subcontractor costs, matched to the purchase order and to the milestone they support Allocated overhead, applied by a stated method and reviewed each period

Overhead needs particular care. Allocating a share of rent, software, and administrative time to each job is common practice, but the method should be stated and kept stable. If the allocation changes every month, job margins move for reasons that have nothing to do with the work. A board member or investor will ask how the method was chosen, and the answer should fit on a single page without special pleading.

In a hypothetical example, a small firm sells a fixed-fee design phase and an hourly support phase to the same client. The design phase has a planned effort of 120 hours. The team records 150 hours. Without phase codes, those extra 30 hours sit inside the client total and look like a small shortfall. With phase codes, the design phase shows up as 25 percent over its planned effort, which is a signal to review scope before the build starts. The arithmetic is simple. The value is in seeing it while it can still change the plan.

Coding discipline also helps with the next job. When the phase codes and cost categories stay the same across engagements, a new project can start from a template rather than a blank page. Comparisons between jobs become meaningful, and patterns show up sooner. A design phase that runs over on every fixed-fee job is a pricing problem, not bad luck on one engagement.

Why timekeeping and cost entries decide whether the job cost ledger can be trusted

A job cost ledger is only as good as the entries that feed it. Most errors that undermine project cost accounting are small: a timesheet filed a week late, hours charged to a default code, a vendor bill posted to general overhead. Each one looks minor on its own. Together they shift job margins enough to change a decision about pricing, staffing, or whether to accept the next change request.

Timekeeping deserves the most attention, because it is where effort turns into cost. People tend to record hours when it is convenient, which often means at the end of a busy week. Late or rounded time creates a gap between what the team did and what the job shows. The fix is usually a simple rule: time is entered by a fixed day, and the job lead reviews it before payroll closes. Reviewing entries takes less time than correcting them later.

Cost entries have their own timing issues. A vendor invoice may arrive after the period closes, and a subcontractor may bill against a milestone that the team has not yet confirmed. If those items wait, the job looks more profitable than it is. An accrual helps here. It records a cost in the period in which the work happened, even before the bill arrives, so the job's cost is complete when the report is read.

Reporting deadlines are the practical test. If the monthly close happens before timesheets and vendor bills are in, the job report is an estimate that looks like a fact. Ask who is responsible for each feed, and whether the close has a checkpoint for open items. A report can be accurate and still late. For a board reading a packet, late information often does the same damage as wrong information.

Access matters too. If one person can enter time, approve it, and post the cost, the ledger has no independent check. This is less about suspicion than about whether an error would be caught. Segregation of duties is a standard control, and a reviewer who did not enter the data is the simplest way to provide one. In a small team, that reviewer may be a controller or an outside accountant working on a monthly schedule, and the check still counts.

Last, ask whether the ledger can be reconstructed. If the job lead leaves, can someone else explain why a cost sits where it does? Notes on unusual entries, a short log of approved overrides, and a record of who approved each timesheet keep the ledger understandable after the people who built it have moved on. Continuity is a control in its own right.

How ASC 606 changes the revenue side of a job billed partly in advance

Revenue recognition is where many finance teams stumble with mixed billing. Under ASC 606, a company recognizes revenue when, or as, it satisfies a performance obligation. The invoice date does not decide that. For services delivered over time, the standard asks the company to measure progress toward completion, using a method that reflects how the service transfers to the client.

One common input method is cost-to-cost. The company estimates total cost for the performance obligation, measures the cost incurred to date, and recognizes revenue in proportion to that progress. This connects the job ledger directly to the revenue schedule, which is why project cost accounting and revenue recognition cannot be run as separate worlds. An error in cost becomes an error in revenue for the same period, so the same care applies to both.

Billing and revenue will often differ. If a client pays in advance, the company records a contract liability until it performs the work. If work is performed before billing, the company may record a contract asset. These are balance sheet items. They affect cash conversations and reporting even when the income statement looks steady. A reader can see the difference between cash received and revenue earned only if the two are reported side by side.

The method choice is a judgment, and it should be documented and applied consistently. Whether a contract qualifies for recognition over time, which measure of progress fits the work, and how to treat variable consideration are questions for the CPA or controller who owns the financial statements. Strategic financial support can help frame the trade-offs and the cash effects, but the accounting conclusions belong with the people accountable blog_comment thanks for breaking down how fractional cfo support can fit into a growing business. the point about financial modeling matters more than many owners expect. thanks again those statements. A written memo from the accountable party is the record a reviewer will want to see.

Change orders deserve their own note. A change that adds scope may also add price, and under ASC 606 it may or may not be a separate performance obligation. Whether the change modifies the existing contract or creates a new one depends on the facts, including whether the added goods or services are distinct and whether the price reflects their stand-alone value. The practical habit is to record a cost estimate for each change when it is approved, so revenue and cost effects can be assessed together rather than discovered at the close.

The revenue method should also stay the same from one period to the next unless there is a documented reason to change it. A method that shifts with each report makes margins hard to compare and invites questions from anyone reviewing the packet. When a change is justified, the reason, the effect, and the date of the change should appear in the notes. Consistency is what lets a reader trust a trend.

How a mixed-billing job shapes the cash forecast and the board report

Job-level costs feed the cash forecast directly. A 13-week cash forecast is a common tool for seeing the next quarter in weekly detail, and mixed billing makes it harder to build well. Hourly billing follows timesheets and invoice cycles. Fixed-fee milestones follow the contract. Each needs its own timing assumptions, or the forecast averages them into a single number that matches neither.

Start with the cash-in side. For each job, list the billing triggers: invoice dates, milestone approvals, payment terms, and any retainage held back until completion. Then list the cash-out side: payroll for the job's team, vendor payments, and subcontractor payments. The gap between the two, week by week, shows whether a job is funding itself or drawing on the rest of the business. That is the question a board is really asking when it asks about cash.

In a hypothetical case, a fixed-fee milestone is scheduled for invoice in week six, but the client's approval usually takes about two weeks after delivery. A forecast that assumes payment in week six overstates cash by roughly two weeks of receipts. The correction is not complicated. It requires someone who knows how the client approves work and who is willing to write that habit into the assumptions, so the next forecast starts from a realistic timeline.

The board report should show job margin and cash position side by side, not in separate decks. A board member can ask why revenue is up while cash is down, and the answer is often a billing schedule rather than a problem with the work. Showing both on the same page avoids a debate about which number is the true one, and it gives the board a shared starting point for the question that matters.

Reporting deadlines set the rhythm. If the job report arrives after the board has already reviewed the cash forecast, the discussion runs on stale information. A simple calendar, showing when job costs close, when revenue schedules update, and when the forecast refreshes, keeps the sequence correct. Continuity matters here: the same calendar should still work after a change in staff, because the dates belong to the process rather than to a person.

Who owns the job cost numbers when an outside CPA or controller reviews them

Many growing companies already have a CPA, a controller, or an internal bookkeeper, and they add strategic financial support without replacing anyone. That is a sensible approach, but mixed-billing jobs expose a coordination gap. Each party may assume another has set the job codes, reviewed the timesheets, or confirmed the revenue method. When everyone assumes, nobody checks.

Clarity starts with a written split of responsibilities. The operational team owns time and cost entries. The bookkeeper or controller owns posting, reconciliations, and the close. The CPA owns the accounting method and the year-end conclusions. Strategic support owns the forecasts, the job economics, and the questions the board asks. When the lines are written down, a missing item has an owner, and the owner knows the deadline.

Consider a common failure. A job lead assumes the controller set up the cost codes for a new phase. The controller assumes the job lead did, because the template came from the prior year. The new phase has no code, so its costs post to a general account. Nobody notices until the job review, by which time the phase has absorbed a month of effort. The fix is not blame. It is a short checklist that assigns code setup to a named person at the start of every new job.

A single job register helps everyone start from the same facts. It lists each job with its number, billing type, revenue method, owner, and status. Keeping that register as a written, controlled document is the kind of documented process that ISO 9001 quality management asks organizations to maintain. Systems matter too. ERP and financial systems can enforce required fields and approval steps, but a system enforces only the rules someone has defined. The register is the human layer that tells the system what those rules are, and it is the first document a new team member should read.

Meeting cadence is the last piece. A monthly review of open jobs, attended by the controller, the CPA where useful, and the person who prepares the forecast, catches issues before the close. Keep the meeting short and built around a list of exceptions. The question for each job is simple: what changed since last month, and who is acting on it? A meeting that answers that question in ten minutes is worth more than a long one that answers it in an hour.

Organizations funded by grants, or by a mix of grants and fees, may need additional tracking by funder, and this article does not cover those requirements. Some other funding models also carry restrictions that change how costs are coded. Where that applies, the same discipline holds, but the register and the cost codes need to reflect the funder's rules before any report is prepared.

Practical checks to run before the next board or investor report

A mixed-billing job is easier to manage when the checks are routine rather than heroic. Run these before the next report goes out. None of them requires a new system, and each can be done by someone who already touches the job. The list is meant to be short enough that it actually gets done.

Confirm that every active job has a unique number, a billing type, and a named owner. Compare recorded hours with budgeted hours by phase, and flag any phase running over plan. Check that vendor bills and subcontractor costs for the period are posted or accrued. Confirm the revenue method for each contract and that it matches the method used last period. Match billing triggers and expected payment dates to the 13-week cash forecast. Record a cost estimate for each approved change order before the work starts.

Each item is a question with an owner and a date, not a general intention to review things later. If an item cannot be answered, that is useful information in itself. It shows which part of the process needs attention before a board member or investor asks about it, and it gives the team time to fix the gap rather than explain it.

The checks have limits, and they should be described honestly. They do not replace an audit, and they do not settle accounting conclusions. The CPA or controller decides the revenue method and the year-end treatment. Strategic support can show the economics and the cash effects, but the statements belong to the people accountable for them. A clean job report should never stand in for a review of the contract terms.

Keep the checks in writing. A short note each month, listing what was checked, what changed, and what remains open, makes the next review faster and gives a new team member a record to start from. Over time the notes show whether the process keeps pace with the business, or whether the same exceptions return every quarter. A repeated exception is usually a sign that the process needs a new owner or a clearer rule, not a more careful person.

If you can only do one thing this month, pick the job with the largest gap between billing and cost, and walk it through the list above from start to finish. That single exercise tends to reveal which checks matter for your business and which can wait. From there, the routine can grow to cover the rest of the portfolio at a pace the team can sustain.