Government and defence contracting in Australia operates under procurement frameworks and contract structures that have no equivalent in commercial engagements. The Australian Standard for Defence Contracting (ASDEFCON) suite governs how most Department of Defence contracts are structured, and the Commonwealth Procurement Rules (CPRs) dictate how invoices must be submitted and how payments are processed. Bookkeepers who apply generic project-accounting approaches to these engagements will misstate revenue, mishandle retentions, and potentially create fringe benefits tax exposure where none exists — or miss it where it does.
ASDEFCON Contract Structure and Performance Obligations
ASDEFCON contracts are structured around a Statement of Work (SOW) that identifies discrete deliverables, milestones, and acceptance events. For revenue recognition under AASB 15 Revenue from Contracts with Customers, the first question is whether the contract contains a single performance obligation or multiple distinct obligations.
In most ASDEFCON contracts, the deliverables are highly interdependent — a complex defence system cannot be used in isolation from its documentation, training, and support components. Under AASB 15.27–29, this interdependence means the contract is likely a single performance obligation recognised over time, not a series of distinct deliverables each triggering separate revenue events.
The practical consequence: revenue is recognised using either the percentage-completion method (input or output measures) or the completed-contract method. For long-duration contracts (3–7 years is common in major capability programmes), percentage completion is almost always appropriate. The completed-contract method defers all revenue to final customer acceptance — which is technically permissible under AASB 15.38(c) only if the outcome cannot be reliably estimated.
Progress Billing vs. Milestone Acceptance Billing
Commonwealth procurement creates an important distinction that bookkeepers often conflate.
Progress billing occurs when the contractor invoices periodically based on costs incurred or work performed, often monthly or quarterly, before any formal acceptance event. These invoices are essentially payment on account — the contractor is drawing down on the contract value as work proceeds. Under AASB 15, revenue recognition follows the performance obligation completion curve, not the billing schedule. If billings exceed revenue recognised to date, the excess is a contract liability (deferred revenue). If revenue recognised exceeds billings, the balance is a contract asset (unbilled revenue or WIP).
Milestone acceptance billing ties each invoice to a specific contractual event — delivery of a design review, completion of a test phase, acceptance of a sub-system by the Commonwealth's authorised representative. Each milestone may constitute a separate billing trigger in the contract, but under AASB 15 that does not make each milestone a separate performance obligation unless it is genuinely distinct and the customer can benefit from it independently.
Invoice submission under CPRs requires a valid purchase order (PO) reference, the correct Commonwealth entity identifier, and GST-compliant tax invoice format. Submissions without a valid PO reference are commonly rejected and delayed — this creates a cash flow gap that does not represent a revenue recognition issue, but does affect the debtor ageing and needs to be tracked separately from ordinary commercial debtors.
WIP Measurement and the Percentage-Completion Calculation
For contracts recognised over time, the percentage-completion rate drives the revenue recognised in each period. Under AASB 15.B16–B19, the input method (costs incurred to date as a proportion of total estimated contract costs) is the most commonly applied method for defence contracts.
The bookkeeper must maintain a WIP schedule for each contract showing:
- Total contracted revenue (including approved variations)
- Total estimated costs to complete
- Costs incurred to date
- Percentage complete (costs incurred ÷ total estimated costs)
- Revenue recognised to date
- Revenue to recognise in the current period
- Billings to date and the resulting contract asset or liability
The WIP schedule is not optional — it is the audit support document for every revenue entry on a defence contract. Any change in the estimated total cost to complete (cost overrun, scope change, unresolved variation) flows directly through to the percentage-completion calculation and requires immediate reassessment of the revenue trajectory.
Security Clearance Costs and FBT
Defence contractors and Commonwealth agencies routinely require personnel to hold security clearances issued by the Australian Government Security Vetting Agency (AGSVA) for NV1/NV2 levels, or by the ADF for lower classifications. Clearance costs can run to several thousand dollars per individual for higher-level vettings.
The fringe benefits tax question is whether paying for an employee's security clearance constitutes a fringe benefit. The answer turns on who benefits from the clearance. Under the Fringe Benefits Tax Assessment Act 1986 (FBTAA), a fringe benefit arises when an employer provides a benefit to an employee in respect of their employment. But where the benefit is required as a condition of performing work for a specific Commonwealth client — and the clearance is not portable to other employers or personal in nature — the prevailing analysis is that the benefit flows to the employer (to enable contract performance) and to the Commonwealth (to satisfy its security obligations), not primarily to the employee.
The ATO has not issued a specific ruling on AGSVA clearance costs, but the principle that employer-directed, work-essential expenditure is not a fringe benefit (consistent with the analysis in Essenbourne Pty Ltd v FCT [2002]) supports treating these costs as ordinary business expenses deductible under s.8-1 ITAA 1997, with no FBT liability. Document the contractual requirement for the clearance in the employee's file.
Export Market Development Grants as Assessable Income
Defence exporters and dual-use technology companies that market their products internationally may receive Export Market Development Grants (EMDG) from Austrade. EMDG payments are assessable income under s.6-5 ITAA 1997 in the income year in which they are received. They are not a capital receipt and not a government grant that requires deferred income treatment.
For GST purposes, EMDG payments are not consideration for a supply — the exporter is not providing a taxable supply to Austrade in exchange for the grant. Accordingly, no GST is payable and no tax invoice is issued to Austrade. The journal entry is simply: debit bank account, credit other income (assessable government grant).
Retentions: Revenue Recognised, Cash Not Received
ASDEFCON contracts commonly include a retention clause — typically 5–10% of each progress payment is held back by the Commonwealth until final acceptance of the deliverable or expiry of the defect liability period. The retention creates a split between revenue recognised under AASB 15 and cash received.
The revenue is recognised as the work is performed — the retention is not a refundable amount contingent on future performance obligations (assuming the defect liability period represents a standard warranty, not a distinct service obligation). The retained amount is a debtor on the balance sheet, sitting in a separate ledger account (retentions receivable) with an expected collection date tied to the final acceptance event. At year end, classify retentions due within 12 months as current and those due beyond 12 months as non-current.
End-of-Period Checklist for Defence Contractor Bookkeepers
- Update the WIP schedule for each active contract: confirm costs incurred, revised total estimated costs, and the percentage-completion rate; recalculate revenue to recognise in the period
- Reconcile contract billings to the WIP schedule: identify contract assets (unbilled revenue) and contract liabilities (billings in excess of revenue recognised) and confirm balance sheet treatment
- Review all progress invoices for valid PO references and correct Commonwealth entity identifiers; follow up overdue Commonwealth debtors separately from commercial debtors
- Confirm retentions receivable balance: split into current and non-current based on contractual acceptance dates; obtain the retentions schedule from the project manager
- Review security clearance cost postings: confirm they are coded as business expenses under s.8-1 ITAA 1997 with no FBT liability; retain contractual requirement documentation
- Check EMDG receipts are coded as assessable income (not GST supplies) with no GST payable
- Review any approved contract variations — ensure the contracted revenue figure in the WIP schedule includes all approved change orders at the correct revenue amount