Batch clearing — simulated scheme
Simulated schemeACH-style batch payments cleared by this module's own deterministic settlement engine. An entry that passes validation posts immediately as a balanced pair — the customer account is debited and an internal scheme-settlement suspense account is credited — and the payment sits in pending settlement until its configured settlement lag elapses.
SIMULATED clearing scheme — this module's own settlement engine, not a real scheme connection
Batch (ACH-style) payments in this module clear through an INTERNAL SIMULATION of a clearing scheme, not through a real one. There is no connection to ACH, Bacs, SEPA, FedACH or any other scheme, no file is exchanged with any counterparty, and nothing recorded here has any effect outside this database. The adapter is this module's own deterministic settlement engine: an outbound entry is validated and immediately posted as a balanced pair — debiting the customer account and crediting an internal scheme-settlement suspense account — and is then marked pending settlement until the configured settlement lag elapses, at which point the scheduled settlement job settles it or, at the configured simulated return rate, returns it with an R-code style reason. Every batch record stores the adapter identifier and a simulated flag so a stored record can never be mistaken for real scheme traffic.
Exactly what the simulation does
- An outbound entry passes exactly the same pre-release validation gate as any other payment: required fields, positive whole-cent amount, available funds, per-customer limits, payee state, sanctions screening and high-value step-up.
- On passing, it posts IMMEDIATELY as a balanced pair — DEBIT the customer account, CREDIT the internal scheme-settlement suspense account — and the payment moves to pending settlement.
- Each entry carries the settlement lag configured at the moment its batch was built, and the exact instant its simulated settlement becomes due.
- When that instant passes, the scheduled settlement job settles the entry by moving the suspense balance to the internal scheme-clearing position with a balanced pair; at the configured simulated return rate it is instead returned with an R-code style reason and reversed by an equal-and-opposite compensating posting, which also opens a case in the exceptions queue.
- No file, message or instruction is sent anywhere. Nothing outside this database is affected at any point.
adapter: internal-simulated-clearing.v1 · simulated: true · no real scheme connection exists
Settlement suspense balance
USD 0.00
CTRL-SCHEME-001
Entries pending settlement
0
USD 0.00 of value, 0 already due
Settlement lag
1 h
Module default — nothing configured
Simulated return rate
0‰
0‰ — no entry is ever returned by the simulation
Build a batch
Every entry passes exactly the same pre-release validation gate as any other payment in this module. Entries that pass post immediately; entries that fail are recorded as rejected or held payments with their named reason codes and post nothing. Nothing is transmitted to any real scheme at any point.
Batches
Not polling: nothing on screen can change status any more. Showing state as of .
No batch has been built yet. Build one above to see it here with its identifier, item count, total value and status.
Sample book disclosure: the customer accounts, staff users and sanctions watchlist in this environment are seeded demonstration data created by this module — there is no connection to a real core banking system, payment scheme or sanctions feed. Batch (ACH-style) clearing and high-value wire settlement both run through this module's own SIMULATED settlement engine, never a real scheme or wire network.