Straight into the service manual page
WrenchQuarry
More

Job costs to post before an invoice: 2 entries, 1 check

WrenchQuarry Editorial Team · Published · 11 min read · How these guides are written

Post direct expenses and work in process before you invoice, then check budget variance, so your project reports and your invoice tell the same story. The sequence is deliberate: expenses feed WIP, WIP feeds the invoice, and variance reads both against a flexible plan. Skip a step and the next reading is off.

Key takeaways

  • Post direct expenses first. Code parts, subcontractor charges, fuel, and travel allowances to the job number as they are incurred, so the expense side is already clean when the field says the job is done.
  • Calculate and post work in process. WIP puts a dollar value on work done but not yet billed; Business Central values task groups separately.
  • Run budget variance against a flexible plan. Compare actual cost to a budget restated at actual volume to catch mis-coded entries, missed change orders, or scope problems before the customer sees them.
  • Confirm retention treatment. Check your contract terms, and on Ohio public work, the statutory deadline for paying retained funds after final completion.
  • Draft the invoice from the posted books, then relieve WIP. The invoice becomes a readout of what is already recorded, and the WIP asset becomes a receivable.

Why posting first matters

You close a service job. The crew is done, the parts are gone, and the customer is waiting for a bill. The temptation is to invoice right away and catch the books up later. That habit is how project books drift from the invoice.

Work in process exists to solve exactly this problem. As Microsoft Learn explains it, the work in process (WIP) feature lets you estimate the financial value of ongoing projects in the general books (Microsoft Learn, Monitor project progress and performance). WIP is the bridge between the day your crew spends money and the day your customer pays you.

As a project progresses, materials and resources are consumed and expenses incurred that you must post to the project (same source). An invoice alone does not record what the job consumed. That is the gap this post closes.

Two kinds of job cost belong in the books before the invoice goes out, and one check comes before billing too. The first is raw expense posted against the job. The second is work in process, which estimates the value of unfinished work. The third is budget variance, which shows how actual spend compares with the plan. Post the first two, check the third, then invoice, and your project reports and your invoice agree.

Post expenses against the job before you invoice

The first cost you post is the direct expense: parts, subcontractor charges, fuel, travel allowances, and anything else tied to the job number. In many cases, you might post expenses for a project before invoicing (Microsoft Learn). That sequence matters. If you invoice first and post later, the books show a receivable with no matching cost. Your profit report looks fine for a week, then wrong for a month.

But if you only post expenses, your financial statement is inaccurate (Microsoft Learn). Expenses alone do not tell you the value of work still in the field. A job that is half built and half paid still has cost sitting in the books that no invoice has matched. That is why the second kind of cost exists.

Practically, posting expenses first means your dispatch and accounting teams agree on a job number before the crew rolls. Every parts purchase gets coded to that number. Every subcontractor invoice gets coded to it. When the field says the job is done, the expense side is already clean. You are not hunting for missing costs at month end. Set up the job numbers first; the job costing setup for field service guide covers the settings.

Every project-related entry is recorded in project registers and sequentially numbered, starting with 1 (Microsoft Learn). Those registers give you an audit trail. If a customer disputes a line on the invoice, check it against the expense entries coded to that job number. If your own team questions a cost, check it against its entry in the register.

What counts as an expense to post

Direct job costs are the obvious ones. But you also post anything the job absorbed that you intend to bill or absorb: equipment rental, special permits, overnight shipping, and the like. The rule of thumb is simple. If the cost exists because this job exists, it belongs on this job number before you invoice.

Schedule the posting. Waiting until the invoice is drafted means you are reconciling costs while a customer waits. Posting on a cadence — daily for a busy crew, at job close for a one-off — keeps the books current. The invoice then becomes a readout of what is already recorded.

Calculate and post work in process

Work in process is the second kind of cost, and the one most shops skip. WIP puts a dollar value on work you have done but not yet billed. It is recorded in the general books as an estimate of unbilled value, not as a receivable, because no invoice exists yet.

Microsoft Learn describes the mechanics in plain terms: as a project progresses, materials and resources are consumed and expenses incurred that you must post to the project. Until those costs are posted, the job's record is incomplete.

How WIP groups tasks

WIP is not calculated as one lump sum across the whole job. Business Central groups project tasks and values each group separately. For tasks 1000 through 1299, WIP is calculated separately for that group (Microsoft Learn). For tasks 1300 through 1399, WIP is calculated separately for that group as well.

That grouping lets you see which phase of the job holds value. If your install phase is heavily loaded and your punch-list phase is empty, WIP shows the imbalance before the invoice does. You can then decide how to bill: full progress billing, milestone billing, or holdback.

Two tasks in the example structure — 1010 and 1110 — are excluded from the WIP calculation because their project task type is Posting (Microsoft Learn). Cost coded to a Posting-type task must be posted directly, because WIP will not pick it up. Knowing that boundary matters.

Calculating and posting WIP

Business Central offers a guided path: follow the assistance steps to calculate and post the WIP, or follow steps 5 and 6 to do so manually (Microsoft Learn). Either way, the calculation runs against the task groups and the expense entries you already posted. This is why the first step in this post — posting expenses — comes before WIP.

Post WIP before you invoice. When the invoice goes out, you reverse or relieve the WIP and recognize the revenue against the receivable. The record moves from "work done, unbilled" to "work done, billed." Nothing is lost in the handoff because both states existed in the books.

