Official recipe

Reconcile travel spending against individual budget exceptions

A team can appear over budget when a report ignores personal exceptions, mixes expense categories or counts unapproved claims. A blanket warning can unfairly implicate someone whose spending was authorized.

Read original recipe

Proposed inputs

Name
Expense export
Owner
Finance owner
Minimum scope
One invented quarter for three fictional employees
Quality check
Keep expense IDs, categories, dates, currency and approval status.
Name
Limit register
Owner
Travel program owner
Minimum scope
Default and individual fictional limits
Quality check
Include effective dates and exception ownership.

Access and setup — proposed or unknown

Proposed minimum: Use local copies with no employee contact details.
Preserve excluded rows and the reason for excluding them.
Compatibility unknowns: Unknown: actual expense connectors, policy interpretation and historical exception availability.
External actions requiring approval: Employee communications, expense-status changes or modifications to budget limits.

Detailed steps and output format

At a glance

Suggested result: An employee-level reconciliation showing included expenses, applicable limits and unresolved exceptions.Suggested; untested.
Tool: Claude API; programmatic tool callingSource-named; check current access.
Suggested inputs: Expense export; Limit registerProposed; access notes below.
Human review: Proposed: Employee communications, expense-status changes or modifications to budget limits.Suggested boundaries; source approvals below.
Setup notes: Use local copies with no employee contact details. Preserve excluded rows and the reason for excluding them.Guide notes; proposed setup untested.
Cost: Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth: Source-linked example · suggestions untestedDepth does not establish successful execution.

Check source evidence and limits ↓

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Suggested task · untested

Proposed: Build an offline exception-adjusted travel-budget review.

What you could produce

An employee-level reconciliation showing included expenses, applicable limits and unresolved exceptions.

Where these suggestions come from

Core problem: Our suggestion; no result reported by the source
Agent job: Our suggestion; no result reported by the source
Expected output: Our suggestion; no result reported by the source
Relevant job roles: Our suggestion; no result reported by the source
Benefit type: Our suggestion; no result reported by the source

Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original decision guidance and first check are proposals. The source supports the attributed task; this guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

The useful question is whether spending exceeds the limit that actually applied.
A traceable reconciliation lets the owner correct data or policy gaps before any message about an employee is sent.

Why an agent / simpler alternative

Useful judgment: Recognize unclear expense categories and explain missing or conflicting exception evidence.
Simpler alternative: Use a spreadsheet join and group-by when categories, dates and limits are clean.
Unsuitable when: The task asks the agent to discipline staff or decide reimbursement eligibility.

Expected deliverable and review checks

Proposed artifact: An employee-level reconciliation showing included expenses, applicable limits and unresolved exceptions.
Critical checks: Only in-scope travel and approved statuses enter totals.
Each exception applies to the selected employee and period.
Missing limits remain unresolved rather than defaulted silently.
Missing output evidence: Unknown: no independently inspected run artifact or live outcome.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Three fictional employees: one below a personal limit, one over the default, and one with an undated exception and a reversed expense.
Acceptance checks: Separate all three outcomes.
Show included and excluded row IDs.
Leave the undated exception unresolved.
Stop conditions: Real employee disclosures, disciplinary conclusions or record changes.

Tasks: Travel & transport Money & accounting Data & analysis

Useful for: Personal and household

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

Claude API; programmatic tool callingIndependent testing: No

Failure handling, costs and limits

Failure signals and proposed responses

Signal
Exception lacks an effective date
Why it matters
The allowed amount may belong to another period.
Proposed response
Flag the uncertainty and ask the policy owner.
Signal
Duplicate or reversed entry
Why it matters
A total may overstate actual approved spending.
Proposed response
Retain the linked rows and reconcile their net treatment.

Effort and cost — unknown

Setup work: Agree on categories, period boundaries and exception precedence.
Ongoing review: Review ambiguous classifications and unresolved effective dates.
Unknowns: Unknown: implementation effort, review time, usage charges and error frequency. No savings estimate established.

Limits

This review identifies reconciliation questions, not misconduct or reimbursement entitlement.

Full source evidence

Official recipe · Tool workflows

Original task title: Reconcile travel spending against individual budget exceptions

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/anthropics/claude-cookbooks/blob/main/tool_use/programmatic_tool_calling_ptc.ipynb ↗

Attributed to: Anthropic

Official recipe

Original action type: tool_action
What the source reports: Retrieves team members and quarterly expenses, totals approved travel entries, checks individual budget exceptions, and reports which people exceed the applicable limit.
Source outcome limits: Simulated expense service. Published comparison output is not an independently reproduced performance result. No independent execution test.
Evidence attribution caveat: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: Read-only mock tools are shown; no expense approval or employee action is performed.
Named tools: Claude API; programmatic tool calling
Model or version: claude-sonnet-4-6, as specified in the recipe
Publication date: Unknown
Source last checked: 2026-10-14
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed: an authorized local owner must verify availability, privacy, policy and professional-review requirements. Canadian execution is unknown.
Recommended approval boundaries: Proposed: Employee communications, expense-status changes or modifications to budget limits.