A CFO's tutorial: consolidating a two-currency group from Xero and Zoho Books exports with Claude in three review-gated prompts

In two sentences

Zain ul Abideen, an FCCA who works as a CFO for small and mid-sized businesses, published a step-by-step method for consolidating a two-entity, two-currency group with Claude: a UK parent on Xero and a Dubai subsidiary on Zoho Books, taken from raw trial balances to a consolidated P&L and balance sheet. The key is not the arithmetic but where he makes Claude stop: three prompts, each ending in a review, and every decision that changes the group’s numbers left to the accountant.

Who does it and what kind of evidence this is

The walkthrough was published on 27 September 2026 on the site of AI for Finance Circle, the training company Zain ul Abideen founded in August 2026, and it is written up from a 13-minute video on his Claude for Finance YouTube channel published on 21 September. On his About page he says he spent more than a decade in commercial finance and FP&A for multinational groups in the UAE, moved to the UK in 2025 and serves as CFO to SMEs through CompassPoint Consulting.

Three things set the level of evidence:

• It is a demonstration on fictional data. The video description says so explicitly: dummy data for a fictional business, nothing from a real company or a live consolidation. The differences Claude “finds” were built into the data.
• The time saving is his own statement. In a LinkedIn post he says a consolidation of this kind used to take him “two, sometimes three, working days”, almost none of it judgement, and that his method now produces one in under an hour. Nobody has measured that on a real group.
• He sells training. His company sells Claude courses and workshops for finance teams, and the three exact prompts are in his free online community rather than in the public article. We therefore do not reproduce them; the briefs further down are ours.

Why it is still worth a long read: consolidation is the close task where AI demos are rarest, and this one is unusually specific about inputs, control rules and the judgement points. It is also honest about what the checks prove.

The problem it tackles

Small groups rarely have a consolidation tool. The group accountant receives exports that “export nothing the same way” (his words), a subsidiary in another currency, staff recharged between entities and an intercompany loan that agrees in one ledger and not in the other. In the demo:

• Parent: UK company reporting in GBP on Xero.
• Subsidiary: 100% owned Dubai company reporting in USD on Zoho Books, acquired on 2 January 2026.
• Four intercompany flows that must disappear every month: a monthly management fee, a staff recharge at cost plus 10%, a USD 250,000 loan with rolled-up interest and two interim dividends.
• Framework: FRS 102, GBP as the consolidation currency, and a short group accounting and consolidation policy issued by the CFO. Period: January to August 2026.

A reader on Reddit’s r/FPandA describes the same pain from the other end: an analyst in a large company whose team consolidates sensitive month-end data in Excel because it may not go to the company’s data platforms. He had Claude write a Python script, run locally, that replaced 30-plus minutes of copying tens of thousands of rows with about two minutes, and he still spends about five minutes verifying the result. Different scale, same pattern: AI writes or does the mechanical part, the person checks.

Tools and architecture

There is no integration and no connector. Everything goes through files:

1. Nineteen files in five folders, “the way a group accountant actually receives them”: business context for each entity; the agreements (management services, staff secondment and recharge, the loan, transfer pricing policy); each entity’s monthly trial balance, general ledger extract, chart of accounts, opening balances and intercompany schedule; and a group folder with the CFO’s reporting format, the consolidation policy and daily exchange rates.
2. Claude, which reads the folder and builds an Excel workbook. The walkthrough does not say which model or Claude product he used.
3. Three prompts, each one closing a milestone and ending in a stop.
4. The CFO, who reads the control sheet and the decisions log between prompts and answers in writing.

He insists on one rule that runs against most people’s instinct: do not tidy the data first. Normalising the exports is part of the work and part of the evidence trail.

Getting the exports out of Xero and Zoho Books

The walkthrough does not explain how he pulled the files, so here is what the vendors’ own help pages say, and the traps we would watch for:

• Xero. The Trial Balance by Date Range report (Reporting → All reports) shows account balances for a period, and can compare against past periods. Xero Central warns that with multicurrency the report shows balances in your base currency, and that this report calculates retained earnings for the period shown, unlike the standard Trial Balance report, which calculates it from the start of the financial year. In our reading, if you mix the two reports across months, your retained earnings line will not roll forward and the mapping will look broken when it is not.
• Zoho Books. Reports → Accountant → Trial Balance; switch As of Date to Date Range and add the Opening Balance and Closing Balance columns with Customize Report Columns to get movements and balances in one export.

Export the same report type, with the same column layout, for every month of every entity. Claude can normalise inconsistent layouts, but you will review faster if the inconsistency is not of your own making.

Step by step

Milestone 1: the foundation, with no eliminations

The first prompt makes Claude read the context, sets the rules the workbook must obey and asks for the first milestone only. The rules, as he lists them, are what make the output reviewable:

• inputs, workings and outputs on separate sheets;
• raw data loaded as received and never overtyped;
• every figure a formula that traces back to the inputs;
• one sign convention and all exchange rates in one place;
• a check on every sheet and a single control sheet;
• a decisions log recording every judgement Claude makes and why.

The milestone is to normalise both trial balances into one layout, map both charts of accounts to the group’s reporting lines (flagging anything it cannot map with confidence), and produce a master trial balance with the subsidiary translated under the group policy. Nothing is eliminated yet.

In the demo Claude returned a 27-sheet workbook, forty checks and twenty-two logged decisions, plus its questions. It had already noticed that the loan did not agree after translation, by GBP 7,583.69 at August, and left it alone because the policy says differences are investigated before elimination.

