Paying in date order ignores what each invoice actually costs
Invoices are paid in the order they appear, which is the order they were entered. That order ignores everything that makes one invoice more urgent than another.
Early payment discounts are money you lose by inaction. A discount of two percent for paying ten days early is one most businesses would take. The offer expires without anyone deciding not to take it.
Late-payment penalties and relationship cost sit on the other side. A critical supplier and an occasional supplier do not tolerate delay equally. Neither the amount nor the due date captures that.
Cash on hand is part of the picture. If a priority list has no available balance next to it, a person has to re-sort it in their head.
How the ActionFlow runs on the canvas
Selection is by due date. Ordering is by everything else. A Start Scheduled node runs the review. A PostgreSQL or Google Sheets node reads the open payables.
A Date node computes days to due. A Filter node keeps those that fall inside your payment window.
A Google Sheets node supplies supplier terms: discount windows, penalty rates, and criticality. That data turns a date list into a priority list. A Math node values each remaining discount and the cost of each possible delay.
An HTTP Request node reads the current cash position so the output stays within what can actually be paid.
A Generate Object node returns a prioritized list with a reason on each line: discount expiring, penalty risk, supplier criticality, or simply due.
A Sort node sorts the list. A Create Excel node produces the payment run as a file. A Slack node sends the summary, with the total and the cash position side by side.
Payment is not part of the flow. A Human in the Loop node holds approval. Execution stays in your banking system, where it belongs.
Nodes this ActionFlow uses
- Start Scheduled: runs the payables review on your payment cycle.
- PostgreSQL (Data): reads open payables. Google Sheets fits the same slot.
- Date (Util): computes days to due for the selection.
- Google Sheets (Integration): supplies supplier terms, discount windows, and criticality.
- Math (Util): values each available discount and each potential delay cost.
- Generate Object (AI Core): returns the prioritized list with a reason on every line.
- Create Excel (Data): produces the payment run as a file for approval.
- Slack (Human in the Loop): carries the approval. Payment execution stays in your bank.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.