Field note · 18 June 2026

What belongs in a permit payment file?

A practical record list for tracing development permit application payments from assessment to municipal receipt.

Organised paper files with handwritten labels

An EFT confirmation proves that an instruction was processed. It does not, by itself, prove that a municipality allocated the money to the intended development application. A useful payment file connects the assessment, transfer and receipt.

Begin with the authority’s request

Keep the invoice, assessment notice or portal screen that states the amount due. Record the date it was downloaded because fee schedules and portal balances can change. If the calculation uses floor area, property value or an application category, retain the supporting schedule submitted by the professional team.

Preserve the payment instruction

The bank confirmation should show the beneficiary, date, amount and reference exactly as entered. Where a managing agent, architect or town planner paid on the applicant’s behalf, request both their remittance note and proof of transfer. This prevents the consultant’s internal invoice from being mistaken for municipal evidence.

Close the loop with a receipt

A municipal receipt or updated account should carry an application, property or customer reference that can be tied back to the file. If the reference differs, preserve correspondence explaining the allocation. A screenshot without a date or page context is weak evidence; save the complete page as a PDF where permitted.

Keep a short chronology

One line per assessment, payment, receipt, adjustment and resubmission is enough. The chronology quickly exposes payments that pre-date an invoice, repeated amounts, and balances that reappear after an amended submission.

Your own application

Turn scattered records into a traceable account.

Discuss an audit