View all Professional Packs

Free Professional Pack

Finance & Accounting

Practical AI resources for financial close, reconciliation, forecasting, reporting, cash, controls, analysis and finance decisions.

For accountants, controllers, FP&A professionals and finance teams. Choose the job you need to do and start with the strongest resource or Workflow for it.

Use the Pack as a working toolkit: download editable finance Templates, follow connected review Workflows, and practise with synthetic and real cases that help turn source evidence into clearer analysis and better-supported decisions.

Finance controller reviewing a management report and forecast at a desktop workstation

Close and report

Close the month with a clear review pack

Start here when you need to bring close areas, evidence and unresolved matters together for the controller.

Bring: Close timetable, authorised ledger exports, reconciliations, proposed adjustments and actual review records.

Supporting methods (1)

Your review: Staff collect evidence and make authorised system changes outside Amo.ng. The controller decides what can be released; unfinished work stays visible.

Investigate a reconciliation difference

Use this when a prepared account reconciliation has unexplained, recurring or stale items—even if its final total balances.

Bring: Ledger and independent source balances, dated reconciling items, source records and matching rules.

Your review: Equal totals are not proof of a valid reconciliation. An authorised accountant decides clearance, correction or escalation.

Short example

Fictional illustration. A preparer adds a round amount labelled “historic timing” to make the bridge balance. Keep it unresolved until its origin and clearance are supported.

Review a journal, accrual or estimate

Use this before accounting approval when the calculation, event, policy basis or uncertainty needs challenge.

Bring: Proposed entry or estimate, supporting event records, method, reporting period and applicable policy or standard excerpts.

Your review: Accounting treatment and posting authority stay with qualified humans. Missing policy evidence limits the review.

Check statements and reporting evidence

Use this when statements, notes and schedules need to tie to approved underlying records.

Bring: Versioned statements, notes, trial balance, schedules, comparatives and supplied disclosure requirements.

Your review: This is an evidence and consistency review, not an IFRS/GAAP compliance engine or statutory review.

Plan and manage cash

Prepare or challenge a budget and forecast

Start here when actuals, drivers and assumptions must become a reviewed planning package.

Bring: Authorised actuals, planning horizon, business drivers, approved assumptions, model formulas and executed scenario outputs.

Supporting methods (1)
  • Prompt · AMO-P-000317

    Forecast Assumption and Model Drift Challenge

    Already have a model? Challenge its assumptions, recent changes and supplied backtests.

    Produce: A bounded forecast-fitness assessment, sensitivities and refresh triggers.

Your review: A competent owner builds and runs the linked model externally. Review assumptions, capacity and cash before human approval.

Understand cash pressure and working capital

Start here when profitability and available cash tell different stories, or a forecast needs a cash-risk review.

Bring: Actual and forecast financials, receivable/payable ageing, inventory movements, cash restrictions and known commitments.

Your review: Do not confuse profit, attributed explanations or a cash scenario with verified receipts, financing availability or an insolvency conclusion.

Short example

Fictional illustration. Profit rises while receivables and inventory grow. Build a cash bridge and verify collection timing before describing growth as cash-generative.

Understand performance and decisions

Understand why costs or margins changed

Use this when reported profitability may reflect mix, prices, allocation changes, timing or spreadsheet errors.

Bring: Comparable sales/cost extracts, definitions, cost pools, allocation drivers and approved source totals.

Your review: Separate contribution, gross and operating margin. A cost reclassification is not automatically an economic saving.

Explain actual-versus-plan performance

Use this when a KPI or financial result moved and management needs a defensible explanation.

Bring: Comparable tables, metric definitions, periods, thresholds, known events and source references.

Supporting methods (1)
  • Prompt · AMO-P-000228

    Business KPI Dashboard Trust and Definition Audit

    When dashboards disagree, check definitions, filters, freshness and source totals before explaining performance.

    Produce: A metric trust review and unresolved definition/data questions.

Your review: Verify arithmetic and comparability; label explanations that remain hypotheses.

Challenge a capital request

Start here before an organisational capital decision when costs, benefits, timing or appraisal assumptions need review.

Bring: Business case, alternatives, dated incremental cash flows, approved discount basis and supplied calculations.

Your review: Humans authorise capital expenditure. This is not personal investment advice, securities analysis or a certified valuation.

Prepare credible management commentary

Use this to explain reviewed numbers and decisions to management or the board.

Bring: Reviewed financial metrics, business outcomes, risks, assumptions, decision requests and distribution limits.

Your review: Do not turn a target into a forecast or an assertion into a fact. The finance owner approves the narrative and distribution.

Check data, controls and AI use

Review finance controls and exceptions

Use this when a finance process has unclear ownership, approvals, evidence or exception handling.

Bring: Process description, current procedures, actual incidents, supplied control requirements and owners.

