The CFO's Guide to Claude Cowork

The CFO's Guide to
Claude Cowork

A practical implementation guide for CFOs and finance leaders — covering setup, integration patterns, and 10 production-ready workflows for closing, reporting, forecasting, and compliance. Adapt the stack, file paths, and thresholds to your own environment.

Version 1.0
Current release
CFOs & Finance Leaders
Target audience
NetSuite · Google · Excel
Your stack
~45 min read
Full guide
Part I

Foundation

What Claude Cowork is, how it differs from other AI tools, and the conceptual framework finance leaders need before deploying it.

01

Introduction & Executive Summary

How to Use This Guide

This guide is designed to be adapted, not followed verbatim. File paths reference a Finance_Cowork/ folder structure — rename these to match your own drive. ERP navigation examples use NetSuite, but the export logic applies to any ERP. Workflow prompts use placeholder column names — update them to match your actual export headers before running for the first time.

Finance leaders spend a disproportionate share of their week on work that is necessary but not strategic — assembling reports, reconciling data across systems, chasing approvals, formatting variance commentary, and packaging material that someone else reads in five minutes. Conservative estimates put this at 12–18 hours per week for a typical finance team member.

Claude Cowork is Anthropic's desktop tool designed for non-developers who want to automate repeatable, multi-step workflows across files and applications. For finance teams, this narrows the gap between "we have a process" and "that process mostly runs itself" — without requiring IT involvement or a line of code.

What This Guide Covers

This guide is written for CFOs and senior finance leaders who want to move past experimentation and deploy Cowork as a genuine operational tool.

  • Part I — The conceptual foundation: what Cowork is and how it differs from other AI tools
  • Part II — Implementation: connecting your stack, configuring security, building your first automation
  • Part III — Ten concrete, fully-specified finance workflows ready to adapt and deploy
  • Part IV — Scaling: team rollout, measuring ROI, and change management
The Strategic Case

This is about cognitive reallocation, not headcount reduction. When your finance team stops assembling data and starts interpreting it, you get better forecasts, faster decisions, and professionals who operate as strategic partners rather than report factories.

02

What is Claude Cowork & How It Differs

Anthropic offers multiple ways to work with Claude. Understanding the distinctions is important before choosing which tool to deploy for which finance task:

ProductPrimary UseFinance Application
Claude.ai Conversational analysis, drafting, ad-hoc questions Drafting board commentary; asking one-off analytical questions; reviewing a contract
Claude Code Developer-grade automation; API and ERP integrations; advanced scripting Building custom financial models; direct ERP API integrations (requires technical skill)
Claude Cowork Repeatable desktop workflows for non-developers; file and task automation Automating the monthly close; assembling board packs; processing NetSuite exports into reports

Cowork operates at the desktop level. It reads files on your computer, processes them using Claude's intelligence, and produces outputs — populated templates, summaries, alerts, or completed documents. You invoke it manually via plain-language instructions or saved shortcuts. It does not run as a background service or independently monitor your file system unless paired with OS-level scheduling tools.

Important Expectation Note

Cowork is powerful but is an on-demand tool, not a fully autonomous background agent. You trigger it — either manually or via an OS scheduler — and it executes. This is by design: for financial workflows, having a human trigger point before processing is a feature, not a limitation.

The Core Cowork Loop

You Trigger
A shortcut you run manually, or one scheduled via OS Task Scheduler / macOS Automator
Cowork Reads
Specified files on your computer: NetSuite exports, spreadsheets, PDFs, prior reports
Claude Processes
Analyses, compares, writes, summarises, or calculates using your instructions
You Review
A draft document, alert, or updated file — always reviewed by a human before use
03

Core Concepts for Finance Leaders

You don't need to be technical to use Cowork effectively. These four concepts cover everything you need to design and operate finance automations.

Shortcuts (Workflows)

Saved, reusable automation instructions you write once and run repeatedly. A "Run Month-End Close Package" shortcut will follow the same logic every time, applied to whatever input files you point it at.

Instructions (Prompts)

Plain-English directions that tell Cowork exactly what to do, what files to read, what logic to apply, and what output to produce. The more specific your instructions, the more consistent and useful your outputs will be.

Context Files

Reference documents you provide to give Cowork background about your organisation — your chart of accounts, entity list, variance thresholds, reporting calendar. Better context = better outputs.

Outputs

Files Cowork produces: populated Word or Excel templates, written summaries, alert documents, or drafted emails. Outputs are always created as new files — Cowork does not modify your source data.

Design Principle

The best Cowork automations mirror how a skilled analyst would approach the task — they have a defined starting point, clear instructions, a consistent output format, and a built-in human review step before anything consequential happens downstream.

04

Prerequisites & Setup Checklist

The investment you make in pre-work directly determines the quality of every automation you run. Most items here take under 30 minutes. A few require IT coordination.

Technical Prerequisites

Process Prerequisites

Governance Prerequisites

Part II

Implementation

Connecting your finance stack, configuring Cowork, and building your first working automation end-to-end.

05

Getting Started: First-Time Configuration

First-time setup for a finance team takes 2–3 hours if done properly. That investment determines the quality of everything you run afterward.

Step 1 — Install & Authenticate

Download and install Cowork from Anthropic's website on your desktop. Sign in with your Anthropic account credentials. If your organisation uses a Claude Team plan, join the correct shared workspace so shortcuts can be shared across your finance team.

Step 2 — Create Your Finance Folder Structure

Create a dedicated folder in Google Drive named Finance_Cowork — this is Cowork's working area. Once created, it will sync to your desktop automatically via the Google Drive for Desktop app, making it accessible as a local folder on your machine. A clean, predictable structure prevents automations from operating on the wrong files and makes troubleshooting straightforward.

📁 Finance_Cowork/ ├── 📂 inputs/ ← NetSuite exports land here │ ├── 📂 gl_exports/ │ ├── 📂 monthly_close/ │ ├── 📂 payroll/ │ ├── 📂 banking/ │ ├── 📂 expenses/ │ ├── 📂 contracts/ │ ├── 📂 intercompany/ │ ├── 📂 board_packs/ │ ├── 📂 cashflow/ │ ├── 📂 Budgets/ │ └── 📂 audit/ │ └── 📂 evidence/ │ ├── 📂 templates/ ← Board pack, mgmt pack, audit schedule templates │ └── 📂 audit/ │ ├── 📂 outputs/ ← Cowork drafts — never write back to NetSuite │ ├── 📂 monthly_close/ │ ├── 📂 board_packs/ │ ├── 📂 expenses/ │ │ └── 📂 emails/ │ ├── 📂 working_capital/ │ ├── 📂 variance/ │ │ └── 📂 emails/ │ ├── 📂 bva/ │ ├── 📂 contracts/ │ ├── 📂 cashflow/ │ ├── 📂 intercompany/ │ ├── 📂 audit/ │ │ ├── 📂 organised/ │ │ └── 📂 schedules/ │ └── 📂 alerts/ │ └── 📂 context/ ← Chart of accounts, entity list, FX rates, thresholds

Step 3 — Build Your Context Library

The context library is a folder of reference files that you point Cowork to within your automation instructions. The more it knows about your organisation, the less you need to explain each time. Key files to prepare:

Step 4 — Validate with a Simple Test Before Building Complex Workflows

Before committing to complex automation builds, run a basic validation: ask Cowork to summarise a recent GL export in plain English, or compare two monthly P&Ls and list the five largest movements. This confirms Cowork can correctly read your specific export column structure and handle your file format — issues here will cascade into every workflow you build.

Common First Mistake

Building a sophisticated monthly close automation before validating that Cowork correctly reads NetSuite's CSV column structure. Always test with a simple read task first. Your ERP may export numbers with commas as thousands separators, or dates in non-standard formats — identify these early.

06

Connecting Your Finance Stack

Your Stack at a Glance

NetSuite is your source for all financial data exports (GL, trial balance, aging, budgets, intercompany). Google Drive is your file hub — all inputs and outputs live in your synced Finance_Cowork folder, accessible from any device. Google Docs & Sheets are your primary document and spreadsheet formats; download as .docx / .xlsx when Cowork needs to read or write structured files. Excel handles complex financial models (cash flow, BvA dashboard) where Google Sheets falls short on advanced formatting. Gmail receives your Cowork-drafted email content — paste, review, and send manually.

Cowork does not require native integrations with your ERP or payroll systems. It works through file-based inputs — exports you pull from NetSuite and save to your Google Drive inputs folder, which Cowork then reads and processes. This keeps setup simple and avoids any write-access risk to live systems.

The Two Core Integration Patterns

Pattern A — Manual Export + Shortcut

You run your standard ERP report, save the export to the inputs folder, then invoke the relevant Cowork shortcut. This is the most reliable pattern and gives you full control over which data version is processed. Best for month-end and board pack workflows.

Pattern B — Scheduled Export + OS Scheduler

Configure your ERP to email or drop a scheduled export (e.g., daily GL export at 6am). Use Windows Task Scheduler or macOS Automator to save the file and launch the Cowork shortcut at a set time. More complex to set up but reduces manual steps for recurring workflows like cash monitoring.

Hard Boundary

Cowork should have read-only access to export files only — never write access to your live ERP, payroll system, or banking platform. Cowork reads exports and writes to your Google Drive outputs folder (synced locally). A human reviews outputs before anything is uploaded, sent, or acted upon. This preserves your ERP as the system of record and maintains an auditable human-in-the-loop control.

Recommended Export Configurations by System Type

SystemRecommended Export FormatKey Config Notes
Cloud ERP (NetSuite, Sage Intacct, MS Dynamics, QuickBooks) CSV with column headers in row 1 Include: account code, account name, entity, period, debit, credit, running balance. Exclude subtotals/summary rows — Cowork works better with raw transaction-level or account-level detail.
Payroll Platforms (Deel, Remote, Rippling, ADP) CSV payroll register Use employee ID rather than full name where possible. Include: cost centre, gross pay, statutory deductions, net pay, jurisdiction. Aggregate by cost centre if headcount data is sensitive.
Banking & Treasury CSV statement (OFX can be converted) Include: date, description, debit, credit, balance, reference. Remove account numbers from file — reference by last 4 digits or account nickname only.
Excel-based Models XLSX (direct, no export needed) Ensure data is in clean tabular format: consistent column headers in row 1, no merged cells in the data range, no formulas in rows that Cowork will read as data.
AP/AR Platforms CSV aging report Include: vendor/customer name, invoice date, due date, amount, aging bucket (current/30/60/90+), currency. One row per invoice — not pre-summarised by vendor.
07

Security, Access Controls & Data Governance

As CFO, data governance is your responsibility to define before any team-wide deployment. Work through this framework with your IT security and legal teams.

Data Classification Framework

