Tutorial Hub / Finance AI Assistant / Consolidated FS
O

Consolidated Financial Report — Working Procedure

Six stages that take the group's numbers from source files to a signed-off consolidated financial statement (FS) — built in Claude Code, with comments and review notes throughout.

The ongoing task

Prepare the consolidated financial statement (FS) for the group of companies — the parent company plus 3 subsidiaries.

  • Group financials are prepared in Excel.
  • The FS template is ready on the server (shared drive).
  • Deliverable: the consolidated FS built from the template, with comments and review notes based on the group financials and the contents of the 3 subsidiaries' financial statements.
The rule

This procedure runs end-to-end in Claude Code. Rule throughout: the AI drafts, the finance team reviews and approves. No number goes into the final FS that a team member has not checked against the source.

The six stages at a glance

Each stage has a copy-paste prompt, a check you must do, and a file Claude saves into your notes/ folder.

STAGE STAGE STAGE STAGE STAGE STAGE STAGE 0 1 2 3 4 5 6 Prepare the workspace Summarise each subsidiary FS Read the group financials Eliminations analysis Populate the template Draft the consolidated FS QA & sign-off applies to every stage The rule: the AI drafts — the finance team reviews and approves No number goes into the final FS that a team member has not checked against the source.
Stage 0 through Stage 6 — the draft/review rule sits under the whole pipeline.

Stage 0 — Prepare the Workspace

Do this manually, about 15 minutes.

1

Create a local folder for this task, e.g.:

Windows: C:\Finance\2026-08 consolidated FS\
Mac: ~/Finance/2026-08 consolidated FS/

2

Copy into it, from the server share:

  • FS_Template.xlsx (or .docx/.csv) — the consolidation template
  • The group's financial Excel file(s) — the working financials
  • Each subsidiary's FS: Subsidiary-A-FS.xlsx / Subsidiary-B-FS.xlsx / Subsidiary-C-FS.xlsx (plus PDFs of the signed statements, if available)
3

Add a notes/ subfolder — that's where Claude will save all drafts and commentary so review history stays tidy.

4

Start Claude Code in this folder (VS Code → Terminal → claude).

TIP

If any file is .xlsx and Claude says it can't read it, use this one-liner:

PROMPT — copy & paste
Write a Python script to open this workbook, print the name of every sheet, and dump each sheet as a CSV file into a csv/ folder, then run it.

Claude will create and run the script itself (it installs openpyxl when needed). From then on, you and Claude work with the CSV versions.

Stage 1 — Read & Summarise Each Subsidiary's FS

The 3 subsidiaries. Run this once per subsidiary — it builds the input picture for consolidation.

Prompt (repeat for A, B, C):

PROMPT — copy & paste
Read Subsidiary-A-FS.csv (and any PDF statement in this folder for subsidiary A).

Produce a structured summary:
1. Balance sheet (as at the reporting date): total assets, current/non-current split,
   cash, receivables, inter-company balances, payables, borrowings, equity items.
2. Income statement: revenue, cost of sales, gross profit, operating expenses,
   operating profit, finance costs, profit before/after tax.
3. Key notes extracted from the FS: revenue recognition policy, related party /
   inter-company transactions, guarantees, commitments, any audit qualifications
   or emphasis-of-matter paragraphs.
4. Anything unusual or material (> 5% of revenue, or > SGD 50,000) that the
   consolidating team must know.

Save as notes/subsidiary-A-summary.md
CHECK

Spot-check 5 figures against the actual FS. If a figure is wrong, correct it in the summary and tell Claude: "fix the total borrowings — correct figure is X".

Stage 2 — Read the Group Financials

The Excel working file.

PROMPT — copy & paste
Read the group financial workbook (all sheets, including the consolidation working
paper). Summarise:
- the group-level trial balance / financials as prepared (which is the parent-only
  versus group picture, if both are present)
- any adjustments already booked in the working paper
- any notes, comments, or open questions the preparer has left in the file
Save as notes/group-financials-summary.md
CHECK

Confirm you understand which adjustments are already booked so you don't double-count them in Stage 4.

Stage 3 — Inter-Company & Elimination Analysis

This is where consolidation errors usually live. Do it explicitly.

PROMPT — copy & paste
Using the subsidiary summaries and the group financials:
1. List every inter-company balance or transaction I can identify between the
   parent and each subsidiary, and between subsidiaries (due to/due from, loans,
   dividends, management fees, sales between group companies).
2. For each, show: counter parties, amount, which books it appears in (parent, A, B, C),
   and whether both sides are present.
3. Identify the elimination entries needed for consolidation:
   - eliminate intra-group balances (due to/due from)
   - eliminate intra-group revenue/expenses
   - any dividends declared by subsidiaries to the parent
   - investment in subsidiaries vs their equity (share capital + retained earnings
     of each subsidiary at acquisition, and since acquisition)
4. Flag anything that appears on only one side — these need investigation before
   finalising. Save as notes/eliminations.md
CRITICAL

For every elimination, both sides exist and amounts agree. One-sided balances are errors or timing differences — chase them in the source files.

Stage 4 — Populate the Consolidation Template

PROMPT — copy & paste
The FS template structure is in csv/template/ (I will point you at it) and the
consolidation working paper is in the group financials.

Build the completed consolidation worksheet:
1. For each line of the template, put the parent's figure, each subsidiary's figure
   (A, B, C), and the consolidation adjustments from notes/eliminations.md.
