How to Track Retainage in QuickBooks by Job

Track earned, billed, retained, eligible-for-release and paid amounts separately. Each represents a different stage in the job's billing process.

Retainage is an amount withheld under the contract's payment terms. The percentage and conditions for release depend on the agreement and applicable rules. Do not treat an example percentage as a rule for every job.

For each job, distinguish the amount earned, the amount included in a billing application, the retained amount, the amount eligible for release and the cash received. These describe different stages. A signed-off pay application does not prove payment, and a book balance does not establish that release conditions have been met.

Have your accountant verify the retainage account and invoice-item setup, then test withholding, release and payment on one job before using it broadly.

A common approach uses a retainage receivable account and an invoice item to separate the withheld portion from the amount currently due. Have your accountant verify the account mapping, tax treatment and cash-versus-accrual reporting before using it.

Use one test job to follow the entire cycle: progress billing, withholding, release billing and payment. Check the customer balance, job or project reports, receivables and general ledger at each stage. This is more useful than assuming a copied invoice example must produce the right reports.

Keep the job assignment on the relevant transactions. If your reports cannot answer a job-level question, establish whether the cause is missing assignments, the report configuration, a product limitation or a genuinely separate workflow.

Identify who checks release conditions, raises the release invoice and follows up on payment. Keep that work connected to the accounting record.

Ask who knows when release can be requested. Where is the supporting document? Who checks that a release invoice was actually raised, follows up when it remains unpaid and hands that task over when someone is away?

An accompanying register can hold the job reference, source billing document, release condition, next action and supporting evidence. It should point back to the accounting records rather than become an unexplained second balance.

If the existing product and a clear procedure answer those questions, use them. An automation project should address the remaining gap, not recreate features you already have.

Our documented case study tests pay-application values and formatting against a source file. It does not establish universal QuickBooks limitations or guaranteed savings.

Our AIA billing case study describes a system checked against a contractor's existing pay application. The documented tests compare generated values and formatting with the source file.

That is evidence about document reproduction and reconciliation checks. It is not evidence that QuickBooks lacks project reporting, that every monthly task has disappeared, or that a new reader will achieve a particular saving. A person still reviews the application before it is sent.

Trace one retained amount through billing, accounting, release conditions and payment. Use the gaps you observe to choose configuration, a clearer handoff or automation.

Choose a recent job and trace one retained amount from the source application to the accounting entry, release conditions and eventual payment. Write down where someone has to search, re-enter a value or ask the only person who knows.

That gives us something concrete to review together. We can identify whether the next step is configuration, a clearer handoff or a defined automation build. The aim is a process your team can operate on its own, with records it can check.