Foreign advances: connect the contract, receipt and later invoices

Build a clear working record when a customer pays before the final export invoice is issued.

An advance arrives before all the later invoicing or delivery events exist. That makes it easy to lose the connection between the early receipt and the completed work. Start with the contract reference and maintain the link as invoices are raised, payments are adjusted or the engagement changes.

Open an advance record with its own reference

Save the agreement, expected service or milestone, payer details and receipt evidence. Record whether the amount is intended for one invoice or a series of milestones. Avoid inventing a final invoice date while work is still pending. Keep the advance visible as a receipt awaiting allocation rather than treating it as several unrelated new payments later.

Follow the allocation and any change of plan

When invoices are issued, record how much of the advance is applied to each. If the project is cancelled or the route changes, preserve the correspondence and ask the bank how it should be handled. A refund, an allocation and a proposed adjustment are different actions. Keep evidence of the actual action and the bank’s response before marking the record finished.

Distinguish an advance from a paid invoice

Record the document supporting the early payment, such as the contract or milestone schedule, and explain what it is intended to fund. An advance may precede the final invoice, so the record should not invent an invoice reference or date that does not yet exist. Use a stable internal advance reference and link the issued commercial documents when they become available.

Keep the actual receipt currency, payer and transfer evidence. If a provider deducts charges, preserve those separately. A working entry showing an advance received is not a final declaration about how the authority treats the transaction. Ask the bank about the process appropriate to the arrangement and retain the response with the contract and receipt.

Allocate an advance across milestones carefully

When the customer is invoiced, record the amount of the advance applied to each invoice. Keep the remaining unapplied advance visible. An advance used against two milestones must not be allocated in full to both. Compare the allocation total with the original receipt evidence and any supported adjustments or refunds.

Show the invoice’s full commercial amount and the advance allocation separately. Otherwise the final invoice list can understate the agreed work by presenting only the remaining cash due. Keep customer instructions or contract terms supporting the allocation. If the customer changes which milestone the advance funds, preserve the correspondence and update the working allocation with an explanation rather than erasing the earlier record.

Handle cancellation, refund and route changes as new events

If work is cancelled, identify whether the advance is refundable, partly applied or still under discussion using the actual agreement and correspondence. Do not record a refund until there is evidence of the payment being returned. Ask the bank about the required handling and supporting records before treating an unresolved advance as finished.

If the bank or receipt route changes during the project, explain the original and proposed routes to the institutions involved. Preserve instructions and references rather than moving the advance silently between unrelated working files. A chronological note should connect the initial receipt, work performed, invoices issued, allocations and any later return or adjustment. This gives the reviewer a complete story instead of an isolated early bank credit.

A fictional example

A customer advances AUD 500 toward a later AUD 2,000 engagement. The working file keeps the AUD 500 receipt and links it to the final invoice. The invoice is not reduced to AUD 1,500 merely to hide the advance allocation.

Preparation checklist

Keep the original contract reference.
Allocate advances once.
Ask about route changes and cancellations through the official desk.

Can a draft worksheet confirm the treatment of an advance?

No. It organises the facts for review; your bank confirms the applicable process.

FICTIONAL WALKTHROUGH

A deposit is applied to two project milestones

A fictional business receives EUR 600 in advance under a EUR 2,000 engagement. The contract specifies two later milestones. The preparer records the EUR 600 receipt under an advance reference, with the contract and transfer evidence, without inventing a final invoice at that stage.
When milestone invoices are issued, EUR 300 is applied to each. The invoices retain their full commercial values and the allocations show how the early receipt reduces later cash due. The working advance remainder becomes zero only after both supported allocations are recorded.
The customer subsequently requests a scope change. The exporter preserves the request and asks about any resulting document or process changes. It does not delete the advance history merely because its allocation balance is now zero.

Your next step

See the advance example

Sources and scope

Sources reviewed 9 October 2026. The routines and fictional examples are editorial preparation suggestions. They do not confirm your bank’s acceptance, classification or transaction status.