Data TypeRisk LevelCowork Guidance
Management P&L, variance reports, KPI dashboards Medium Permitted. Classify outputs as "Management – Confidential" and restrict distribution to authorised recipients.
Individual payroll records (names + salaries) High Use aggregate exports by cost centre only. Anonymise to Employee ID before passing to Cowork. Review Anthropic's enterprise data handling terms before proceeding.
Full bank account numbers, routing details Critical Do not include in any Cowork input file. Reference accounts by last 4 digits or nickname only.
Pre-release investor or M&A financials Critical Consult legal before using Cowork for this data. Apply strict need-to-know access controls on all outputs.
Budget vs. actuals, operational metrics Medium Permitted. Label outputs with your internal confidentiality classification.
Publicly available benchmarks, market rates Low No restrictions.

Access Control Recommendations

Non-Negotiable Internal Control

Every Cowork output is an AI-assisted draft until a qualified human has reviewed and approved it. Build a named, documented sign-off step into every finance automation before any output is distributed, filed with a regulator, or used to make a payment decision. "The AI produced it" is not an acceptable internal control response during an audit.

08

Building Your First Automation — A Walkthrough

This walkthrough builds a practical first automation: a weekly P&L summary draft. It is intentionally simple so you can focus on the mechanics before tackling the complex workflows in Part III.

1
Write the task in plain English
Before opening Cowork, create your Finance_Cowork folder in Google Drive (it will sync to your desktop automatically via the Google Drive desktop app). Then write a paragraph describing exactly what you want: "Read the current month P&L export, compare it to last month, identify the top 3 variances above 5%, and draft a 200-word email summary for the leadership team." Getting this clear on paper first produces significantly better automation instructions.
2
Prepare and name your input files consistently
Save the current month P&L to Google Drive/Finance_Cowork/inputs/gl_exports/PL_Current.csv and prior month to Google Drive/Finance_Cowork/inputs/gl_exports/PL_Prior.csv. Using fixed names (not date-stamped for the first test) keeps the instruction simple to write.
3
Create a new Shortcut in Cowork
Open the Cowork desktop application and select "New Shortcut." Name it clearly — "Weekly P&L Summary Draft." Start with "Run manually" as the trigger. Add scheduling once you've validated the output quality.
4
Write specific, detailed instructions
Paste your instructions into the shortcut. Reference exact file paths. Specify output format, variance threshold, and tone. Vague instructions produce vague outputs — the more specific you are, the less editing you'll do on the other end.
Example Automation Instructions Read the file at Google Drive/Finance_Cowork/inputs/gl_exports/PL_Current.csv (this month's P&L) and Google Drive/Finance_Cowork/inputs/gl_exports/PL_Prior.csv (last month's P&L). Both files have the following columns: Account Code, Account Name, Current Month ($), Prior Month ($). Rows are individual P&L line items. Step 1: Calculate the variance for each row: (Current - Prior) in $ and as % of Prior. Step 2: Rank all rows by absolute dollar variance, descending. Step 3: Identify the top 3 rows where the % variance exceeds 5%. Step 4: Write a 150-200 word email draft addressed to the leadership team that: — States the month-to-date net revenue and EBIT headline figures — Calls out the top 3 variances with a brief factual description of each — States whether the business is tracking ahead or behind the prior month Output: Save the draft to Google Drive/Finance_Cowork/outputs/PL_Summary_Draft.docx. Do not send anything. This is a draft only for CFO review.
5
Run, review, and iterate
Run the shortcut and review the output critically. Expect to refine 2–4 times. Common issues on first run: the output format isn't quite right, the tone is too generic, or Cowork misread a column name. Each refinement to your instructions makes every future run better.
6
Once satisfied: add scheduling (optional)
If your ERP deposits a fresh export every Monday morning, use Windows Task Scheduler (Windows) or macOS Automator (macOS) to trigger the Cowork shortcut automatically at 7:00 AM. This turns a manual step into a near-autonomous recurring output. Cowork must be open and logged in for this to work.
Time Reality Check

A well-built automation like this takes 60–90 minutes to configure and validate. Once running, it saves 2–4 hours per week. The payback period is less than one week of use. Every subsequent automation you build is faster because your context library and templates are already in place.

Part III

The 10 CFO Workflows

Ten production-ready automation workflows — each guide follows the same pattern: export data from your ERP, save files to your local working folder, run the Cowork shortcut, and review the output. Adapt file paths, column names, and thresholds to match your own systems.

How Every Workflow Works — Read This First

If this is your first time using Claude Cowork, every workflow in this section follows the same five-step pattern. Once you've done it once, the rest will feel familiar.

Step 1
Gather your files
Export the files listed in "Before You Start" from NetSuite or your other sources, and save them to your Google Drive/Finance_Cowork/inputs/ folder (synced locally via Google Drive for Desktop)
Step 2
Open Cowork
Launch the Cowork desktop app and sign in. Click New Shortcut and give it a clear name
Step 3
Paste the prompt
Copy the Sample Prompt from this guide, paste it into Cowork, and replace all [BRACKETED] text with your real values
Step 4
Click Run
Hit Run and wait. Most workflows take 1–3 minutes to complete. Do not close Cowork while it runs
Step 5
Review the output
Open the output file in your /outputs/ folder. Check numbers, read commentary, and approve before using or distributing
First-Timer Rule

Never use or distribute a Cowork output without reading it first. Every output is an AI-assisted draft — you are the reviewer, approver, and accountable person. This is not optional; it is a basic internal control that must be documented.

01
Monthly Close · Reporting
Monthly Close Package Automation
Assemble the full month-end management reporting package — P&L, balance sheet, cash summary, and variance commentary — from NetSuite exports into a board-ready draft document.
⏱ Saves 6–10 hrs/month ★ High Impact Finance team-wide
Required Inputs
  • Trial balance export — current month and prior month (CSV)
  • Balance sheet export (CSV)
  • Year-to-date budget file (same structure as actuals)
  • Prior month management pack (for consistency reference)
  • Output template (your standard management pack format — DOCX or XLSX)
Expected Outputs
  • Populated management reporting template
  • Executive summary with CFO commentary draft (marked where your judgement is needed)
  • Variance analysis table: actuals vs. budget and vs. prior month
  • Top material variances listed with factual one-sentence commentary each
  • KPI summary section
  • Anomalies flagged for human review before distribution
📁 Before You Start — Exporting from NetSuite & Google Drive
A
Export four reports from NetSuite
In NetSuite, navigate to Reports → Financial. For each report, click Export → CSV from the report toolbar. Save to your synced Google Drive folder:

• Trial Balance (this month): Reports → Financial → Trial Balance → set Period to current month → Export CSV → save as Google Drive/Finance_Cowork/inputs/monthly_close/TB_Current.csv
• Trial Balance (prior month): Same report, change period to prior month → Export CSV → save as Google Drive/Finance_Cowork/inputs/monthly_close/TB_Prior.csv
• Budget YTD: Reports → Budgeting → Budget vs. Actual → Export CSV → save as Google Drive/Finance_Cowork/inputs/monthly_close/Budget_YTD.csv
• Balance Sheet: Reports → Financial → Balance Sheet → Export CSV → save as Google Drive/Finance_Cowork/inputs/monthly_close/BalanceSheet_Current.csv

NetSuite tip: Save each as a Saved Report (Customize → Save As) so next month is a one-click run — no need to reconfigure periods or filters.
B
Prepare your management pack template in Google Docs
Open your existing management pack in Google Docs (or upload your Word template to Google Drive and open it). Add placeholder markers where Cowork should insert content:

[INSERT P&L TABLE HERE]
[INSERT CFO COMMENTARY HERE]
[INSERT VARIANCE ANALYSIS HERE]

Then: File → Download → Microsoft Word (.docx)
Save the .docx to: Google Drive/Finance_Cowork/templates/ManagementPack_Template.docx

Keep the Google Doc as your master — download a fresh copy each month. Cowork writes to the .docx; you review and reopen in Google Docs for final editing.
🖥️ Step by Step in Cowork
1
Open Cowork and create a new Shortcut
Launch the Cowork desktop app. Click New Shortcut in the left panel. Name it something clear like "Monthly Close Package". Set the trigger to Run Manually for now — you can add scheduling later once you've validated the output.
2
Paste the prompt below and personalise it
Copy the Sample Automation Prompt below and paste it into the Shortcut instructions. Then replace every item in [BRACKETS] with your real values — your file paths, your materiality thresholds (e.g., "flag variances over $10,000 or 8%"), and your company's account groupings. The more specific you are here, the less editing you'll do on the output.
3
Click Run and wait (approx. 2–4 minutes)
Hit Run. Do not close Cowork while it works. You'll see it processing in real time. When it finishes, it will show a completion message and the output file will appear in your Google Drive/Finance_Cowork/outputs/monthly_close/ folder.
4
Refine the instructions if needed (expect 2–3 iterations)
First runs rarely produce a perfect output — and that is completely normal. The most common issues on a first run: a column name doesn't match what you told Cowork, the output format is slightly off, or the commentary tone needs adjusting. Each refinement takes 5 minutes and every future run benefits from it.
Sample Automation Prompt — Copy, Paste, Personalise Read the following CSV files from Google Drive/Finance_Cowork/inputs/monthly_close/: - TB_Current.csv: current month trial balance (columns: Account, Description, Debit, Credit, Balance) - TB_Prior.csv: prior month trial balance (same structure) - Budget_YTD.csv: year-to-date budget (columns: Account, Description, Budget_YTD) Also read the template at Google Drive/Finance_Cowork/templates/ManagementPack_Template.docx. Tasks: 1. Build a P&L from the trial balance using the account groupings in Google Drive/Finance_Cowork/context/chart_of_accounts.csv. Show: Current Month Actual, Prior Month Actual, Month Variance ($), Month Variance (%), Budget YTD, Actual YTD, YTD Variance ($), YTD Variance (%). 2. Identify all line items where month variance exceeds [YOUR THRESHOLD e.g. $10,000 or 8%]. 3. For each material variance, write one factual sentence (direction + magnitude only). Mark these lines [CFO TO ADD CONTEXT] — do not invent causes. 4. Write a 3-paragraph executive summary: (a) headline P&L result vs. budget, (b) top 3 variances explained factually, (c) cash and balance sheet highlights. 5. Insert all of the above into the template at the marked placeholder locations. 6. Save draft to Google Drive/Finance_Cowork/outputs/monthly_close/MgmtPack_[MONTH]_DRAFT.docx

Tip: To review collaboratively, upload the output .docx to Google Drive and open with Google Docs (right-click → Open with → Google Docs). To edit privately, open directly in Microsoft Word.

✅ Reviewing Your Output — What to Check Before Distributing
  • Headline numbers: Spot-check net revenue and EBIT against NetSuite — these must match exactly
  • Variance calculations: Pick 3–4 line items and verify the $ and % variances manually
  • Commentary: Read each AI-drafted commentary sentence — remove or correct anything factually wrong. Add your strategic context where you see [CFO TO ADD CONTEXT]
  • Template placeholders: Confirm all [INSERT ... HERE] markers have been replaced and none remain in the output
  • Sign off before sharing: Do not distribute to leadership or the board until a qualified person has reviewed and approved — document your sign-off