Your review: Control design is distinct from proof that a control operated. Process owners approve changes; this is not an audit opinion.

Check finance data and spreadsheet reliability

Start here before relying on a financial model, workbook or reporting extract.

Bring: Readable formulas, source totals, workbook versions, mappings, overrides and decision outputs.

Supporting methods (2)
  • Prompt · AMO-P-000056

    Messy Dataset Audit Prompt

    Check the completeness, keys, types and joins of a finance extract before it feeds a model.

    Produce: A data-quality review and required validation checks.

  • Prompt · AMO-P-000263

    Metric Definition Contract and Semantic Layer Blueprint

    Use with finance/data owners when a recurring KPI needs an agreed definition across tools.

    Produce: A proposed metric definition, ownership and test plan; implementation remains a separate technical task.

Your review: Preserve originals. Test actual formulas and data; an AI description is not an executed check or an approved system change.

Use AI with evidence and human review

Start here when an AI-generated analysis or narrative may influence a finance decision.

Bring: AI draft, original evidence, authorised provider/data rules, review criteria and named decision owner.

Your review: Approve data use before generation. Minimise confidential data, verify numbers independently and leave financial approval with people.

Short example

Fictional illustration. An AI narrative says every adjustment was approved, but the file contains only preparer names. Check the actual approval evidence and keep that claim unverified.

Templates

Four editable Markdown working records. Preview the structure or download and adapt it to your process. These records organise evidence and human decisions; they do not certify compliance or approve accounting treatment.

Template · editable · Markdown

Period-End Close Evidence and Controller Review Record

Bring close-area evidence, reconciliations, estimates and unresolved decisions together for controller review.

Preview template: Period-End Close Evidence and Controller Review Record

Period-End Close Evidence and Controller Review Record

Editable Markdown working material. Copy this file and replace blank fields; add rows as needed. It does not calculate, approve transactions or certify compliance. Keep detailed confidential records in authorised systems and use evidence references here. Share only material authorised for the chosen provider. AI observations and actual human decisions must remain separate. Apply agreed organisational retention/access rules; no retention period is prescribed here.

Use this when preparing a controller review across close areas. Start with the agreed close perimeter, link each completion claim to evidence, and keep unresolved matters visible until the authorised person decides.

Close control sheet
Field Entry
Record ID / version / prepared date —
Entity/group and reporting period —
Reporting framework, edition, adoption basis and supplied policy references —
Currency/unit, source versions and cut-off —
Included/excluded cycles and rationale —
Controller / preparer / reviewers / backups —
Deadline, dependencies and approved review criteria —
Distribution and data authority —
Area evidence and completion

Use statuses not started / evidence missing / prepared / under review / human accepted / held. “Prepared” does not mean reviewed. A checklist tick requires a source and dated reviewer record.

Area ID / cycle / account Owner and due date Required evidence / source version Actual evidence reference and date Completion status Reconciliation reference / residual Dependency / next action
— — — — evidence missing — —

Cover the scoped cycles, for example cash, receivables, payables, payroll, inventory, fixed assets, intercompany and reporting schedules. Do not mark a cycle not applicable without a human rationale.

Adjustment, estimate and exception record
Item ID / affected area Proposed or actually posted? Amount / currency / period Event, calculation and evidence references Policy/estimate uncertainty / contrary evidence Reviewer question Management response and supporting source Owner / deadline / status
— proposed — — — — — —

Link actual journal/approval/posting/reversal records if they exist. Do not turn a proposal into a posted action. An unsupported difference remains open even when a management explanation is plausible.

Control operation and AI contribution
Review/control claim Design requirement Evidence it actually operated / date / population Exception or override AI observation and source check Human reviewer / challenge / outcome
— — — — — —

A policy is design evidence, not proof of operation. Record AI tool/use scope only if actually used; attach the original numerical/evidence checks rather than treating the AI response as accounting evidence.

Controller disposition
  • Decision date, scope and authorised controller: —
  • Release / hold / revise / further evidence required: pending human decision
  • Unresolved amounts, affected statements and restrictions: —
  • Accepted limitations and rationale, with authority reference: —
  • Rejected proposals and required correction/evidence: —
  • Separately authorised external posting, ERP close or issuance references, if executed: —
  • Follow-up owner, due date and reopening/next-period trigger: —

Before handoff, verify that every completion claim has evidence, source versions agree, unresolved matters are prominent, and the actual human disposition is recorded without an AI-generated signature.

Template · editable · Markdown

Account Reconciliation Review Record

Trace balances and reconciling items to evidence, reviewer questions and actual human disposition.

Preview template: Account Reconciliation Review Record

Account Reconciliation Review Record