If you invoice without posting WIP, your profit and loss statement shows cost with no offsetting work-in-process asset. Your balance sheet looks underweight. Your project profitability report shows a loss for the period the job was in the field, then a windfall the period the invoice hit. Both readings are wrong.

Compare the three costs side by side

Here is how the three kinds of cost differ, and where each sits in the books.

Cost typeWhen you post itWhere it landsWhat it tells you
Direct expensesAs incurred, before invoiceJob cost, credit cash or APWhat the job consumed
Work in processBefore invoice, after expensesWIP value in the general booksValue of unbilled work
Budget varianceNot posted; review before invoiceVariance report against planHow actual compares to budget

Read the table in order: expenses first, then WIP, then the variance check.

Show budget variance before you close the job

The third item is not posted the same way as the first two. Budget variance is a check, not a journal entry. But it belongs in your pre-invoice routine because it is the check that catches mistakes before the customer sees them.

To account for actual sales and expenses differing from budgeted sales and expenses, companies often create flexible budgets that allow budgets to fluctuate with future demand (OpenStax, Principles of Managerial Accounting). For a service shop, a practical version of this is to scale the budget for a job with the hours worked and the parts used, not with the number you wrote at estimate time.

Run the variance after expenses and WIP are posted; the job-cost comparisons guide lists checks to run. If actual cost is wildly above the flexible budget, something is wrong: a mis-coded entry, a missed change order, or a scope problem. Catch it now. The customer has not yet received an invoice built on a bad number.

If variance is under budget, resist the urge to quietly pocket the difference. Confirm the job is truly complete. Unbilled scope shows up as low variance and an incomplete punch list at the same time.

The variance conversation with the customer

A clean variance report lets you invoice with confidence. You know the cost side matches the books. You know WIP is ready to relieve when the invoice posts. You know the plan and the actual differ by an amount you can explain.

If variance is large and the cause is a change the customer approved verbally, now is the time to get it in writing before the invoice. If the cause is your own estimating miss, decide whether to absorb it or raise it. Either way, you are deciding with full information rather than discovering the gap after the invoice is out.

Illustrative example: one service job

Suppose a crew posts 3 parts entries and 1 subcontractor entry to a job, all coded to its job number. Together they total $1000. The work is finished, but the invoice has not gone out, so work in process holds the value of that unbilled work. Once the invoice posts, WIP is relieved and the invoice is drawn from the posted costs. Before billing, compare the $1000 of actual cost with the flexible plan. If the plan for this volume is well below $1000, look for a mis-coded entry or an unapproved change before the customer sees the bill.

Retention and final completion

Some of your work carries retention. Money is held back from progress payments until the job is finished. That retained amount is an asset you expect to collect, and it deserves a place in your pre-invoice review. For the subcontractor side, see retainage figures.

Ohio's Revised Code covers this directly for public work. Any retained funds withheld after substantial completion of, occupation of, use of, or acceptance of the project, and pending final completion of the project, and interest thereon accrued, must be paid to the primary contractor not later than thirty days after the date of final completion of the project (Ohio Laws, ORC Section 153.13).

If your shop does public work in Ohio, that deadline shapes your job close. Final completion starts the clock. Your books should already show the retention as an asset by then, because the expenses and WIP behind it were posted long before. You are not creating the record at the deadline. You are pointing at a record that exists.

For private service work, retention terms come from your contract. Whatever the terms, the principle holds: post the cost, value the work, then invoice. Retention is simply a portion of the invoice you already understand.

A closeout sequence that works

Bring the three costs together in a repeatable order. This is the sequence your dispatcher and your bookkeeper should both know.

  • Post direct expenses to the job number. Do this while the cost details are fresh and the crew's notes are still available.
  • Calculate and post work in process. Group tasks are valued separately, so review the groups before you post.
  • Run budget variance against the flexible plan. Confirm actual cost matches the plan, or explain the gap.
  • Confirm retention treatment. Check the contract or, on Ohio public work, the statutory final-completion deadline.
  • Draft the invoice from the posted books. The invoice becomes a readout, not a research project.
  • Relieve WIP when the invoice posts. The asset becomes a receivable. Nothing is lost between the two.

Run this once on your next job. The first pass will surface mis-coded costs and tasks sitting in the wrong group. The second pass will feel routine. By the third, your invoice and your project reports will tell the same story without anyone staying late to reconcile them.

Next step today: pick one open job and check that every cost on it carries its job number before you draft the next invoice.

Common questions

What happens if I invoice before posting expenses? Your receivable exists with no matching cost. Profit looks high until the expenses post, then snaps down. The invoice itself is fine, but the books behind it were wrong for the period in between.

Do I need WIP if I invoice at job completion? Short jobs may not show a meaningful gap. Longer jobs will. Any job where cost is incurred more than a billing cycle before the invoice benefits from WIP. Without it, the general books underreport the value of work already done.

Which tasks should not carry WIP? Posting-type tasks are excluded from the WIP calculation in Business Central. Cost coded to those tasks must be posted directly rather than expected to flow through the WIP groups. Check your task setup before you rely on the calculation.

How does budget variance relate to the invoice? Variance does not change the invoice amount. It flags whether the amount needs review before the bill goes out. If actual cost far exceeds the flexible plan, you either have a coding error, an unrecorded change, or a real overage to discuss with the customer first.

What if my state has retention rules like Ohio's? Ohio's thirty-day post-final-completion rule applies to Ohio public work. Your state may differ, and your contract may add its own terms. Ask your state's construction board or your attorney which rule governs your jobs, then build that deadline into your closeout checklist.

Sources

More field guides