Billings in Excess of Costs — Contract Liability When Government Billed Ahead of Performance
Recording the contract liability when a defense contractor has billed the government more than the revenue earned to date — representing the obligation to perform future contract work.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| Cash / Accounts Receivable (Government Invoice — Advance Milestone Billing) | Asset (+) | 15,000,000.00 | - |
| Contract Liability — Billings in Excess of Costs and Estimated Earnings | Liability (+) | - | 5,500,000.00 |
| Revenue (Earned Portion — Based on POC) | Revenue (+) | - | 9,500,000.00 |
💡 Accountant's Note
Contract liabilities ('billings in excess of costs and estimated earnings' or 'unearned revenue on government contracts') arise when a defense contractor invoices the government MORE than the revenue it has earned using the POC method. Common scenarios: (1) Milestone-based billing where a major milestone ($15M payment upon design review completion) is invoiced when the design review occurs, but the overall POC may indicate only $9.5M of revenue is earned to date. (2) Advance payments on new contracts where the government funds the start of a program. (3) Favorable billing terms that allow front-loaded invoicing. The contract liability represents the government's prepayment — money received for work not yet performed. This must be carefully balanced against the contract asset on OTHER contracts — ASC 606 requires presentation on a contract-by-contract basis (assets and liabilities cannot be netted across different contracts).
Practitioner & Systems Framework
💻 ERP Architecture
The contract asset/liability position at the contract level is the key output of the government contract accounting system. For each contract: (Revenue earned per POC) vs. (Amounts billed to date) = Contract Asset if billed < earned; Contract Liability if billed > earned. These are presented separately on the balance sheet — the gross amounts cannot be netted. Contractors with many contracts will typically have both contract assets and contract liabilities simultaneously (different contracts at different stages of billing vs. performance).
⚠️ Audit Flags
The contract asset/liability balance is a primary revenue cycle audit area. Auditors test: (1) Are the POC percentages accurate (driving the 'earned' revenue)? (2) Are billings properly recorded (complete and in the correct period)? (3) Are contract assets and liabilities properly separated by contract (no netting of different contracts)? Large contract liabilities on mature contracts (work nearly complete but large advance balance remaining) may indicate overbilling or performance problems.
📄 Required Documentation
Revenue recognition calculation by contract (POC %, earned revenue, costs incurred), billing records (invoices submitted to government), contract asset/liability schedule by contract, contract-level netting prohibition (confirmation that assets and liabilities are not netted across contracts), balance sheet disaggregation of contract assets and liabilities, and roll-forward of contract balances.
Professional Excel Template
Get the automated version of this entry. Includes built-in IFRS checks, VAT calculators, and SAP-ready upload formats.
Expert Analysis by Qusai Ahmad
General Accountant Supervisor & IFRS Specialist
Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.
Related Journal Entries
Defense, Aerospace & Government Contracting
Cost-Plus-Fixed-Fee (CPFF) Contract — Revenue Recognition as Costs Are Incurred
Defense, Aerospace & Government Contracting
Firm Fixed-Price (FFP) Contract — Cost-to-Cost Percentage of Completion Revenue
Defense, Aerospace & Government Contracting