Review stop. He opens the control sheet first, then the decisions log, then the mapping gaps.

Milestone 2: the intercompany matrix, with no postings

The second prompt starts by answering Claude’s questions in writing (those answers become part of the record), then asks it to read the agreements and reconcile every intercompany balance and transaction at every month end in a matrix: each side, the difference, what Claude thinks the difference is and what it would do. It must not post anything and must wait for decisions.

Review stop. This is where the accountant earns the fee. The three decisions in the demo:

• The cut-off. The recharge invoice is dated 31 August and the agreement makes it an August cost, so the subsidiary’s books are the incomplete ones and the accrual goes there.
• The rate residual. Both entities followed their agreements; the GBP 140 comes from translating at monthly averages what the subsidiary booked at daily spot. Nothing is wrong in either ledger, and the group policy sends it to foreign exchange.
• The loan. Claude set out both possible treatments and did not pick one. Under FRS 102 section 30, as the ICAEW helpsheet summarises it, exchange differences on a monetary item that forms part of the net investment in a foreign operation (settlement neither planned nor likely in the foreseeable future) go to other comprehensive income and equity in the consolidated accounts, and are never recycled; otherwise they go to profit or loss. The agreement makes the loan repayable on demand with repayment expected in 2027, so he treats it as an ordinary receivable. Had the agreement said otherwise, he notes, group profit would have been GBP 7,584 higher. “That is a judgement, not a calculation.”

A small inconsistency worth knowing about: the article speaks of three problems built into the data, while the video description says Claude found four intercompany differences. We report the three the article details.

Milestone 3: post, eliminate and report

The third prompt opens with his decisions on each difference, then asks Claude to:

• post the corrections as labelled consolidation adjustments, so the input sheets stay exactly as received;
• post the eliminations at every month end, including the investment against the subsidiary’s equity, with goodwill and its amortisation;
• produce three outputs in the CFO’s format: the consolidated P&L, a five-column consolidation view (each entity, adjustments, eliminations, group) and the consolidated balance sheet with a balance check in every column.

He is explicit that in real life the entity accountants would correct their own ledgers and send fresh trial balances; the adjustments are how the demo keeps moving while leaving an honest record.

A starting brief (ours, not the author’s)

These are our own skeleton briefs following the structure he describes. Replace the bracketed parts and keep the stop sentence at the end of each one.

Brief 1. “Read every file in [GROUP FOLDER]. Build an Excel workbook that obeys these rules: [the six rules above]. Milestone 1 only: normalise the trial balances of [ENTITY A] and [ENTITY B] into one layout, map both charts of accounts to the lines in [REPORTING FORMAT], list anything you cannot map with confidence, and translate [ENTITY B] under [POLICY FILE]. Do not eliminate anything. Record every judgement in the decisions log. End by listing your questions and stop.”

Brief 2. “My answers to your questions: [ANSWERS]. Read the agreements and reconcile every intercompany balance and transaction at every month end in a matrix with both sides, the difference, your explanation and your proposed treatment, citing the clause or policy you rely on. Do not post any adjustment. Stop and wait for my decisions.”

Brief 3. “My decisions: [DECISION AND REASON FOR EACH DIFFERENCE]. Post them as labelled consolidation adjustments without changing the input sheets. Post all eliminations at every month end, including investment against equity and goodwill under [POLICY]. Produce the consolidated P&L, the five-column view and the balance sheet with a balance check in every column. Update the control sheet and the decisions log, then stop.”

Results, as stated

• Time: from “two, sometimes three working days” to “under an hour”, according to the author. Not measured by a third party and not shown on a real group.
• Output in the demo: 27 sheets, 40 checks, 22 logged decisions; all checks reading zero at the end; every group figure traceable to a trial balance.
• What Claude found: the three planted differences above. It did not decide any of them.

Limitations and risks

• Fictional, clean-ish data. Two entities, one currency pair and four known flows. Real groups bring minority interests, mid-year acquisitions with fair-value adjustments, hyperinflation, more entities and messier agreements.
• Checks prove consistency, not correctness. He says it himself: checks that read zero tell you the model agrees with itself, not that it is right.
• Judgement can be smuggled in. Mapping a chart of accounts is a series of small judgements. The decisions log only helps if someone reads it.
• Confidential data. Agreements, trial balances and payroll recharges are sensitive. Check what your Claude plan does with uploaded files, and whether your firm allows it, before you start.
• Accounting framework. The loan decision is specific to FRS 102. Under IFRS (IAS 21) the logic is similar, although those differences are reclassified to profit or loss when the foreign operation is disposed of; under other local GAAPs, including the Spanish chart of accounts, check the rule before copying the treatment.

Common mistakes

• Asking for the consolidated statements in one prompt, so there is nowhere to stop and look.
• Cleaning the exports by hand before giving them to Claude, which destroys the trail back to the source.
• Letting Claude “fix” an entity’s books instead of posting a labelled adjustment.
• Reviewing the numbers before the control sheet and the decisions log.
• Mixing Xero’s standard and date-range trial balance reports across months, which breaks retained earnings.

Conclusions

The interesting part of this tutorial is not that an AI can add up two trial balances; it is the discipline around it: rules written into the first prompt, milestones that end in a stop, written answers that become audit trail, and a clear line between what Claude prepares and what the accountant decides. The evidence is a single practitioner’s demonstration on dummy data, so try it first on a group you have already closed and compare every line before you rely on it.