On this page
A useful accounting rollout proves one complete cycle: a transaction enters, someone reviews it, the ledger records it, cash reconciles and the period closes with evidence. Learn the Accounting module in that order. Each app handles a part of the cycle; the general ledger connects the results.
1. Establish the books before entering activity
The controller defines the entity, base currency, chart of accounts, control-account mappings and fiscal calendar. Grant company Accounting access and the right entity scope, with different people preparing and approving. Project Financials permissions do not grant accounting authority.
For a migration, reconcile your source exports at one cutover date. Import master data, then open AP and AR, then the opening trial balance. The control balances must agree with the imported documents. Payroll year-to-date wages have their own import and need verification before the first pay run. See setup and imports.
Evidence to keep: the approved account mappings, opening trial balance, open-document totals and import review. Completing an upload is not the same as proving the opening books.
2. Prove a purchase-to-payment workflow
Use the Accounts payable app for a representative vendor bill. Confirm the entity, project, cost code, commitment match and retainage. Attach the supporting invoice and review any compliance hold. Submit the bill for independent approval, then review and release its payment through the payment-run workflow.
For example, a $10,000 subcontract bill with $1,000 retainage represents $10,000 of cost, $9,000 currently payable and $1,000 held. Paying the current amount does not erase the retainage obligation. Follow the posted source through AP and the general ledger to confirm the coding and balances.
Evidence to keep: the bill, match exceptions, approval and payment reference. The construction three-way match explains the decisions behind those controls.
3. Prove a billing-to-cash workflow
Use the Accounts receivable app for the owner billing. For progress work, the supported handoff starts with a certified owner pay application and creates an invoice with linked schedule-of-values lines and retainage. Review and post it in accounting. Record a draft receipt, allocate it to eligible invoice lines and review any unapplied cash. Have a different authorized reviewer approve it, then post the approved receipt before grouping it with other eligible posted receipts into a deposit.
Separate the milestones: approved work, posted billing, received cash and a cleared bank deposit answer different questions. A receipt can pay current AR while retainage stays open. See progress billing, receivables and banking.
Evidence to keep: the certified pay app, posted invoice, receipt allocations and deposit. Compare aging and the bank reconciliation using the same date.
4. Review labor, equipment and remaining cost
Run the applicable Payroll, Fixed assets and Leases workflows for the period, with their required approvals and posting steps. Then use Job cost inquiry to inspect posted actuals and Job cost forecast to review remaining commitments and PM cost-to-complete estimates. A budget is a plan; a posted cost is an accounting event; neither alone predicts the final cost.
For each job, assign an entity and resolve missing coding or source exceptions. Keep pending changes visible without silently treating them as approved contract value. See payroll, assets, leases, and job cost and WIP.
Evidence to keep: posted run references, approved forecast assumptions and explanations for material changes in projected margin.
5. Compute, review and post WIP
Compute the period-end WIP snapshot. Review its contract value, posted cost, billed amount, forecast and exceptions for every included job. A controller other than the preparer approves the revision before posting. A later posting can make the snapshot stale; resolve it with a new revision rather than accepting an old result because the total looks plausible.
The posted snapshot supports the WIP schedule and close tie-out. Review historical source coverage and apply your company’s revenue-recognition policy with its accounting advisers. The software’s calculation does not establish the right policy for a contract.
6. Close with a reviewable packet
Reconcile bank accounts, run the financial statements and subledger checks, and resolve the period’s blockers. Prepare the close checklist and have a different authorized person approve it. The app checks current evidence before closing; a changed balance may require another review. See financial reports and Close the month.
Evidence to keep: dated statements, reconciliations, the posted WIP revision, approvals and open follow-ups. A useful final review can answer who prepared each item, who approved it and which source explains the number.
Make the next cycle easier
Track exception causes rather than just counting completed tasks: missing commitment changes, miscoded costs, delayed receipts, stale forecasts or incomplete opening data. Assign each recurring issue to the team that can prevent it. Use project-to-accounting reconciliation for a joint PM/controller review and the Accounting app guide to choose the next workflow to learn.
Share this article