Vendor payment tracking

Hold the payment run, the remittance advice, and the outstanding check register in step, so nothing is paid late, twice, or into a voided account.

macOS — coming soonSee the automation
Finance / AUTOMATE.md

Before each payment run, compare the approved batch total with the cash position and email the controller the gap if the run is larger than the cash available.

Ready-made: Payment Run Cash Check

The job, and what good looks like.

The payment run is assembled in a spreadsheet on the morning it goes out, and the approved-but-unpaid list is often the only record of what still owes money. When that spreadsheet and the ledger disagree, the vendor relationship manager is the one taking the calls, because the vendor says nothing arrived and nobody can produce a remittance. A check that is issued and never logged disappears just as quietly, and the same invoice comes back around at the next run. This workflow keeps the run, the ledger, and the vendor's view of the account as one list. Approved invoices are aged by due date and by payment terms, and each shows what is queued, what is in the bank, and what has been confirmed lost. Remittance advice is generated from the run and reaches every vendor on it the same day. Checks outstanding past the stale date are listed for investigation rather than left in a drawer. A person still releases the batch and confirms the total against available cash.

When it is handled

  • Every payment traced to an approved invoice
  • Unpaid invoices aged and visible weekly
  • Stale checks cleared on a schedule
  • Remittance advice sent with every run

Works with tools like

  • NetSuite
  • Tipalti
  • Kyriba
  • Bill.com
  • Coupa

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.

Payment Run Cash Check

Before each payment run, compare the approved batch total with the cash position and email the controller the gap if the run is larger than the cash available.

Before each scheduled payment run

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.

Payment Run Cash Check

Approve before it sends the email?

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