Editable Markdown working material. Copy this file and replace blank fields; add rows as needed. It does not calculate, approve transactions or certify compliance. Keep detailed confidential records in authorised systems and use evidence references here. Share only material authorised for the chosen provider. AI observations and actual human decisions must remain separate. Apply agreed organisational retention/access rules; no retention period is prescribed here.

Use this to review one prepared reconciliation. Keep account-level balances and item-level support connected; do not clear items just to reach zero.

Scope and sources
Field Entry
Record/version, account, entity, period and as-of date —
Currency/unit and debit/credit/sign convention —
Ledger source/version/extraction date/control total —
Independent/source balance, provenance and whether independently generated —
Population/exclusions and matching/cut-off rules —
Preparer, reviewer, approving owner and review criteria —
Prior open items and material limitations —
Signed bridge

State the direction before filling the table: source balance + signed reconciling items = expected ledger balance, or document a different approved direction. Record amounts consistently; a debit or credit is not universally positive.

Bridge line Signed amount Currency / unit Evidence / source location Supported, asserted or unresolved?
Independent/source opening comparison balance — — — —
Reconciling item ID — — — —
Expected ledger balance after listed items — — — —
Actual ledger balance — — — —
Residual: actual ledger less expected ledger — — — unresolved until supported

Keep gross differences; do not offset unrelated items. This Markdown file does not calculate the bridge. Reperform arithmetic in an authorised tool and record method/output reference: —.

Item review
Item ID / original date / age at review Amount/sign and transaction ID Explanation / timing, error or unresolved Evidence supporting and contradicting it Prior appearances / subsequent clearance evidence Owner / proposed resolution Reviewer challenge / missing evidence Human disposition and authority
— — — — — — — pending

Record the actual age basis; equal amounts do not prove duplicate events. Later clearance needs identity/date evidence. Reference any candidate correction to its separate journal review; do not treat a plug as resolution.

Review conclusion and follow-up
  • FACTS established from examined records: —
  • ASSERTIONS not yet supported: —
  • Remaining differences and affected use: —
  • Evidence not supplied / populations not tested: —
  • Proposed next actions, owners and dates: —
  • Human decision: pending / accepted within stated limits / held / further evidence required
  • Actual reviewer, date, rationale and approval-system reference: —
  • Any executed correction and rechecked balance references: —

A zero residual demonstrates arithmetic agreement only. Account completion, adjustments and write-offs require actual authorised decisions and sufficient support.

Template · editable · Markdown

Forecast, Cash and Financial Model Assumption Register

Record assumption sources, scenarios, sensitivities, dependencies and human acceptance or rejection.

Preview template: Forecast, Cash and Financial Model Assumption Register

Forecast, Cash and Financial Model Assumption Register

Editable Markdown working material. Copy this file and replace blank fields; add rows as needed. It does not calculate, approve transactions or certify compliance. Keep detailed confidential records in authorised systems and use evidence references here. Share only material authorised for the chosen provider. AI observations and actual human decisions must remain separate. Apply agreed organisational retention/access rules; no retention period is prescribed here.

Use this with a budget, rolling forecast, cash projection or financial model. It connects each important assumption to a source, an actual model version, uncertainty and the human decision to use or reject it.

Model and decision scope
Field Entry
Register ID/version, planning question and decision owner —
Entity, horizon, time grain, currency/unit and framework —
Actuals cut-off, approved budget and prior/current forecast versions —
P&L, balance-sheet and cash model/output locations —
Calculation tool/method and actual execution reference —
Capacity, funding, permission and decision constraints —
Assumptions
ID / model cell or driver Assumption / target or forecast? Source/date and owner Base value / unit / timing Alternative range/scenario and basis Dependency / affected output Uncertainty / contrary evidence Last update / refresh trigger
— — — — — — — —

Do not imply a probability merely because a scenario is called “base”. Distinguish contracted facts, approved assumptions and management aspirations. Do not invent a discount rate, exchange rate, collection probability or valuation.

Sensitivity and model-run record
Run/version ID and date Assumptions changed and unchanged Calculation method / evidence of execution P&L / balance-sheet / cash checks Output change / minimum available cash / headroom Limitation or unresolved difference
— — not executed until evidenced — — —

Separate one-variable sensitivities from coherent combined scenarios. Record interactions and the comparison basis. Distinguish total, restricted and available cash, and an internal headroom target from a contractual covenant. Proposed tests are not run results.

Challenge and decision log
Assumption/run ID Reviewer question Owner response and evidence Approved / rejected / revised / pending Actual human decision, rationale, date and authority Follow-up / responsible owner
— — — pending — —
  • AI-assisted observations and independent checks: —
  • Specialist interpretation needed and affected reliance held: —
  • Budget/forecast/capital decision and limits: pending human decision
  • Rejected assumptions retained for traceability: —
  • Next comparison with actual outcomes and owner: —

Before relying on the model, confirm the stated version was actually calculated, assumptions match the run, linked statements reconcile, residuals are visible and an authorised person decided. A filled register does not certify a forecast or approve spending.

