Expense reconciliation
Match every card charge and submitted claim to its receipt and cost center, and close the month without paying out on trust.
Every Friday at 3:00pm, find submitted expenses with no receipt and email each employee the specific items to attach.
The job, and what good looks like.
Expense reports get approved in bulk at month end because the receipts are still sitting in people's inboxes, and the bookkeeper spends the first week of the new month matching card lines to claims that do not exist. What is missing is the receipt image attached to the charge, and the person chasing it is the accounts payable clerk, one email at a time. This workflow works the population continuously instead of at the cutoff. Card transactions are read as they post and matched to a claim on amount, date, and merchant. Anything with no claim, and any claim with no card match, is collected before the reimbursement run rather than after it, and the employee is asked for the specific missing item instead of receiving a general reminder. Coding is checked against policy at submission, so a meal over the limit is flagged before the money moves rather than clawed back afterwards. A person still decides which policy exceptions are worth granting and approves the final batch.
When it is handled
- Every card charge carries a receipt
- Claims paid in the run they were filed
- No aged unreceipted items at close
- Policy exceptions approved before payment
Works with tools like
- Expensify
- Ramp
- Brex
- NetSuite
- HighRadius Autonomous Reconciliation
Ready-made automations. Pick the one that fits.
Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.
You stay in charge.
At every step.
It does the checking. You approve what gets paid and posted.
- Nothing paid or posted on its own
Payments, journals and approvals stay with you. It prepares them and flags what doesn't match.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only the books you open to it
Each automation reaches only the folders and systems you connect for it.
Receipt Gap Chase
Approve before it sends the email?
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Rules in your accounting software
Coding recurring transactions the same way every time.
They can't read an unusual invoice, ask the requester a question or explain why a match failed.
Flowchart automation tools
Moving data between apps at high volume.
Every exception becomes another branch someone has to build, test and maintain.
AI chat assistants
Explaining a document when you paste it in.
Nothing happens until you come back and ask again, and the procedure lives in a chat.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.