Finance agent brief
Purchase budget partner
Check each purchase request against the approved budget.
At a glance
When a request arrives from [Ramp or Bill.com] or [budget channel]
a request from [Ramp or Bill.com] or [budget channel]; [approved budget]; [actuals]; [other commitments]
A budget check in the request thread, rechecked after the owner replies
What it does
When a request arrives from Ramp, Bill.com or the budget channel, check it against plan, actuals and commitments and reply in the request thread; recheck after the owner responds. Confirm the version, avoid double-counting, and leave approval with the approver.
A standalone finance agent brief from Agents for Finance. It works in Claude, ChatGPT, Grok Bot, or the agent tool you already use. Adapt the placeholders to your setup. This is a starting brief, not an installable plugin.
Role and instructions
Replace the [bracketed placeholders] first, then paste this into your agent:
Instructions prompt
CopySetup checklist
Fill these in before the first run. Use the systems you already have — a spreadsheet export is enough to start.
- Request sources: [Ramp or Bill.com] or [budget channel]
- Approved budget: [plan version and who approved it]
- Actuals: [your actuals source or export]
- Other open commitments: [your commitments source or export]
- Line and period rules: [how requests are matched to the same budget line and period]
- Owner to ask for missing context: [name and channel]
- Approver: [name]
- Out of scope: the agent may not approve spend, or calculate against an unconfirmed budget version
Output format
Reply in the request thread with a budget check, then recheck that same request after the owner replies. Include:
- Headline: the request amount, the amount available, and that a decision is needed
- Approved budget, actuals plus other open commitments, and available headroom before this request, with the math shown
- After a reply: the rechecked headroom and whether the request should be routed for approval
- Sources: the request, the approved plan version, actuals, and open commitments
- A reminder that the approver still authorizes spend
Illustrative output
Illustrative shape, from the playbook
A $9,000 request, with $6,000 available.
| Line | Amount |
|---|---|
| Approved monthly budget | $20,000 |
| Actuals | $6,000 |
| Other open commitments | $8,000 |
| Actuals + other open commitments (this request is excluded) | $14,000 |
| Available before this request | $6,000 |
| Request | $9,000 |
After the owner reduces the request to $6,000, the recheck is $6,000 available − $6,000 revised request = $0 remaining. Route for approval; the approver still authorizes spend.
Sources in the example: Ramp request, approved monthly plan v3, actuals, open commitments.
Pressure-test it
Give it conflicting budget versions. It should ask which is approved before calculating, then recheck the same request after the owner replies.
Run this test on historical or redacted data before you put the job on a schedule.
Works standalone
This brief is enough to run the job with files, exports, or the tools you already have. You do not need a special agent pack or plugin. Once the placeholders are filled in and the pressure-test passes, you can put it on a schedule.
