Simulation — shows exactly what the scenario does with sample data

Invoice Chaser for Xero — Make scenario simulation

This page replays the exact module logic shipped in invoice-chaser.blueprint.json: a daily Xero sweep → days-overdue maths → a five-way escalation router (nudge at 3 days · firm follow-up + PDF at 10 · final notice + owner alert at 21 · thank-you when paid · Monday digest). Nothing here calls a network — every value below is computed in-page from the sample ledger, the same data as sample-run.md.

runningcompleted
= 3 days = 10 days = 21 days PAID < 24 h Mon · ≥ 1 day xero Watch invoices daily 8am sweep fx Days overdue + your details API Online invoice pay-now link Router @ Friendly nudge day 3 email PDF Invoice PDF @ Firm follow-up day 10 + PDF @ Final notice day 21 email # Alert owner Slack @ Thank you payment received # Paid ping Slack Σ Aggregate all overdue # Weekly digest Slack, Mondays

Execution log — the real data at every hop

Simulation of the importable Make scenario sold with this listing. In the real product the connections (Xero, your mailbox, Slack) are yours, the rungs (3 / 10 / 21 days) are plain filter values you can move, and paid invoices stop being chased automatically.