Template · editable · Markdown

Financial Performance Commentary Review Record

Separate observed movements, explanations, causal claims and missing evidence before commentary is approved.

Preview template: Financial Performance Commentary Review Record

Financial Performance Commentary Review Record

Editable Markdown working material. Copy this file and replace blank fields; add rows as needed. It does not calculate, approve transactions or certify compliance. Keep detailed confidential records in authorised systems and use evidence references here. Share only material authorised for the chosen provider. AI observations and actual human decisions must remain separate. Apply agreed organisational retention/access rules; no retention period is prescribed here.

Use this before distributing financial commentary. Start from reconciled numbers, keep explanations separate from observations, and record who approved the wording and for what audience.

Reporting basis
Field Entry
Record/version, period, entity, currency/unit and audience —
Approved source report/model versions and comparison basis —
Metric definitions, denominator, allocation/classification rules —
Decision requested, owner and distribution restrictions —
Claim review — repeat this block per material claim
Field Evidence-aware entry
Claim ID and exact proposed wording —
Observed movement and source numbers/locations —
Calculation/bridge, control total and residual —
Management explanation and supporting source —
Alternative explanation / contrary evidence —
Attribution or causal claim being made —
What the evidence can establish / cannot establish —
Missing evidence, uncertainty and pending test —
Decision implication if the claim is wrong —
AI-generated wording or observation, if any —
Reviewer challenge and response —
Revised wording proposed —

Do not label correlation or an accounting bridge as proof of causality. Explain timing, allocation, classification, scope or model changes before attributing improved performance to management action. Preserve adverse evidence and distinguish forecast from actual.

Human publication/distribution decision
Claim IDs / package version Reviewer / role Accepted, revised, rejected or held Rationale and remaining limitations Actual authority/date/approval reference Permitted audience and next action
— — pending — — —
  • Unresolved claims withheld or qualified: —
  • Reconciled final figures and verification reference: —
  • Follow-up owner/date and trigger to correct an issued narrative: —

This record does not authorise external disclosure or issue financial statements. Confirm actual human approval and access restrictions before any communication is sent.

Practice Cases

Two ways to learn: analyse fictional evidence before deciding what it supports, or examine a real authoritative record and its professional lessons. Neither provides an accounting ruling for your organisation.

Synthetic practice cases

The organisations, data and events are fictional. Work through the learner evidence before drawing conclusions. Facilitator guidance and answer keys are not included.

Synthetic practice case · learner version · Markdown

Unresolved Close Adjustments Before Reporting Deadline

Review conflicting reconciliation records, proposed entries and missing approval under deadline pressure.

Preview learner evidence: Unresolved Close Adjustments Before Reporting Deadline

Unresolved Close Adjustments Before Reporting Deadline

Synthetic practice case. All organisations, roles, records and amounts are fictional. CU means fictional currency units. This learner file contains no facilitator solution. Work from the supplied evidence; uncertainty is intentional.

Your job

You are the reviewing accountant at fictional Aster Quay Workshop. September 2026 management reporting is due at noon on 3 October. Prepare the controller's open-item decision brief. You may organise evidence and propose questions; you cannot approve journals, contact a bank or issue reports in this exercise.

Evidence C1-E1 — frozen balances, 30 September

The ledger export at 18:00 shows bank account B01 at 128,400 debit CU. The separately supplied bank statement closes at 133,900 positive CU. Both cover the same entity/account/currency. These are supplied control totals, not a full transaction population. All later proposed entries below are absent from this ledger version.

C1-E2 — preparer's reconciliation, version 2

Direction used: bank statement plus deposit in transit less outstanding payments equals expected ledger.

Item Amount CU Original date Preparer description
D01 +2,400 30 September Deposit submitted after cut-off
P01 -5,000 29 September Supplier payment awaiting bank clearance
P02 -2,000 30 September Payment sent; treasury later says cancelled
P03 -1,200 27 June Old supplier payment, carried forward
X01 +300 not supplied “Historic timing adjustment” entered to reach ledger

No evidence reference or owner is recorded for X01. The reconciliation is labelled “complete”; reviewer signature is blank.

C1-E3 — limited subsequent records
  • Bank advice identifies debit ADJ-930 for 300 on 30 September, included in the closing bank balance. Its description is “account adjustment”; fee/return classification is not explained. No matching ledger transaction is identified in the supplied extract.
  • Bank advice on 1 October shows P01 cleared once for 5,000. A treasury spreadsheet repeats that event on two rows with the same bank event ID. The spreadsheet is not a second bank confirmation.
  • A 2 October bank credit matches D01 for 2,400 by deposit reference.
  • The bank excerpt supplied through 2 October does not show P02 or P03. Later records are unavailable.
C1-E4 — fictional internal messages

