Wallet top-up history

Retrieves the company wallet top-up history with datetime format handling and pagination. Useful for cash flow tracking and reconciliation of funding transactions.

↓ Download skill (.md)
81/100Β·πŸ“† MonthlyΒ·BeginnerControllerFinance Analyst
ReconciliationReportsget_wallet_loads

🎯 Skill purpose

Retrieves the company wallet top-up history with datetime format handling and pagination. Useful for cash flow tracking and reconciliation of funding transactions.

πŸ“Š What it produces

Chronological list of wallet top-ups with dates, amounts, currencies, and metadata for each transaction.

⚑ Benefit

Before

Manual search in the Spendesk UI, CSV export required to analyze past top-ups.

After

Complete top-up history directly in Claude, ready to analyze and reconcile.



# Instructions β€” Wallet top-up history

## ⚠️ Date format: full ISO 8601 + timezone recommended

The MCP documentation states that YYYY-MM-DD alone is not accepted and that a full datetime is required.
In practice, `from="2026-06-01"` is accepted by the API (tested live β€” 16 results returned).

**Despite this tolerant behavior, always use full ISO 8601 with timezone:**
```
from: "2026-06-01T00:00:00.000Z"
to:   "2026-06-30T23:59:59.999Z"
```

Reason: coercion from YYYY-MM-DD to midnight can produce unexpected results depending on the server's timezone. Using `T00:00:00.000Z` (UTC) is unambiguous.

## ⚠️ Not for exact bank reconciliation

`get_wallet_loads` returns the **Spendesk record date**, not the **bank value date**.
β†’ Do not use it to align Spendesk balances with a bank statement.
β†’ For exact reconciliation, cross-check with your bank.

## ⚠️ 24h cache (86400 seconds)

The returned data may be up to 24h stale.
β†’ Do not use for a real-time balance β€” use `get_wallet_summary` for that.

## Step 1 β€” Call with period and recommended parameters

```json
{
  "companyId": "...",
  "from": "YYYY-MM-DDT00:00:00.000Z",
  "to": "YYYY-MM-DDT23:59:59.999Z",
  "pageSize": 100
}
```

## Step 2 β€” Interpreting the fields

For each load:
- `amount`: `{ amount, currency, precision }` β†’ amount = `amount / 10^precision` EUR
- `type`: `"wireTransfer"` (only type observed on this account)
- `bankName`: `sfs` | `adyen` | `other`
  - `sfs` = Spendesk Financial Services (main account)
  - `adyen` = Adyen (accounts for certain subsidiaries)
  - `other` = external transfer
- `createdAt`: date recorded in Spendesk (β‰  bank value date)

## Step 3 β€” Pagination

Check `meta.pagination.hasNextPage` β€” if `true`, paginate with `page=2, 3, ...` and the same filters.

## Live example (real data, June 2026)

16 loads in June 2026, including:
- 2026-06-23: EUR 500,000.00 (sfs transfer)
- 2026-06-10: EUR 600,000.00 (sfs transfer)
- Total for the month: ~EUR 1,105,721 (including two large test loads)

## Example prompt

- "Show wallet top-ups from last month" β†’ from/to = last month + ISO 8601
- "How much did we load into the wallet in 2026?" β†’ from=2026-01-01T00:00:00.000Z, to=today + pagination
- "What is the current wallet balance?" β†’ use `get_wallet_summary`, not `get_wallet_loads`

How to install this skill

/
  1. 1
    Download the file s02-wallet-loads-datetime.md using the button above.
  2. 2
    Place the file in the .claude/ directory of your project (or ~/.claude/ for a global install).
    cp s02-wallet-loads-datetime.md .claude/s02-wallet-loads-datetime.md
  3. 3
    Use 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 get_wallet_loads.

Similar skills

β˜… Top
95/100Β·πŸ” Ad hocΒ·Expert

MCP coverage audit & gap analysis

Probes all available MCP tools, re-evaluates coverage of 50 persona use cases, detects new fields or tools, and regenerates the gap analysis report.

CFOControllerAP Manager
90/100Β·πŸ“… WeeklyΒ·Beginner

Card requests via get_requests

Explains how to use get_requests for card requests and why expense reimbursements don't appear there. Avoids a frequent source of confusion between two distinct workflows.

ControllerFinance Analyst
90/100Β·πŸ” Ad hocΒ·Intermediate

Active vs archived cost centers

Distinguishes active cost centers from archived ones with correct use of get_cost_centers. Avoids the counter-intuitive isArchived vs isActive naming convention pitfall.

ControllerFinance Analyst