Project delivery systems answer whether work is progressing. Billing must answer a narrower question: which agreed event makes a specific amount chargeable now? Confusing those questions produces premature invoices, missing revenue and disputes that arrive after the team has moved on.
A controlled hand-off connects the commercial agreement to accepted delivery evidence, approved billable inputs and the outgoing review decision.
Separate progress from a commercial trigger
A percentage-complete update is useful for delivery management but may not authorise a charge. The contract might require a named milestone, acceptance record, approved time period or fixed calendar event.
Record the trigger in language finance can test. If acceptance is conditional, retain the condition and the evidence that it was met.
Preserve the source of every line
Fixed fees, time, expenses and usage can coexist on one project. Each line needs its own source, rate, period and approval state before the lines are assembled into an invoice.
Do not flatten a mixed project into one unexplained total. The customer may see a concise document, but finance should still be able to reconstruct the amount.
Control changes and exceptions
Scope changes should become approved commercial records before they become charges. A project note or chat message can describe a change without proving authority to bill it.
When a rate or milestone is overridden, retain the previous value, new value, approver and reason. An exception without ownership becomes the next invoice's precedent by accident.
Close the hand-off after sending
Delivery is not completion. Keep the customer receipt state, dispute owner, next collection action and payment match connected to the invoice.
If a project invoice is corrected, link the correction to the original version so delivery, finance and accounting are not working from different records.
Map the agreement into billable components
Begin with the commercial agreement, not the project dashboard. Break the arrangement into components such as fixed mobilisation, accepted milestones, approved time, reimbursable expenses and recurring support. For each component, record the customer, issuing entity, currency, amount or rate, billing trigger, evidence owner and effective dates. A project can use several components, but each one must have a decision rule finance can test independently.
This map prevents broad project status from becoming a substitute for billing authority. Eighty percent delivery may be meaningful to the project manager while producing no invoice if the next charge depends on formal acceptance. Conversely, an approved time period may be billable even when the overall project remains incomplete. Preserve both facts and allow the agreement to determine which one controls the charge.
Define a handoff package finance can verify
A project handoff should include the contract or order reference, customer and entity, billing component, service period, trigger date, acceptance evidence, approved quantity, rate source, change orders and customer-facing description. The handoff owner should confirm that the evidence belongs to the same version of the scope being billed. Finance should not have to infer whether a later project note replaced an earlier commercial instruction.
Use a visible exception state when the package is incomplete. Examples include acceptance received from an unauthorised contact, time approved without a client rate, an expense outside policy or a change order without an effective date. The exception stays attached to the proposed charge, has a named owner and records the resolution. Removing the charge from view or discussing it only in email makes the next billing cycle repeat the same investigation.
Control mixed fixed and variable invoices
Mixed invoices are useful when the customer expects one document, but the internal record must not collapse unlike sources into one unexplained total. Keep fixed fees tied to their schedule or milestone, time tied to approved entries and rates, expenses tied to receipts and policy, and usage tied to a closed quantity period. The invoice can present a concise summary while finance retains the underlying calculation for review and dispute handling.
Apply the same discipline to tax and currency context without making unsupported jurisdictional assumptions. The billing workflow should preserve the issuing entity, invoice currency, source amounts and identifiers required by the authorised accounting and tax process. Accounting remains responsible for ledger treatment. Stable identifiers let the project, invoice and ledger records be reconciled without pretending they are one system.
Handle change orders without rewriting history
A change order should state what changed, the commercial effect, who approved it and when it becomes effective. Link it to the original scope and preserve both versions. Work performed before approval may be operationally valid but should not become a customer charge unless the agreement and authorised decision permit it. Where provisional work is allowed, give it a separate state rather than presenting it as an approved invoice input.
When a change affects an invoice already under review, identify the affected lines and reopen the necessary decision. Keep prior calculations and approval timestamps so reviewers can see what changed. After sending, use a controlled correction or credit process appropriate to the situation instead of editing the issued record. The goal is an audit trail another person can follow from agreement through correction.
Close the loop after the invoice is sent
The project-to-billing handoff is not complete at send. Retain delivery evidence, customer questions, dispute classification, collection owner, payment references and any remaining balance against the invoice. Feed a dispute about scope, acceptance or rate back to the commercial and project owners with the exact line and source involved. This improves future handoffs without obscuring the current receivable.
Review one difficult project at period close. Confirm that every proposed line has a trigger and source, every exception has an owner, every approved change has an effective date and every sent invoice can be matched to its project and accounting identifiers. The review should expose missing records before they become customer-facing errors or unexplained differences between delivery, billing and the ledger.
Decision summary
Keep the commercial trigger and source evidence visible for every material charge.
Separate preparation, review, correction, sending and accounting responsibilities.
Retain versions, reasons, owners and timestamps whenever a decision changes.
Test the control with one difficult invoice another authorised person can reproduce.
Put the control into practice
Choose a project with fixed and variable work. Trace one invoice from contract to payment. Any step that depends on memory rather than a retained record is a hand-off to redesign.
Run the review on a real case
A project is reported as 80 percent complete, but the contract bills only on accepted milestones. Finance should ignore the progress percentage for invoicing and wait for the named acceptance event. Approved time can be billed separately only when the agreement creates that second trigger.
The hand-off is complete when the project team supplies the contract reference, accepted deliverable, approval evidence, authorised time, change orders and the customer-facing description that finance will use. Missing context becomes a visible exception rather than an inferred charge.
Case-review checklist
Commercial trigger is explicit
Acceptance evidence names the authority
Approved time is separated from recorded time
Change orders carry effective dates
Invoice review retains the source trail
Project status remains useful for delivery management. It becomes billing evidence only where the agreement says it does; the page should never encourage finance to convert general progress into an amount by assumption.
Continue in context