Treasury, 2 October: “P02 was probably cancelled. I cannot find the cancellation reference yet.”

Accounts payable, 2 October: “The supplier says it has not received P02. P03 may have been reissued, but I have not checked the payment register.”

Finance manager, 3 October: “Please clear the 300 so the bank review is green. We also need to release the unused maintenance accrual to stay within budget.”

These are assertions requiring corroboration, not authorisation or external evidence.

C1-E5 — proposed journals, not posted
Proposal Debit Credit Amount CU Support / approval
J01 Miscellaneous expense Bank B01 300 “Clear reconciliation”; controller approval absent
J02 Maintenance accrual liability Maintenance expense 6,000 “Service not used”; controller approval absent

J02 concerns a 6,000 accrual already in the ledger. A purchase order refers to September maintenance. A supplier email says work took place on 28 September; the operations note says “some tasks still outstanding”. No signed acceptance, itemised invoice or quantified completion schedule is supplied.

C1-E6 — supplied exercise policy, not a legal/accounting standard

The fictional organisation requires event support, calculation, accounting rationale, independent review and an actual approval record for journals. Unexplained reconciliations remain visible to the controller. Thresholds prioritise review, not permission to ignore missing support. The exercise supplies no universal materiality threshold or full financial-reporting framework; do not invent either.

Work to produce
  1. Reperform the bank bridge with and without X01. Preserve original figures and a signed residual.
  2. Classify each item as supported within limits, asserted, conflicting or unresolved. Record age, clearance evidence and missing evidence.
  3. Challenge J01 and J02 separately: calculation, event, period, policy evidence, uncertainty and approval.
  4. Explain what must remain open in the controller pack and who should obtain the next evidence. Decide what you would recommend, without claiming an actual controller decision.
  5. Use the Account Reconciliation Review Record and Period-End Close Evidence and Controller Review Record. If using AI, identify which observations you independently checked.

Do not force a balancing plug, infer fraud, or equate the reporting deadline with approval. More than one bounded recommendation may be defensible; unexplained evidence cannot be described as resolved.

Synthetic practice case · learner version · Markdown

Reported Profitability Improvement but Increasing Cash Pressure

Compare profit, working capital, ageing and a cash forecast before recommending a bounded next decision.

Preview learner evidence: Reported Profitability Improvement but Increasing Cash Pressure

Reported Profitability Improvement but Increasing Cash Pressure

Synthetic practice case. Fictional Cedar Vale Supply; no real organisation or personal data. All amounts are CU thousands. This is a simplified management-accounting dataset, not statutory financial statements. No facilitator solution appears here.

Your job

It is 2 October 2026. Management says improved profitability supports a further capital commitment. Prepare a source-backed cash and forecast challenge for the finance director. Payments, borrowing and investment approval remain human decisions.

C2-E1 — supplied quarter results
Item Q2 Q3
Revenue 5,000 6,000
Cost of sales 3,400 3,900
Gross profit 1,600 2,100
Operating expenses, including depreciation 1,200 1,500
Operating profit 400 600
Depreciation included above 100 120

For this simplified exercise there are no interest, tax, FX, acquisitions, dividends, borrowings, disposals or other non-cash/profit-to-cash adjustments beyond those explicitly listed. Do not generalise that simplification to real companies.

C2-E2 — balance movements and cash
Item 30 June 30 September
Receivables 1,800 2,600
Inventory 1,400 1,900
Trade payables 1,000 1,300
Total cash 900 220
Restricted cash included in total 50 50

Q3 capital cash payments were 400. Other relevant operating balances are unchanged. Inventory records show opening 1,400 plus cost additions 4,400 less expensed cost 3,900 equals closing 1,900. The extract does not establish whether all stock is saleable.

C2-E3 — receivable ageing, same population
Age 30 June 30 September
Current 1,000 1,200
1–30 days overdue 500 700
31–60 days overdue 200 450
More than 60 days overdue 100 250

An account-level note says 120 within the oldest bucket is disputed. No approved credit note or collectability decision is provided. Sales says the dispute is “administrative”; collections has not obtained a written resolution.

C2-E4 — October cash forecast v4

Opening available cash is 170, excluding restricted cash. The forecast contains no new borrowing or use of restricted funds.

Week Forecast collections Forecast cash payments Model closing available cash
1 300 360 110
2 320 380 50
3 350 330 70
4 400 370 100

The final figure is a supplied model output to check, not an authoritative bank balance. The finance director's internal review floor is 100; it is not represented as a legal solvency test or bank covenant.

The week-2 collections include a 100 receipt from fictional account C-17. Sales expects week 2; a customer operations note says payment processing may move to week 4. There is no confirmed payment date. Treat a move to week 4 as a requested timing sensitivity, not a predicted outcome or probability.

C2-E5 — decisions and assertions

