Reconcile mobilisation advances and recoveries on running bills

Identify the counterparty, contract, advance type, currency, approved amount, disbursement date and payment evidence. Distinguish an approved advance from money actually paid. If disbursement occurs in instalments, record each instalment separately.

Capture the reviewed recovery basis: when recovery starts, which bill value it applies to, applicable rates or stages, caps and any special treatment. These are contract-specific inputs. Do not assume that one percentage or commencement threshold fits every subcontract.

Track related security requirements, validity and review dates in linked records. A remaining advance balance and a valid security are different facts. Neither should be inferred from the other. Finance and commercial owners should confirm the applicable treatment and authority for changes.

A bill may be prepared, submitted, certified, posted and paid on different dates. Decide which stage the recovery schedule uses for its financial balance and show other stages separately where useful.

Autodesk's payment application guidance illustrates structured bill and payment-application workflows. The project's advance ledger should use its agreed accounting and contractual basis rather than assuming every submitted deduction has already settled the advance.

For each recovery, retain the bill reference, version, base amount, rate or calculation basis, recovery amount and status. Link the posted accounting entry where applicable. This makes it possible to reconcile the schedule without treating a provisional bill as a final transaction.

For the recovery example, assume ₹10 lakh has actually been disbursed. Two valid posted recoveries are ₹2 lakh and ₹3 lakh. With no other adjustments, the outstanding balance is ₹5 lakh.

If a replacement bill later produces a valid ₹2.5 lakh recovery, the balance becomes ₹5.5 lakh. The replacement should reference the cancelled bill and reversal. Simply appending ₹2.5 lakh to the original ₹5 lakh balance would incorrectly show ₹2.5 lakh remaining.

These figures illustrate the movement logic only. The actual recovery amounts must follow the reviewed contract terms and finance policy, including the treatment of certification, posting and settlement.

The schedule should calculate the proposed recovery from the applicable bill basis and limit it to the amount permitted by the contract and the supported outstanding balance. If the proposed deduction exceeds the remaining recoverable amount, show the exception for review rather than allowing a negative balance silently.

Handle rounding consistently and document the final-bill treatment. Small residuals can remain after repeated percentage calculations. The responsible finance owner should define how they are resolved under the agreement and accounting policy.

If a recovery is deferred or modified, record the authority, reason, effective period and revised expectation. Do not change the historical rate to make the new balance appear correct. Preserve the original terms and the approved amendment or exception.

A subcontract may include mobilisation, material or other advances with different conditions. Track them as separate balances unless the agreement and accounting design explicitly combine them. A recovery intended for one advance should not reduce another simply because both share the same vendor code.

Where several contracts exist with one counterparty, reconcile by contract as well as supplier. Cross-adjustments require the appropriate authority and evidence. A net vendor balance alone may conceal an unrecovered advance on a closed package.

For client advances received by the contractor, maintain a separate schedule from advances paid to subcontractors. Their recovery timing and obligations can differ. Use the project cash forecast to show the combined timing effect without merging the underlying balances.

Before final billing or package closure, reconcile disbursements, recoveries, reversals and remaining balances with finance. Review any unposted or disputed bills that could change the position. Confirm the treatment of related securities through the applicable approval process.

Do not release a security solely because a spreadsheet shows zero. Verify the ledger and the contractual conditions, including any other obligations the security covers. Conversely, an expired instrument does not prove that the underlying advance has been recovered.

Assign owners to residual balances and unresolved deductions. A small balance may be a rounding issue; a large one may reflect cancelled work, insufficient future bills or a dispute. The next action should follow the actual cause.

Run the ₹10 lakh example through the configured system, including cancellation and replacement of the second recovery. Confirm that the outstanding balance returns to ₹8 lakh before the replacement is applied.

Also test a final recovery larger than the remaining balance, a deferred recovery and two advance types on the same contract. The system should preserve the distinction and require the defined authority for exceptions.

At period-end, compare the schedule with the relevant ledger accounts and source bills. Investigate differences by transaction identity rather than adjusting the total manually. A reconciled balance should be reproducible from the valid movements.

An advance schedule is useful when procurement, commercial and finance teams can agree what has been paid, what has been recovered and what remains subject to action. That agreement depends on transaction history as much as calculation.

1. Record actual disbursements separately from approved advance limits.
2. Validate the recovery basis and reporting stage for each contract.
3. Link recoveries to bill versions and accounting evidence.
4. Reverse cancelled transactions before applying replacements.
5. Reconcile remaining balances and security conditions before closeout.