contract asset and the contract liability balances. This explanation may use qualitative
information. [IFRS 15.117].
An entity is also required to provide an explanation of the significant changes in the
contract asset and the contract liability balances during the reporting period. This
explanation is required to include both qualitative and quantitative information. The
standard identifies the following examples of changes in the entity’s balances of contract
assets and contract liabilities: [IFRS 15.118]
• changes due to business combinations;
• cumulative catch-up adjustments to revenue that affect the corresponding contract
asset or contract liability, including adjustments arising from a change in the
measure of progress, a change in an estimate of the transaction price (including any
changes in the assessment of whether an estimate of variable consideration is
constrained) or a contract modification;
• impairment of a contract asset;
• a change in the time frame for a right to consideration to become unconditional
(i.e. for a contract asset to be reclassified to a receivable); and
• a change in the time frame for a performance obligation to be satisfied (i.e. for the
recognition of revenue arising from a contract liability).
Entities are permitted to disclose information about contract balances, and changes
therein, as they deem to be most appropriate, which would include a combination of
tabular and narrative information. The IASB explained in the Basis for Conclusions that
these disclosures are intended to provide financial statement users with information
they requested on when contract assets are typically transferred to accounts receivable
or collected as cash and when contract liabilities are recognised as revenue.
[IFRS 15.BC346].
In addition to the disclosures on contract balances and changes, the standard requires
entities to disclose the amount of revenue recognised in the period that relates to
amounts allocated to performance obligations that were satisfied (or partially satisfied)
in previous periods (e.g. due to a change in transaction price or in estimates related to
Revenue
2301
the constraint on revenue recognised). As noted in the Basis for Conclusions, the Board
noted that this information is not required elsewhere in the financial statements and
provides relevant information about the timing of revenue recognised that was not a
result of performance in the current period. [IFRS 15.BC347].
The example below is an example of how an entity may fulfil these requirements.
Example 28.99: Contract asset and liability disclosures
Company A discloses receivables from contracts with customers separately in the statement of financial
position. To comply with the other disclosure requirements for contract assets and liabilities, Company A
includes the following information in the notes to the financial statements:
20X9
20X8
20X7
$
$
$
Contract asset
1,500
2,250
1,800
Contract liability
(200)
(850)
(500)
20X9
20X8
20X7
$
$
$
Revenue recognised in the period from:
Amounts included in contract liability
at the beginning of the period
650
200
100
Performance obligations satisfied in
previous periods
200
125
200
We receive payments from customers based on a billing schedule, as established in our contracts.
Contract asset relates to our conditional right to consideration for our completed performance under
the contract. Accounts receivable are recognised when the right to consideration becomes
unconditional. Contract liability relates to payments received in advance of performance under the
contract. Contract liabilities are recognised as revenue as (or when) we perform under the contract.
In addition, contract asset decreased in 20X9 due to a contract asset impairment of $400 relating to
the early cancellation of a contract with a customer.
Disclosing contract assets and liabilities and the revenue recognised from changes in
contract liabilities and performance obligations satisfied in previous periods is likely a
change in practice for most entities. In addition, because paragraph 116(a) of IFRS 15
requires entities to separately disclose contract balances from contracts with customers,
it is necessary for entities that have material receivables from non-IFRS 15 contracts to
separate these balances for disclosure purposes. For example, an entity may have
accounts receivable relating to leasing contracts that would need to be disclosed
separately from accounts receivable related to contracts with customers. Entities need
to make sure they have appropriate systems, policies and procedures and internal
controls in place to collect and disclose the required information.
For example, consider a sales-based or usage-based royalty received by the entity in
reporting periods after it delivers a right-to-use licence of intellectual property. In this
example, the royalties relate to a previously satisfied performance obligation, but are
revenue that the entity receives in subsequent periods. As such, it would be disclosed
separately in accordance with paragraph 116(c) of IFRS 15.
Before providing its disclosure of key movements in contract balances, General
Dynamics Corporation provides a brief explanation of the requirements of the revenue
standard in respect of its contract balances in Extract 28.8 below. It then provides
2302 Chapter 28
qualitative and quantitative information together (to meet the US GAAP disclosure
requirements that are equivalent to those in paragraphs 116(b)-118 of IFRS 15). The
explanations of the significant changes in the contract asset and the contract liability
balances during the reporting period are included in both Notes B and H. Opening and
closing balances are included in the primary financial statements and in the notes to the
financial statements.
Extract 28.8: General Dynamics Corporation (2017) (US GAAP)
NOTES TO CONSOLIDATED FINANCIAL STATEMENTS [Extract]
(Dollars in millions, except per-share amounts or unless otherwise noted)
B. REVENUE [Extract]
Contract Balances. The timing of revenue recognition, billings and cash collections results in billed accounts receivable, unbilled receivables (contract assets), and customer advances and deposits (contract liabilities) on the Consolidated Balance Sheet. In our defense groups, amounts are billed as work progresses in accordance with agreed-upon contractual terms,
either at periodic intervals (e.g. biweekly or monthly) or upon achievement of contractual milestones. Generally, billing occurs subsequent to revenue recognition, resulting in contract assets. However, we sometimes receive advances or deposits from our customers, particularly on our international contracts, before revenue is recognized, resulting in contract liabilities.
These assets and liabilities are reported on the Consolidated Balance Sheet on a contract-by-contract basis at the end of each reporting period. In our A
erospace group, we generally receive deposits from customers upon contract execution and upon
achievement of contractual milestones. These deposits are liquidated when revenue is recognized. Changes in the contract
asset and liability balances during the year ended December 31, 2017, were not materially impacted by any other factors.
Revenue recognized in 2017, 2016 and 2015 that was included in the contract liability balance at the beginning of each year was $4.3 billion, $4.2 billion and $6 billion, respectively. This revenue represented primarily the sale of business-jet aircraft.
H. UNBILLED RECEIVABLES
Unbilled receivables represent revenue recognized on long-term contracts (contract costs and estimated profits) less
associated advances and progress billings. These amounts will be billed in accordance with the agreed-upon
contractual terms or upon achievement of contractual milestones. Unbilled receivables consisted of the following:
December 31
2017
2016
Unbilled revenue
$ 21,845
$ 25,543
Advances and progress billings
(16,605) (21,331)
Net unbilled receivables
$ 5,240
$ 4,212
The increase in net unbilled receivables was due primarily to the timing of billings on large international vehicle
contracts in our Combat Systems group.
G&A costs in unbilled revenue on December 31, 2017 and 2016, were $282 and $234, respectively. Contract costs also may include estimated contract recoveries for matters such as contract changes and claims for unanticipated contract costs. We record revenue associated with these matters only when the amount of recovery can be estimated reliably and realization is probable.
We expect to bill all but approximately 20% of our year-end 2017 net unbilled receivables balance during 2018. The
amount not expected to be billed in 2018 results primarily from the agreed-upon contractual billing terms.
Revenue
2303
Raytheon Company explains, in Extract 28.9 below, how the timing of satisfaction of its
performance obligation relates to the typical timing of payment and the effect those
factors have on the contract asset and contract liability balances. In Note 7, it discloses
the opening and closing balances of contract assets and contract liabilities in a separate
table. Below the table, it explains significant changes in the net contract asset balances
during the reporting period using a narrative format. It also provides detailed
information on the composition of the contract assets. In the same note, Raytheon
Company discloses revenue recognised that was included in the net contract assets at
the beginning of the period and explains the significant changes during the reporting
period in a narrative format.
Extract 28.9: Raytheon Company (2017) (US GAAP)
NOTES TO CONSOLIDATED FINANCIAL STATEMENTS [Extract]
Note 1: Summary of Significant Accounting Policies [Extract]
Revenue Recognition – Effective January 1, 2017, we elected to early adopt the requirements of Accounting Standards
Update (ASU) 2014-09, Revenue from Contracts with Customers (Topic 606). For additional information on the new
standard and the impact to our results of operations, refer to Accounting Standards below.
The vast majority of our revenues are from long-term contracts associated with the design, development,
manufacture or modification of complex aerospace or defense equipment or related services. These contracts
primarily are with the U.S. government (including foreign military sales contracted through the U.S.
government). Our contracts with the U.S. government typically are subject to the Federal Acquisition
Regulation (FAR) and are priced based on estimated or actual costs of producing goods or providing services.
The FAR provides guidance on the types of costs that are allowable in establishing prices for goods and services
provided under U.S. government contracts. The pricing for non-U.S. government contracts is based on the
specific negotiations with each customer.
Under the typical payment terms of our U.S. government fixed-price contracts, the customer pays us either
performance-based payments (PBPs) or progress payments. PBPs are interim payments up to 90% of the contract
price based on quantifiable measures of performance or on the achievement of specified events or milestones. Progress
payments are interim payments up to 80% of costs incurred as the work progresses. Because the customer retains a
portion of the contract price until completion of the contract, our U.S. government fixed-price contracts generally
result in revenue recognized in excess of billings which we present as contract assets on the balance sheet. Amounts
billed and due from our customers are classified as receivables on the balance sheet. The portion of the payments
retained by the customer until final contract settlement is not considered a significant financing component because
the intent is to protect the customer. For our U.S. government cost-type contracts, the customer generally pays us for
our actual costs incurred within a short period of time. For non-U.S. government contracts, we typically receive
interim payments as work progresses, although for some contracts, we may be entitled to receive an advance payment.
We recognize a liability for these advance payments in excess of revenue recognized and present it as contract
liabilities on the balance sheet. The advance payment typically is not considered a significant financing component
because it is used to meet working capital demands that can be higher in the early stages of a contract and to protect
us from the other party failing to adequately complete some or all of its obligations under the contract.
2304 Chapter 28
Note 7: Contract Assets and Contract Liabilities
Net contract assets (liabilities) consisted of the following at December 31:
(In millions)
2017
2016
$ Change
% Change
Contract assets
$ 5,247
$ 5,041
$ 206
4%
Contract liabilities – current
(2,927)
(2,646) (281) 11%
Contract liabilities – noncurrent
(127)
(128) 1
(1)%
Net contract assets (liabilities)
$ 2,193
$ 2,267
$ (74)
(3)%
Total net contract assets (liabilities) was relatively consistent from December 31, 2016 to December 31, 2017.
Included in the change of total net contract assets (liabilities) was a $206 million increase in our contract assets,
primarily due to contractual billings terms on U.S. government and foreign military sales contracts, and a
$280 million increase in our contract liabilities, primarily due to new advances on an international award in the
fourth quarter of 2017.
Impairment losses recognized on our receivables and contract assets were de minimis in 2017, 2016 and 2015.
Contract assets consisted of the following at December 31:
(In millions)
2017
2016
U.S. government contracts (including foreign military sales):
Unbilled
$10,748
$9,356
Progress
payments
(6,637)
(5,651)
4,111
3,705
Other customers:
Unbilled
1
,368
1,742
Progress
payments
(232)
(406)
1,136
1,336
Total contract assets
$5,247
$5,041
The U.S. government has title to the assets related to unbilled amounts on contracts that provide progress
payments. Included in contract assets at December 31, 2017 was $76 million which is expected to be collected
outside of one year.
Contract assets include retentions arising from contractual provisions. At December 31, 2017, retentions were
$96 million. We anticipate collecting $27 million of these retentions in 2018 and the balance thereafter.
In 2017, 2016 and 2015, we recognized revenue of $1,434 million, $1,403 million and $1,400 million related to our
contract liabilities at January 1, 2017, January 1, 2016 and January 1, 2015, respectively.
Revenue
2305
As shown in Extract 28.10 below, Syngenta AG included a roll-forward of contract
liabilities to disclose significant changes in the balance during the reporting period.
Although such a roll-forward is not required under IFRS 15, it may be an effective way
to provide the disclosures required by paragraph 118 of IFRS 15. Syngenta AG applied
the modified retrospective approach for transition purposes. Therefore, it shows the
impact of adopting IFRS 15 in the roll-forward.
Extract 28.10: Syngenta AG (2017)
Notes to the Syngenta Group Consolidated Financial Statements [Extract]
16. Trade accounts payable and contract liabilities [Extract]
Contract liabilities consists of advance payments from customers and deferred revenue, mainly from customer loyalty programs.
Movements in contract liabilities for the year ended December 31, 2017 are as follows:
International GAAP® 2019: Generally Accepted Accounting Practice under International Financial Reporting Standards Page 458