Invoice processing

Turn each incoming invoice into a coded, approved ledger line with its document attached, or into a held exception with a stated reason.

macOS — coming soonSee the 5 automations
Finance / AUTOMATE.md

Pre-check each invoice that arrives at invoices@acme.inc: match it to its purchase order, file it in Expenses, and flag anything unusual for my review.

## Flag for review
SituationWhat to do
No matching POAsk the requester
Amount differsFlag with both amounts
Over $10,000Flag, even if it matches
## Exceptions
-**Duplicate** invoice → flag it, don’t file it.
-New supplier → check their bank details with me.
-Every Monday, send me totals by department.
Ready-made: Invoice pre-check

The job, and what good looks like.

Invoices arrive as email attachments, scanned pages, and photographs taken at the counter, and they get keyed by hand because nobody trusts the extraction enough to post straight from it. The coding, the cost center, and the approval are what get skipped, so the invoice either sits unpaid past its due date or gets paid twice. This workflow moves each invoice along one path. The document is read for the vendor, the number, the date, and the tax line, then matched against the open purchase order and the goods receipt where one exists. Anything that does not match with confidence is held in an exception queue with the specific reason attached, rather than posted and corrected weeks later. Coding is proposed from the vendor's history and the receiving department, and a duplicate check runs against what is already booked so a re-sent document does not become a second payment. Due dates are tracked from submission, so an invoice stuck with an approver is visible on its own. A person still rules on the exceptions and sets the payment terms.

When it is handled

  • Every invoice coded or held same day
  • No invoice paid without an approval trail
  • Duplicate submissions blocked at intake
  • Due dates met without a manual chase

Works with tools like

  • NetSuite
  • Bill.com
  • Tipalti
  • Coupa
  • SAP Ariba

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.

Duplicate Invoice ID Check

When a new invoice lands in the intake folder, compare it to the ones already booked and email the AP clerk any match on vendor, amount, and number.

When a new invoice lands in the intake folder

Expense Reconciliation

Match uploaded receipts to bank transactions and archive in named folders.

Expense Reimbursement

Sort incoming expense reports by employee name in the ledger and file into folders.

Invoice pre-check

Pre-check each invoice that arrives at invoices@acme.inc: match it to its purchase order, file it in Expenses, and flag anything unusual for my review.

Each new invoice

Vendor Invoice Sorting

Sort incoming vendor files into document folders based on type and name.

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.

Invoice pre-check

Approve before it updates the sheet and moves the files?

ReviewApprove

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. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 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.

macOS — coming soon