Claude Skills for Accounting: Setup and Practical Examples

Claude skills for accounting are saved prompt instructions that help with preparation work: structuring reconciliation checklists, organizing transaction categories, and flagging items that need a CPA's review. They do not replace licensed professional judgment. Every output needs human review before it touches a financial record.

Tools like fenbs store the approved procedures and standing review rules alongside the skills. That means the next session starts from the same approved boundaries rather than rebuilding them, and every change to a procedure is recorded so your team knows what was decided and when.

What Claude can and cannot do in accounting

Claude can organize information, apply a labeling structure you define, check for internal consistency in a list, and ask the questions a checklist requires. It cannot apply professional judgment, sign off on a financial statement, or satisfy the review requirements set by the AICPA or any state board of accountancy.

The skills in this article treat Claude as a preparation assistant: it structures the work so a CPA can review it faster. Every skill includes a sign-off prompt that names the human review step explicitly. Removing that step removes the reason for using the skill.

Do not pass client account numbers, tax IDs, or personal financial data into Claude. Describe the type of transaction or account in general terms. A skill for "categorize these expense descriptions" works without including the client's name or account number.

Setting up review boundaries before writing a skill

Before writing a skill, write down what decision the output informs and who must approve it. A reconciliation checklist informs whether an account balance is ready for review. The CPA signs off. That boundary goes into the skill as a final line: "All figures and conclusions require review by a licensed CPA before use in financial reporting."

Record those boundaries as Decisions and rules in fenbs before connecting any assistant. That way the boundary is part of the project context the assistant reads at the start of every session, not just part of a skill that might be called without the context. An assistant that reads the rule first will include it in any output it produces.

A skill for account reconciliation preparation

A reconciliation preparation skill structures the steps for a given account type and flags common variance sources. It does not perform the reconciliation. It gives the reviewer a consistent starting checklist.

Prepare a reconciliation checklist for the following account.

Account type: {{e.g., bank account, accounts receivable, accounts payable}}
Period: {{e.g., September 2026}}
Known issues from prior period: {{list any or write "none"}}

Output exactly this structure:

Reconciliation steps:
  1. [first step]
  2. [second step]
  (continue through all standard steps for this account type)

Common variance sources to investigate:
  - [item 1]
  - [item 2]

Items requiring CPA review before sign-off:
  - [item 1]
  - [item 2]

Sign-off statement: All figures and conclusions in this checklist require review and approval
by a licensed CPA before being used in financial statements or tax filings.

A skill for categorizing expense descriptions

Expense categorization is one of the most time-consuming preparation tasks. This skill applies a labeling structure you define to a list of transaction descriptions. You provide the categories; Claude applies them and flags anything that does not clearly fit.

Categorize the following expense descriptions using the categories listed.

Categories: {{list each category, e.g., Travel, Software, Office Supplies, Meals, Other}}
Expense descriptions:
{{paste each description on its own line}}

For each description, output:
  Description | Suggested category | Confidence: High | Medium | Low | Needs review

Mark "Needs review" for any item where:
- The description is ambiguous
- It could fit more than one category
- It might not be a deductible expense under standard rules

After the list:
Items flagged for CPA review: [count]
Note: Category suggestions are for preparation only and require CPA review before being recorded.

Saving lessons from each engagement

After a reconciliation cycle, record what the checklist missed and what variances were harder to spot than expected. Those notes become the "known issues from prior period" input the skill asks for, closing the loop between past experience and future preparation.

fenbs does not hold client financial data. Keep that in your accounting software or secure file store. fenbs holds the procedure, the lessons, and the record of who approved what. Those three are the things most likely to be lost between engagements if they live only in a chat window. Moving them to a shared project record makes them available to every team member and every session without anyone having to rebuild the context each time.

How to do this with fenbs

1. Create a free account and add a project for each client engagement or recurring accounting cycle.
2. Add each skill to Skills and prompts: "Reconciliation checklist", "Expense categorization".
3. Record the CPA review requirement and any standing engagement rules as Decisions and rules before connecting an assistant.
4. Connect Claude over MCP from Integrations. Confirm it reads the rules at the start of the session before using a skill.
5. After each cycle, add lessons: what the checklist missed, what variances appeared, what to check next time.

For skill setup and testing, see how to create a Claude skill. For patterns across a team, see Claude skills for project management.

What to record after each engagement

After each reconciliation cycle, record what the checklist missed and what variances were harder to identify than expected. Those observations become the "known issues from prior period" input that the reconciliation skill asks for, closing the loop between past experience and future preparation.

If the categorization skill consistently mislabels a specific transaction type, update the skill instruction to handle it explicitly. Describe the transaction pattern in general terms without including client-specific data: "vendor rebates labeled as revenue" is useful guidance without identifying the client.

Keep the improvement record in fenbs. A firm that tracks how its skills improved over twelve months of engagements has a concrete record of process development. That record is useful for internal quality reviews and for onboarding new team members who need to understand why the procedures are structured the way they are. Skills that improve after each engagement produce preparation work that is increasingly useful and increasingly trusted.