02
Expense Management · Compliance
Expense Report Policy Compliance Review
Automatically review all submitted expense reports against your expense policy — flagging violations, categorising breach types, calculating policy-non-compliant spend, and drafting exception notifications to managers before reimbursement is processed.
⏱ Saves 3–5 hrs/week ★ High Impact Controllers / Finance Ops
Required Inputs
  • Expense report export from your expense platform (CSV or XLSX — one row per line item)
  • Expense policy document (PDF or DOCX — your current approved policy)
  • Per-diem and category spending limits reference (context CSV)
  • Employee-to-manager mapping (context CSV — for notification drafts)
  • Prior period compliance report (for trend comparison)
Expected Outputs
  • Full compliance review — every line item flagged as COMPLIANT, EXCEPTION, or REQUIRES RECEIPT
  • Policy breach summary by violation type (e.g., over-limit, missing receipt, unapproved vendor, personal expense)
  • Total non-compliant spend value by department and by employee
  • Repeat offender flag — employees with policy violations in 2+ consecutive periods
  • Draft exception emails to line managers (not sent — draft only)
  • Clean summary for finance sign-off before payroll/reimbursement run
📁 Before You Start — Exporting from NetSuite & Google Drive
A
Export expense data from NetSuite at the line-item level
In NetSuite, navigate to Reports → Employees → Expense Reports. Run the Expense Report Detail report for the current period. Click Export → CSV — this gives one row per expense line item (not one row per report).

For the most control, use a Saved Search: Lists → Search → Saved Searches → New → select Expense Report → add columns for Employee, Submission Date, Expense Date, Category, Amount, Currency, Receipt Attached, Business Purpose, Department. Export as CSV.

Save as: Google Drive/Finance_Cowork/inputs/expenses/Expense_Export.csv
B
Create your policy limits reference file
Open Google Sheets and create a new spreadsheet with these columns: Category, Per_Item_Limit, Daily_Limit, Receipt_Threshold, Notes. One row per expense category (meals, travel, accommodation, per diem, etc.).

Export as CSV: File → Download → Comma Separated Values (.csv)
Save as: Google Drive/Finance_Cowork/context/expense_limits.csv

Keep the Google Sheet as the editable master — re-export to CSV whenever policy thresholds are updated. Every future automation run picks up the changes automatically.
C
Copy your expense policy PDF into the context folder
Save your current expense policy document as Google Drive/Finance_Cowork/context/Expense_Policy.pdf. Cowork reads this alongside the limits file to understand qualitative rules (approved vendors, prohibited categories, etc.).
🖥️ Step by Step in Cowork
1
Open Cowork and create a new Shortcut
Launch Cowork. Click New Shortcut. Name it "Expense Compliance Review". Set the trigger to Run Manually. You can schedule it to run automatically before each reimbursement cycle once you're happy with the output quality.
2
Open your expense export and confirm the exact column names
Before pasting the prompt, open your Expense_Export.csv and look at the header row. Note the exact column names for: employee name, expense date, category, amount, currency, receipt attached, and business purpose. You'll need to replace the column names in the prompt with your real ones — they vary by platform.
3
Paste the prompt and customise your policy rules
Copy the Sample Automation Prompt below. In the checks section, update the dollar thresholds and rules to match your actual policy. The more precisely your rules match your policy document, the fewer manual exceptions you'll need to resolve.
4
Run 48 hours before your reimbursement cycle
Time this to run before — not after — your payroll or reimbursement run. This gives you 48 hours to resolve flagged exceptions, get manager approvals, or override with documented justification. Running it after the fact defeats the purpose entirely.
Practical Setup Note

When exporting from NetSuite, always use the Expense Report Detail report or a custom Saved Search — not the summary-level Expense Report report. The detail version gives one row per expense line item; the summary gives one row per report, which isn't specific enough for policy compliance checking. If you use a Saved Search, confirm the exported CSV has the column headers listed in the prompt before running.

Sample Automation Prompt — Copy, Paste, Personalise Read the expense report export at Google Drive/Finance_Cowork/inputs/expenses/Expense_Export.csv. Columns: Employee_ID, Employee_Name, Submission_Date, Expense_Date, Category, Amount_Local, Currency, Merchant, Receipt_Attached (Y/N), Business_Purpose, Cost_Centre, Manager_ID. Read the policy limits at Google Drive/Finance_Cowork/context/expense_limits.csv. Read the employee-manager mapping at Google Drive/Finance_Cowork/context/employee_managers.csv. Read the full expense policy at Google Drive/Finance_Cowork/context/Expense_Policy.pdf. For each line item, apply the following checks: 1. AMOUNT LIMIT: Is the amount within the per-item limit for this Category? If over: flag as [POLICY BREACH — OVER LIMIT]. State: limit, actual, overage. 2. RECEIPT: Is Receipt_Attached = Y for all items over $25? If missing: flag as [POLICY BREACH — MISSING RECEIPT]. 3. BUSINESS PURPOSE: Is the Business_Purpose field populated? If blank: flag as [REQUIRES BUSINESS PURPOSE]. 4. CATEGORY CHECK: Is the Category a recognised policy category? If not in the limits file: flag as [UNRECOGNISED CATEGORY — REVIEW]. 5. DATE CHECK: Is the Expense_Date more than 90 days before Submission_Date? If yes: flag as [LATE SUBMISSION — POLICY ALLOWS 90 DAYS MAXIMUM]. After checking all line items: 6. Calculate total spend by COMPLIANT vs. EXCEPTION status, by department. 7. List any Employee_ID who has EXCEPTION flags in both this period and the prior period report at Google Drive/Finance_Cowork/outputs/expenses/Compliance_Prior.xlsx. Mark these: [REPEAT POLICY EXCEPTION — ESCALATE TO MANAGER]. 8. For each manager with team members who have EXCEPTION flags, draft a short email (3–5 sentences) listing the specific exceptions requiring resolution. Save drafts as Google Drive/Finance_Cowork/outputs/expenses/emails/Manager_[ManagerID]_Draft.txt. Do not send. 9. Save the full compliance report to: Google Drive/Finance_Cowork/outputs/expenses/Compliance_Report_[date].xlsx with: — Tab 1: All line items with compliance status — Tab 2: Exceptions only, sorted by breach type — Tab 3: Department summary (total spend, compliant %, exception %) — Tab 4: Repeat offenders
✅ Reviewing Your Output — What to Check Before Acting
  • Spot-check 5 flagged items: Pick five exceptions at random and verify manually against the source export — confirm the flag is correct before escalating to managers
  • Check the "compliant %" total: If it's unusually low (below 70%) your policy limits file may have a threshold set incorrectly — review before sending manager emails
  • Review repeat offender list: These are sensitive conversations — confirm the flags before escalating. Verify the prior period file was read correctly
  • Manager draft emails: Read every draft email before it leaves your system. Edit tone as needed — Cowork's tone is factual, not diplomatic. You add the diplomacy
  • Never auto-send: The prompt explicitly instructs Cowork not to send. Confirm the output folder contains .txt draft files, not sent emails
03
Working Capital · Cash
AP/AR Aging Exception Alerts
Process AP and AR aging reports to surface overdue balances, concentration risks, upcoming payment obligations, and early payment discount opportunities — with a prioritised action list.
⏱ Saves 2–4 hrs/week ★ High Impact Controllers / Finance Ops
Required Inputs
  • AR aging report by customer (CSV — one row per invoice)
  • AP aging report by supplier (CSV — one row per invoice)
  • Customer credit limit file (CSV — customer name, limit, currency)
  • Prior period aging (for trend comparison)
Expected Outputs
  • AR: Top 10 overdue accounts — dollar value and days outstanding
  • AR: Accounts where 60+ day balance exceeds credit limit
  • AR: DSO calculation and movement vs. prior period
  • AP: Invoices due in next 7 and 14 days
  • AP: Early payment discounts within window
  • AP: DPO calculation and movement
  • Working capital health one-pager with RAG status
📁 Before You Start — Exporting from NetSuite & Google Drive
A
Export AR and AP Aging Detail reports from NetSuite
In NetSuite, run these two aging reports at the transaction (invoice) level — one row per open invoice:

• AR Aging Detail: Reports → Accounts Receivable → Accounts Receivable Aging Detail → Export CSV → save as Google Drive/Finance_Cowork/inputs/ar_aging.csv
• AP Aging Detail: Reports → Accounts Payable → Accounts Payable Aging Detail → Export CSV → save as Google Drive/Finance_Cowork/inputs/ap_aging.csv

NetSuite tip: Before exporting, select "No Grouping" in the report options to get clean one-row-per-invoice data without subtotals. Subtotals in the CSV will break the Cowork analysis.
B
Create a customer credit limits file in Google Sheets
Create a new Google Sheet with columns: Customer_Name, Credit_Limit, Currency. One row per client or customer. Credit limits are typically defined in customer contracts or set by your credit team — check your CRM or contract management system if you don't have them centrally documented.

Export as CSV: File → Download → CSV
Save as: Google Drive/Finance_Cowork/context/credit_limits.csv
🖥️ Step by Step in Cowork
1
Open Cowork and create a new Shortcut
Launch Cowork. Click New Shortcut. Name it "AP/AR Aging Exception Alert". Set the trigger to Run Manually. Once validated, you can schedule this to run every Monday morning automatically — just ensure Cowork is open when the schedule triggers.
2
Check your aging report column names
Open your ar_aging.csv and check the exact column headers. Common ones include: Customer, Invoice_Date, Due_Date, Amount, Days_Overdue, Aging_Bucket. Note them down — you'll reference them in the prompt so Cowork reads the file correctly.
3
Paste the prompt and set your overdue thresholds
Copy the Sample Automation Prompt below. Update the aging bucket thresholds to match your business (e.g., you may use 30/60/90/120+ buckets instead of the default). Set your DSO target — Cowork will flag when you're running above it.
4
Click Run — output arrives in under 2 minutes
Hit Run. The output XLSX will appear in Google Drive/Finance_Cowork/outputs/working_capital/. Open it and review before sharing with the collections or AP team.
Sample Automation Prompt — Copy, Paste, Personalise Read Google Drive/Finance_Cowork/inputs/ar_aging.csv and Google Drive/Finance_Cowork/inputs/ap_aging.csv. Both files have columns: Vendor/Customer, Invoice_Date, Due_Date, Amount, Currency, Days_Overdue, Aging_Bucket (Current/1-30/31-60/61-90/91+). Read credit limits from Google Drive/Finance_Cowork/context/credit_limits.csv. AR Analysis: 1. List all customers with invoices in the 61-90 or 91+ bucket, ranked by total amount DESC. Flag any customer where total 60+ day balance exceeds their credit limit. 2. Calculate DSO: (Total AR Outstanding / [INSERT YOUR AVERAGE DAILY REVENUE]). Compare to your target DSO of [INSERT YOUR DSO TARGET] days. Flag if exceeded. 3. Identify the top 5 customers by total outstanding balance regardless of aging bucket. 4. Flag any single invoice over [INSERT YOUR LARGE INVOICE THRESHOLD e.g. $50,000] that is more than 30 days overdue. AP Analysis: 5. List all supplier invoices due in the next 7 days. Total the cash required. 6. List all supplier invoices due in the next 14 days. Total the cash required. 7. Identify any invoices with early payment discount terms where the discount window has not yet expired. Calculate the discount value. 8. Calculate DPO: (Total AP Outstanding / [INSERT YOUR AVERAGE DAILY COGS]). Output: 9. Save a working capital health summary to: Google Drive/Finance_Cowork/outputs/working_capital/AgingAlert_[date].xlsx Tab 1: AR exceptions (overdue, credit limit breaches) Tab 2: AP calendar (due this week, due next week, discount opportunities) Tab 3: One-page working capital dashboard with DSO, DPO, and RAG status
✅ Reviewing Your Output — What to Check Before Sharing
  • DSO figure: Verify against what you know — if it looks off, check that your daily revenue denominator in the prompt is correct
  • Credit limit flags: Confirm flagged customers against your credit limit file — a mismatch usually means a customer name doesn't exactly match between the two files
  • AP due this week: Cross-reference the top 3 amounts manually against your ERP to verify the figures before cash planning
  • Discount opportunities: Verify discount terms and expiry dates on any flagged invoices before authorising early payment
