Xero bills due: a weekly digest, drafted for your approval
Supplier bills get paid late when nobody looks at the due dates. A scheduled agent reads your Xero bills every week, lists what is due soon, and drafts a digest its department head reviews and you approve.
What you’ll set up
Connections
Xero read access (invoices) · Required
Reads supplier bills, due dates and amounts due. Read scope is enough; nothing changes in Xero.
Upgrades
Delivery (channel or inbox)
Delivers the approved digest to your channel or inbox.
Inputs
Look-ahead window (days) · Optional
Number, default 14
Flag bills above this amount · Optional
Number, default 2000
Suppliers paid on a fixed day · Optional
Text, no default
Ready by · Required
Time, default 08:00
Brief · Required
Text, prefilled and editable during setup.
Runs
Runs every Monday at 08:00
Done by Business analyst
You approve before anything goes out.
You approve every report · Free to start
How it runs
One agent does the work. Its department head reviews it, then you approve.
- 1Business analyst
Runs every Monday at 08:00 and prepares the report from your connected sources.
- 2COO · Review
The department head reviews the report before it reaches you.
- 3You
You approve before anything goes out.
What you get
Sample, not live data. Suppliers and amounts are invented.
Bills due, week of 10 Nov (sample)
| Group | Bills | Amount due |
|---|---|---|
| Overdue | 2 | 1,240.00 |
| Due in 7 days | 5 | 3,880.50 |
| Due in 8 to 14 days | 4 | 2,115.00 |
Over your 2,000.00 flag: Northwind Print, due 13 Nov, 2,450.00.
Needs your approval before it is sent.
Why due dates slip
Xero stores every supplier bill with a due date, but the date helps if someone looks. Bills arrive by email, get approved, and wait. Nothing reminds the person who pays them. A short weekly list fixes this: what falls due this week, what falls due next week, and what is already late. The list is small enough to act on in ten minutes and regular enough to trust.
How the scheduled job works
You add the job and grant read access to your Xero organisation. Each Monday a scheduled agent requests invoices of type ACCPAY, which is how the Xero accounting API marks supplier bills, and filters to those that are authorised but not yet paid. For each bill it reads the contact, due date, total and amount due. It groups the results into overdue, due in the next seven days, and due after that up to your look-ahead window (14 days by default, so the second group stretches if you change it). It totals each group and flags any single bill above the amount you set. It reads and reports. It does not approve, pay, edit or delete a bill.
Review and approval
Before the digest reaches you, the department head agent checks it: do the group totals match the sum of the lines, is any bill counted twice, and are partly paid bills shown at the amount still due rather than the full total. Then you approve, edit or skip the digest, and nothing is delivered until you do. Use the notes field for suppliers you pay on a fixed day, so they stop looking urgent.
What to do with it
Treat the digest as the agenda for your weekly payment run. Pay the overdue group before the rest, schedule the next group, and query anything unfamiliar before it is paid. If the same supplier appears as overdue week after week, check whether the due date on the bill is wrong rather than paying late again. The digest also gives a rough cash need for the fortnight, which is useful when you decide how much to move into the paying account.
Questions
Related jobs
Connects to: Invoicing or accounting tool (read) (required)
Chase late invoices without chasing people who already paid
A morning list of overdue invoices with a drafted, checked follow-up for each. Nothing goes out until you approve it.
Connects to: Accounting tool or bank feed (read access) (required)
Categorise bank transactions on a schedule
Each week, new bank and card transactions get a draft category, uncertain or unusual lines are flagged for you, and spend is summed by category.
Connects to: Remote MCP server with Stripe read access (required)
Automate failed payment follow-ups for subscriptions
A daily list of failed payments that retries have not fixed, with a drafted follow-up for each.