Expenses reconciled
without an accountant chasing.
Expense reports are the universal complaint. Receipts pile up in inboxes, employees forget to submit, finance chases for weeks. A Loomal agent watches an expense inbox, matches each receipt to the right card transaction, and emails the right people when something doesn't line up.
API Primitives used
mail_list_messagesRead forwarded receipts
Employees forward receipts to a single agent address. extractedText feeds clean line-items into the matcher.
vault_getPull card transactions
Card-statement API tokens live encrypted in the vault. Agent fetches transactions and matches them against the receipt corpus.
mail_sendChase the missing ones
Agent emails employees with outstanding charges and a single-click forward path — closing the loop without finance lifting a finger.
Receipt chasing eats finance teams.
Every finance team spends a week each month chasing receipts. The work is identical every cycle: pull the card statement, match what was submitted, list what wasn't, email each employee, wait, escalate, repeat. The cost is real — hours of senior finance time on a task that creates zero value.
An agent owns the cycle end-to-end. It reads the receipts as they arrive, matches them against the live card feed, and chases the gaps autonomously. Finance reviews the exceptions; the agent runs the conveyor.
How to build it.
mail_list_messagesRead incoming receipts
Agent watches expenses@ for forwarded receipts. The LLM parses vendor, amount, date, and category from each message.
vault_getMatch against card data
Agent pulls card transactions via the stored API token and matches receipts by amount and merchant — flagging the unmatched.
mail_sendChase the gaps
Unmatched charges trigger a friendly reminder to the employee, threaded against their original submissions for context.
Example prompt
“Match every receipt forwarded to expenses@ this month against our Brex transactions. For any charge over $50 with no receipt, email the employee asking them to forward it.”
What finance teams build.
Monthly reconciliation
Agent runs the entire match cycle on the close date, leaving finance with only exceptions to review.
Real-time matching
As each charge posts, agent looks for the matching receipt and chases immediately if missing.
Category enforcement
Agent enforces expense policy — flagging out-of-policy categories and asking for context inside the email thread.
Multi-card support
Agent reconciles across multiple corporate card programs from a single identity.
Audit prep
Agent assembles audit-ready packages with every receipt and matched transaction in one folder per period.
Why reconciliation belongs to an agent.
Receipt chasing is the textbook job for an agent — repetitive, thankless, and sensitive enough that traditional automation can't be trusted with it. It needs the inbox, the card-feed credentials, and the ability to send chase emails at human scale.
Loomal puts all three in one identity. The card credentials stay encrypted in the vault. The receipts come into the agent's inbox. The chase emails go from a real address. Finance gets clean books; employees get fewer Slack pokes.
Card credentials encrypted
Card-feed API tokens live in vault entries scoped to the finance identity.
Per-period audit
Every match, mismatch, and chase email is logged with the agent identity and originating transaction.
Scoped per program
Multiple card programs can each get their own identity with isolated access.