Claude Projects for Finance Teams: A Complete Setup Guide

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.

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.

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.

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.

1. Project name: Month-End Reporting — [Year]
2. 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)
3. Knowledge — permanent: Chart of accounts, cost centre descriptions, business context document, two prior board pack sections as style references
4. Knowledge — updated monthly: Prior period actuals summary (one page), any strategic context relevant to the current month (e.g. budget revision, one-off items)
5. Connector: SharePoint Finance Reports library (read-only access to current board pack template and prior pack archive)
6. Skills: Variance Commentary, Reconciliation Summary, Board Narrative, Journal Narrative
7. 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.

Frequently Asked Questions