Plan for clients paying late
Treasury's What if section: look 30, 60 or 90 days ahead, make receivables late or missing, change what bills cost, and see the first short day, the bills it touches and what the figure is built from.
On Treasury, right under Next 30 days, a folded section asks What if clients pay late? Open it to see what late or missing receivables, and a change in what bills cost, would do to the operating wallet over the next 30, 60 or 90 days: the first day the balance would run short, the bills due while it is, advice in words, what moves it most, and what the figure is built from. Every member of the workspace can use it, viewers included. It works the same on Arc testnet and on Arc mainnet.
Its line under the title says "Nothing here is paid; a scenario is kept only when you save it." It is worked out in your browser from what Treasury already shows: changing a setting asks the server nothing, writes nothing to the ledger and reaches no payment and no decision of the agent. Only Save as a version keeps a scenario, as below. Safe to spend today, the agent and every check before a payment still count no receivable, whatever you set here.
What it starts from
The section counts what Next 30 days counts, by the same rules, over up to 90 days:
- Cash is the operating wallet's USDC and the USYC reserve's, which comes back to the wallet within seconds. It is the only money counted as held. No bank balance is counted.
- Bills you owe that are still open, each on its day: a scheduled bill on the day it is scheduled for, any other on its due day, or today when it is overdue. A bill held for a person counts too.
- Open milestones, today: a milestone has no payment day, so it is counted as if paid now, unless its USDC is locked in escrow.
- Recurring payments not billed yet: the periods of each running recurring payment that have no bill yet, each on its due day (one already due, today). A period's bill is created up to 7 days before its due day, so over 60 or 90 days most periods are not billed yet. Each is marked "recurring, not billed yet". This is the one way the section differs from Next 30 days, which counts only bills already created.
- Receivables: your open receivables in USDC, already invoiced, a deal's released lines among them; a part-paid one for what is still owed, since what arrived is in the wallet already. Each adds to the balance only on the day it arrives in that case: if clients pay on time, on its due day, or today when it is overdue.
- Deals not invoiced yet are not counted. A deal's lines not released yet are named under What this is built from, with what they come to, and add to no balance: a line counts as a receivable once it is released. See Turn a signed deal into a collection schedule.
- EURC bills and receivables are paid from and into the EURC balance. They are listed as left out, never converted and never added to a USDC figure.
Set a scenario
- Look ahead: 30, 60 or 90 days. The section opens on 60.
- Clients pay late by (days): from 0 to 90; it opens on 14. A receivable is late from its due day, or from today when it is already overdue. One that would arrive after the days you look ahead does not arrive within them.
- Change in bill costs (%): from -50 to 100. 10 is 10% more, -10 is 10% less. It changes bills and recurring payments; milestones keep their amounts, since they are agreed in USDC.
- The change applies to: Every bill, or Bills written in another currency, the bills shadow mode took in your business's own currency and worked out in USDC at a rate. That choice says how many such bills fall in the days you look ahead.
- Receivables due in the next 60 days (or 30, or 90) lists each receivable in those days, with its amount and due day. Set each to Late, On time or Never arrives. Each is Late until you change it.
These are settings you choose, not predictions: nothing is weighted by how likely it is.
Read the result
If clients pay on time and In this scenario sit side by side. The first assumes every client pays on its due day, and says so under its name: "Each receivable on its due day, an overdue one today. Next 30 days counts none." So it can show no short day where Next 30 days, which counts no receivable until it arrives, says the wallet runs short. To count none here too, set every receivable to Never arrives. Each case says "Runs short on" the first day the balance falls below zero, or "Never short in the next 60 days"; the lowest balance and its day; and "Below the cushion from" the first day the balance falls under the cushion the treasury keeps, 15% of what leaves in the 7 days from that day, when that comes before any short day. Under In this scenario is what you changed: how many receivables are late, and how many of those land after the days you look ahead; how many never arrive; and how much more or less the bills cost.
Below them, one line gives the cash today, says "No bank balance is counted.", gives the receivables due in the days you look ahead and how much of them arrives within those days in this scenario, and says "Deals not invoiced yet are not counted."
- The chart draws the balance every day, if clients pay on time (grey, dashed) and in this scenario (solid), with the first short day marked. Point at a day to read both balances. Day by day opens the same figures as a table: today, then each day either balance changes.
- Due while the balance is short lists the bills, recurring payments and milestones that leave on a day the balance in this scenario is below zero, with their day and amount.
- What could help, "advice only: nothing here changes a payment", shows only when the scenario runs short, with at most three points:
- how much more USDC the wallet would need, by the first short day, to pay every bill on its day;
- a bill scheduled for a day before its due day and no later than the short day, whose due day comes after it, that would help if paid on its due day instead. The section works the scenario out again with the bill moved and names it only when the balance then runs short later or by less, saying which: a later short day, less USDC needed, or no short day within the days you look ahead. It ends "Any early-payment discount it was scheduled for is lost." Of several such bills, it names the one that leaves the least to find;
- of the receivables that would have arrived by the short day but do not in this scenario, the largest.
- What moves it most names, by the first short day (or by the lowest day when the balance never runs short), the three sources that pull the balance down most: a payee, with its bills, recurring payments and milestones leaving by then together (a milestone counts for its contractor); a client whose receivables this scenario makes late past that day or drops, all of them together, with the day the last of them arrives, how many arrive after the days you look ahead and how many never do; and a rise in bill costs, as one source.
A short day is not an instruction to do anything with your money. Nothing in the section pays, schedules or moves money, and none of its advice is a link to do so: what to pay, chase or move stays your decision, made where you make it today.
What this is built from
What this is built from says how much of the picture is known. Its badge, "Bills on record in 5 of 9 weeks" in the picture, counts the weeks from today (the last one may be shorter) in which a bill or a recurring payment leaves. A bill far ahead fills only its own week. A bill or recurring payment that was due before today, held or scheduled ones included, leaves today but fills no week: it says nothing about the bills of the days ahead. When fewer than half the weeks have one, the badge is amber. Bills nobody has added yet are not counted, so the weeks with none on record may look better than they will be, and the section says so under the list.
The list gives:
- the bills: how many, their total and the latest due day (a scheduled bill's own due day, not the day it is scheduled for);
- the recurring payments not billed yet: how many, their total, and from how many schedules. When they could not be read, it says "Recurring payments could not be read, so none is counted.";
- the open milestones, counted today;
- the receivables: how many, their total, and how many come from clients who have paid before;
- for each such client, its record: how many receivables it paid on time and how many late, and how many days late on average. A payment is on time when it arrived on or before its due day (UTC), as the agent counts it before it reminds a client to pay. "Client records are counts, not a prediction.";
- what is left out: EURC bills and receivables;
- the deal lines not invoiced yet, due within the days you look ahead: how many and what they come to, in USDC and in any other currency apart, "Planned from deals, not invoiced yet and in no balance".
The section ends with "A what-if from the bills and receivables on record, not a forecast."
Exchange rates, and saving a scenario
When an open bill was written in another currency, Exchange rates lists each such currency, with the latest reference rate recorded beside it, its time and its age, and Use the latest rate. Leave a currency empty to keep each bill at the rate it was converted at, or type a rate to see that currency's bills at it. With a reporting currency set, the section also gives the cash today and the scenario's lowest balance in it. An owner or admin keeps a scenario under Saved scenarios with Save as a version; saving again makes the next version, and Open sets the levers back to one. See Work in your own currency.
When something changes
Treasury reads its rows again every 20 seconds, and the section works out its figures again from them each time, keeping what you set: a bill whose due day moves moves on the chart, a new bill is counted, and a receivable that is paid or removed leaves the list. Closing the page forgets the scenario; nothing is kept.
Not in this version: counting a deal line before it is released, a lateness of its own for each client, and saving or sharing a scenario. Telegram's /today and Slack's /vestiarion today still answer for the next 30 days.