Management: “Profit grew 50%, so the cash reduction is entirely capex and we can commit another 150 to equipment in November.”

Operations: “Inventory rose to support growth, but slow-moving stock data are incomplete.”

Treasury: “Do not use the restricted 50. We need an agreed action if available cash falls below the internal floor.”

November's proposed equipment commitment is absent from the October forecast. No approved financing action, deferral agreement or supplier payment change is supplied.

Work to produce
  1. Reconcile the Q3 change in total cash using profit, depreciation, working capital and capex. Explain what the arithmetic does and does not establish.
  2. Review ageing and inventory evidence, distinguishing growth from timing and collectability uncertainty.
  3. Recalculate forecast v4. Produce the C-17 timing sensitivity using the same payment assumptions and identify affected weeks.
  4. Challenge the capital-commitment assertion without automatically approving or rejecting the investment on incomplete evidence.
  5. Record assumptions, alternative explanations, missing evidence and human decisions in the Forecast, Cash and Financial Model Assumption Register. Prepare qualified commentary using the Financial Performance Commentary Review Record.

No conclusion of insolvency, misconduct or universal financial compliance follows from this exercise. Do not invent collection probabilities or assume management can defer obligations without authority.

Synthetic practice case · learner version · Markdown

Margin Improvement with Spreadsheet and Narrative Conflicts

Investigate changed allocation, spreadsheet formulas and a confident narrative against the underlying evidence.

Preview learner evidence: Margin Improvement with Spreadsheet and Narrative Conflicts

Margin Improvement with Spreadsheet and Narrative Conflicts

Synthetic practice case. Fictional Linden Arc Products; all records and CU amounts are invented for learning. Analyse the evidence before any facilitator discussion. This file contains no answer key.

Your job

The commercial director wants to publish a favourable September margin explanation. Finance has found different cost totals. Prepare a model, allocation and commentary review without changing the workbook or approving the narrative.

C3-E1 — approved August comparison, CU
Product Units Revenue Direct cost Allocated overhead Gross profit
A 1,000 100,000 60,000 20,000 20,000
B 500 100,000 65,000 20,000 15,000
Total 1,500 200,000 125,000 40,000 35,000

August management gross profit includes the full overhead pool. This is a supplied management definition, not a universal accounting rule.

C3-E2 — September source records
Product Units Revenue Direct cost in source schedule
A 1,100 110,000 63,800
B 500 100,000 65,000
Total 1,600 210,000 128,800

The finance-approved September overhead control total is 42,000. Under the previous comparison method the pool would be allocated equally between A and B. No inventory movement, tax or currency effect changes these exercise totals.

Procurement says A's direct unit cost benefited from a temporary supplier promotion on this batch; the source schedule supports the total but no evidence establishes a permanent cost change or general productivity improvement.

C3-E3 — report v7, not yet approved
Product Revenue Direct cost in report Overhead in gross margin Reported gross profit
A 110,000 63,800 15,000 31,200
B 100,000 60,000 15,000 25,000
Total 210,000 123,800 30,000 56,200

A mapping note moves 12,000 of overhead below the gross-profit subtotal. The controller's approval field is blank. August's displayed comparative was not remapped. The note says “management presentation only”; no change to the source ledger is evidenced.

C3-E4 — readable workbook excerpt
Cell Content / formula Supplied result
B-direct F14 30,000 30,000
B-direct F15 30,000 30,000
B-direct F16 5,000, late cost row 5,000
B-direct F18 =SUM(F14:F15) 60,000
Report B direct cost ='B-direct'!F18 60,000

Only this excerpt is available. No whole-workbook execution, hidden-sheet inspection or complete formula scan has occurred. A workbook note says F16 was added after the original sum range.

C3-E5 — proposed commentary and pressure

AI-generated draft supplied by the analyst: “Gross margin improved to 26.8%, entirely due to permanent purchasing efficiency. All figures have been verified.”

Commercial director: “The presentation is easier to understand. Do not distract management with technical accounting details.”

Finance reviewer: “Please show the cost-control reconciliation, comparable basis and what the evidence supports. No statement about approval or verification may be invented.”

Work to produce
  1. Reperform source and reported margins. State denominator and distinguish percentage movement from percentage-point movement.
  2. Reconcile report v7 costs to the source total and separate possible formula, allocation/classification and economic effects.
  3. Produce a like-for-like view using the supplied previous management method, preserving the reported view separately.
  4. Explain the genuine movement without claiming a causal or permanent effect unsupported by the evidence. Record what further checks require the actual workbook.
  5. Challenge the draft narrative and propose qualified wording in the Financial Performance Commentary Review Record. Record model/version and assumption issues separately.

Do not change financial classifications, publish commentary, accuse anyone of fraud, or claim a full model audit. Human finance owners decide policy, correction and disclosure.

