What it means
A project reaches technical completion, and finance prepares the final invoice. A missing acceptance record, unresolved change or unapproved retainage amount can make that invoice premature or wrong.
Project final invoice readiness rate measures the share of eligible closeout cases with all required billing checks complete before finalization. Define the final invoice, since it may settle the original contract, approved changes and withheld amounts, but the composition depends on the agreement.
Oracle describes a project contract invoice approval workflow where assigned reviewers approve, reject or seek more information, and PMI discusses work acceptance and contract closeout as distinct activities. These are process guides, not automatic authority to bill.
Choose the cohort to include projects or contract lines that reached a declared final-bill review stage, and build a checklist, since accepted deliverables, approved variations, billing terms, tax details and prior invoice reconciliation may apply. Verify the customer entity, because bill-to name and purchase order can differ among projects for the same corporate group, and check the contract version so the final invoice reflects authorized amendments, not an obsolete schedule of values.
Reconcile previous bills so deposits, progress invoices, credits and retention are not charged twice. Check unbilled work, since some items may be eligible for a final claim while others remain disputed or unapproved, and record acceptance, because a project manager's done status may not satisfy a signed-customer-acceptance condition.
Review retainage, as a release request and the final invoice may be distinct under the agreement, and check tax treatment, since place, service and timing can matter and qualified review is needed for jurisdiction-specific rules. Distinguish a draft, because a complete draft ready for approval is not necessarily authorized for delivery.
Define readiness to require verified documentation and correct calculation, not merely nonempty fields, and check amounts by summing original contract, authorized changes and credits against the agreed total and previous invoicing. Show open cases, because a high ready percentage among reviewed cases can hide projects still waiting for closeout evidence, and count one unit, as project, final invoice and contract line are not interchangeable denominators.
Handle conditional acceptance by verifying whether the contract permits billing with a punch list or prohibits it, and preserve disputes so an unresolved customer claim is not silently netted against the final invoice without authority. Check currency, since contract and ledger currency differences need documented exchange treatment, and avoid duplicate release because a separate progress invoice issued at month-end may overlap the intended final amount.
Track approval, as finance, project owner and legal may have different review roles for material closeout, and separate issuance, because readiness rate says what could be finalised under the process and is not the percentage already sent. Protect the customer relationship, since an incorrect final bill can damage trust even if a credit is possible later; audit a sample by tracing the draft amount to signed terms, accepted work and all prior billings, keep time context because a ready case can become not ready if a late amendment or credit arrives before issuance, include the customer submission route (a portal, purchase order reference or supporting statement) without assuming permission to send, record any contractual final-claim window and seek qualified review if delay could waive rights, and use the rate to prevent preventable final-billing errors without forcing unresolved obligations into closure.
In practice
Real-world examples.
Example
A final invoice draft ties accepted work, signed changes and earlier progress invoices to the approved contract total. The reviewer initials each tie-out before the draft moves to approval.
Example
A draft includes an unsigned variation and fails readiness until its status is resolved. Finance removes the amount from the draft and lists it separately as a disputed item.
Example
A retainage amount already billed separately is removed from a duplicate final-bill line. The corrected draft shows the retention release as its own reference.
Formula
Calculation
Illustrative readiness rate = eligible final-bill cases passing every applicable documented control / all eligible cases checked x 100. Report blocked cases and amounts separately.
Worked example. A fictional finance team checks 25 eligible closeout cases. Twenty pass every control, while five are blocked by an unsigned variation, a missing acceptance record or an unreconciled progress invoice.
- Readiness rate = 20 / 25 x 100 = 80%.
- For one ready case, the draft check is an original contract of $500,000 plus approved changes of $40,000, giving $540,000; less $450,000 already billed, the final invoice draft is $90,000.
- The five blocked cases are listed with their amounts, so management can see how much billing is waiting on documentation.Case study
Seen in the real world.
This entirely fictional case follows Cedar Engineering. Finance drafted a final invoice after project completion but found a change order still under customer review. It kept the disputed amount separate, reconciled prior billings and waited for the authorized decision before finalising the correct draft. This case does not authorize sending any real invoice.
Watch out
Common mistakes.
- Treating internal completion as proof all billing conditions are met.
- Charging an unapproved change or previously invoiced retention twice.
- Calling a ready draft a sent or paid invoice.
Questions
People also ask.
Does readiness mean the invoice can be sent now?
Only after the remaining approval and delivery rules are met.
Can a disputed amount be included?
Check the governing contract and authorized review rather than assuming.
Is final invoice readiness revenue recognition?
No. Accounting recognition is a separate determination.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related