Finance areas · Expense management
Cards, receipts, per diem and mileage — submitted from chat, email or the dashboard, checked against your policy, approved by risk, posted to the ledger and reimbursed. Your team reviews exceptions; agents do the processing and the chasing.
The whole expense surface
01 / The lifecycle
An employee forwards a receipt by email, snaps it in chat, or a card transaction lands from the bank feed. No portal, no form.
Vendor, amounts, VAT and category are extracted and mapped to expense accounts — card merchants resolve through MCC mappings your team can tune.
Per-diem day rates, mileage rates, monthly caps and receipt requirements come from your entity's configuration — exceptions are flagged, not silently passed.
Reports route through the lanes your policy defines: recognized low-risk claims execute, everything else waits for the reviewer your rules require.
An approved report posts as a governed transaction — expense accounts debited per line, the employee's payable credited. Every line keeps its receipt.
The payment proposal agent picks up the payable, the batch goes to the bank, and the confirming statement line clears the balance — end to end on one audit trail.
Expense reports and reimbursement payouts are governed transaction types — posted through the same workflow engine, dry-run and approvals as everything else.
02 / Coverage
Card transactions match to receipts, categorize by merchant, and settle through reconciliation — collector cards and employee cards both covered.
Email, photo or upload. Missing receipts get chased by an agent, not by your finance team.
Country day rates with tiered and partial-day rules, calculated by a deterministic engine — not typed into a spreadsheet.
Vehicle-type rates with per-month caps, validated at submission.
Risk lanes, amount thresholds and reviewer requirements are your entity's configuration — the same rules every time, with exceptions surfaced.
Approved reports become employee payables, flow into payment batches, and clear automatically when the bank confirms.
03 / Who does the work
Each one has a job description, an audit trail, and limits your policy sets.
Processes employee expense submissions from email — receipts, per-diem requests, and mileage claims — into expense reports.
Sends escalating reminders to employees with missing receipts on submitted expense reports.
Builds payment batches from outstanding AP invoices and approved expense reports, grouped by method, currency, and source bank.
Produces a proposed batch only. A human reviews every line against its bill and approval, then approves and transmits the bank file. No agent moves money.
Not limited to three
Accountants describe the work to Claude in plain language — what starts it, what to check, when to ask a person. Claude turns it into an agent with its own triggers, steps and limits, running under the same controls and audit trail as the three above.
04 / Go deeper
Start with this workflow
Bounded risk, visible pain, measurable result — run a month of expenses in shadow mode and compare the manual effort you didn't spend.
hello@ar-ti-fi.com