When a valid construction cost is posted to the wrong job, preserve the source document and original posting before making an approved correction. Then compare both affected job reports before and after the change. The company-wide cost should remain the same when only the job assignment changes.
This is different from a corrected vendor invoice. The vendor, amount, and obligation may all be right while the internal job reference is wrong.
Prove the intended job before changing the record
Collect the invoice, purchase or work-order reference, delivery location, approval, and any field note that identifies the job receiving the materials or service. A familiar vendor name is not enough because the same supplier may serve several active jobs.
The IRS identifies invoices, receipts, paid bills, and proof of payment as supporting business records.1 A combination of documents may be needed to show the business purpose. Keep those documents with the correction rather than replacing them with a spreadsheet note.
Build a six-field correction bridge
Use a correction ID and record:
- the original transaction and source-document references;
- the incorrectly assigned job and cost code;
- the supported job and cost code;
- the evidence and approval for the change;
- the method and date used under the firm’s accounting process; and
- the before-and-after totals for both jobs and the company.
QuickBooks documents that job-related transactions can be assigned through the Customer/Project field when the Projects feature is used.2 Product access and navigation depend on the current subscription and setup. The bookkeeping control here applies regardless of software: change the job dimension only after the intended project is supported.
Worked example: the company total should not move
Illustrative example. A $6,400 lumber invoice is valid and already approved, but it was posted to Job C-219. The invoice, delivery ticket, and purchase-order reference all identify Job C-214. The project manager confirms the intended job under the contractor’s approval map.
| Report point | Job C-214 | Job C-219 | Company total |
|---|---|---|---|
| Before correction | $0 | $6,400 | $6,400 |
| Approved job reassignment | $6,400 | ($6,400) | $0 |
| After correction | $6,400 | $0 | $6,400 |
The bridge proves that the correction changed job reporting without creating a second company expense or deleting the source invoice. The responsible accountant determines the exact transaction method and accounting period, especially if a prior period is closed.
Check every connected record
A job reassignment can affect more than one report. Review the commitment or purchase-order link, vendor bill, job-cost detail, cost-code report, payment reference, and any exported project report that depends on the same job field.
Do not change the vendor document to manufacture a new job reference. Add the approved internal correction ID and preserve the invoice as received. If one invoice truly covers two jobs, document the supported allocation instead of moving the entire amount to one project.
Stop when the evidence is incomplete
Keep the item in an exception queue when:
- the invoice and delivery ticket identify different jobs;
- the project manager has not approved the intended assignment;
- a prior-period report was already issued and the correction timing is undecided;
- the transaction is duplicated rather than merely miscoded; or
- changing the job also changes an account, entity, vendor, or amount.
Those facts require a broader review. A wrong-job bridge should not hide a duplicate bill, altered vendor obligation, or cross-entity transaction.
Close with a two-direction check
Open Job C-214 and trace the added cost back to the invoice and correction approval. Then open Job C-219 and confirm the cost no longer appears there while the original transaction remains traceable. Finally, verify the company-wide total is unchanged and record the correction in the month-end review log.
Use the completed-job exception guide when one of the affected jobs is already closed. Use the vendor coding guide to prevent the same job-reference problem in future intake.
Footnotes
Sources and further reading
Source links provide background. The workflow and illustrative examples above are original educational material.