04
Board Reporting · Executive
Board & Investor Reporting Pack
Compile the financial section of your board or investor pack from multiple source documents — pulling data, applying template formatting, and drafting the CFO narrative pages.
⏱ Saves 8–14 hrs/quarter ★ High Impact CFO / VP Finance
Required Inputs
  • Completed management accounts (output from W1, reviewed and approved)
  • KPI tracking spreadsheet (XLSX)
  • Board pack template (DOCX)
  • Prior board pack (for narrative consistency)
  • Covenant compliance data (if applicable)
  • Any approved strategic commentary notes from leadership discussions
Expected Outputs
  • Financial summary section — populated with current period data
  • CFO narrative pages — draft, with strategic sections flagged for your voice
  • KPI dashboard with period-on-period trends
  • Covenant compliance table (if applicable)
  • Talking points document — 8 bullets for your board presentation
Strategic Use Note

The board pack workflow is a first-draft accelerator. Cowork handles data assembly and structural drafting; you contribute strategic narrative, forward-looking judgment, and tone. The CFO's voice in a board pack cannot and should not be fully automated — but the 10+ hours of assembly work can be.

📁 Before You Start — Exporting from NetSuite & Google Drive
A
Confirm your management accounts are reviewed and approved
This workflow builds on top of W1. Your management pack must be approved by a qualified person before feeding it into the board pack. The board pack is not the place to catch a number error — that should have happened at month-end close.

Approved management pack location: Google Drive/Finance_Cowork/outputs/monthly_close/MgmtPack_[MONTH].docx

Note on file naming: W1 outputs the file as MgmtPack_[MONTH]_DRAFT.docx. After your sign-off, save a copy without the _DRAFT suffix (i.e. rename it to MgmtPack_[MONTH].docx) so this workflow reads the approved version.
B
Gather your supporting files from Google Drive
Save these to your Google Drive inputs folder. For DOCX files, download from Google Docs:

• KPI tracker: Save your Excel KPI file → Google Drive/Finance_Cowork/inputs/kpi_tracker.xlsx
• Board pack template: Open your existing board pack template in your document editor → export/download as Word (.docx) → save as [Your Drive]/Finance_Cowork/templates/BoardPack_Template.docx
• Prior board pack: Download last quarter's approved pack from Google Drive → save as Google Drive/Finance_Cowork/inputs/board_packs/BoardPack_Prior.docx
• CFO notes: Open a new Google Doc, bullet-point your strategic context and narrative points → File → Download → Plain Text (.txt) → save as Google Drive/Finance_Cowork/inputs/board_packs/CFO_Notes.txt
🖥️ Step by Step in Cowork
1
Create a new Shortcut named "Board Pack Draft"
Open Cowork. Click New Shortcut. Name it "Board Pack — CFO Financial Section". Set trigger to Run Manually. This workflow runs quarterly or at each board cycle — manual triggering is fine.
2
Add your strategic context notes to the prompt
The prompt below produces a factual structural draft. Before running, add a section at the end of your instructions like: "My strategic context notes are in CFO_Notes.txt. Use these to inform the forward-looking section only — do not invent strategic narrative not found in these notes." This keeps the AI factual while incorporating your thinking.
3
Run and review the structural draft (allow 3–5 minutes)
Hit Run. The draft will populate your board pack template with financial tables, KPI updates, and a narrative skeleton. Every section marked [CFO TO ENHANCE] or [CFO TO ADD FORWARD GUIDANCE] needs your personal input before the pack is board-ready.
4
Add your voice — this is the most important step
Open the draft output and work through every [CFO TO...] marker. Replace each with your actual strategic judgment. The draft handles the data and structure; you provide the context, conviction, and forward guidance that only you can bring. Budget 60–90 minutes for this — it is time well spent on the highest-visibility deliverable you produce.
Sample Automation Prompt — Copy, Paste, Personalise Read the approved management accounts at Google Drive/Finance_Cowork/outputs/monthly_close/MgmtPack_[MONTH].docx and the KPI file at Google Drive/Finance_Cowork/inputs/kpi_tracker.xlsx. Read the board pack template at Google Drive/Finance_Cowork/templates/BoardPack_Template.docx. Read the prior board pack at Google Drive/Finance_Cowork/inputs/board_packs/BoardPack_Prior.docx for tone and structure reference only. 1. Insert the P&L summary table on the designated page of the template, formatted to match the existing template style (fonts, column widths, shading). 2. Update the KPI section with current period figures from the KPI file. 3. Write a 4-paragraph CFO Commentary covering: (a) Overall financial performance vs. budget — factual summary (b) Top 2 material variances — factual description only, mark [CFO TO ENHANCE] (c) Cash position and liquidity headroom (d) Material risks or opportunities — mark [CFO TO ADD FORWARD GUIDANCE] 4. Populate the covenant compliance table using ratios calculated from the management accounts. 5. Create a separate talking points document with 8 concise bullet points for the board meeting presentation. Save this to Google Drive/Finance_Cowork/outputs/board_packs/TalkingPoints_[QTR].docx. 6. Save the main board pack draft to Google Drive/Finance_Cowork/outputs/board_packs/BoardPack_[QTR]_DRAFT.docx.
✅ Reviewing Your Output — What to Check Before the Board Sees It
  • Every number in the pack: Verify headline P&L, revenue, EBIT, and cash figures against your approved management accounts — these must match exactly
  • KPI figures: Spot-check 3–4 KPIs against the source tracker file
  • All [CFO TO...] markers: Do a document search for this text — every single one must be resolved before distribution. A board pack with placeholder markers in it is never acceptable
  • Talking points document: Read every bullet — edit for your voice and ensure they align with the narrative in the pack
  • Final approver: The CFO must personally approve this document before it reaches the board. Do not delegate this sign-off
05
FP&A · Performance Management
Variance Analysis & Commentary Generation
Generate structured variance analysis with factual commentary across all departments, plus individual department pages and draft request emails to cost centre owners — ready for review and distribution.
⏱ Saves 3–5 hrs/month ★ High Impact FP&A / Controllers
Required Inputs
  • Actuals by department / cost centre (current month CSV)
  • Budget file (same account structure as actuals)
  • Department head contact list (CSV: name, email, cost centre code)
  • Variance commentary template (DOCX)
  • Materiality threshold definition (in your instructions)
Expected Outputs
  • Variance analysis by department — $ and % for all line items
  • Factual commentary for each material variance
  • Individual department page per cost centre (separate DOCX files)
  • Draft email per department head requesting explanations (TXT files, not sent)
  • Consolidated CFO variance summary (all departments on one page)
📁 Before You Start — Exporting from NetSuite & Google Drive
A
Export department actuals and budget from NetSuite
Run these two exports from NetSuite, structured to Department Code + Account Code + Amount:

• Actuals by Department: Reports → Financial → Income Statement → customise → add Department dimension → Export CSV → Google Drive/Finance_Cowork/inputs/gl_exports/Actuals_by_Dept.csv
• Budget by Department: Reports → Budgeting → Budget vs. Actual → filter current month → Export CSV → Google Drive/Finance_Cowork/inputs/Budgets/Budget_Current.csv

Important: Make sure department codes match exactly between both files — the same label must appear identically in both actuals and budget exports. Even minor differences (e.g., "Ops-North" vs "North Operations") will cause Cowork to fail to join the datasets. Check your ERP's department/class dimension setup if codes don't align.
B
Create a department contacts file in Google Sheets
Create a new Google Sheet with columns: Department_Code, Department_Name, Head_Name, Head_Email. One row per cost centre or department. Use email addresses for each department head.

Export as CSV: File → Download → CSV
Save as: Google Drive/Finance_Cowork/context/dept_contacts.csv

Cowork uses the email addresses from this file to address draft variance emails. These become the "To:" line in each draft — you review, edit, and send manually.
🖥️ Step by Step in Cowork
1
Create a new Shortcut named "Monthly Variance Analysis"
Open Cowork. Click New Shortcut. Name it "Monthly Variance Analysis & Commentary". Set trigger to Run Manually — this workflow runs once per month after close.
2
Define your materiality threshold in the prompt
The most important customisation in this workflow is your materiality threshold. Set it to match your internal policy: e.g., "Flag any variance exceeding $5,000 OR 5% of budget — apply both tests, flag if either is breached." Being too tight creates noise; too loose misses real issues.
3
Run and check the CFO consolidated summary first
Hit Run. When it finishes, open CFO_Summary.docx first — this is the one-page view of all departments. Use this to triage which individual department files need the most attention before you review each one.
4
Review and release draft emails one department at a time
Cowork will have drafted one email per department head with variance questions. Open each .txt draft in your outputs folder. Edit the tone for each relationship — some department heads need a gentle nudge, others a firmer ask. Copy-paste the edited text into a Gmail compose window. Do not use a bulk send approach for these; each one benefits from your personal touch.
Sample Automation Prompt — Copy, Paste, Personalise Read Google Drive/Finance_Cowork/inputs/gl_exports/Actuals_by_Dept.csv (current month actuals by department) and Google Drive/Finance_Cowork/inputs/Budgets/Budget_Current.csv (current month budget by department). Both files have columns: Department_Code, Department_Name, Account_Code, Account_Name, Amount. For each department: 1. Calculate: Actual - Budget in $ (positive = overspend, negative = underspend). Calculate: Variance as % of Budget. Format: positive variance = unfavourable (red), negative = favourable (green). 2. Identify all lines exceeding materiality: >[YOUR THRESHOLD e.g. $5,000] OR >[YOUR % e.g. 5%] (apply both tests; flag if either is breached). 3. Write 1–2 factual sentences per material variance describing direction and magnitude. Example: "Headcount costs are $12k (8%) over budget." Do NOT speculate on causes. Mark speculative items [DEPT HEAD TO EXPLAIN]. 4. Create one individual variance file per department named: Google Drive/Finance_Cowork/outputs/variance/[DeptCode]_Variance.docx 5. For each department, write a short email to the department head (contact list at Google Drive/Finance_Cowork/context/dept_contacts.csv) asking them to review and explain variances marked [DEPT HEAD TO EXPLAIN]. Save emails as: Google Drive/Finance_Cowork/outputs/variance/emails/[DeptCode]_Email_Draft.txt DO NOT send. Draft only. 6. Produce a consolidated summary at Google Drive/Finance_Cowork/outputs/variance/CFO_Summary.docx listing all departments, their total variance, and a RAG status.
✅ Reviewing Your Output — What to Check
  • CFO_Summary RAG statuses: Verify the GREEN/AMBER/RED assignments make sense relative to your business context — adjust thresholds in the prompt if they're systematically off
  • Department variance totals: Spot-check 2–3 departments by re-running the math manually: do the actuals, budget, and variance figures add up?
  • Draft emails: Read every email before it leaves your team. Cowork writes factually — you add relationship awareness and tone. Gmail's Bcc or Groups features are useful if you want to copy the finance team on all variance request emails
  • Commentary marked [DEPT HEAD TO EXPLAIN]: Ensure these items are genuinely unknown to finance — don't ask a department head to explain something you already have context on
