Accounting & bookkeeping
Project Accounting: Correct a Misallocated Project Cost
Project accounting associates work and costs with the project that incurred them. A total can be correct for the organization while one project is overstated and another understated. This exercise follows project codes and correction evidence; it does not calculate remaining budget or make a revenue-recognition decision.
Read the project-coded source records
The fictional projects are Atlas and Birch. The approved practice labor rate is 25 per hour. A shared service charge of 90 has an explicitly approved allocation of 60 to Atlas and 30 to Birch. Those allocation amounts are supplied assumptions, not a general rule.
Original source sheet
T-11: Atlas, 6 hours, 150.
T-12: Birch, 4 hours, 100.
T-13: coded Atlas, 2 hours, 50; the approved task record identifies Birch as the project that received this work.
S-07: shared charge, 90; approved split Atlas 60 and Birch 30.
Calculate the initial and corrected subtotals
Before correction, Atlas contains 150 + 50 + 60 = 260 and Birch contains 100 + 30 = 130. Their combined total is 390. The task-record evidence identifies T-13 as a classification error, not a new cost.
Original cost-transfer proposal
Transfer reference CT-04: move the T-13 allocation of 50 from Atlas to Birch, subject to approval.
Corrected Atlas = 260 − 50 = 210.
Corrected Birch = 130 + 50 = 180.
Combined cost remains 210 + 180 = 390.
Preserve the correction lineage
The proposed transfer should identify the original line, old and new project code, amount, reason, supporting task record and review status. Preserve T-13 and link CT-04 rather than deleting the original line and pretending it never existed.
OpenStax’s job-cost discussion distinguishes tracing costs to jobs from the organization’s aggregate amount. This case applies that distinction to supplied codes: the correction changes the project view, while the combined cost stays constant. No additional expense is created by the stated reallocation.
Give an answer that separates proposal from approval
A reviewer should be able to see which values describe the current record and which describe the proposed corrected view.
Original practice explanation
“The current allocation totals 390 but puts 50 on the wrong project. Based on the approved task record, I propose CT-04 from Atlas to Birch. If approved, the project subtotals become 210 and 180; the combined total stays 390.”
Avoid a balancing transfer without evidence
Do not move costs merely because one project appears over budget. Here the task record, not a desired financial result, supplies the reason. Also do not change the labor rate to force the project subtotal to a preferred amount.
To check your understanding, imagine CT-04 is entered on Birch but not removed from Atlas. The combined total would rise to 440, exposing a duplicate allocation. Conservation of the combined total is a useful check, but it does not replace checking the correct receiving project.
Questions, answered
Can a correct total contain a wrong project allocation?
Yes. The initial combined total is 390, but T-13 assigns 50 to the wrong project.
Should the original line be silently replaced?
No. This exercise retains the source and links a documented, reviewed transfer proposal.
Sources and examples
ResumizeAI team. Examples are fictional teaching material, not customer results. Replace sample details with your own facts.
Your experience. A complete resume.
Build in Resumize with ATS-friendly templates, guided editing and a live preview. Start free, then upgrade when you need more.
Free account required. Free-plan PDF exports include a watermark.