Forecasting an account
The Forecast panel runs an account forward and shows you what it will do. It is a projection, not a posting. Nothing is written, nothing reaches the ledger, and running it changes no balance.
What makes the answer trustworthy is that it is not a separate calculator. The forecast runs the account through the same end-of-day processing the account goes through every night — the same schedules, the same day count, the same business day rules. It just runs it over days that have not happened yet.
What you see
The panel opens already run to the end of the account’s life, because the question it exists to answer is “what does this account do over its life”. The end is the account’s last scheduled event, after business-day rules move it. If that event pays money out, the run continues until the payment settles. A fixed deposit maturing on Sunday 2 May matures on Monday 3 May and pays out on Tuesday 4 May. The panel opens to 4 May. You can change Target Date to any date. If the account has no maturity date — a call deposit, say — the field starts empty and nothing runs until you pick one.
The table shows one projected transaction per row, latest first:
| Column | What it holds |
|---|---|
| Type | The transaction type, as the customer would see it |
| Trading Date | The date the projected transaction is raised |
| Value Date | The date it counts from — see value dating |
| Amount | The projected amount, signed against the account |
| A balance column per position | The running balance after that row |
| System | Marks a row the engine raises rather than a person |
A tax the account will be charged shows as its own row, on the same dates as the transaction it is charged on. Withholding tax on projected interest is one example. VAT on a projected service fee is another.
The bottom row is the Starting balance — the account’s real balance today. Every balance above it is a continuation of that one, so you can read a column downward and see where the account ends up. Use Balance View to choose which position columns appear; the views on offer belong to the account type. See position types.
You can export the projection from the panel as a spreadsheet, CSV or JSON.
Where the forecast starts
The forecast starts from the day after the account’s last processed day, and from today’s real balances. It never replays history.
That distinction matters when you read the table. An account that has already received 1,000 shows the interest that 1,000 will earn, but not the 1,000 again — the deposit is already in the starting balance, and repeating it would double-count the running column.
A payment you have booked with a future value date is not history yet. It settles inside the window and appears as a row. A deposit of 100 value-dated 10 June shows up in a forecast run to 15 June.
An account still being captured forecasts too. Before it is activated there is no history at all, so the forecast opens the account in memory and projects from what it would open with — the answer to “what happens if I activate this?”. A closed, closing or suspended account cannot be forecast, and the panel says so.
There is no limit on how far ahead you can go. A long horizon costs time, because every day between here and the target date is processed one at a time.
What one projected day does
Each day in the window runs in the order money actually moves.
flowchart LR
A["Start of day: instalments and other dated postings fall due"]
B["Collections raised for what is due"]
C["Payments already in flight settle on their value date"]
D["End of day: interest, fees, capitalisation"]
E["Notices reaching expiry pay out"]
A --> B --> C --> D --> E
The order is the reason a day’s rows read sensibly. An instalment falls due before the payment that clears it, and interest for the day accrues on the balance those movements leave behind.
Assuming the repayments
Assumptions tells the forecast what to assume about money coming in. It changes the answer, so choose it deliberately.
The Assumptions menu appears only when your organisation has set some up for this account type. Each entry is a tick box. The ticks your organisation marks as standard are on when the panel opens. Untick one, or tick another, and the forecast re-runs.
If you untick everything, the forecast assumes the customer stops paying. That is the worst case. A fixed deposit offers no assumptions, so its panel shows no menu.
Two examples of what an assumption can be:
| Assumption | What it assumes | Use it for |
|---|---|---|
| Instalments paid | Every instalment is paid in full on its due date | The contractual case |
| Arrears repaid today | The whole arrears balance is paid on the first forecast day, once | A customer who clears what they owe |
Your organisation names and sets these up, so the menu on your account type may differ. Rows an assumption booked carry a small tag with the assumption’s name. A row without a tag comes from the account’s own timetable, not from an assumption.
Take a loan that is 2,500 behind, with three monthly instalments of 1,250 due in the window. The example has no interest, so no day count convention applies.
| You tick | What the forecast shows |
|---|---|
| Nothing | No payments. Arrears grow to 6,250 |
| Instalments paid | Each 1,250 is paid on its due date. Arrears stay at 2,500 |
| Instalments paid and Arrears repaid today | 2,500 on the first forecast day, then each 1,250 on its due date. Arrears end at 0 |
Arranged collections are projected only when you tick Debit orders (or Standing orders, where offered). A loan of 100,000 with an instalment of 1,500 collected by direct debit, with debit orders ticked, shows two rows on the due date: the instalment falling due, and the 1,500 received. A debit order that is already in flight settles once, not twice.
See the repayment schedule for how instalments are set, and how a repayment is recorded for what happens when one actually arrives.
Trying a what-if
Select Add Simulated Entry to put a transaction into the projection that has not happened. Give it a type, an amount and a value date. It appears as a chip above the table, and the forecast re-runs on its own.
A call deposit with nothing in it forecasts nothing. Add a simulated deposit of 100,000 dated on the account’s start date, and the projection fills with the daily interest that balance earns on the account’s own day count convention.
You can date a simulated entry in the past. That answers “what if I had booked this at trade date?” on a deal that has not started yet. The entry lands on the date you gave it, and scheduled work still waits for the account’s start date: a deal starting 1 June with a simulated deposit dated 4 May accrues nothing until 1 June.
A simulated entry is never saved. Remove it with the x on its chip, or leave the panel — either way nothing was recorded.
Forecasting a change before you commit it
Changes staged in Studio are included. Stage a deposit, a rate change or a revised instalment plan, and the forecast projects from the account as it would be once those changes apply — not as it is now.
Studio holds staged changes on the account itself. Everyone who opens the account forecasts from the same staged changes, and they survive closing the tab.
Stage a deposit of 100,000 on an account holding nothing, and the forecast’s starting balance reads 100,000. Run the plain forecast alongside it and the starting balance reads zero, because nothing is committed.
That is what lets you shape a change and see its effect before anyone signs it off. Where a change needs a second pair of eyes, the approver sees the same projected effect — see countersign.
Forecasting a product change on one account
A product’s change set can be forecast before anyone submits it. Select Forecast on an account on the change set, and pick an open account on that product. The panel opens as Draft forecast. See what a product change reaches.
If the change set creates a product by copying another, the new product has no accounts yet. The open accounts on its account type are listed instead. The panel then reads As if on the new product’s name, so you see how an existing account would run under the copy.
If you are drafting a change to account types, select Forecast on an account and choose a type first. The open accounts on that type are listed, whatever their product.
The panel walks the account twice to the same date: once under the rules in force today, once under the change set’s rules. It opens twelve months on from today, with the account type’s usual assumptions ticked. It then shows only where the two walks differ:
- First difference — the first date the two walks part.
- Each balance that ends differently, before and after.
- Each transaction that is in one walk only, or differs in amount or in what posted it.
What posted a payment counts as a difference even when the amount is the same. For example, Staff Personal Loan has no collection rule today, so the forecast assumes each instalment is paid. Alex drafts a debit order collection. Every instalment then reads “assumed paid → collected by debit order”, and the first difference is the first instalment due date.
If either walk stops early, the panel compares the two up to the earlier stop and says so. If the walks agree, the panel reads “This draft does not change this account’s forecast”, with the reach line beside it.
Some rules are not walked. A statement schedule changes no balance, and a rule read only when an account opens cannot change this one. Those appear under Not forecast, as before and after, with who they reach. Nothing in the change set is saved or submitted while you forecast.
Why the forecast matches what the account goes on to do
Because it is the same run. A worked case: 100,000 at 10%, accruing on
ActualActual for the first two days and on Actual360 from the third, after a
convention change dated mid-window. Forecast five days, then let five nights
process. The five projected accruals equal the five booked accruals, to the
cent — including the two either side of the switch. The per-day amounts for those
conventions are in day count conventions.
The same holds for money leaving. An account holding 1,000 with notice given on 400 over 32 days shows the 400 paying out three days after expiry — the settlement lead time on the rail, not the expiry date itself. Nothing special was done to make the notice appear: the forecast runs the expiry step the nightly run runs. See notice periods and business day conventions.
Capability switches move both sides together. Switch notice periods off and the forecast projects no payout, because the nightly run would instruct none. A forecast can never show you work the engine will not do.
What would make the forecast and reality differ
The engine is the same. The inputs are what can drift.
| Cause | What to do about it |
|---|---|
| Activity nobody told it about — a deposit, a withdrawal, an early settlement | The forecast assumes the account is left alone. Re-run it after anything moves |
| Rates that move | Each projected day is priced at the rate in force as of that day, from today’s rate card. A rate agreed tomorrow was not knowable today — see changing a rate |
| The ticked assumptions | “Instalments paid” is an assumption, not a fact. An account in arrears will not match it |
| Simulated entries | They answer a what-if. A forecast carrying them is not a prediction |
| A capability switched on or off between now and then | Both sides move together, but they move on the day of the switch, not retrospectively |
There is also work the nightly run does that the forecast does not project. The forecast covers the account’s own dated timetable — scheduled postings, interest, instalments and their collections, payments settling, notices expiring, and withholding tax. It does not project arrears classification and default, provisioning, write-off of small residues, prescription, expiry of a settlement quote, or repricing driven by a card tier. Those still run at night. If one of them is material to your answer, read the forecast as the account’s timetable rather than as the whole night.
What your organisation configures
- Whether the panel appears at all. Account forecasting is a licensable capability — see switching features on and off.
- Who may forecast a product change. It is a separate permission from running the plain forecast.
- The assumptions each account type offers. Their names, which are ticked when the panel opens, and what each one books.
- Which other capabilities are on. Each one the nightly run performs is projected only while it is enabled, and stops being projected the moment it is not.
- The balance views on each account type. They decide which position columns the panel offers and which one it opens on.
- Whether the account type carries a maturity date. If it does, the panel opens run to the last scheduled event and its settlement. Without one, you choose the horizon yourself.
- The account type’s schedules, transaction types, day count convention and pricing. The forecast walks whatever they say — see how interest is calculated and compounding and capitalisation.
- The settlement lead time on each rail. It decides how long after a due date projected money actually lands — see how a payment picks its rail.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.