06
Treasury · Cash Management
Rolling Cash Flow Forecast Refresh
Update the rolling 13-week cash forecast with bank actuals, score prior week forecast accuracy, and project forward weeks based on known commitments.
⏱ Saves 3–4 hrs/week ★ High Impact CFO / Treasury
Required Inputs
  • Weekly bank statement export (CSV)
  • Prior 13-week cash flow model (XLSX — your working model)
  • AP payment schedule — upcoming committed payments (XLSX)
  • Payroll schedule — dates and net amounts (context CSV)
  • Committed capex / large one-off payments schedule (if material) — include in ap_payments.xlsx or as a separate XLSX in inputs/cashflow/
Expected Outputs
  • Updated 13-week model with last week's actuals rolled in
  • Forecast accuracy scorecard: prior week predicted vs. actual by category
  • Forward 13-week closing cash balance by week
  • Minimum cash balance week identified with date and amount
  • Liquidity headroom vs. your minimum operating threshold
  • One-paragraph cash commentary for distribution
Practical Note on XLSX Outputs

When Cowork updates an XLSX cash flow model, it writes a new file — it does not modify your source model in place. Always save the previous week's model first so you have a version history. Name outputs with the week date: CashFlow_13W_Week20250127.xlsx.

📁 Before You Start — Exporting from NetSuite & Google Drive
A
Export this week's bank statement
Log into your bank's online portal and download the current week's transactions as a CSV. For multi-entity operations, run one export per entity bank account and merge them before saving.

Merge them into a single file with an added Entity column (e.g., "Entity-A", "Entity-B", "Entity-C") before saving.

Save as: Google Drive/Finance_Cowork/inputs/banking/Statement_This_Week.csv

FX note: For multi-currency operations, ensure each row includes the transaction currency — the prompt will convert to your group reporting currency for the consolidated model.
B
Create a bank transaction categorisation file in Google Sheets
One-time setup. Create a spreadsheet with columns: Keyword, Entity, Cash_Flow_Category. Map bank transaction description keywords to your cash flow categories. Examples:

"PAYROLL", "Entity-A", "Payroll — [Entity A name]"
"PAYROLL", "Entity-B", "Payroll — [Entity B name]"
"DEEL", "ALL", "Payroll Processing Fees"
"CLIENT NAME", "ALL", "Client Receipts"

Export as CSV: File → Download → CSV
Save as: Google Drive/Finance_Cowork/context/bank_categorisation.csv

This file is the heart of the workflow — the more complete it is, the fewer [UNCATEGORISED] items each week.
C
Save your current 13-week cash model
Before running, save this week's working model to a backup location so you have version history. Then put the active model at:
Google Drive/Finance_Cowork/inputs/cashflow/CashFlow_13W.xlsx
D
Export your AP payment schedule from NetSuite
The cash forecast prompt reads upcoming committed payments from an AP schedule file. In NetSuite, run a Saved Search on open AP transactions sorted by due date:

Lists → Search → Saved Searches → New → Transaction → filter Type = Vendor Bill, Status = Open → add columns: Vendor, Due Date, Amount, Currency → sort by Due Date ascending → Export CSV

Convert the CSV to XLSX and save as: Google Drive/Finance_Cowork/inputs/ap_payments.xlsx

Update this file each week before running the forecast — stale AP data will produce an unreliable cash projection.
E
Create your payroll schedule reference file
One-time setup. Create a Google Sheet listing every scheduled payroll run with these columns: Pay_Date, Entity, Gross_Amount, Currency, Notes. For multi-entity businesses, include one row per entity per payroll cycle.

Export as CSV: File → Download → Comma Separated Values (.csv)
Save as: Google Drive/Finance_Cowork/context/payroll_dates.csv

Update whenever payroll dates or net amounts change. The cash forecast uses this file to project outflows in the correct forward weeks.
🖥️ Step by Step in Cowork
1
Create a new Shortcut named "Weekly Cash Forecast"
Open Cowork. Click New Shortcut. Name it "Weekly 13-Week Cash Forecast Refresh". Once validated, this is an excellent candidate for scheduling — set it to run every Monday morning using your OS scheduler (Windows Task Scheduler or macOS Automator), ensuring Cowork is open before it triggers.
2
Set your minimum cash threshold in the prompt
The most important number to personalise: your minimum operating cash threshold. This is the floor below which you'd take immediate action (draw on credit facility, defer payments, etc.). Replace [INSERT YOUR THRESHOLD] with the actual dollar amount.
3
Review uncategorised transactions first
After running, your first check should be the [UNCATEGORISED - REVIEW] items. These are transactions Cowork couldn't match to your categorisation file. Add the new keywords to your bank_categorisation.csv and rerun — over time your categorisation rate approaches 100%.
Sample Automation Prompt — Copy, Paste, Personalise Read the bank statement at Google Drive/Finance_Cowork/inputs/banking/Statement_This_Week.csv. Read the cash flow model at Google Drive/Finance_Cowork/inputs/cashflow/CashFlow_13W.xlsx. The model has columns: Week_Ending, Category, Forecast, Actual, Variance. The category mapping is at Google Drive/Finance_Cowork/context/bank_categorisation.csv. 1. Match each bank transaction to a cash flow category using the categorisation file. Flag any transaction that does not match a known category as [UNCATEGORISED - REVIEW]. 2. For last week: sum actuals by category. Replace last week's Forecast figures with these actuals. Calculate Variance = Actual - Forecast. Flag any category where the variance exceeded 15% of forecast. 3. Extend the model by one week: roll all forward weeks forward by one row. Apply the AP payment schedule (Google Drive/Finance_Cowork/inputs/ap_payments.xlsx) and payroll schedule (Google Drive/Finance_Cowork/context/payroll_dates.csv) to the correct weeks. 4. Identify the week with the lowest projected closing balance. State the date and amount. 5. Calculate liquidity headroom: lowest projected balance minus minimum operating threshold of [INSERT YOUR MINIMUM CASH THRESHOLD e.g. $500,000]. Flag as [LOW LIQUIDITY WARNING] if headroom drops below 20%. 6. Write a one-paragraph cash commentary summarising position, outlook, and any risks. 7. Save updated model to Google Drive/Finance_Cowork/outputs/cashflow/CashFlow_13W_Updated_[date].xlsx. Save commentary to Google Drive/Finance_Cowork/outputs/cashflow/CashCommentary_[date].txt.
✅ Reviewing Your Output — What to Check
  • Opening balance: Confirm last week's closing balance in the model matches your actual bank balance — if these don't reconcile, the entire forecast is built on a wrong foundation
  • Uncategorised transactions: Resolve all [UNCATEGORISED - REVIEW] items before relying on the forecast. Unknown transactions distort every category total
  • Low liquidity warnings: If a [LOW LIQUIDITY WARNING] flag appears, verify it manually before escalating — check the specific week, the amount, and whether your AP schedule assumptions are current
  • Commentary paragraph: Read and edit before distributing — ensure it accurately reflects what you know about the business, not just what the numbers say in isolation
07
FP&A · Performance Tracking
Budget vs. Actual Dashboard Update
Automate the weekly update of your BvA performance dashboard — populate KPI scorecards by business unit, assign RAG status, and generate a leadership highlight email draft.
⏱ Saves 2–3 hrs/week ★ Medium-High FP&A / Business Partners
Required Inputs
  • Weekly actuals P&L by business unit (CSV)
  • Annual budget file — phased by week or month (XLSX)
  • KPI data file — operational metrics (revenue, headcount, utilisation, etc.)
  • BvA dashboard template (XLSX with chart data tables)
Expected Outputs
  • Updated BvA dashboard with current week data
  • RAG status per business unit (based on YTD tracking)
  • Top 3 "tracking ahead" items
  • Top 3 "tracking behind" items requiring attention
  • Draft leadership email with weekly performance snapshot (TXT, not sent)
📁 Before You Start — Exporting from NetSuite & Google Drive
A
Export weekly actuals from NetSuite and budget from Excel
Run these two exports:

• Weekly actuals from NetSuite: Reports → Financial → Income Statement → customise → set period to current week → add Department/Class dimension → Export CSV → save as Google Drive/Finance_Cowork/inputs/gl_exports/Weekly_Actuals.csv
• Annual budget from Excel: Open your annual budget model → save a copy as Google Drive/Finance_Cowork/inputs/Budgets/Annual_Budget_Weekly.xlsx

Important: Use the exact same business unit names in both files — your ERP's department codes must match your budget's column labels exactly. A mismatch (e.g., "Ops-North" vs "North Operations") will cause Cowork to fail to join the datasets. Standardise labels in both systems before building this automation.
B
Prepare your BvA dashboard template in Excel
Open your existing BvA Excel dashboard. Ensure it has clear named data table areas (not just charts) — Excel Tables work best here. Charts should reference those named tables so they auto-update when Cowork writes new data.

Save the template to: Google Drive/Finance_Cowork/templates/BvA_Dashboard.xlsx

Tip: Keep this file in Google Drive so it's accessible from any device and auto-backed up. Open it in Microsoft Excel (not Google Sheets) for editing — complex Excel formatting and named ranges don't always survive in Google Sheets.
C
Create your KPI data file
The BvA dashboard reads operational metrics from a weekly KPI file. Create a Google Sheet with one row per KPI per business unit per week. Suggested columns: Week_Ending, Business_Unit, KPI_Name, Actual, Target, Unit.

Key KPIs to consider: Revenue per headcount, Gross margin %, Client count, Headcount by business unit, and any service-line revenue split relevant to your business model.

Export as CSV: File → Download → Comma Separated Values (.csv)
Save as: Google Drive/Finance_Cowork/inputs/kpi_data.csv

