Automated FundThrough Payment Aging Report
Every Monday, WebRun opens FundThrough, reads payment aging across all factored invoices, and writes a structured aging report to Google Sheets broken into current, 30-day, 60-day, and 90-plus-day buckets, then sends a short Telegram summary with the totals so you spot recourse risk at a glance.
How do I automatically generate a payment aging report for my factored invoices?
WebRun opens FundThrough every Monday, reads the payment aging for all factored invoices, and writes a structured Google Sheets report bucketed into current, 30, 60, and 90-plus-day aging groups. A Telegram summary then delivers the totals and recourse-risk flags to your finance channel before the week begins.
- Recourse risk is visible every Monday before it becomes a problem
- Four-bucket aging report replaces manual invoice tracking
- Telegram summary puts key totals in your pocket in seconds
Built for CFOs · accounts receivable managers · invoice factoring clients · small business finance teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.fundthrough.comin a real browser with your saved login - no setup, no API keys. -
1
FundThrough - read payment aging for all factored invoices
fundthrough.com
WebRun opens FundThrough to read payment aging for all factored invoices. - Open FundThrough and navigate to the funded invoices view
- Capture each invoice with its debtor, client, original amount, funded date, and days outstanding
- Group invoices into aging buckets: current (under 30 days), 30 to 60 days, 60 to 90 days, and 90-plus days
- Flag any invoice approaching the recourse window defined in your factoring agreement
Done when Every funded invoice is categorized into an aging bucket with recourse risk noted.
-
2
Google Sheets - write the structured aging report by bucket
google.com
WebRun opens Google Sheets to write the structured aging report by bucket. - Open the payment aging tracking sheet
- Write each invoice row into its corresponding aging-bucket tab with all captured fields
- Update the summary totals row at the top of each bucket tab
- Timestamp the report so the team knows exactly when the data was pulled
Done when The Google Sheet has an up-to-date aging report across all four buckets with fresh timestamps.
-
3
Telegram - send a summary of totals and risk flags
telegram.org
WebRun opens Telegram to send a summary of totals and risk flags. - Send a short Telegram message to the finance channel with the total outstanding in each aging bucket
- Call out any invoices flagged as approaching the recourse window
- Include the date of the report and a link to the full Google Sheet
Done when The Telegram channel has this week's aging summary with recourse risk highlighted.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
How does it know my recourse window?
You tell WebRun the recourse threshold in days during setup (commonly 90 days). It then flags any invoice within 14 days of that limit so you have time to act.
Can it chase debtors when an invoice ages past a threshold?
No. The report is read-only. Any debtor outreach must be initiated by your team after reviewing the aging report.
Will the sheet overwrite last week's data?
By default, WebRun appends a date-stamped snapshot each Monday so you retain a history of how aging shifts week over week.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.