Analyse card requests
Analyses card request volume and average amount by type (single purchase, subscription, multi-use), before spend is committed.
ProcurementCFO๐ MonthlyIntermediateRead-only
Ask it like this
How many card requests this quarter, by type?
When to use it
When you want to know the volume and amount of card requests, before the spend.
What it produces
Breakdown of card requests by type with total amount, count, and average amount.
How it works
- 1Counts the period's card requests
- 2Breaks them down by type, month or requester
- 3Works out the average amount of a request
- 4Compares with the previous period on request
- 5Recalls that deleted requests are still counted
What protects you
- This skill only reads: it changes nothing in Spendesk
- It acts with your permissions and your role, never beyond
- The assistant cannot approve or pay
โธTechnical detail72/100 ยท 1 tools
Budget & POsSpend analysisspendesk_analyze_requests
# Analysing card requests (before spend)
## What this tool covers โ and what it doesn't
`spendesk_analyze_requests` covers ONLY card requests: `single_purchase`, `subscription`, `multi_use_card`, `multi_use_card_top_up`, `multi_use_card_end_date_change`, `card_load`. **It does not cover supplier-invoice requests or expense/reimbursement requests** โ those are separate objects. Never present its totals as "all requests" for the company.
This is an intent view (before actual spend) โ for spend already committed, use `spendesk_analyze_spend`.
## Call
```json
{
"tool": "spendesk_analyze_requests",
"params": {
"companyId": "<companyId>",
"fromDate": "2026-06-01",
"toDate": "2026-08-31",
"groupBy": ["type"]
}
}
```
`fromDate`/`toDate` filter on `createdAt` (request creation date), not the approval date or card availability date.
## Observed result
```
{"summary":{"totalCount":14,"totalAmount":{"formatted":"EUR 15097.00"},"totalAverageAmount":{"formatted":"EUR 1078.36"}},
"data":[
{"key":"Subscription card","amount":{"formatted":"EUR 11296.00"},"count":6,"averageAmount":{"formatted":"EUR 1882.67"}},
{"key":"Single purchase card","amount":{"formatted":"EUR 3301.00"},"count":7,"averageAmount":{"formatted":"EUR 471.57"}},
{"key":"Multi-use card","amount":{"formatted":"EUR 500.00"},"count":1,"averageAmount":{"formatted":"EUR 500.00"}}
]}
```
Keys shown are human-readable labels ("Subscription card"), not raw slugs (`subscription`) โ never show a raw slug to the user when a label exists.
## Deleted requests trap
Requests deleted in Spendesk are not excluded: they are still counted, with no marker, whenever their state matches โ including the requests of an employee removed from the company. Even with `filters.state` set, a pending or approved total can therefore overstate the live workload: say so when quoting it. Same limit on `get_requests`.
## Currency trap
Grouping by `currency` keeps amounts in functional currency: a row keyed `"USD"` is the functional-currency total of requests submitted in USD, **not** a USD total. Never relabel a row's amount with its group key's currency.
## Example user prompts
- "How many card requests this quarter, by type?"
- "What's the average amount of a single-purchase card request?"
- "Compare subscription card request volume vs single-purchase over the last 3 months"
How to install this skill
/
- 1Download the file
s66-analyse-demandes-cartes.mdusing the button above. - 2Place the file in the
.claude/directory of your project (or~/.claude/for a global install).cp s66-analyse-demandes-cartes.md .claude/s66-analyse-demandes-cartes.md - 3Use in Claude Code โ the skill is automatically discovered. Describe your need in natural language and Claude will apply the skill instructions.
๐ก Make sure the Spendesk MCP is configured in your
.claude/settings.json with the tools spendesk_analyze_requests.Similar skills
โ
Top