Update this file each week before running. Keep the Google Sheet as the editable master — re-export to CSV each run.
🖥️ Step by Step in Cowork
1
Create a new Shortcut named "Weekly BvA Update"
Open Cowork. Click New Shortcut. Name it "Weekly Budget vs. Actual Dashboard". This is a strong candidate for weekly scheduling once validated — set it to run each Monday after your ERP drops the prior week's actuals.
2
Define your RAG thresholds
In the prompt, set your RAG criteria to match your business tolerance. The defaults in the sample prompt (GREEN within 3%, AMBER 3–8%, RED beyond 8%) are a reasonable starting point, but adjust to what your business and board consider normal variance. Too tight and everything is RED; too loose and the signal is lost.
3
Run, open the dashboard, verify charts updated correctly
Hit Run. Open the output XLSX and check that the data tables updated and the charts reflect the new data. If a chart looks wrong, check whether the data table range in the template is picking up the new rows Cowork wrote.
4
Edit the leadership email draft before sending
Open the LeadershipEmail_Week[X].txt draft. Cowork writes factually — your job is to add your read on the numbers, decide whether to emphasise a concern or celebrate a win more strongly, and personalise the tone for your specific audience.
Sample Automation Prompt — Copy, Paste, Personalise Read Google Drive/Finance_Cowork/inputs/gl_exports/Weekly_Actuals.csv and Google Drive/Finance_Cowork/inputs/Budgets/Annual_Budget_Weekly.xlsx and Google Drive/Finance_Cowork/inputs/kpi_data.csv. Read the BvA dashboard template at Google Drive/Finance_Cowork/templates/BvA_Dashboard.xlsx. 1. For each business unit, calculate YTD actual vs. YTD budget (cumulate weekly data to date). Assign status: GREEN (within [X]% of budget), AMBER ([X]–[X]% behind budget), RED (>[X]% behind OR >[X]% ahead — both require explanation). 2. Update the data tables in the BvA_Dashboard template with current week figures. Do not modify chart configurations — only update the underlying data tables. 3. Identify the 3 business units most ahead of budget (celebrate) and 3 most behind (watch). Write one sentence per item. 4. Write a 150-word leadership email titled "Week [X] Performance Snapshot" covering: (a) Overall company YTD tracking vs. budget (one sentence headline) (b) 3 celebrate items (c) 3 watch items Save draft email to Google Drive/Finance_Cowork/outputs/bva/LeadershipEmail_Week[X].txt. Do not send. 5. Save updated dashboard to Google Drive/Finance_Cowork/outputs/bva/BvA_Dashboard_Week[X].xlsx.
✅ Reviewing Your Output — What to Check
  • YTD actuals total: Verify the company-wide YTD revenue and cost totals match what you'd expect from NetSuite — these are your anchor numbers
  • RAG assignments: Do a quick sense-check — does the RED/AMBER/GREEN picture reflect your actual business reality this week?
  • Charts in the dashboard: Open the XLSX and visually confirm charts updated — a chart stuck on prior week data is a common first-run issue (usually a template data range problem)
  • Leadership email tone: Adjust before sending. The "watch" items in particular should be framed with appropriate context — an amber flag in isolation can look alarming without your accompanying narrative
08
Commercial Finance · Risk
Contract & Renewal Monitoring
Maintain a live view of all financial commitments in supplier and customer contracts — surfacing renewals, auto-renewals, price escalations, and expiry deadlines before they become financial surprises.
⏱ Saves 2–3 hrs/week ★ Medium-High CFO / Legal / Procurement
Required Inputs
  • Contract register (XLSX — one row per contract with key dates and values)
  • Individual contract PDFs or summaries (for Cowork to read specific financial terms — text-based PDFs only, not scanned)
  • Renewal policy document (your defined notice periods and escalation thresholds)
  • Budget impact reference — cost centre per contract (context CSV)
Expected Outputs
  • Contracts expiring in 30 / 60 / 90 days with RAG flags
  • Auto-renewal contracts where opt-out deadline is within 60 days (URGENT)
  • Price escalation clauses triggering in next 90 days
  • Total committed spend in expiring contracts this quarter
  • Action list with contract owner and recommended next step
Contract Categories to Track

The highest-value contracts to monitor typically fall into three categories: Client agreements or MSAs (revenue contracts with renewal and rate escalation terms), Supplier contracts (SaaS tools, office leases, service vendors), and Payroll processing arrangements (monitor for fee changes, volume tier triggers, and notice period requirements). Your contract register should include all three categories with the relevant cost centres assigned.

📁 Before You Start — Exporting from NetSuite & Google Drive
A
Build or update your contract register in Excel
If you don't have a contract register yet, this is the one-time setup task. Create an Excel file with one row per active contract. Required columns:
Contract_ID, Supplier_or_Customer, Type, Start_Date, Expiry_Date, Annual_Value, Auto_Renewal (Y/N), Opt_Out_Notice_Days, Escalation_Clause (Y/N), Escalation_Date, Owner, Cost_Centre

Save as: Google Drive/Finance_Cowork/inputs/contracts/Contract_Register.xlsx

Tip: Even an imperfect register with 80% of contracts is enormously valuable. Start with your top 20 contracts by annual value — key client agreements, major vendor arrangements, critical SaaS tools — and add the rest over time.
B
Note today's date — you'll need to insert it manually
This workflow calculates days-to-expiry relative to today. The prompt includes a [INSERT TODAY'S DATE] placeholder. Each time you run, replace it with the actual current date in YYYY-MM-DD format (e.g., 2025-07-01).
🖥️ Step by Step in Cowork
1
Create a new Shortcut named "Contract Monitor"
Open Cowork. Click New Shortcut. Name it "Contract & Renewal Monitor". This workflow is well-suited to a weekly or monthly schedule — auto-renewal risk in particular warrants a regular check rather than a reactive one.
2
Pay special attention to the auto-renewal section
The most financially dangerous items in this workflow are auto-renewals where the opt-out window is closing. These get a special [AUTO-RENEW RISK] flag. Check Tab 2 of the output first — if there's an auto-renewal you've missed, the time to act is now, not after the renewal date has passed.
3
Run and assign owners to the action list
Hit Run. The output will include a 10-item action list in Tab 1. Review it and add a named owner and deadline for each item — Cowork generates the list, but you assign accountability. Send the relevant tab or row to each contract owner directly.
Sample Automation Prompt — Copy, Paste, Personalise Read the contract register at Google Drive/Finance_Cowork/inputs/contracts/Contract_Register.xlsx. Columns: Contract_ID, Supplier/Customer, Type, Start_Date, Expiry_Date, Annual_Value, Auto_Renewal (Y/N), Opt_Out_Notice_Days, Escalation_Clause (Y/N), Escalation_Date, Owner, Cost_Centre. Today's date: [INSERT TODAY'S DATE in YYYY-MM-DD format]. 1. Calculate Days_To_Expiry for each contract (Expiry_Date - today). Assign: RED (≤30 days), AMBER (31–60 days), WATCH (61–90 days), GREEN (>90 days). 2. Identify all auto-renewal contracts where the opt-out deadline (Expiry_Date minus Opt_Out_Notice_Days) falls within 60 days. These are URGENT — mark [AUTO-RENEW RISK]. 3. Identify all contracts with escalation clauses where Escalation_Date is within 90 days. Estimate the expected annual cost increase (if % escalation is in the register data). 4. Sum the Annual_Value of all RED and AMBER contracts to quantify this quarter's renewal decision value. 5. Produce the output in Google Drive/Finance_Cowork/outputs/contracts/Contract_Monitor_[date].xlsx: — Tab 1: All contracts sorted by Days_To_Expiry (ascending) + 10-item action list at top — Tab 2: URGENT items (auto-renewals + opt-out deadlines) — Tab 3: Price escalations with estimated cost impact — Tab 4: Financial exposure summary by category
✅ Reviewing Your Output — What to Check
  • Tab 2 — Auto-Renew Risk: This is your highest-priority review. Verify the opt-out deadlines independently before deciding whether to act
  • Days-to-expiry calculations: Spot-check 2–3 contracts using the actual dates in your register to confirm Cowork's math is correct
  • Cost escalations (Tab 3): Verify any escalation % figures — these directly affect your budget model if they're triggering soon
  • Action list owners: Review and assign each of the 10 action items to a named person with a deadline before distributing
  • Missing contracts: If the total contract count looks lower than expected, check whether all contract types were included in your register before the run
09
Compliance · Audit
Audit & Compliance Documentation Package
Automate the assembly, organisation, and cross-referencing of audit support documentation — reducing the most time-consuming part of audit preparation from weeks to hours.
⏱ Saves 10–20 hrs/audit cycle ★ High Impact Controllers / Audit Liaison
Required Inputs
  • Auditor's PBC (Provided By Client) list — XLSX or PDF
  • Trial balance and sub-ledger exports (CSV)
  • Bank statements and reconciliations (PDF or CSV)
  • Supporting invoices and contracts folder
  • Prior year audit file for comparative schedules
  • Audit schedule templates (prepayments, accruals, fixed assets, intercompany)
Expected Outputs
  • PBC completion tracker with COMPLETE / PARTIAL / MISSING status per item
  • Organised evidence folder with files renamed to PBC reference numbers
  • Pre-populated standard audit schedules
  • Outstanding items task list — what to gather, from which system
  • Audit readiness percentage by category
Mandatory Human Review

All Cowork-generated audit schedules must be reviewed and certified by a qualified accountant before submission to external auditors. Cowork organises and assembles — it does not certify the accuracy of financial statements. Maintain documented human sign-off for every schedule in your audit workpapers.

📁 Before You Start — Exporting from NetSuite & Google Drive
A
Get the auditor's PBC list and save it
Your external auditors will provide a "Provided By Client" (PBC) list — the master list of everything they're requesting. This is typically an Excel or PDF document.

Save as: Google Drive/Finance_Cowork/inputs/audit/PBC_List.xlsx

If it arrives as a PDF, convert to Excel first so Cowork can read and process each row as a distinct item. To convert: open the PDF in Google Drive → right-click → Open with Google Docs → the table will be extracted as text, which you can then copy into Google Sheets and export as XLSX. Alternatively, use Adobe Acrobat (Export PDF → Microsoft Excel).
B
Gather all evidence into a shared Google Drive folder
Create a shared Google Drive folder and collect every piece of audit evidence — bank reconciliations, NetSuite exports, invoices, contracts, reconciliation schedules:

Google Drive/Finance_Cowork/inputs/audit/evidence/

Use descriptive file names. For Google Docs/Sheets files, download as PDF or Excel first — Cowork reads PDFs and XLSX/CSV natively.

NetSuite exports for audit: The most commonly requested items are the year-end trial balance, sub-ledger detail (AR, AP, Fixed Assets), and bank reconciliations — all exportable from NetSuite as CSV.
C
Save your audit schedule templates to Google Drive
Copy your standard audit schedule Excel workbooks to:
Google Drive/Finance_Cowork/templates/audit/

If your templates are currently in Google Sheets, download as Excel (.xlsx) first. Cowork pre-populates these from the NetSuite year-end trial balance export — saving the most time-consuming part of audit prep.

