Project Financials and company Accounting: where the records meet

A project manager and a controller can look at the same job and ask different questions. The PM wants to know what the work should cost, what has been committed and what might change. The controller needs to know what has been posted to the company’s books. Those numbers are related, but they do not mean the same thing.

Start with the project record

Project Financials holds the budget, contracts, commitments, change events and orders, direct costs and payment applications. A budget is a plan; a subcontract or purchase order is a commitment to buy work or materials. A pending change describes possible exposure. An approved change can affect the project budget or commitment, depending on its type. None of those facts by itself means cash has moved or an expense has been posted to the general ledger.

For example, a $100,000 subcontract with a $10,000 approved commitment change represents $110,000 of committed scope. If a $30,000 bill arrives, the team should check its scope, coding and progress against that commitment. The bill is a separate accounting document: approval and posting determine the accounting entry. Retainage may affect what is currently payable without reducing the gross cost of the work.

The company books answer a different question

Company Accounting is organized around entities, accounts, periods and posted transactions. Its AP implementation can reference a project commitment and compare bills with commitment lines, approved commitment changes and, for purchase orders, receipts. The accounting job-cost forecast implementation brings together project budget and approved commitment sources with posted job-cost entries. It treats pending changes separately and does not turn the forecast into a journal entry.

These are implemented workflows, not a promise that every company has access to them or that every project record posts automatically. The forecast requires an entity assignment and has coverage limits; for instance, it cannot reconstruct a project source that was edited after the selected historical date. Review the source and cutoff before using a forecast for close.

Keep the handoffs visible

Project payment applications and cash allocations are distinct from accounting AR invoices and receipts. An automatic project pay-app or cash bridge is not available in the accounting workflow. Do not enter the same real-world receipt twice and assume the two records reconcile themselves. Agree on the book of record and a manual tie-out with your controller.

The accounting import implementation supports a bounded CSV journal workflow with review and approval, limited to base-currency GL accounts. It does not provide connected vendor transport, dimensional or subledger imports. QuickBooks, Sage and Vista code or design references are not evidence of a working live sync. Confirm availability and scope before planning a migration.

WIP locking and posting are unfinished, and historical as-of AR aging is not established by the current AR workflow. Continue your existing close and aging procedures. For a practical AP review, see the construction three-way match; for the underlying project change process, see change events and change orders.