Run expense and AP inside Claude instead of Concur. 9 prompts code expenses to the GL, match receipts to the card feed, flag fraud, and close the corporate-card month. For controllers and CFOs.
Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.
A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.
Free account, no card, 30 seconds. This tab stays open so you can come back.
Open claude.ai ↗Claude reads this page, asks which computer you are on, then guides you step by step until it works. If anything errors, tell Claude what you see, and it fixes it with you.
I want to INSTALL the real setup so Claude codes my expenses and runs my month close on actual data, not just a chat demo. Walk me through it step by step, do not skip the install. Treat me like a controller or founder who has never installed an Office add-in or built a Claude Project, and define every term once.
This is NOT a Terminal or coding install. There is nothing to compile. It is two clicks-and-paste paths. Recommend Path 1 if I want the coding worksheet to live in real Excel formulas; Path 2 if I just want to run the prompts on uploaded exports.
## Path 1 (RECOMMENDED for the close) — Claude for Excel add-in
This puts Claude inside Excel so the coding worksheet, accruals, and tie-out recompute as real formulas I own.
Walk me through ONE step at a time, waiting for me to confirm each, against the CURRENT Excel UI (labels move, so look, do not guess):
1. **What I need.** Excel for Microsoft 365 (desktop or web) and a Claude account. Claude for Excel is generally available. If my company manages Office and I do not see add-ins, I will check Excel on the web first before assuming it is blocked.
2. **Install the add-in.** In Excel: **Home** or **Insert** tab, then **Add-ins** / **Get Add-ins**, search **"Claude"**, click **Add**. Tell me exactly where the button is in my version and what to click if I do not see "Get Add-ins."
3. **Sign in.** Open the Claude add-in (it docks as a side panel), sign in. Confirm I see the Claude panel inside Excel.
4. **Build the close workbook.** New workbook named for the period. Tabs: Card Feed, Receipts, Coding Worksheet, Journal Entries, Exceptions, Close Pack.
5. **Load data.** Paste or import the card feed and export your GL and policy. Drop receipts into a Claude Project (see Path 2) for the read, or summarize them in Excel.
6. **Run the vault.** Run prompt 01, pick data source (C) Excel add-in. Then prompt 03: "Write the coding worksheet into my workbook as real formulas, with a SUM that ties to the card statement total." Run 07 for the journal entries and 08 for the tie-out, in formulas, so any mismatch is a cell error to fix, not a guess.
7. Pin **Opus 4.8** for the close, accruals, and CFO pack. A named human signs the close.
## Path 2 (QUICK START, no install) — run the prompts in a Claude Project
1. Open Claude, pin **Opus 4.8**, create a private Project "Expense Close". Your card feeds, receipts, and GL stay in your own tenant.
2. Drop the card feed CSV, receipts PDF, GL export, and policy doc into the Project knowledge.
3. Run prompt 01, choose data source (A) upload. Run 02 to 09 in chat. **Important:** because the math is in chat here, prompt 08 (reconciliation self-check) is your guard, run it before the close pack and fix any FAIL.
4. When you can, move to Path 1 so the coding worksheet lives in real formulas.
## Rules for walking me through this
- One step at a time. Define every term once: add-in, ribbon, side panel, Project, GL coding, three-way match, accrual, `<review_gate>`, `{{TOKEN}}`.
- Do NOT tell me a step is "not possible." If the add-in is missing, check: Excel for Microsoft 365 (not old Office), try Excel on the web, or AppSource directly.
- Never paste live employee PII into a public Claude window. Use a Claude Project with your tenant controls.
- A named human signs the close. Claude does the coding and the tie-out; a person owns the GL.
First message: ask me "Path 1 (Claude for Excel add-in, the coding worksheet lives in formulas) or Path 2 (no-install, run in a Claude Project)? And are you on Excel desktop or web, company-managed or personal?" Then start step 1.Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.
Run expense and AP inside Claude instead of Concur
The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.
Back to the prompts ↑We would deliver a private close workspace: the 9 prompts loaded into your Claude tenant, your chart of accounts and expense policy wired into the coding rulebook, a card-feed and receipt pipeline, and a controller review gate so nothing posts to the GL unchecked. Done with you, then handed over so you own it.
Book a build call →Prompt set authored by consultance.ai. SAP Concur is referenced as the incumbent the pack replaces, no affiliation implied. Your expense data stays in your own Claude tenant; we never see it. A named human signs the close.
Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.
The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.
More like this
For founders, CFOs, and deal teams: 9 Claude prompts that rebuild the cap table from the signed documents instead of the spreadsheet, run the waterfall clause by clause against the actual LPA or charter, and recompute fee and carry independently, so a stale sheet gets caught before a round closes on it.
For CFOs and finance leaders: the map of seven finance desks, deal, diligence, close, tax, underwriting, family office, and market, each one a free prompt vault that runs inside your own Claude, plus the order to install them in so a team actually adopts them.
For CFOs and controllers: 11 Claude prompts that run the month end close reconciliation itself, match bank and subledgers both directions, catch the account that will not foot, and draft the flux memo, so a 6 day close lands in 2.
The person drowning in this every week is the one who'll actually want it.
Replace Concur Expense and AP is a finance and data build in the consultance.ai AI Build Library. Run expense and AP inside Claude instead of Concur. 9 prompts code expenses to the GL, match receipts to the card feed, flag fraud, and close the corporate-card month. For controllers and CFOs. It fits controllers, CFOs, and founders at $5M to $500M who sign the expense-platform cheque and want the month close run without the seat or the implementation consultant. Setup difficulty is Medium, with 4 plain-English steps.
Run expense and AP inside Claude instead of Concur. 9 prompts code expenses to the GL, match receipts to the card feed, flag fraud, and close the corporate-card month. For controllers and CFOs.
It fits controllers, CFOs, and founders at $5M to $500M who sign the expense-platform cheque and want the month close run without the seat or the implementation consultant.
Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 9 ready-to-run prompts on the resource page.
We would deliver a private close workspace: the 9 prompts loaded into your Claude tenant, your chart of accounts and expense policy wired into the coding rulebook, a card-feed and receipt pipeline, and a controller review gate so nothing posts to the GL unchecked. Done with you, then handed over so you own it.
Prompt set authored by consultance.ai. SAP Concur is referenced as the incumbent the pack replaces, no affiliation implied. Your expense data stays in your own Claude tenant; we never see it. A named human signs the close.
Replace Concur Expense and AP is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.
This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.