Key schedules to have ready: prepayments, accruals, fixed asset roll-forward, and our intercompany matrix (directly connected to W10).
🖥️ Step by Step in Cowork
1
Create a new Shortcut named "Audit Readiness"
Open Cowork. Click New Shortcut. Name it "Audit Documentation Package". This workflow is typically run once or twice per audit cycle — manual triggering is appropriate here.
2
Run the readiness check first — before you think you're ready
Don't wait until the day before auditors arrive to run this. Run it 3–4 weeks before the audit begins. The MISSING items list is your work plan — and some items will require you to retrieve documents from other teams or systems that takes time.
3
Work the MISSING items list systematically
Hit Run. Open the Readiness dashboard output and go straight to the MISSING items. Assign each missing item to a team member with a due date. Re-run the workflow as evidence comes in to track progress toward 100% completion.
4
Have a qualified accountant certify every pre-populated schedule
Cowork pre-populates audit schedules from your trial balance data — this is a significant time saver on mechanical population. But each schedule must be reviewed, verified, and signed off by a qualified accountant before it goes to auditors. Cowork's work is a starting point, not a finished product.
Sample Automation Prompt — Copy, Paste, Personalise Read the PBC list at Google Drive/Finance_Cowork/inputs/audit/PBC_List.xlsx. The file has columns: PBC_Ref, Description, Category, Requestor, Due_Date. Scan all files currently in Google Drive/Finance_Cowork/inputs/audit/evidence/ folder. 1. For each PBC item, check whether a matching file exists in the evidence folder. Match on keywords from the Description column. Assign: COMPLETE (clear match found), PARTIAL (file found but may be incomplete), MISSING (no match found). 2. For COMPLETE items: copy the evidence file to Google Drive/Finance_Cowork/outputs/audit/organised/[PBC_Ref]_[original_filename]. 3. For MISSING items: create a task list noting what needs to be gathered and from which system (use context from the Description to infer source system). 4. Using trial balance data at Google Drive/Finance_Cowork/inputs/gl_exports/TB_YearEnd.csv and the schedule templates at Google Drive/Finance_Cowork/templates/audit/, pre-populate: prepayment schedule, accruals schedule, and fixed asset roll-forward. Save each to Google Drive/Finance_Cowork/outputs/audit/schedules/[name]_DRAFT.xlsx. 5. Produce an Audit Readiness dashboard at Google Drive/Finance_Cowork/outputs/audit/Readiness_[date].xlsx: — % PBC items COMPLETE / PARTIAL / MISSING, by category — Estimated work to close outstanding items — List of ALL MISSING items for immediate action
✅ Reviewing Your Output — What to Check
  • PARTIAL items: These require your judgment — open the evidence file and decide if it actually satisfies the PBC request or if a better document is needed
  • MISSING items list: This is your audit prep work plan. Assign each item to a named person with a deadline immediately after reviewing the output
  • Pre-populated schedules: Every DRAFT schedule must be opened, reviewed line-by-line, corrected if needed, and signed off by a qualified accountant. Do not submit to auditors without this step
  • File organisation in /outputs/audit/organised/: Confirm that the renamed files are correctly labelled with the PBC reference before transferring to your auditors
10
Multi-Entity · Month-End
Intercompany Reconciliation
Reconcile intercompany balances across all entities, identify unmatched transactions and disagreements, produce elimination entries for consolidation, and generate a clean intercompany matrix report.
⏱ Saves 4–8 hrs/month ★ High Impact Controllers / Group Finance
Required Inputs
  • Intercompany receivables and payables extract per entity (CSV)
  • Entity list with functional currencies (context CSV)
  • FX rates for translation to group currency
  • Prior month intercompany balances (for movement analysis)
  • Materiality threshold for elimination entries
Expected Outputs
  • Intercompany matrix — all entity pairs, receivable and payable by each
  • Matched vs. unmatched balances — mismatches flagged with dollar difference
  • Proposed elimination journal entries in NetSuite's CSV journal import format
  • Unresolved differences task list with entity contact for each
  • Month-on-month movement summary
Why This Workflow Exists

Intercompany reconciliation failures are one of the top causes of delayed consolidations and audit adjustments. When Entity A records a $500k receivable from Entity B but Entity B shows a $487k payable, that $13k difference needs to be resolved before close. Cowork surfaces every disagreement automatically, so your team spends their time resolving differences — not finding them.

📁 Before You Start — Exporting from NetSuite & Google Drive
A
Export intercompany balances from your ERP for all entities
In your ERP, run an intercompany transaction export for each entity. In NetSuite, use a Saved Search on Transactions filtered to Intercompany type:

Lists → Search → Saved Searches → New → Transaction → filter by Type = Intercompany and Subsidiary = [entity]

Export one CSV per entity:
• Philippines entity → Google Drive/Finance_Cowork/inputs/intercompany/IC_PHIL.csv (PHP)
• Colombia entity → Google Drive/Finance_Cowork/inputs/intercompany/IC_COL.csv (COP)
• Canada entity → Google Drive/Finance_Cowork/inputs/intercompany/IC_CAN.csv (CAD)

Required columns: Counterparty_Entity, Transaction_Type (receivable/payable), Amount_Local, Currency, Description

Note: The prompt will translate all local currency amounts to your group reporting currency using today's FX rates.
B
Prepare your entity list and daily FX rates
Create two reference files (one-time setup, update FX rates each run):

• Entity list (one-time): Create a spreadsheet with one row per entity. Columns: Entity_Code, Entity_Name, Functional_Currency, Finance_Contact_Email. Example:
ENTITY-A, [Entity A name], [currency], [finance contact email]
ENTITY-B, [Entity B name], [currency], [finance contact email]
ENTITY-C, [Entity C name], [currency], [finance contact email]
Export as CSV → Google Drive/Finance_Cowork/context/entity_list.csv

• FX rates (refresh each run): Get today's PHP/USD, COP/USD, and CAD/USD rates from xe.com or your bank's published rates. Create a simple 3-row CSV:
PHP, USD, [rate]
COP, USD, [rate]
CAD, USD, [rate]
Save as: Google Drive/Finance_Cowork/inputs/banking/FX_Rates_Today.csv

FX tip: If you use a specific FX provider for cross-border payments, use their published rates rather than spot rates — these reflect your actual conversion costs more accurately.
🖥️ Step by Step in Cowork
1
Create a new Shortcut named "Intercompany Recon"
Open Cowork. Click New Shortcut. Name it "Intercompany Reconciliation — Month End". Set trigger to Run Manually. This workflow runs once per month as part of your close checklist.
2
Set your mismatch tolerance in the prompt
The prompt uses a $500 matching tolerance by default. Replace this with your own materiality threshold — for a mid-market company this might be $100–$500; for a large multinational it might be $5,000. Below your threshold, minor FX translation differences won't trigger false mismatches.
3
Verify the elimination journal format before running
Check NetSuite's journal import format requirements (column names, debit/credit format, entity codes). Update the prompt if your ERP requires specific formatting — getting this right means the elimination entries can be imported directly without manual reformatting.
4
Assign mismatches to entity contacts immediately
Hit Run. After reviewing the output, send the MISMATCH items directly to the finance contact at each entity — don't let them sit. Each day an intercompany mismatch is unresolved is a day closer to your close deadline with an open item on the consolidation.
Sample Automation Prompt — Copy, Paste, Personalise Read the intercompany extract for each entity from Google Drive/Finance_Cowork/inputs/intercompany/ The files are named IC_[EntityCode].csv. Each file has columns: Counterparty_Entity, Transaction_Type (receivable/payable), Amount_Local, Currency, Description. Also read Google Drive/Finance_Cowork/context/entity_list.csv (entity codes and functional currencies) and Google Drive/Finance_Cowork/inputs/banking/FX_Rates_Today.csv. 1. Translate all local currency amounts to group reporting currency ([YOUR GROUP CURRENCY e.g. USD]) using today's rates from FX_Rates_Today.csv. 2. Build an intercompany matrix: a table with all entities as both rows and columns. Each cell shows: Entity A's receivable FROM Entity B (row) and Entity B's payable TO Entity A (col). 3. For each entity pair, compare A's receivable vs. B's payable (both translated to group currency). Identify: MATCH (within [YOUR TOLERANCE e.g. $500]), MISMATCH (difference above tolerance). For each MISMATCH, state: Entity pair, A's balance, B's balance, difference in group currency. 4. Generate proposed elimination journal entries for all MATCHED pairs in the format: Dr Intercompany Payable [Entity], Cr Intercompany Receivable [Entity], Amount [GROUP CURRENCY]. Save elimination entries to Google Drive/Finance_Cowork/outputs/intercompany/Eliminations_[month].csv in ERP import format (columns: Account, Entity, Debit, Credit, Description). 5. Produce a mismatch resolution task list: for each MISMATCH, list the entity pair, the amount, and the relevant finance contacts from Google Drive/Finance_Cowork/context/entity_list.csv. 6. Save the full intercompany matrix to Google Drive/Finance_Cowork/outputs/intercompany/IC_Matrix_[month].xlsx.
✅ Reviewing Your Output — What to Check
  • Matrix totals: The total intercompany receivables and payables across all entities should net to zero at the group level — if they don't, there's an input file issue or a missing entity
  • MISMATCH items: Review each one to determine if it's a timing difference (invoice posted in one entity but not yet in the other) or a genuine discrepancy. Assign each to an entity contact with a resolution deadline
  • Elimination journal format: Open the Eliminations_[month].csv and verify it matches NetSuite's import format exactly before uploading — a column mismatch will cause the import to fail
  • FX translation: Spot-check one or two translated amounts manually using the rates in your FX file — translation errors compound across every subsequent consolidated figure
  • Sign-off before close: Do not proceed to consolidated reporting until all material mismatches are resolved or formally documented as acceptable with an explanation
Part IV

Scaling & Governance

Moving from personal use to a team-wide deployment — with the measurement, change management, and governance frameworks to make it sustainable.

19

Rolling Out to Your Finance Team

The most common deployment mistake is moving too fast. A phased rollout builds team confidence, catches edge cases before they become audit findings, and creates internal advocates who accelerate adoption in later phases.

Phase 1 — CFO Pilot (Weeks 1–4)

The CFO or Controller runs 2–3 workflows personally. The goal is not output perfection — it is developing a genuine, first-hand understanding of how Cowork handles your specific data, where it adds most value, and where human guardrails are essential. Direct experience makes you a credible advocate and a sharper quality reviewer when the broader team starts using it.

Phase 2 — Finance Core Team (Weeks 5–10)

Expand to 3–5 people: your FP&A lead, Controller, and senior analysts. Deploy 4–5 validated workflows. Hold a weekly 30-minute debrief to collect feedback, refine instructions, and document what is working. Begin building your internal Cowork Playbook — a shared document of your approved, tested automation configurations.

Phase 3 — Finance Function-Wide (Weeks 11–20)

Expand across the full finance function. By this point you have a library of proven workflows and a team that understands both the tool and its limitations. Establish a Cowork Steward role at this stage — one person responsible for maintaining the shared library, reviewing new automation proposals, and managing the governance framework.

Governance Structure

RoleResponsibility
CFOFinal approver for any automation touching external reporting, board packs, or regulatory submissions
Controller / Finance DirectorApproves new automation designs; quality reviewer for close and audit workflows
Cowork StewardMaintains the shared workflow library; trains new users; first reviewer of new automation proposals; owns the Cowork Playbook
Finance Team MembersCan run approved workflows; must flag unexpected outputs; cannot modify or publish production automations without Steward review
IT / SecurityApproves new data connections; maintains data classification register; manages access controls
20