2. Compute the consolidated column: parent + A + B + C + adjustments.
3. Where a template line has no data, leave it blank and list it in a "lines not
   completed" section at the end.
4. Save as csv/consolidated-working.csv AND as notes/consolidation-working.md (table
   format) so it can be reviewed by a human.

Then check your own work:
- Do total assets equal total liabilities + equity in the consolidated column?
- Do the subsidiaries' inter-company balances fully cancel out?
- Does consolidated profit reconcile to the sum of individual profits after
  eliminations?
Report the result of each check, and list any line that fails.
CRITICAL

Walk the balance sheet line by line with the source files open. The balance must balance before you move on.

Stage 5 — Draft the Consolidated FS

Template + comments + reviews.

Now build the deliverable: the consolidated FS document in the template's structure, with comments and review notes added based on the group financials and the subsidiaries' FS content.

PROMPT — copy & paste
Using the template structure (csv/template/) and csv/consolidated-working.csv:

1. Produce the consolidated financial statement in the exact template layout —
   statement of financial position, statement of profit or loss, statement of
   changes in equity, cash flow statement (if in template), and the notes schedule.

2. For every note in the template, draft the note text using:
   - the group financials (for group-level figures and policies)
   - the subsidiary summaries (for anything specific to a subsidiary, e.g. its
     revenue recognition, loans, guarantees, commitments)
   Where the subsidiaries disagree on a policy or disclosure, say so explicitly.

3. Add a Comments and Review section as a separate part (not in the FS itself):
   - management comments on material movements and year-on-year changes
   - review notes: questions for each subsidiary's finance team, items pending
     confirmation, and anything the auditor is likely to ask
   - a sign-off checklist mapping each item to who approves it

4. Save:
   - consolidated-FS-draft.md (the full draft)
   - notes/comments-and-reviews.md (comments + review notes + checklist)

How the consolidation fits together

Parent + 3 subsidiaries feed in, eliminations are applied, and the consolidated FS comes out — with comments and reviews produced alongside it.

Parent company Subsidiary A Subsidiary B Subsidiary C ELIMINATIONS intra-group balances, revenue & expenses, dividends, investment vs equity CONSOLIDATED FS built in the template layout with comments & review notes sign-off by the finance team Comments & Reviews management comments, review notes & sign-off checklist
Consolidation data flow — inputs (light), eliminations (navy), final output (teal), comments & reviews side output (amber).

Stage 6 — QA & Sign-Off

Team work — the AI helps.

Prompt for the QA sweep:

PROMPT — copy & paste
Perform a final QA pass on the consolidated FS draft:
- re-check that total assets = liabilities + equity (both current and prior year)
- check every line in the statement appears in the working paper with the same number
- check the notes tie back to the statement line items
- check year-on-year movements of > 20% are explained in the comments
- list any template sections still blank or any figure you could not source
Save as notes/qa-report.md

Then, as a team:

1

Each reviewer reads the draft with the source files open and corrects any figure — tell Claude about each correction ("fix revenue note — should be X per group financials") and it updates the draft.

2

Clear every open review question in notes/comments-and-reviews.md with the subsidiary teams.

3

When clean: export the draft to the official format (ask Claude to convert the markdown draft into the template — it can script this) and upload to the server share.

4

Archive the working folder (it is your audit trail — keep it for the audit).

Where your files are saved

Every stage ends with a file Claude saves into the working folder — this is your review trail.

StageFiles saved
Stage 1notes/subsidiary-A-summary.md (repeat for B and C)
Stage 2notes/group-financials-summary.md
Stage 3notes/eliminations.md
Stage 4csv/consolidated-working.csv and notes/consolidation-working.md (table format, for human review)
Stage 5consolidated-FS-draft.md (the full draft) and notes/comments-and-reviews.md (comments + review notes + checklist)
Stage 6notes/qa-report.md

Final QA checklist

Everything below must be ticked before the draft is converted and uploaded.

FINAL QA QA & sign-off — tick every box before the draft is uploaded Total assets = liabilities + equity — current and prior year Every line in the statement appears in the working paper with the same number The notes tie back to the statement line items Year-on-year movements of more than 20% are explained in the comments No template sections left blank; every figure sourced Reviewers checked every figure against the source files The AI runs the sweep — the finance team does the sign-off.
The final QA sweep — every box ticked before the draft becomes the official document.

Tips specific to consolidation

  • Run the elimination stage twice (Stage 3) — inter-company mismatch is the most common cause of a non-balancing consolidated FS.
  • Keep prior-year columns in the working paper — Claude can spot-check that movements are plausible if the prior-year file is in the folder too.
  • Every comment must cite a figure. In Stage 5, tell Claude: "every comment must reference the exact figure and source file in brackets". This makes review fast.
  • If the group uses a reporting currency other than SGD for subsidiaries, ask Claude to build the FX conversion table into the working paper (rate per entity, gain/loss line) and check it in Stage 4 before finalising.
  • Minority interest: if any subsidiary is not 100% owned, ask Claude to add an NCI line (share of equity and share of profit) in Stages 4 and 5.

Sensitive-data rules for this task

CRITICAL
  • Work only in the local task folder. Do not upload drafts to any public or AI web tool.
  • Only the company-issued DeepSeek API key may be used.
  • The working folder contains confidential group financials — protect it as you would any financial file (encrypted drive / password-protected folder if shared).