Real case studies

These concise summaries connect finance questions to primary SEC records. Read the questions before opening the authority’s outcome. The jurisdiction and settlement status matter; historical findings do not establish a universal accounting rule.

Real case study · Reconciliation and close evidence

GTT — unsupported reconciliation adjustments

A preferred total cannot replace item-level reconciliation and support for an adjustment.

Read case study: GTT — unsupported reconciliation adjustments
Background and issue

SEC · United States · 25 September 2023. GTT faced persistent differences between operational cost systems after acquisitions.

The record connects unsupported cost adjustments and misleading reporting with accounting-control failures.

Questions for your review
  • Which records would explain the system difference rather than select a preferred total?
  • What supports a prepaid-cost adjustment, and what must remain unresolved if it is absent?
Read the authority’s outcome and professional lesson
What was found, agreed or ordered

The entered SEC order makes findings under an accepted settlement, without admission or denial except jurisdiction. No civil penalty was imposed, with cooperation and remediation credited; that is not exoneration.

Professional lesson

Keep source ownership, contradictory records and unresolved amounts visible to the controller. A balancing entry cannot repair missing evidence.

Related methods
Primary sources
Status and professional boundary

Primary records rechecked 11 October 2026. Focused official-record checks found no material reversal of this settlement record; this is not an exhaustive litigation search. Findings concern the cited historical conduct, not current compliance.

This learning summary does not determine your legal compliance or establish current compliance by the organisation discussed. Lessons are Amo.ng’s interpretation, not authority endorsement. Apply relevant local requirements with appropriate professional advice.

Real case study · Costs, estimates and financial commentary

Kraft Heinz — supplier agreements and reported savings

Reported savings need support for their substance and period of benefit.

Read case study: Kraft Heinz — supplier agreements and reported savings
Background and issue

SEC · United States · 3 September 2021. The SEC examined procurement arrangements and financial reporting at Kraft Heinz.

Supplier documentation obscured future commitments and contributed to premature expense savings and inflated reported performance.

Questions for your review
  • How would you distinguish an earned rebate from an upfront payment linked to future commitments?
  • Which evidence should challenge a savings target before it reaches commentary?
Read the authority’s outcome and professional lesson
What was found, agreed or ordered

The corrected cease-and-desist order contains settlement findings concerning the company and Eduardo Pelleissone, accepted without admission or denial subject to its specified exceptions. Separate individual complaints are not findings against other people.

Professional lesson

Read the full agreement and compare accounting periods, cost bridges and contrary evidence before calling a reduction sustainable savings.

Related methods
Primary sources
Status and professional boundary

Primary records rechecked 11 October 2026. Focused official-record checks found no material reversal of this settlement record; this is not an exhaustive litigation search. Findings concern the cited historical conduct, not current compliance. The September 2026 order directs Fair Fund disbursement; it does not reverse the accounting findings.

This learning summary does not determine your legal compliance or establish current compliance by the organisation discussed. Lessons are Amo.ng’s interpretation, not authority endorsement. Apply relevant local requirements with appropriate professional advice.

Real case study · Estimates, assumptions and reporting

Hertz — estimates and reporting pressure

An estimate change needs evidence and a defensible method, not only a favourable result.

Read case study: Hertz — estimates and reporting pressure
Background and issue

SEC · United States · 31 December 2018. The SEC order concerns Hertz Global Holdings and The Hertz Corporation.

It describes inaccurate reporting involving estimates, including receivable allowances, and reporting pressure; it also addresses fleet holding-period disclosure and earnings guidance.

Questions for your review
  • What supports a changed allowance or useful-life assumption?
  • What should a reviewer do when internal projections conflict with external commentary?
Read the authority’s outcome and professional lesson
What was found, agreed or ordered

These are findings in an entered settlement order, without admission or denial except jurisdiction. They are not a criminal conviction or trial determination against all staff.

Professional lesson

Keep method changes, contrary evidence, historical outcomes and forecast uncertainty visible to the approving accountant.

Related methods
Primary sources
Status and professional boundary

Primary records rechecked 11 October 2026. Focused official-record checks found no material reversal of this settlement record; this is not an exhaustive litigation search. Findings concern the cited historical conduct, not current compliance.

This learning summary does not determine your legal compliance or establish current compliance by the organisation discussed. Lessons are Amo.ng’s interpretation, not authority endorsement. Apply relevant local requirements with appropriate professional advice.

Real case study · Forecasting and disclosure evidence

Under Armour — revenue timing and performance explanations

A recorded number can still support a misleading explanation if important context is omitted.

Read case study: Under Armour — revenue timing and performance explanations
Background and issue

SEC · United States · 3 May 2021. The SEC record concerns orders brought forward from future quarters.

Reporting did not adequately explain the effect on growth and future revenue uncertainty.