Measuring ROI & Time Savings

Hold your AI investment to the same standard as any other operational investment. Measure across three categories:

Time Recovered

Track hours per task before and after automation. Multiply by loaded hourly rate. The 10 workflows in this guide typically recover 40–70 hours per month across a 5–10 person finance team.

Error Reduction

Track manual errors caught vs. missed. Most valuable in reconciliation and audit prep workflows, where errors carry direct financial or regulatory consequences.

Speed-to-Insight

How many days after month-end is your management pack ready? How quickly are variance and cash reports available? Target a 30–50% reduction in reporting cycle time.

Strategic Capacity

The hardest to quantify but most valuable: what share of your team's time has shifted from assembly to analysis and business partnering? Survey your team at 3 and 6 months.

ROI Tracking Reference

WorkflowHours BeforeHours AfterTypical Monthly Saving
Monthly Close Package8 hrs1.5 hrs6.5 hrs
Board Pack Assembly12 hrs2 hrs~10 hrs per pack
AP/AR Aging Alerts3 hrs/week0.5 hrs/week10 hrs
Cash Flow Refresh3 hrs/week0.5 hrs/week10 hrs
Intercompany Recon6 hrs1 hr5 hrs
Audit Package20 hrs/cycle3 hrs/cycle17 hrs per audit
21

Change Management for Finance Leaders

Finance teams often show the most resistance to AI tools — and for understandable reasons. Finance professionals are trained to be precise, cautious, and accountable. Address these concerns directly and early.

"What if it makes a mistake?" — Cowork makes errors, just as humans do. The difference is that its errors are consistent and detectable, which makes them easier to catch. The answer is not to avoid automation — it is to build review checkpoints that are at least as rigorous as today's (which, for many manual processes, are weaker than they appear).

"Is this going to replace my job?" — Be direct: automation replaces tasks, not roles. A finance analyst who spends 60% of their week assembling reports will spend 10% assembling them with Cowork — and 90% analysing, advising, and partnering with the business. That analyst becomes significantly more valuable. Finance teams that adapt grow; those that don't become commoditised.

"How do we handle this in an audit?" — Document your automation design, your review process, and your human sign-off at each critical step. An auditor evaluates controls and evidence — they do not care whether a human or a machine performed the calculation. A well-documented, consistently-controlled automated process is often more defensible than a manual one.

"Our data is too sensitive." — This deserves a proper answer, not dismissal. Review Anthropic's enterprise data handling and privacy terms with your legal and IT teams. Operate within the data classification framework in Section 07. For the most sensitive data, maintain human-only processes until you have the governance structure you need.

22

Troubleshooting & Common Pitfalls

ProblemMost Likely CauseFix
Output quality is inconsistent run-to-run Instructions are too vague or ask Cowork to make judgment calls without sufficient guidance Tighten instructions: specify exact column names, exact thresholds, exact output format. Test with the same input file twice — if outputs differ significantly, the instructions need more specificity.
Cowork reads the wrong columns Your ERP export has column headers that differ from what you specified in the instructions Open the actual CSV file and copy the exact column header text into your instructions. Don't assume — paste it verbatim.
Numbers don't match my ERP Export includes items that should be excluded (e.g., intercompany before elimination, or tax lines within EBIT) Adjust your ERP export query to apply the correct filters before export. Alternatively, add explicit exclusion logic to your instructions: "Exclude all accounts in range 9000–9999."
Commentary is generic and not useful Cowork lacks enough context about your business and cost structure to write specific commentary Expand your context library: add a one-page business model summary, a description of each major cost category, and 2–3 examples of the commentary style you want. Cowork improves significantly with richer context.
Scheduled automation doesn't run Cowork application is not open or user is not logged in when the OS scheduler fires Cowork must be open and authenticated for OS-triggered shortcuts to run. If automated running is critical, consider leaving Cowork open in the background on a dedicated machine or workstation.
Team members produce different quality outputs Individuals are modifying the shared automation instructions without going through the review process Keep production automation instructions in a locked shared document. Require Steward review before any modification to an approved workflow. Maintain version history.
Output XLSX charts don't update Cowork updated the data but Excel's chart references point to named ranges or pivot tables that need a manual refresh Open the output XLSX and press Ctrl+Alt+F5 (Windows) or Cmd+Option+F9 (Mac) to refresh all calculations. Design your templates to use simple data table references rather than pivot tables where possible.
Appendices

Reference Materials

A

Prompt Library for Finance Automations

These reusable prompt building blocks can be combined into any automation. Copy and adapt them — fill in your specific file paths, column names, and thresholds.

Variance Calculation Block

Reusable Component For each row in the data, calculate: 1. Absolute variance: [Column A] minus [Column B]. Positive = unfavourable (overspend), negative = favourable (underspend). [Adjust direction convention for your context.] 2. Percentage variance: (Absolute variance / [Column B]) × 100. Round to 1 decimal place. 3. Materiality flag: mark a row MATERIAL if the absolute variance exceeds $[X] OR the percentage variance exceeds [Y]%, whichever test is triggered first. Sort all MATERIAL rows by absolute variance, descending.

Executive Summary Block

Reusable Component Write a [100–150 word / 200–250 word] executive summary for a CFO audience. The summary must: (1) Lead with the single most important headline finding in the first sentence. (2) Support with 2–3 specific data points in the second and third sentences. (3) Close with one sentence on action, risk, or forward implication. Tone: direct, confident, factual. No hedging language. No passive voice. Do not use bullet points. Write in short, declarative sentences. Mark any judgment or forward-looking claim with [CFO TO REVIEW].

File Reconciliation Block

Reusable Component Compare [File A] and [File B]. Use [key field name] as the matching key. For each item, attempt to find a matching record in the other file. Produce three separate output sections: Section 1 — IN FILE A, NOT IN FILE B: list each item and its value. Section 2 — IN FILE B, NOT IN FILE A: list each item and its value. Section 3 — IN BOTH FILES, VALUES DIFFER: list item, File A value, File B value, and the difference — only include where the difference exceeds $[tolerance]. At the end, state: total unmatched items, total value of differences.

Date & Deadline Alert Block

Reusable Component Today's date is [date]. For each item with a [deadline/expiry/due] date: 1. Calculate days remaining: [date field] minus today. 2. Assign status: RED (0–30 days), AMBER (31–60 days), WATCH (61–90 days), OK (>90 days). 3. Sort output: RED first, then AMBER, then WATCH, then OK. 4. For RED items: add the text [IMMEDIATE ACTION REQUIRED] and state the specific deadline date. 5. For AMBER items: add [ACTION REQUIRED BY (date)] calculated as [deadline] minus 14 days. At the top of the output, include a count: X RED, X AMBER, X WATCH, X OK.

RAG Status Summary Block

Reusable Component For each item in the following list, assign a status: GREEN: [define condition — e.g., "within 3% of target"] AMBER: [define condition — e.g., "3–8% below target"] RED: [define condition — e.g., "more than 8% below target OR more than 5% above"] Output format: — A summary count at the top: [X GREEN / X AMBER / X RED] — A sorted list: all RED items first with a one-sentence recommended action each, then AMBER with a one-sentence monitoring note each, then GREEN (no action text needed).
B

Integration Compatibility Reference

Cowork works with any system that produces a file export. This table summarises recommended export configurations and known formatting considerations for common finance platforms.

System TypeRecommended FormatKey Configuration NotesKnown Issues to Avoid
Cloud ERP
NetSuite, Sage Intacct, MS Dynamics, QuickBooks Online		 CSV with headers in row 1 Include: account code, account name, entity, period, amounts. Suppress summary/subtotal rows. NetSuite often includes thousands-separator commas in number fields — export in "no formatting" mode or Cowork will misread numbers as text.
Global Payroll Platforms
Deel, Remote, Rippling, ADP, Paylocity		 CSV payroll register Use Employee_ID not name. Include: cost centre, gross pay, employer taxes, net pay, jurisdiction code. Rippling and Deel sometimes export multi-currency amounts in the same column with currency codes embedded in the value — separate into Amount and Currency_Code columns before saving to inputs.
Banking & Treasury CSV statement Date, description, debit, credit, running balance. Remove full account numbers — last 4 digits only. OFX/QFX formats need converting to CSV first. Most bank portals offer a direct CSV download — use that where available.
Excel Models XLSX direct Headers in row 1, no merged cells in data range, no formulas in cells Cowork reads as data inputs. Merged cell headers cause column misreading. Flatten all merged cells before pointing Cowork at the file.
AP/AR Platforms
Bill.com, Tipalti, SAP Ariba		 CSV aging report One row per invoice. Include: counterparty, invoice date, due date, amount, aging bucket, currency. Some platforms export aging as a pre-summarised pivot (totals only) — ensure you export the detail-level (invoice-by-invoice) version, not the summary.
PDF Reports Text-based PDF only Any text-based PDF Cowork can read directly. Scanned PDFs (image-only) cannot be read by Cowork. Convert to searchable PDF using OCR software (e.g., Adobe Acrobat) before processing.
C

Glossary

TermDefinition in this Guide's Context
ShortcutA saved set of Cowork instructions that performs a named, repeatable task. Equivalent to a named macro, but written in plain English.
Instructions / PromptThe plain-English directions inside a shortcut telling Cowork exactly what to read, what logic to apply, and what to produce. The quality of your instructions determines the quality of your outputs.
Context LibraryA folder of reference documents (chart of accounts, entity list, policies) that Cowork can read to understand your organisation. Referenced explicitly in your automation instructions.
TriggerWhat initiates a shortcut. In Cowork, this is primarily manual (you run it) or OS-scheduled (Windows Task Scheduler or macOS Automator launches it at a set time, with Cowork open).
Output TemplateA pre-formatted DOCX or XLSX file containing placeholder markers where Cowork inserts data and analysis. Ensures every run produces consistently formatted outputs.
Human-in-the-LoopA mandatory review and approval step performed by a qualified human before a Cowork output is distributed, filed, or acted upon. Essential internal control for all financial reporting workflows.
Cowork StewardThe designated team member responsible for maintaining the shared shortcut library, reviewing new automation designs, and training users. Created at Phase 3 of the rollout.
Cowork PlaybookYour team's internal documentation of all approved, tested automation configurations — including instructions, input requirements, expected output format, and review owner.
PBC ListProvided By Client — the list of documents and schedules your external auditors request from you to complete the annual audit. A standard term in external audit engagements.
Materiality ThresholdThe minimum dollar or percentage value at which a variance or exception is significant enough to require commentary, investigation, or escalation. Must be defined before building variance alert workflows.
RAG StatusRed / Amber / Green — a traffic-light classification system used in several workflows to indicate severity or performance tracking status at a glance.
CFO Cowork
© Finance Leaders · Not for redistribution without permission
Claude Cowork Implementation Guide · 2025
The CFO's Guide to Claude Cowork · Built by F28 Studio · John Fong Book a discovery call  ·  More AI experiments