Anthropic's corporate finance team published a quiet but useful piece on how they use Claude inside their close, board prep, and CFO communications. Alice Fong, who runs corporate finance and strategy, described shifting roughly ten to twenty hours per week away from rote narrative assembly and toward strategic positioning. For an Australian CFO office sitting on top of ASX continuous disclosure obligations, APRA prudential reporting, ASIC director-duties exposure, and a board that wants the story behind every variance, that figure is the interesting one.
AU finance teams sit inside a denser compliance lattice than most US counterparts. Half-year and full-year reporting cycles run alongside monthly board packs, quarterly investor briefings, and a continuous-disclosure obligation that turns every materiality call into a documented decision. The work surrounding the numbers, especially the consistent narrative across all of those artefacts, eats a disproportionate share of senior FP&A and finance team capacity. That is the work Claude removes first.
The narrative work that surrounds the numbers
Sit with a Sydney or Melbourne CFO for a week and the pattern is consistent. The numbers themselves close fairly quickly because the ERP runs on a known calendar and the team has rehearsed the trial balance. The week that follows is spent assembling the story: lining up commentary against last month, last quarter, the board's prior questions, the half-year guidance, and any ASX release sitting on the wire. A senior FP&A analyst on $180,000 to $220,000 base typically spends fifteen to twenty hours of every board cycle on that assembly. Two cycles a month times twelve months is roughly $90,000 of fully loaded time across a single role.
Scale that to a mid-cap ASX-listed CFO function with four to six analysts touching each pack, plus a financial controller and the CFO themselves, and the annual narrative cost sits comfortably between $280,000 and $420,000. Smaller private companies pay it too, just in different currencies: missed deadlines, owner-operator time, or an external advisor's hourly rate on top. Most CFOs we work with in Australia have already accepted this cost as a fact of the role. The opportunity is that Claude, applied carefully to the narrative layer and not the trial-balance layer, takes back the majority of that capacity inside a quarter.
Where Claude fits inside an AU finance team
The honest answer is: not where most vendors are selling it. Claude is not closing your books, reconciling intercompany, or replacing your financial controller's review. It is doing the assembly, drafting, and reconciliation of language that surrounds the numbers. The four places it pays for itself fastest inside an Australian finance team look like this:
Board-pack narrative assembly: pulling variance commentary from prior packs, this period's variance file, and the CFO's notes into a draft narrative the controller and CFO edit rather than write from scratch.
ASX continuous-disclosure drafting: producing a first-draft Listing Rule 3.1 announcement from the underlying material, anchored on the prior six announcements so tone and terminology stay consistent.
Monthly management reporting: commentary against budget, prior month, and prior year, in the same voice the board has been reading for the last twelve months.
Investor and analyst Q&A prep: synthesising recent analyst notes, prior-quarter calls, and the current numbers into a briefing pack before the CFO meets the sell-side.
A concrete board-pack workflow
The pattern that holds up best in practice is a Claude project per reporting entity, loaded with the prior twelve months of board packs, the company's accounting policies, the segment definitions, and a short style guide that captures the tone the board reads each month. The CFO or controller drops the current period's variance file, the operational notes from each function head, and any draft ASX wording into the project. The output is a draft pack narrative, organised in the format the board has seen before, with every figure tagged to its source so the controller's review is a verification pass rather than a write-from-scratch. End-to-end the workflow looks like this:
Load: drop the current month's variance pack, function-head notes, and any external comparators (peer ASX releases, broker notes) into the project.
Draft: ask Claude to produce a board narrative in the existing house format, calling out movements above the materiality threshold the CFO has set and flagging anything it could not source.
Reconcile: the controller checks every figure against the source file. Anything Claude could not tag goes back as an explicit question.
Edit: the CFO rewrites the two or three passages that need their own voice (typically the outlook, the asks, and the risk narrative) and accepts the rest.
Cross-check: Claude runs a final read against the last six packs and any open ASX disclosures to surface inconsistencies in tone, definition, or quoted figures.
Companies that have committed to this pattern report board-pack assembly time falling from fifteen to twenty hours per cycle to four or five, with the saved hours moving into deeper variance investigation, investor pre-reads, and the CFO actually rehearsing the board conversation. The accuracy improvement is the part most CFOs find surprising. Inconsistencies between the pack narrative, the prior ASX release, and the management commentary in the half-year report were a regular embarrassment. Claude catches them on the cross-check pass.
ASX continuous disclosure and the consistent-voice problem
Listing Rule 3.1 is not a drafting exercise; it is a judgement call about materiality and timing. Claude does not make that call. What it does well is the part that follows the call: producing a first draft that uses the same definitions, segment names, accounting treatment, and tone the market has read in the company's last six releases. ASIC's attention to misleading and deceptive statements, in the context of climate disclosure, half-year results, and forward-looking guidance, means tone drift between releases is not a cosmetic issue. It is a regulatory one. The continuity check Claude runs against prior releases is the part that pays for itself the first time a release goes out under deadline.
There is a related discipline that matters more than the speed. CFO offices that have used Claude for six months on continuous disclosure tend to write fewer and tighter releases. The reason is that the cross-check forces a conversation about whether new wording is justified by new substance. If the only reason a phrase changed is because the analyst writing the release felt like a fresh take, the question gets asked before the release goes out rather than after a market query.
What stays with the humans
Every AU CFO conversation we have ends in the same place: which decisions cannot be delegated to an AI, and how do we make sure the team treats those as inviolable. The list is shorter than most CFOs expect, but it is rigid. Approval of any external statement, the materiality call for continuous disclosure, the relationship with the auditor, and the directors' meeting itself all stay entirely with human officers. Inside the Australian regulatory perimeter, these are the items that determine personal liability for officers and directors:
Listing Rule 3.1 materiality calls: the decision to disclose, the timing, and the final wording approval.
Director sign-off on the directors' report and the half-year and full-year accounts under the Corporations Act.
Auditor interaction: representations, management letters, and responses to ISA 580 written representations.
Internal control assertions: anything that touches the CFO's signoff on the effectiveness of financial reporting controls.
Whistleblower and AUSTRAC reporting decisions: these go through the company's compliance officer, not a drafting tool.
Rolling it out across an AU CFO office in four weeks
Most AU finance teams over-engineer the rollout. The pattern that actually lands is closer to four weeks than the six-month strategic program a consulting firm will sell. The shape is to pilot one cycle, learn from the controller's edits, then expand to the next artefact. Budget around $25,000 to $40,000 of internal time and a few thousand in subscription cost for the first cycle, and expect the payback inside the second board pack.
Week 1: stand up a Claude project for the reporting entity, load the last twelve months of packs and the accounting policies, and write a one-page style guide that captures the board's preferred voice.
Week 2: run the current month's pack through the workflow alongside the existing process. The controller marks every edit, and those edits feed back into the style guide and the project notes.
Week 3: switch to Claude-first drafting. The controller's role becomes verification and tone editing. Measure assembly time and accuracy against the prior cycle.
Week 4: extend to the next artefact (typically ASX releases or the monthly investor email) and decide which third-party advisors the team can step back from.
If you are an AU CFO thinking about where Claude actually pays for itself inside your finance function, the right next step is a short conversation rather than a vendor demo. We work with Sydney and Melbourne CFO offices on the rollout above and can sit through one cycle with your controller to make the call. Book a thirty-minute brainstorm via the Automata AI contact page.
