Close expenses with one message per person
Nineteen people, one specific message each listing their own missing reports and receipts. Plus the dinners over the per-head limit and the coding that would have surfaced at reconciliation.
Nineteen people owe a report, four have submitted, two of those are missing receipts over the threshold, and one has categorised a client dinner as office supplies. Somebody in finance now writes fifteen individual messages.
A companion reads the reports and expenses, works out exactly what each person owes, and writes the fifteen messages. One line per person is a completely different response rate from four generic ones.
| Expensify rules and Concierge | A Strawberry companion | |
|---|---|---|
| Flag a missing receipt on submission | Yes, immediately | Chases the ones already in, one message per person |
| SmartScan a receipt photo | Yes, from the phone | Chases the expenses that arrived without one |
| One message per person covering everything they owe | Sends per-report reminders | Drafted, grouped, you send |
| Check coding against your own ledger mapping | Manual review | Reported as mismatches with report links |
| Approve or reject a report | Yes, with your approval chain | Assembles what the approver needs to sign |
| Compare against a stated travel policy | Rule-based within the policy | Reads the description and the amount |
What does the chase list look like?
One line per person.
Who has not submitted, who has submitted with missing receipts, who has expenses that conflict with the policy you described. Three groups with names and amounts.
Then one drafted message per person covering everything they owe. Fifteen specific messages get answered; sixty generic ones get filtered.
Comparing expenses against a stated policy
A companion compares against a policy you state and reports the differences: a dinner over the per-head limit, a hotel above the city cap, a category that does not match the description written next to it.
Approving or rejecting is an accountability decision, so it stays with the person whose name goes on it.
What about the accounting handoff?
A miscoded expense becomes a wrong number in a ledger somebody else reconciles later.
A companion reads the approved expenses, checks the coding against your own mapping, and reports mismatches with the report they came from.
It assembles evidence. Nothing it produces is accounting advice. Related: automate expense report collection and ai for finance teams.
The card feed and the personal-card problem
Company card feeds reconcile themselves reasonably well.
The mess is the personal card: a flight booked in a hurry, reimbursed six weeks later, sitting in a report with no receipt and a description that says “travel”.
A companion lists reimbursable expenses over a threshold with no receipt and no useful description, per person, which is the specific pile worth chasing.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents