Simulation
A demonstration tenant with a small organisation already in it, operating entities, staff, customers and accounts, and a simulator that plays out each trading day inside the day-end, so the real day-end has something to work on.
An empty system tells you very little.
Banking software tends to be shown off a demo database where every account was opened that morning. It looks tidy, and it can't show you the things you actually want to see: what an account looks like after a year of accruals, what happens when a debit order bounces, or what suspense looks like at the end of the month when nobody has got round to clearing it. We've spent twenty-five years building software for lending and deposit books, and the interesting part of a bank is always the second month, so we built the simulation to get there.
A simulation tenant comes with history. We can open its book up to two years back and walk it forward one trading day at a time until it reaches today, through the same day-end a live bank runs. The screens on this site were captured from one after a year of that.
You pick a template, and the simulation fills it in.
On the Provision Tenant page you choose a template, a retail bank, a microlender or a structured-finance book, and tick Simulation data. You say how many customers you want beside the one fixed demo customer, nine if you don't say, and which of the template's account types to open for them. What comes out is a small organisation that hangs together: the customers bank with a branch, the branch belongs to an operating entity, the operating entity has bank accounts and books of its own, and someone on the staff has work waiting in their queue.
If the template can't support a step, a microlender with no companies to seed, say, the whole step is skipped and the result screen tells you why. It never claims to have seeded something it didn't. The tenant then carries a SIMULATION badge in its header, so nobody mistakes it for the real thing.
Operating entities and branches
Each with bank accounts in its currency and its own books, so the trial balance ties per legal entity from the first day.
Staff, teams and tills
Organisational units, collection teams and cashier tills, so the work the day-end raises has somewhere to go.
Counterparties
People, companies, trusts and partnerships, with identity documents, tax residencies and compliance clearances, and a few non-resident holders to keep the compliance sweeps busy.
Accounts, cards and a merchant
Accounts of the types you chose, with limits, approved beneficiaries and payer accounts for debit orders, cards from a simulated card processor, and a merchant for acquiring. The retail template adds accounts set up to reach in duplum and the statutory default process, because those are the first things a South African credit manager asks about.
Swipe sideways to follow the whole diagram.
The simulator plays the trading day, and the day-end stays real.
In a real bank most of this happens during the day. The rate file arrives in the morning, the card processor and the acquirer send their files when they're ready, the statement comes in, a clerk releases the payment files and somebody else approves them, and the debit orders that bounced trickle back from the clearing house. A simulation tenant has no during the day, because time only moves when a day-end runs, so we fold the day's outside events into the day-end itself. Each simulation step runs just before the real step that would pick up its file, and plays the other party: the simulator stands in for the rate provider, the processor or the bank, and delivers what they would have delivered. The bank's own steps then fetch it, import it and post it exactly as they would in production. So the simulation steps are the only part that wouldn't be in a live day-end, and everything they hand over goes through the real import, the real matching and the real postings.
| Step | What the simulator plays, in place of the day | What the bank does with it |
|---|---|---|
| Exchange rates | Delivers the day's rate file, with each rate moved by up to one percent from yesterday's. | Imports it, marks the rates final and revalues every foreign-currency position, so FX profit and loss moves every day. If you upload a real file for that date, yours wins. |
| Card clearing | Writes the card processor's clearing file for the day's spend. | Fetches, imports and posts each line, releases holds at their expiry and renews cards before they lapse. A simulated card can be given a two-month life, so a demonstration sees one renewed. |
| Card disputes | Moves each open dispute on a stage, as the card schemes would. | Watches the deadlines, so a dispute moved today is watched from tomorrow. |
| Merchant acquiring | Sends the acquiring processor's daily feed. | Imports and posts it, withholds merchant reserves and pays merchants their available settlement balances. |
| Bank statements | Writes one statement for every bank account an operating entity owns. | Matches the lines, posts the customer deposits and parks what nobody recognises to suspense. The next section has the detail. |
| Payment release | Plays two clerks: one asks for the release and the other approves it. | Releases the files through the same four-eyes control your people use. Both names read as the simulator, never as one of yours. |
| Returns | Sends back the debits on payer accounts you marked, with the reason you chose. | Collects the return file and reverses the payments. The file is recorded as Simulated. |
| Email and SMS | Records every message instead of sending it. | Sends statements and letters as normal. They land in the Simulator Outbox, where each opens as the customer would have seen it. |
Between those, the ordinary day-end runs as it would anywhere: interest and fees accrue, debtors are re-aged, compliance thresholds are swept, standing orders and debit orders are raised, approved and submitted, and the books are snapshot at each day's close.
The bank statement is built to give reconciliation something to do.
Every day, for every bank account an operating entity owns, the simulator writes the statement the bank would have sent. It opens on yesterday's closing balance, or on a float of 100,000 if the account is new. It carries a line for every debit and credit order we submitted that is due to clear, with our own reference on it, so matching pairs them off by reference the way it should. It adds one or two customer deposits, which are matched to a customer's account and posted. It adds exactly one line nobody recognises, and that goes where an unknown receipt goes in real life, to the operating entity's suspense account for that currency. And it adds one top-up or withdrawal, the operating entity funding its own account, which is left unmatched on purpose because in real life somebody always forgets to tell the reconciliation team. The closing balance is the opening plus the lines, to the cent, because a statement that doesn't add up is refused at import.
Then the ordinary steps carry on. Expected payments that never turned up go stale, suspense cases age and fire their threshold actions, and at month end the suspense position is recorded. So after a month there is a reconciliation screen with real breaks on it and a suspense account with a history, which is the part of a bank nobody demos and everybody has to run.
Simulation can't be switched on in a live system.
A production host refuses it whatever the setting says, and everything the simulator touches is labelled. A rehearsed return file is recorded as Simulated, so months later nobody mistakes it for one a bank sent. A simulated rate file is labelled as delivered by a simulation, each simulated SMS is badged in the client's history, and a simulated payment release names the simulator rather than a person.
It also proves a little less than it might seem to. The files are built to each scheme's standard and the responses are read the way a real channel's would be, but no payment rail is live yet, and going live on one needs a connection through a bank and that scheme's own certification. The standards page says where each one stands.
Ask to evaluate and we'll walk you through a simulation tenant on the template closest to your book, with a year of day-ends behind it. If you want to see a debit order bounce, we mark the payer's account and run a day-end, and the return file comes in with the payment reversed.