Standards
A summary of what the engine builds to the international standards and to the laws of the countries we have operated in, and where something is not built, we say so.
A standard here is a mechanism, not a badge.
Each standard the engine touches has a row in a register kept beside the code: what it covers, where it lives, and the decision record behind it. A test pins the claimed codes and mappings so the register cannot drift from the build. What follows is that register summarised by family, and a deliberate departure from a standard is recorded with its reason. We know the international standards and the laws of the countries we have operated in, but we don't know yours, and that is what a partner brings.
No payment rail is live yet. For each scheme below, LedgerTM builds the files and reads the responses, and in the demonstration tenants a payment settles by simulation. Going live on a rail needs a connection through a bank and that scheme's own certification, which is part of an implementation.
ISO 4217 · ISO 3166-1 · ITU-T E.164
Source: ISO 4217 · ISO 3166 · ITU-T E.164
Every currency is its ISO 4217 code with the numeric code and minor unit carried beside it, and the minor units are pinned by a test. Every country is its ISO 3166-1 alpha-2 code: the full set ships in code for document issue, while the countries a tenant transacts in and owes tax in are its own configuration. Phone numbers canonicalise to E.164 on entry, with a locally typed number converted against the account's country.
ISO 20022 external code sets · camt.053 · SWIFT MT940 · Bank Transaction Codes
Source: ISO 20022 external code sets
A proxy address, a charge bearer and a service level are modelled as the ISO 20022 code sets, so a PayShap ShapID and a PIX email proxy read as one concept and a rail declares who bears its charges in the wire's own vocabulary. A statement we import carries the bank's own statement identifier from camt.053 or MT940. Every account and transaction type carries an ISO bank transaction code, which drives the camt.053 statement export and the next-payment view; call deposits map to the notice-deposit family because the code list has no call-deposit family, and that choice is written down. The remittance reference a payment carries is modelled on RemittanceInformation, ready for the rail adapters.
Where it stops: No outbound wire message reaches a bank yet. The codes are modelled and asserted, the SEPA, UK and ACH file generators are in build, and a live submission waits on a sponsor bank relationship.
ISO 20022 InterestComputationMethod · ISDA 30/360 · business-day conventions
Source: ISO 20022 external code sets · ISDA
A tenant prices interest on five named day-count conventions from the ISO 20022 code set, Act/360, Act/365 Fixed, 30/360, Act/Act ISDA and 30E/360, and adds another as a settings row. Due dates roll on Following, Modified Following or Preceding against one or more holiday calendars, and an account with a convention must name a calendar. Accrual and maturity schedules stay unadjusted by design.
Where it stops: Inside February, 30/360 accrues to date by skipping the 31st and catching up on the 28th or 29th. That matches the bond basis over any full month or year but differs from ISDA within the month. It reproduces the engine's twenty-five-year behaviour and is recorded as a deliberate deviation.
Impairment provisioning runs on a configured matrix, days past due, coverage percentage, stage and cure probation per tenant, recomputed at day-end, with individually assessed provisions and stage pins behind four-eyes. Writing off a credit-impaired loan derecognises it against its provision and moves the surviving legal claim to a salvage account, so the balance sheet is clean while the claim stays collectable, and recoveries are income when received. A closing account's rounding residue is swept by a configured tolerance. Negative interest posts to its own income and expense accounts rather than netting against positive interest. A cost centre move restates balances from its effective date and leaves earned income where it was earned, following IFRS 8 segment practice by analogy.
Where it stops: Interest on a credit-impaired loan is suspended in full and released on cure, rather than unwound on the net basis IFRS 9 describes. This understates impaired-stage income and is recorded as a deviation.
Act 34 of 2005 §§4, 40, 86, 103, 108–110, 125, 129, 130 · Regulation 35 · Prescription Act 68 of 1969
Source: National Credit Act 34 of 2005
Each agreement is classified as regulated or not, and every charge on a regulated account carries a cost-of-credit category, so statements summarise the Regulation 35 buckets and the in duplum cap counts the right amounts; an uncategorised fee is refused. Statements render the regulated content, issue on the statutory interval, and keep proof of despatch. Early settlement quotes apply the statutory cap as a configured expression: no charge on small and intermediate agreements, three months' interest on large ones. A default notice becomes eligible twenty business days after the oldest unpaid due, counted on the tenant's calendar, and enforcement ten business days after the notice was despatched; a cured account lapses the notice. Debt review is a hold on the customer that stops collection activity and is fully audited. A written-off claim prescribes three years after the last payment, acknowledgement or part-payment restarts the clock, and a prescribed claim refuses further fees. An entity lending under the Act must hold a current credit provider registration on the trading date.
Where it stops: Registration is recorded and enforced, not verified with the regulator. Despatch is proven by email; no registered-mail channel exists yet. The default notice template is a draft. A South African lawyer reviews it before any tenant uses it in production.
FICA 38 of 2001 · SARS IT3(b) · OECD Model Tax Convention Article 11 · CODI · SARB maturity ladders · SACRRA
Source: FIC Act 38 of 2001 · SARS
Customer due diligence is a clearance per legal person with configured requirements, evidence and expiry. An account does not activate until every owning party is cleared, cash movements over a threshold open a threshold report at day-end, and suspicion reports sit behind a restricted permission. Interest income is returned bi-annually on every account holder, resident or not, and each holder's tax certificate is the sum of the two periods so it cannot disagree with the return. Withholding on interest paid abroad applies the statutory rate with treaty rates substituted per residency country when the declared evidence is held. Deposit insurance cover is computed per depositor per bank from the owning roles, so a joint deposit is apportioned. Maturity ladders for liquidity returns are configured time-band profiles frozen into each period's cut.
Where it stops: Screening against a provider is not built; verification rests on clerk-recorded evidence. Regulatory files are produced and uploaded by hand, and no regulator has yet accepted one from us. The credit bureau layout is licensed and not held, so the bureau extract is our own field list: twenty-one columns fixed in code, with only the bureau status codes mapped through settings. Rendering the licensed layout is a follow-up for the first customer who holds the licence.
PayShap · DebiCheck · Real Time Clearing · PayInc universal branch codes · scheme participant identity
Source: BankservAfrica · Payments Association of South Africa
Payments route across ordered rails by speed, amount limit and addressing: PayShap by proxy, in real time and irrevocable; Real Time Clearing same-day by account number; batch EFT otherwise. A debit-order mandate is a collection authority keyed on the agreement it collects, with the authenticated and registered streams as one lifecycle, re-authentication on a material amendment, and a gate at activation and at each collection. The identity a scheme issued the submitting party is a configured slot per channel, entity and sponsoring bank, so onboarding a bank is configuration.
Where it stops: Scheme responses are simulated until a sponsor bank relationship exists: a demonstration settles, a production payment does not leave the building. Universal branch codes are an operator-maintained registry, not yet built.
SEPA Credit Transfer and Direct Debit · ISO 20022 pain.001 / pain.008 · IBAN and BIC (ISO 13616 / 9362) · Bacs Standard 18 · Faster Payments
Source: European Payments Council · ISO 20022 · Bacs
SEPA credit transfer and SEPA direct debit are routable channels alongside Bacs and Faster Payments, and a payment picks its rail from the same ordered ladder the South African schemes use. An IBAN is validated on entry with the ISO 13616 mod-97 check and a UK sort code and account number with their own rules, so a beneficiary in Frankfurt and one in Leeds sit on one external-account model. The pain.001 and pain.008 message layouts are written against the ISO 20022 definitions and the EPC implementation guidelines, with the group header, payment information block and mandate fields a direct debit needs. The scheme identity a file goes out under, the SEPA creditor identifier or a Bacs service user number, is a configured row per channel, entity and sponsoring bank.
Where it stops: The SEPA, Bacs and Faster Payments file generators are in build now: pain.001 and pain.008 validated against the ISO schemas, Standard 18 with a balancing contra, rejections and unpaids read back through the same return leg the South African schemes use. Until a sponsoring bank tests the files, submission stays simulated. No European regulation is modelled: PSD2, GDPR and the AML directives are the partner's and the customer's to bring.
ACH is a routable channel with Fedwire beside it. A US routing number is validated with the ABA check digit, and the NACHA 94-character record layout is written down to the position, including the fifteen-digit trace number whose leading eight are the originating institution. That is the infrastructure a US rail adapter starts from.
Where it stops: The NACHA file generator is in build now: entry hash, batch and file totals, block padding, and returns read back by R-code. The rest is not built for the US market: no FedNow or RTP channel, no US GAAP treatment and no state lending licence model, and because we do not host it, a SOC 2 report would come from whoever runs it. If a North American prospect asks, the honest answer is that the payment plumbing is a head start and everything else is a project.
Segregation of duties · W3C WebAuthn Level 2 · RFC 8292 VAPID
Source: W3C WebAuthn · RFC 8292
Whoever contributed to or submitted a change is barred from approving it, read from the immutable event and with no tenant opt-out. An approver on a phone enrols a passkey and signs each decision with it; the signature is stored on the event and can be verified again without the engine. Push notifications carry only a count and a sign-in link, never the content of what is waiting.
A compliance question has a row and a decision record behind it, and we show the full register to prospects under evaluation.