Claude Project: Accounting Policy Knowledge Base

What This Builds

Instead of answering the same accounting policy questions from your team every week ("What's our capitalization threshold?" "How do we handle lease modifications?" "What's the approval limit for new vendors?"), you'll build a Claude Project that contains all your accounting policies. You or your team can query it like a knowledgeable colleague, getting instant, policy-accurate answers without digging through SharePoint or waiting for the Controller to respond.

Prerequisites

• {{tool:Claude.plan}} subscription at {{tool:Claude.price}} (Projects require a paid account)
• Your accounting policies compiled in Word or PDF format (capitalization, revenue recognition, expense reimbursement, AP policies, close procedures, etc.)
• 1–2 hours to set up the Project and test it
• Time to build: 1–2 hours
• Cost: {{tool:Claude.price}}

The Concept

A Claude Project is like a permanent file room that Claude has already read and memorized. You upload your policy documents once; every conversation inside that Project starts with Claude having already "read" all of them. Your team can ask questions in plain English ("Can we capitalize the cost of this software implementation?" or "What's the approval limit for a capital expenditure?") and get instant answers with policy citations, rather than waiting for the Controller to respond or searching through SharePoint.

Build It Step by Step

Part 1: Compile Your Policy Documents

Before setting up the Project, gather the documents you want Claude to reference:

1. Create a folder on your desktop called "Policy Library for AI"
2. Add these documents (whatever you have; don't wait for perfection):

   • Capitalization policy (fixed assets + software)
   • Revenue recognition policy (ASC 606 application)
   • Expense reimbursement policy (per diems, receipts, approval levels)
   • Accounts payable policy (invoice approval, payment terms, vendor onboarding)
   • Month-end close checklist (the sequence of tasks and deadlines)
   • Internal controls overview (significant controls and owners)
   • Chart of accounts (or a simplified summary version)
   • Journal entry approval policy (who approves what amounts)

If you don't have formal written policies: This is a great opportunity. Use Claude (from the Level 3 guide) to draft each policy memo, then upload those drafts as the knowledge base.

Part 2: Create the Claude Project

1. Go to {{tool:Claude.url}} and sign in to your {{tool:Claude.plan}} account
2. Click Projects in the left sidebar
3. Click New Project
4. Name it: "Accounting Policy Knowledge Base: [Company Name]"
5. On the Project page, find the Knowledge section and click Add files
6. Upload all your policy documents from your folder
7. Wait for each file to process (indicated by a checkmark)

What you should see: Each policy document listed in the Knowledge section of your Project.

Part 3: Write the Project Instructions

Click on Project instructions (or similar field in Project settings) and write:

You are the Accounting Policy Assistant for [Company Name]. Your role is to answer accounting and finance policy questions based on the uploaded policy documents.

How to respond:
- Always cite which policy document your answer comes from (e.g., "Per our Capitalization Policy...")
- If a question isn't covered by the uploaded policies, say so clearly and suggest who to ask
- Be precise about dollar thresholds, approval levels, and timing requirements
- For judgment calls not clearly addressed, flag the ambiguity and recommend the Controller be consulted
- Keep answers concise, usually 2–4 sentences for most questions

Audience: Accounting staff (accountants, AP clerks, payroll specialists) and occasionally department managers asking about expense policies.

Click Save.

Part 4: Test with Common Questions

Start a new conversation inside the Project. Test with questions your team actually asks:

1. "What's our capitalization threshold for equipment purchases?"
2. "Does a 3-year software subscription need to be capitalized or expensed?"
3. "What's the approval limit before a PO needs Controller sign-off?"
4. "How do we handle an invoice that arrives after month-end but relates to the prior period?"
5. "What receipts are required for expense reimbursement vs. corporate card purchases?"

Evaluate each answer: Does it cite the right policy? Is the dollar threshold correct? Is the guidance clear enough for a junior accountant to act on?

Part 5: Refine and Share

1. For any question where Claude's answer was wrong or incomplete, go back and add the missing information to your policy document, re-upload it
2. Once you're confident in the accuracy, share the Project with your accounting team (if your Claude plan allows team features) or keep it for your own reference
3. Communicate to your team: "You can ask [this system] policy questions before asking me. It has access to all our accounting policies."

Real Example: Monthly Close Policy Q&A

Setup: You've built the Accounting Policy Knowledge Base with 8 policy documents uploaded.

Staff question: A senior accountant sends you a Slack message asking: "We received a vendor invoice for $8,500 but it's not in the ERP as approved yet. Can I hold it until next month or do we need to accrue it?"

Old workflow: You respond in Slack after 20 minutes (you're in the middle of reviewing board package materials).

New workflow: The accountant queries the Project: "We have a $8,500 vendor invoice received but not yet approved in the ERP. Should we accrue it at month-end or wait for the next period?"

Project response: "Per our Accounts Payable Policy, invoices received prior to month-end for services rendered in the period should be accrued regardless of approval status, as long as the goods or services have been received. The approval workflow in the ERP is a payment control, not a recognition trigger. You should record the accrual to the appropriate expense account and GL period, then process the invoice for payment in the following month once approved. If the invoice amount exceeds $25,000, notify the Controller before posting."

Time saved: Your 20 minutes becomes 2 minutes for the accountant; you're not interrupted.

What to Do When It Breaks

• Claude gives an incorrect policy threshold → Check that the uploaded policy document has the correct number. If the policy is out of date, update the document and re-upload it to the Project.
• Claude says "I don't have information on that" → This means the policy isn't in your uploaded documents. Either add a policy memo for that topic (using the Level 3 guide) or tell your team that topic requires Controller judgment.
• Answers are too long → Add to Project Instructions: "Keep answers to 3–4 sentences for most questions. Only provide longer answers for complex multi-step situations."
• Claude confuses similar policies → Add a brief table of contents to each policy document so Claude can distinguish them more clearly.

Variations

• Simpler version: Don't create a Project. Just paste your most important policy at the top of a Claude conversation and ask questions in that session. This requires re-pasting each time but is instant to set up.
• Extended version: Include your external auditors' most frequently asked questions and your management responses as a document. Claude can then help draft responses to similar future audit questions.

What to Do Next

• This week: Upload your top 3 most frequently referenced policies and test it with 10 questions your team actually asks
• This month: Expand to cover all significant accounting policies; announce to your team
• Advanced: Schedule a quarterly "policy review" where you ask Claude to summarize any gaps in the uploaded policies (areas where questions were answered with "I don't have information") and fill those gaps with new policy memos

Advanced guide for Controller professionals. These techniques use more sophisticated AI features that may require paid subscriptions.