Claude Projects, Skills & Cowork for Finance Teams: Complete Setup Guide
Most finance teams using Claude are not using it at full capability. They paste context in every conversation, repeat their cost centre structure each month, and start from scratch on every board pack. Claude Projects, Skills, Cowork, Connectors and Computer Use 2.0 change that entirely. This is how to set them up for finance workflows, from the persistent knowledge base to multi-user Cowork sessions and Excel automation.
Umar is an FCCA-qualified accountant who founded Prime AI Solutions to help businesses implement AI in 8–12 weeks with guaranteed ROI, with deep expertise across finance, operations, and revenue functions. Previously at EY, HSBC, Shell, NatWest, Morgan Stanley, ASOS and Unilabs, his work bridges practical commercial experience with applied AI in regulated environments.
30-min strategy call
Speak to an AI consultant before you read on. We’ll tell you whether this article’s approach actually fits your business.
£999 · 2 weeks
AI Audit Assessment
£999 · 2-week turnaround
Get an AI Audit Assessment
Workflow map + prioritised AI roadmap. Refundable if we can’t find 5+ hours/week of savings.
See the auditWhat Projects, Skills, Cowork and Computer Use unlock
- Projects store your finance context (chart of accounts, board pack template, style examples) once, so every conversation starts pre-briefed.
- Skills turn recurring tasks (variance commentary, board narrative, journal write-ups) into one-click reusable workflows.
- Cowork brings multi-user shared context for month-end rooms, board pack drafting, and audit response sessions.
- Computer Use 2.0 executes browser and Excel work that previously needed a human in the loop (HMRC portals, bank exports, templated workbooks).
What Claude Projects Actually Changes
The standard Claude.ai conversation is stateless. Every time you open a new conversation, Claude knows nothing about your business, your reporting structure, your management pack format, or your commentary style. If you use Claude for monthly reporting, you are probably re-explaining these things every month, or copying in the same context block from somewhere else. That friction is exactly what Claude Projects removes.
A Claude Project is a persistent workspace. You load it once with your finance context, chart of accounts, cost centre descriptions, board pack templates, prior commentary examples, the writing style your CFO expects, and that context lives in the Project. Every conversation you open inside the Project starts with Claude already knowing all of that. The first month you set it up, you do the configuration work. Every month after, you just run the workflow.
Skills extend this further. A Skill is a reusable tool you build inside a Project, a structured task that runs a specific workflow when invoked. Connectors go one step further, giving your Project live access to documents in SharePoint, Google Drive, or other connected sources rather than relying on uploaded snapshots. Together, the three features turn Claude from a general-purpose AI into a configured finance tool.
How a London Finance Team Set This Up
One of our clients is a financial services business in London with a compliance-heavy finance function. Their monthly reporting cycle involves a management pack covering six entities, a board narrative covering regulatory capital, and a set of variance commentary sections written to a specific format that the board had approved three years ago and expects consistently each month.
Before Claude Projects, their Finance Director was spending three hours each month briefing Claude afresh before using it for commentary drafts. She had a notes document she would copy from, but it never quite captured the nuance of the regulatory context or the board's preferred framing. The output was inconsistent month to month.
We built a Claude Project called Monthly Management Pack. Into the project knowledge we loaded: their chart of accounts (PDF export from their system), the board pack template (Word document), two prior board narratives as style examples, a summary of the regulatory capital framework they report against, and a one-page document explaining the board's preferred framing for different types of variance. We then built Skills for each commentary section. Now the Finance Director opens the Project, runs the relevant Skill with the month's numbers, and has a first draft in under five minutes. Total setup time: one afternoon. Monthly time saving: two and a half hours.
Want this configured properly first time? Get help setting Claude Projects up for your team
Want to learn this hands-on? Take the AI for Finance Leaders course
Setting Up Claude Projects for Finance
You need a Claude Pro or Team plan. Team is recommended for finance use because it includes a data processing agreement and does not use your data for model training. Create a new Project from the Claude.ai dashboard and give it a specific name, one Project per major workflow works better than one Project for everything.
What to add to project knowledge
- Chart of accounts: Export from your ERP as a PDF or CSV. Include cost centre descriptions, not just codes. Claude uses these to understand context when you paste in financial data.
- Reporting template: Your management pack or board report structure. Claude uses this to understand what sections need to be produced and in what format.
- Style examples: Two or three prior commentary sections that represent the tone and format the board expects. These are the most important piece of knowledge in the Project.
- Business context: A one-page document covering your business model, key metrics, reporting period, and any recurring themes (e.g. "we are in a growth phase and the board accepts higher marketing spend as a strategic investment").
- Project instructions: The system prompt for the whole Project. Set the role, tone, and any absolute rules (e.g. "never use passive voice", "always quantify variances in both absolute and percentage terms").
What NOT to add to project knowledge
- Live financial data, add this per conversation, not as static knowledge (the numbers change every month)
- Confidential individual employee data, project knowledge has the same access controls as your Claude account
- Very large documents (100+ pages), context length has limits; summarise long policy documents rather than uploading them in full
Building Finance Skills
Skills are the feature most finance teams do not discover until they have been using Projects for a month or two. They are worth setting up from the start. A Skill is a saved prompt workflow, a structured task that appears as a tool inside your Project conversations. You invoke it by name and it runs the defined workflow, often prompting you to fill in specific inputs.
For finance workflows, we build Skills for every recurring task in the monthly cycle. The setup is a structured prompt that uses the RACEF framework, Role, Action, Context, Examples, Format, with input fields for the dynamic data that changes each month.
Variance Commentary Skill
Runs the RACEF commentary template for any variance line. You input: line item name, actual, budget, variance, known drivers. Claude produces the commentary section using your project knowledge for context and style.
See our RACEF variance commentary prompts guide for the exact template structure to use when building this Skill.
Reconciliation Summary Skill
Takes reconciliation output (unmatched items, total matched, exceptions) and produces a formatted reconciliation summary section for the management pack. Works for bank reconciliation, intercompany, and sub-ledger tie-outs.
Board Narrative Skill
Takes month-end summary numbers and produces the opening board narrative section: headline performance, key variances, outlook statement. Uses the style examples in project knowledge to maintain consistent tone.
Journal Narrative Skill
For ERP journals requiring a narrative description. You provide: journal type, amount, period, and reason. Claude produces a structured journal narrative meeting your ERP's description format and your audit requirements.
Claude Connectors: Live Data Access
Connectors are available on Claude Max and Team plans. They give your Project live access to external data sources rather than relying on documents you manually upload. For finance teams, the most useful Connectors are SharePoint (for your reporting templates and prior packs) and Google Drive (for teams on Google Workspace).
The practical advantage: when your board pack template changes, your Claude Project automatically reads the updated version without you having to re-upload it. When a new prior period board pack is added to SharePoint, Claude can reference it in the next month's workflow without manual intervention. This is particularly valuable for teams where the reporting template is maintained centrally and updated periodically.
Setting up a Connector: in your Project settings, select 'Add Connector' and authenticate with the relevant service. You can restrict which folders or files the Connector can access, for finance, we recommend restricting to specific SharePoint document libraries (e.g. Finance Reports, Board Packs) rather than giving access to the entire SharePoint.
- SharePoint Connector: Access reporting templates, prior pack archive, policy documents. Best for M365 organisations.
- Google Drive Connector: Access shared finance folders. Best for Google Workspace organisations.
- Notion Connector: Useful if your finance team uses Notion for process documentation or assumptions tracking.
- GitHub Connector: Relevant if your team has structured financial data or automation scripts in GitHub repositories.
A Complete Month-End Claude Project
Putting it together: here is what a fully configured month-end Claude Project looks like for a mid-market finance team.
- Project name: Month-End Reporting, [Year]
- Project instructions: Role (Senior Finance Business Partner), tone (direct, professional, no jargon), rules (quantify all variances, flag any data inconsistency, never use passive voice), and format preferences (paragraph length, whether to include outlook sentences)
- Knowledge, permanent: Chart of accounts, cost centre descriptions, business context document, two prior board pack sections as style references
- Knowledge, updated monthly: Prior period actuals summary (one page), any strategic context relevant to the current month (e.g. budget revision, one-off items)
- Connector: SharePoint Finance Reports library (read-only access to current board pack template and prior pack archive)
- Skills: Variance Commentary, Reconciliation Summary, Board Narrative, Journal Narrative
- Month-end workflow: Export actuals from ERP, paste into a new conversation in the Project, run each Skill in sequence, review and edit output, paste into pack template
The one-time setup takes a half-day. The monthly workflow after setup takes 30-90 minutes depending on pack complexity, down from a typical 3-5 hours for manual drafting. For the consulting and implementation support to build this, see our AI consulting service or our finance function audit which identifies exactly which workflows to prioritise first.
If you are comparing Claude against ChatGPT or Copilot for this setup, see our tool comparison guide for the decision framework. If you are migrating from a ChatGPT workflow, see our ChatGPT to Claude migration guide. For the specific RACEF prompts to use in your Skills, see our variance commentary prompts guide. For the AI for Finance Leaders training that covers Claude Projects in a finance context, see our AI for Finance Leaders course.
Claude Skills for Finance: 10 Pre-built Workflows
Skills are where the time saving compounds. Each Skill is a structured prompt template stored inside a Project that runs on demand. You build them once, then invoke them every month with fresh inputs. The 10 below are the Skills we build for almost every finance client engagement. Use them as a starting template and adapt the RACEF prompt structure to your house style.
1. Variance Commentary
Input: line item, actual, budget, variance, drivers. Output: a board-ready commentary paragraph in your house format.
2. Month-End Close Status
Input: close checklist progress, outstanding items, blockers. Output: status update for CFO and audit committee.
3. FP&A Forecast Memo
Input: latest forecast vs prior, key assumptions, sensitivities. Output: a forecast memo with assumptions log.
4. MD&A Section Draft
Input: financial highlights, period themes, strategic context. Output: management discussion and analysis section in regulatory-acceptable language.
5. Board Pack Cover Note
Input: headline numbers, key issues for board attention, asks. Output: a 1-page cover note in your CFO's voice.
6. AP Invoice Triage
Input: invoice metadata + PO match status. Output: triage decision (approve, query, hold) with reasoning.
7. AR Follow-up Email
Input: customer, invoice age, history, relationship context. Output: a follow-up email pitched at the right tone for the ageing bucket.
8. Audit Prep File Summary
Input: lead schedule, supporting documents list, any audit queries from prior year. Output: a summary memo for the auditor with audit trail references.
9. Expense Classification
Input: expense line description + amount. Output: GL code recommendation with reasoning. Useful for AP teams and expense report review.
10. GL Coding Review
Input: a sheet of recent journal entries. Output: flagged anomalies, suspected miscodings, and questions for the bookkeeper.
Build these Skills in the order they fit your monthly cycle, not all at once. The first three (Variance, Close, Forecast Memo) typically save 4-8 hours per month on their own. The rest compound from there. For the underlying prompt structure, see our RACEF variance commentary prompts guide.
Using Claude Cowork in Finance Teams
Cowork (generally available since March 2026) extends Claude beyond a single-user chat. It is a shared workspace where multiple finance team members can collaborate on the same context, with Claude running as an embedded participant rather than a tool that one person uses at a time.
For finance teams the most useful Cowork patterns are: a monthly close room where all close team members work in the same Cowork session with the close checklist as shared context; a board pack drafting room where the FP&A team builds analysis and the CFO reviews and edits in the same session; and an audit response room where the audit committee, finance team, and external auditor work through queries with shared file context. Cowork sessions persist for as long as the work continues, so context is not lost between days.
Cowork is available on Claude Team and Enterprise plans. Access controls apply per session, so audit committee members can be granted read-only access to close-room context without seeing operational chat. For an end-to-end migration setup, see our ChatGPT to Claude migration guide which covers the Cowork setup steps.
Claude Computer Use 2.0 for Excel and Browser-based Finance Tasks
Computer Use 2.0 (released early 2026) lets Claude take direct control of your desktop and browser to execute multi-step finance tasks: opening Excel files, navigating ERP web interfaces, extracting data from procurement portals, downloading bank statements. For finance teams this is the bridge between Claude's analysis quality and the in-application work that previously required manual execution.
Realistic state in 2026: Computer Use is genuinely useful for repetitive browser-based extraction (e.g. logging into HMRC's VAT portal each quarter, downloading bank exports, pulling reports from supplier portals) and for Excel tasks that follow a predictable pattern (open a workbook, apply a template, save to a fixed location). It is less reliable for unpredictable workflows that involve judgement calls inside the application. We do not yet recommend it for tasks where an error would have audit or material reporting consequences.
Practical setup: Computer Use runs in a sandboxed virtual desktop by default, which is safer but disconnects it from your local Excel files. For Excel work specifically, configure Computer Use to operate on your local machine within a defined folder structure (e.g. month-end working files only) and run it under a service account with read-only ERP access. Treat its output the same way you would treat output from a junior team member: review before it enters the audit trail.
Computer Use is available on Claude Team and Enterprise plans. The 2.0 release significantly improved accuracy on multi-step Excel and browser flows compared to the original Computer Use beta. For teams comparing this against ChatGPT's GPT-5.5 computer use capability, see the comparison guide's desktop automation row.
Free 30-minute consultation
Map your AI opportunities
Book a free 30-minute consultation. We’ll review your workflows, identify the highest-ROI AI opportunities, and tell you whether you need consulting, training, or a fractional CAIO. No pitch, just direction.
Book a 30-minute call