Questions for your review
  • How would you show current growth alongside demand pulled from later periods?
  • Which forecast and commentary claims need qualification when timing practices change?
Read the authority’s outcome and professional lesson
What was found, agreed or ordered

The entered settlement order was accepted without admission or denial except jurisdiction. It expressly makes no finding that revenue from these sales was recorded contrary to GAAP. Do not recast it as a finding that every accelerated sale was improperly recognised.

Professional lesson

Bridge reported growth to timing effects and future-period implications. Distinguish recorded amounts from the completeness of their explanation.

Related methods
Primary sources
Status and professional boundary

Primary records rechecked 11 October 2026. Focused official-record checks found no material reversal of this settlement record; this is not an exhaustive litigation search. Findings concern the cited historical conduct, not current compliance.

This learning summary does not determine your legal compliance or establish current compliance by the organisation discussed. Lessons are Amo.ng’s interpretation, not authority endorsement. Apply relevant local requirements with appropriate professional advice.

Positive practice examples

Published practice accounts show how decisions and specialist collaboration can be organised. They do not independently prove successful outcomes.

Positive practice example

Synergy — documenting a prospective capital decision

Use a published business case to examine options, assumptions and planned benefits.

Read practice example: Synergy — documenting a prospective capital decision

UK Department for Work and Pensions · United Kingdom · 8 April 2026

The summary reports Treasury approval of Full Business Case 2 on 8 December 2025 and sets out options, revised appraisal values, sensitivity and optimism-bias treatment.

Professional lesson

Compare appraisal versions, separate approval from realised value and define how benefits will be measured after implementation.

Questions for your review
  • Which assumptions explain the revised appraisal?
  • What evidence would demonstrate realised benefits without double counting?
Related methods
Primary source
Status and boundary

Rechecked 11 October 2026. This is a prospective public-sector business-case account, not independent proof of project success. Its appraisal basis is not a universal corporate discount-rate rule. No adjudication or appeal status applies.

Positive practice example

GAD / NHS Resolution — specialist evidence and human ownership

Understand where finance needs specialist evidence and who owns the resulting decision.

Read practice example: GAD / NHS Resolution — specialist evidence and human ownership

UK Government Actuary’s Department · United Kingdom · 22 August 2024

GAD describes historical evidence and expert inputs supporting reserving, cash-flow projections and budgets. Its account assigns decision ownership to NHS Resolution’s Reserving and Pricing Committee.

Professional lesson

Record model assumptions, uncertainty, specialist handoffs and the accountable decision owner. Finance can reconcile evidence without issuing an actuarial opinion.

Questions for your review
  • Which inputs require specialist competence and what can finance reconcile?
  • How should uncertainty and changed assumptions reach the decision owner?
Related methods
Primary source
Status and boundary

Rechecked 11 October 2026. First-party practice account, not independently validated outcomes. Historical rate statements are not current guidance. No actuarial or legal instruction, endorsement or adjudication is implied.

Use the resources with your preferred AI

Open a resource to read its instructions and use the named tool. Supported Prompts and Workflow steps can run in Workplace using your own supported provider. Review outputs before carrying them into the next step.

If you run supported resources in Workplace, your selected AI provider may charge for its own API usage.

Building or recalculating a spreadsheet model, collecting evidence, obtaining confirmations, posting entries, closing the ERP and issuing statements remain manual or external. A Workflow does not perform those actions for you. No provider generation or run record is proof of accounting approval.

Only supply data authorised for your selected provider. Minimise confidential and personal details, never paste credentials, and independently verify material calculations against source records.

Need a definition? See Reconciliation, Forecast, Sensitivity Analysis or Human Review.

Professional judgement stays with you

AI can organise evidence, challenge assumptions, structure reconciliations, compare scenarios, check consistency and draft commentary. Its output remains working material.

It must not invent transactions, clear differences, post journals, approve payments, alter ledgers, certify financial statements, issue an audit opinion, determine a tax position, give regulated investment advice or approve capital expenditure. People make the final finance decisions.

Use the applicable reporting framework, period, local adoption rules and your organisation’s policies. IFRS, local GAAP, management reporting and internal policy are not interchangeable. This Pack provides general professional methods, not automatic standards compliance, statutory assurance, legal advice, specialist valuation or a tax opinion. Unresolved material technical questions require qualified review.

Source and standards review: 11 October 2026. Each real case retains its own historical jurisdiction and status. Responsible financial reporting remains with the organisation and its authorised professionals.

For organisations

Bring the Pack to your finance & accounting team

RichlyAI offers facilitated training, private cohorts and organisation-specific adaptation for teams that want to apply these methods across financial reporting, planning, analysis, controls and finance decision-making.

The public Amo.ng Pack remains free. Institutional services add facilitation, adaptation and organisation-specific support.

Use is subject to the Amo.ng Terms.