AI for Construction Contract Accounting Under IFRS 15

IFRS 15 turned revenue recognition for construction contracts into a continuous judgment exercise: identify performance obligations, estimate transaction price including variable consideration, measure progress toward satisfaction, and reassess at every reporting date. For CFOs and controllers in construction, that means every percentage-of-completion figure rests on a chain of estimates — cost-to-complete, labour productivity, subcontractor exposure, change orders, and claims — each of which can move margin materially from one period to the next.

The friction is not conceptual; it is operational. Project managers report progress in their own formats, commercial teams track variations in spreadsheets, and the finance team reconciles it all under deadline pressure. Contract assets and contract liabilities get misclassified, unpriced change orders sit unrecognised for months, and loss-making contracts are provisioned late because nobody surfaced the early warning signals. Auditors then ask for the contract-by-contract evidence trail, and the close slips again.

AI does not replace the accountant’s judgment under IFRS 15 — it compresses the evidence-gathering and consistency-checking work that surrounds it. Used well, a model can read project reports and contract registers, flag where estimated costs to complete have drifted, test that revenue and cost recognition follow the same progress measure, and draft the contract-level disclosure workings. The two prompts below show how to structure that work so the output is auditable rather than opaque.

Where AI adds leverage in the close

The highest-value use cases cluster around three tasks: variance analysis between periods, consistency testing across the contract portfolio, and drafting the memo that documents management’s judgments. Each benefits from a prompt that supplies the standards, the entity’s accounting policies, and a worked example of the desired output — not a vague instruction to “review the contracts.”

I want to review a portfolio of construction contracts for IFRS 15 compliance and flag recognition risks so that the monthly close is defensible and audit-ready.

First, read these files completely before responding:
[ifrs15_policy_memo.md] — the entity’s accounting policy for revenue from construction contracts, including progress measurement method and variable consideration treatment
[contract_register.xlsx.md] — one row per contract with contract value, approved variations, cumulative revenue recognised, cumulative costs incurred, estimated costs to complete, and contract asset/liability balance
[prior_period_workings.md] — last month’s contract-level workings and any judgments documented

Here is a reference for what I want to achieve:
[Upload a prior period review memo as markdown showing the structure: contract ID, issue identified, IFRS 15 paragraph reference, quantitative impact, recommended adjustment]

Here’s what makes this reference work:
Each finding is contract-specific, cites the relevant IFRS 15 requirement, quantifies the impact in currency, and states a clear recommended action. Tone is factual, no hedging, no generic observations.

Here’s what I need for my version / SUCCESS BRIEF:
Type of output: a contract-by-contract exception report, one paragraph per flagged contract, plus a summary table of total potential adjustments
Recipient’s reaction: the controller should be able to accept or reject each finding in under two minutes and forward the memo directly to the audit team
Does NOT sound like: a textbook summary of IFRS 15, or a list of generic risks with no numbers attached
Success means: every contract where cost-to-complete moved more than [10]% versus prior period, or where contract asset/liability classification looks inconsistent with the progress measure, is surfaced with a quantified impact

My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.

Give me your execution plan (5 steps max) before you begin.

Note the discipline in that prompt: the model is told what a good finding looks like before it is allowed to produce any. That single constraint does more for output quality than any amount of instruction about tone or length.

Drafting the judgment memo

The second high-leverage task is the memo that documents management’s judgments on variable consideration, change orders, and claims — the areas auditors probe hardest. Here the AI should draft from the contract terms and correspondence, not from generic principles, and it should separate priced variations from unpriced claims because IFRS 15 constrains the latter far more tightly.

I want to draft a contract-level IFRS 15 judgment memo covering variable consideration and change orders so that management’s position is documented, quantified, and consistent with the standard.

First, read these files completely before responding:
[contract_terms_summary.md] — key commercial terms for contract [CONTRACT_ID], including variation mechanism, liquidated damages, and payment schedule
[change_order_log.md] — all variations and claims with status: approved, in negotiation, or disputed, plus estimated value and probability assessment
[ifrs15_policy_memo.md] — the entity’s policy on variable consideration, including the expected value versus most likely amount approach and the constraint

Here is a reference for what I want to achieve:
[Upload a prior judgment memo as markdown showing the structure: background, relevant terms, IFRS 15 analysis, conclusion, quantified impact on transaction price]

Here’s what makes this reference work:
The analysis walks from contract terms to the specific IFRS 15 paragraphs to a conclusion, quantifies the constrained amount included in the transaction price, and states what evidence would change the conclusion.

Here’s what I need for my version / SUCCESS BRIEF:
Type of output: a judgment memo of [800-1200] words with a quantified transaction price adjustment
Recipient’s reaction: the auditor should see a complete evidence trail and have no follow-up questions on methodology
Does NOT sound like: a restatement of the standard, or a conclusion without supporting arithmetic
Success means: every variation and claim in the log is addressed individually, the constraint applied to each is justified, and the total adjustment reconciles to the contract register

My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.

Give me your execution plan (5 steps max) before you begin.

A practical tip before you deploy either prompt: run them against a closed prior period where the outcome is known. Compare the model’s flagged exceptions and drafted conclusions against what actually happened and what the auditors accepted. That calibration step takes one afternoon and tells you more about reliability than any vendor demonstration. Once calibrated, move the exception review into the monthly close calendar and keep the judgment memos for contracts above your materiality threshold — that is where the audit risk concentrates and where the time saved compounds fastest.

Published on 19 November 2026 on growwithgpt.com