This is the decision record as it was written, grilled and shipped. It’s copied from our repository unedited, apart from customer, partner and bank names, which read [redacted]. It was written for the people and agents building the product, so expect internal shorthand, and the mistakes are left in.
ADR-837: Cards and Authorisation: the current account, the overdraft facility and the unconditional clearing post
Status: Shipped — 2026-10-03
Context
The Problem
The card series so far funds a card from a call deposit. ADR-836’s oracle walks the funding rule and places a hold on the first account whose available covers the tap, and its clearing step posts the purchase unconditionally. Three things a bank sells with a debit card are missing:
- A current account. The retail package has none.
CorporateCurrentAccountexists in the corporate package with deposit, withdrawal, interest and fees, and nothing in the retail vocabulary is the transactional account a card draws on. - An overdraft. An agreed limit below zero, priced and reviewed. Nothing in the aggregate
refuses a negative balance; a withdrawal is refused by the operation’s guards
(
availabilityGuard: Current > 0on the screen,guard: Current >= $amountat execution), so the aggregate can carry an overdraft today and no type lets it. The oracle’s available (ADR-836 D4) says “a facility’s available joins that sum with the current account ADR” and reads none. - The unarranged overdraft. The clearing line posts past the guard because the bank has already paid the scheme (ADR-836 D7). A call deposit can therefore go below zero, and nothing prices that, shows it, or counts it as credit.
What Already Exists
Facility(LedgerTM.Limits): per counterparty, currency and facility type;Amount,Utilisation,Reserved,Available, freeze;Reserverefuses past available,SetUsagerecords whatever posted (ADR-794).GrantFacilityCommandand the person’s facilities panel.limitIntegrationson an account type (ADR-050 §2): a position wired to the counterparty’s credit limit and to a facility of a named type.UpdateLimitsOnPositionChangedHandlerturns a positive delta on the wired position into usage, a negative one into release — the loan reading, where the wired position is an asset that grows when money goes out.- The two guards on an operation:
availabilityGuarddecides whether the button shows,guardruns at execution; both evaluate onAccountGuardContextBuilder’s bag of positions (bound to available after claims), properties, status, rates and prices. - The day-walk context (
AccountValuation.BuildContext): positions bound to ledger,rate,price,daysInYear,min,max, the ternary. ExternalSourceDispatcherruns a system posting through the type’s operation and evaluates that operation’sguardonly;availabilityGuardis a screen concern (ADR-251 D3).regulatoryRegimeon a type demands a cost-of-credit category on every transaction type (ADR-278), and the NCA statement sweep issues statements for NCA accounts (ADR-279).
Scope
This ADR covers:
CurrentAccountas a retail account type, configured.- The overdraft as a facility wired below zero, and the guards and the oracle reading it.
- The clearing post past the limit, and what the account then shows and charges.
- Debit interest, excess interest and the daily excess fee as type configuration.
- The sample data and the demo: the card funds from the current account first.
Out of scope: collections routing of accounts in excess (the day-end ageing input; a later ADR), a facility per account rather than per customer, facility review and expiry dates, a per-item honouring fee at posting time, the revolving credit card (its own ADR), statements beyond what the NCA sweep already issues, and the corporate package’s current account.
Decisions
1. CurrentAccount is a retail-package account type; the corporate row stays
The retail package gains CurrentAccount: liability nature, positions Current, Accrued
and DebitAccrued, the external integrations and the required properties a call deposit
carries (servicingUnit, taxReportingRegime, interestPayment) plus the two card
integrations (ADR-836), one holder role and regulatoryRegime. The
standing-order integration names a workflow that debits Current under the withdraw guard: a
third-party collection presented against the account is honoured into the overdraft and
refused past it. The debit-order integration stays the call deposit’s inbound credit. It is shaped on CorporateCurrentAccount, not shared with it.
The proposal says “one CurrentAccount type, promoted from the corporate package to the
shared vocabulary”. There is no shared vocabulary beneath the packages: each package is
self-contained and the same row may appear in several (tenant-package model, 789 D1), and an
account type’s key is a stored identity that is never renamed (CLAUDE.md §Critical Rules).
So the proposal’s intent — one shape — holds, and its mechanism changes: two package rows, one
shape. The retail row speaks the retail package’s transaction library (CashDeposit,
CashWithdrawal, TransferIn, TransferOut, InterestCapitalised); the corporate row’s
names (Deposit, Withdrawal, InterestCapitalized) differ and stay, so no test compares
the two by name. “One shape” is the positions Current and Accrued and the operations a
clerk sees. The corporate row keeps its name and gains nothing here. A holder account role
joins the retail role vocabulary: a current account has a holder, not an investor.
2. The overdraft is a facility wired below zero
The overdraft is a Facility of type Overdraft (a new facility-type lookup value) on the
customer, in the account’s currency, wired to Current through limitIntegrations. The
customer’s credit limit may be wired to the same position with the same direction, so an
overdraft consumes the overall exposure the bank has agreed for the customer; the retail
template wires the facility only, because a wired credit limit refuses every payout into the
overdraft for a customer who holds none (CREDIT_LIMIT_REQUIRED_FOR_PAYOUT), and a retail
current account holder is not a borrower. A tenant that grants credit limits to its depositors
adds the wire.
A loan’s wired position is an asset that rises when money goes out. A current account’s
Current is a liability that falls below zero. FacilityIntegration and
CreditLimitIntegration each gain direction: Raise (the default; every existing wire)
or BelowZero. Under BelowZero, the account’s utilisation is the negative part of the
position, and a movement’s effect on the limit is the change in that negative part:
| Current before | Current after | utilisation before | after | sent to the limit |
|---|---|---|---|---|
| 4 200 | −800 | 0 | 800 | usage set to 800 |
| −800 | −2 300 | 800 | 2 300 | usage set to 2 300 |
| −2 300 | 1 000 | 2 300 | 0 | usage set to 0 |
| 4 200 | 3 000 | 0 | 0 | usage set to 0, nothing emitted |
Under BelowZero the handler sends the position’s negative part — max(0, −NewBalance) — as
the account’s absolute usage, and the facility works out the change against what it has
recorded for that account (SetUsageTo). Setting rather than adding repeats safely and
corrects itself: a facility granted to an account already at −800 reads 800 at the next
movement, and the phantom usage a cancelled forward-dated debit leaves behind clears on the
next one. A loan’s Raise wire keeps today’s delta reading. The gates’ asked amount
(LimitExposure.Asked, ADR-794 D2) gains the same reading: under BelowZero the operation asks
for the growth of the negative part across all its lines, and the balance and every credit
net against the lowering lines in order so the ask lands on the lines that cross zero — a
1 000 withdrawal from a 4 200 balance asks for nothing, a 5 000 withdrawal asks for 800, and
the refusal names the 800 of overdraft it needed, not the 5 000 typed. A payout past zero with
no facility is refused as a missing facility, as a loan’s is. An owner change of an account at
−800 asks 800 of the new owner’s overdraft, because usage moves with the account (ADR-794 D12). The payout gate’s “draws on a wired position” test and both of its request-time
checks read the direction too; today they read delta > 0, which is never true of a
withdrawal. A payout operation carries the availability guard only, so the gate is the refusal
a clerk sees and the screen agrees with it (ADR-794 D10).
3. The guards read the facility
Three symbols join the guard bag, bound by Accounts for every type that wires a facility
BelowZero, and bound to zero otherwise:
| Symbol | Meaning |
|---|---|
FacilityLimit |
what this account may draw below zero: the facility’s amount less the usage of the customer’s other accounts on it, each clamped at zero and the whole capped at the amount; 0 with no facility or a frozen one. The facility is the account owner’s; a joint holder’s overdraft never lends |
FacilityAvailable |
FacilityLimit less the facility’s reservations; the headroom this account still has below zero, before its own draw |
Excess |
the amount below zero past the limit: max(0, −ledger Current − FacilityLimit), computed wherever Current is bound and again after each posting in a walk, so the fee’s own posting moves it |
Both facility symbols add this account’s own usage back, so Current + FacilityAvailable
is the account’s headroom whatever the balance’s sign. At −800 on a 2 000 facility the
facility’s own available reads 1 200 and the account’s headroom is also 1 200: −800 +
2 000, not −800 + 1 200. The grill’s press caught the double count (pair 1). With one
account on the facility the two readings agree except for the sign of the balance; with two
accounts each sees the limit the other has left it (Decision 9).
The current account’s withdraw reads availabilityGuard: Current + FacilityAvailable > 0 and
guard: Current + FacilityAvailable >= $amount. An account with no facility declines at
zero; one with a facility declines at the limit; both are the same two lines of YAML. The
figures come through a new Contracts reader, IFacilityAvailabilityReader, implemented in
Limits and read by Accounts for the customer, currency and type the integration names, in the
tenant the caller passes — a day-end step hands over its session’s tenant and no untenanted
session is opened at handler entry (ADR-302 D7).
Payout operations reserve against the facility exactly as ADR-794 D10 has them, with Decision 2’s asked amount. A teller withdrawal posts without a reservation and is held by the guard alone, as today; the exposure between the guard’s read and the posting is one withdrawal’s worth, the same acceptance ADR-836 makes for two cards on one account.
4. The oracle’s available includes the overdraft
AccountAvailability (ADR-836 D4) gains FacilityAvailable, and Available includes it.
The funding walk is unchanged: current, then savings already means current, its
overdraft, then savings, because the overdraft is the facility on the current account and
never an entry in the rule (ADR-835 D5).
5. The clearing post is unconditional, and the limit records what posted
The card operations declare neither guard, so ExternalSourceDispatcher posts whatever the
scheme settled. SetUsage has no ceiling, so a purchase that takes the account past its
facility is recorded as utilisation over the amount; the facility’s panel shows it, and
Excess on the account is the figure. Nothing is parked in suspense: the purchase is on the
customer’s statement where they spent it, and the bank’s payment to the scheme is matched by
the asset it now holds against the customer.
6. The unarranged overdraft is a figure, not a status
The proposal says the unarranged overdraft is “the abnormal state AccountNature already
names”. It is not: AccountNature is Asset | Liability, a classification of the type. The
account’s status stays Active; Excess is a derived amount, zero or positive, bound in the
guard bag and the day-walk context, shown on the account, and the input the collections ADR
will age by. A status would be a second mechanism answering a question the balance answers.
7. Pricing is configuration on the type
Three accruals and one fee, every one a scheduled transaction on CurrentAccount with a
condition and an amount expression; no aggregate or handler branches on a product word — the
symbols and the account detail name the concept, the rows carry the behaviour:
| Scheduled transaction | Condition | Amount | Posts to |
|---|---|---|---|
InterestAccrued |
Current > 0 |
Current * rate('Call', valueDate) / daysInYear(valueDate) |
Accrued |
DebitInterestAccrued |
Current < 0 |
min(0 - Current, FacilityLimit) * rate('Overdraft', valueDate) / daysInYear(valueDate) |
DebitAccrued |
ExcessInterestAccrued |
Excess > 0 |
Excess * rate('UnarrangedOverdraft', valueDate) / daysInYear(valueDate) |
DebitAccrued |
UnarrangedOverdraftFeeCharged |
Excess > 0 |
price('unarranged-overdraft-fee', valueDate) |
Current, daily |
All four run at end of day, the accruals before the fee (the generated types’ sequence
numbers order them), so the day’s interest is priced on the balance the day traded at and the
fee joins tomorrow’s. daysInYear(valueDate) is the calendrical built-in the call deposit
accrues with: the actual days in the year. Interest capitalised at the start of a month
can tip an account into excess, and that day’s end prices it: excess is a balance fact
whatever caused it, and a tenant that wants grace adds a condition to the row. The accrual types carry full precision, as every accrual does; a cent
figure in a scenario is the posting rounded to the cent. Monthly capitalisation moves each
accrued position to Current. Two accrued positions, not one, so the GL and the statement
split interest paid to the customer from interest charged, and arranged from unarranged: the
debit accruals post to a new Overdraft — accrued interest receivable against Interest
Income, the fee to the deposit liability against a new Fee income — unarranged overdraft.
The rates are named rate types read as the call deposit reads rate('Call', valueDate):
credit interest on Call, and two new types, Overdraft and UnarrangedOverdraft, in the
country × package rate cell beside it — tenant pricing, not a property on the account; a
negotiated per-account rate is a later ADR. The fee is a price type (unarranged-overdraft-fee). The daily fee per day in excess is the simplest configurable
reading of the practice; a per-item honouring fee at posting time needs the pre-posting ledger
in a workflow step’s condition, which the step bag does not bind, and is deferred.
The day-walk context binds FacilityLimit and Excess as values the caller resolves and
hands to AccountValuation (the ADR-329 D6 shape: pure domain, no reader inside), so the
day-end steps read the facility once per current account per day, at the moment the step
runs: a limit cut earlier that day prices from that day-end. A type with no facility reads
FacilityLimit 0, so a card post that takes it below zero is entirely excess and priced as
unarranged — the bank lent money it never agreed to lend. The daily fee is a charge for the
day as the day stood: a same-day reversal before day-end means no fee, and a back-dated
reversal re-walks the days it touches (revaluation diffs every scheduled transaction) and takes
the fee and the excess interest with the excess that caused it; a line dated a closed day adds
that day’s fee the same way. The re-walk prices every past day on the facility as it stands
today; the facility’s own history is not read. Today the re-walk fires only for a value date
strictly before the last closed day, and never from an external-source posting; this ADR makes
the boundary inclusive and cascades from the external-source path, because a line or reversal
dated the day just closed — the common case under ADR-836’s day-late clearing — must re-walk it.
8. The overdraft is a credit facility under the NCA
An overdraft facility is a credit facility (National Credit Act 34 of 2005 §8(3)), so
CurrentAccount declares regulatoryRegime as the loan types do; the clerk picks
Unregulated for an account with no overdraft. The property brings ADR-278’s cost-of-credit
classification (every transaction type categorised: DebitInterestAccrued and
ExcessInterestAccrued are Interest, the fee is DefaultAdmin) and ADR-279’s statement
sweep. The standards register gains a Partial row for §8(3): classification is in; the
§103(5) cap on an excess default episode is not claimed here.
9. One overdraft per customer, currency and type
A facility is the customer’s, found by counterparty, currency and type (ADR-050 §4). Two
current accounts in one currency share one overdraft, and UsageByAccount already splits
it. Decision 3’s symbols subtract the other accounts’ usage, so each account’s limit, headroom
and excess are its share of what is left: two accounts at −1 500 each on a 2 000 facility read
FacilityLimit 500 and Excess 1 000 apiece, and the facility reads 1 000 over. The account
viewer still shows the facility’s amount as the limit — the overdraft the customer was granted —
and the share shows through the available and the excess. A frozen
facility reads 0 on both symbols, so every draw on it is excess and priced as unarranged; the
card still posts (Decision 5). A per-account facility is a model change to Limits and is not
this ADR’s.
10. The demo funds the card from the current account first
The za-retail sample data gives the demo customer a ZAR CurrentAccount with an Overdraft
facility of 2 000, and the sample card’s funding rule becomes current, then call deposit.
The oracle’s probe taps past the balance and into the overdraft; the clearing probe posts a
line past the limit and the account shows Excess. reseed: true.
11. The account shows its overdraft
The account viewer’s header positions slot gains, for a type wired BelowZero: the overdraft
limit (the facility’s amount, marked frozen when it is), available including the overdraft
(Current + FacilityAvailable floored at zero — the guard’s own figure, computed when the
detail is read, so the screen and the refusal never disagree), and in excess by when Excess
is positive. A wired type whose customer holds no facility shows a limit of zero and its balance
as available; a type with no wire shows nothing. A card hold is an external reduction on the
account (ADR-836) and reserves nothing on the facility, and the guard bag subtracts it, so the
screen, the teller guard and the oracle read one figure. The customer’s facilities panel already
shows the facility and its utilisation.
Contracts
Ids — none new. CurrentAccount is an AccountTypeId key; Overdraft is a
LookupValueId under facility-type.
Commands — none new. GrantFacilityCommand (Limits) grants the overdraft as it grants a
loan facility.
Events — none new. FacilityUsageSet carries the below-zero utilisation unchanged.
Queries — IFacilityAvailabilityReader (LedgerTM.Contracts/Limits): for a counterparty,
currency and facility type, the facility’s amount, reserved, usage by account and frozen flag,
or null when none is granted. Limits implements it; Accounts derives the three symbols from it.
Consumed from LedgerTM.Contracts — ILimitIntegrationResolver, IAccountPayoutLimitGate,
LimitIntegrations (internal to Limits since ADR-1224), ExposureLine, IAccountAvailabilityReader (ADR-836), PositionChangedTrigger.
Changed — FacilityIntegration and CreditLimitIntegration gain Direction
(LimitDirection: Raise, BelowZero); AccountAvailability (ADR-836) gains
FacilityAvailable; PayoutLimitContext gains the balances the lines start from;
LimitExposure.Asked (Limits) takes the direction and that balance; Facility gains
SetUsageTo and SetFacilityUsageCommand an absolute utilisation; FacilityReadModel gains
usage by account.
Removed — none.
Prior art
| Declared | Search returned | Verdict |
|---|---|---|
CurrentAccount |
CorporateCurrentAccount (corporate package), CallDeposit (retail) |
genuinely new row, reused shape — the package model has no shared base and the corporate key is a stored identity (D1) |
Overdraft (facility type) |
facility-type values PersonalLoan, Guarantee, WorkingCapital, MortgageBond, VehicleFinance |
extend — one more lookup value |
LimitDirection |
ExposureEffect (Increase/Decrease on a movement), ExternalAccountDirection (ADR-713) |
genuinely new — neither says which way a position draws a limit; ExposureEffect is the result, this is the rule |
IFacilityAvailabilityReader |
ILimitIntegrationResolver (Accounts answers Limits), CheckFacilityAvailableCommand (Limits-internal), FacilityReadModel.Available |
genuinely new — the inverse direction: Limits answers Accounts, read-only, through Contracts |
FacilityAvailable, FacilityLimit, Excess (symbols) |
NoticedTotal, PendingNoticeCount (bound beside positions) |
extend — three more context symbols, same binding site |
DebitInterestAccrued, ExcessInterestAccrued, UnarrangedOverdraftFeeCharged |
InterestAccrued, SuspendedInterestAccrued, ServiceFeeCharged |
extend — transaction type rows on one type, named by the posting’s meaning |
Overdraft, UnarrangedOverdraft (rate types) |
Call, Prime, Headline CPI in the country × package RateSettings cell |
extend — two rate-type rows, read as Call is |
unarranged-overdraft-fee |
unpaid-fee, service-fee, arrears-letter-fee |
extend — a price type row |
AccountAvailability.FacilityAvailable |
AccountAvailability (ADR-836, Accepted) |
extend — the field ADR-836 F1 reserved for this ADR |
IAccountAvailabilityReader |
IAccountAvailabilityReader, AccountAvailability (ADR-836) |
reuse — the reader ADR-836 built; its answer gains the facility |
LimitIntegrations, FacilityIntegration, CreditLimitIntegration |
the ADR-050 wiring block, resolved through ILimitIntegrationResolver |
extend — each integration gains Direction; the block’s shape is otherwise unchanged |
IAccountPayoutLimitGate |
IAccountActivationLimitGate, IAccountOwnerChangeLimitGate, PayoutLimitContext |
reuse unchanged — the gate reserves as ADR-794 has it; only the asked amount’s reading changes inside Limits |
AccountTypeId, LookupValueId |
the strongly typed ids the type key and the facility-type value already carry | reuse unchanged |
Relies on
| Symbol | What it does today | What this ADR assumes |
|---|---|---|
Facility |
Amount, utilisation, reservations, available; SetUsage records any amount, Reserve refuses past available |
Usage past the amount is recorded, never refused (D5) |
UpdateLimitsOnPositionChangedHandler |
A positive delta on the wired position is an increase, a negative one a decrease | Gains the below-zero reading (D2) |
LimitExposure |
Asked nets lowering lines against raising ones on the wired position |
Gains the below-zero reading (D2) |
AvailableBalance |
Projects available per position from ledger, claims and (ADR-836) external reductions; the guard bag binds its result | The guard bag binds the facility symbols beside it (D3) |
AccountValuation |
The day-walk’s context: ledger positions, rate, price, daysInYear |
Binds FacilityLimit and Excess from caller-resolved values (D7) |
ProcessStandingOrderPaymentCommand |
A system posting from outside Accounts, run through the type’s workflow with its guard evaluated |
The standing order runs under the withdraw guard (D1); the card operations declare no guard (D5) |
CostOfCreditValidator |
A type with regulatoryRegime must categorise every transaction type |
CurrentAccount declares the property and the categories (D8) |
GrantFacilityCommand |
Grants a facility to a counterparty in a currency | Grants the overdraft (D10) |
ADR-836’s IAccountAvailabilityReader (Accepted, not yet on main) is relied on as declared in its
plan: available of the standard positions after claims and external reductions; this ADR adds the
facility’s available (D4).
Worked example
Fixture: za-retail, the demo customer (Jeremy Rich), a ZAR CurrentAccount opened with
4 200, an Overdraft facility of 2 000, rate types Call 6.25%, Overdraft 18%,
UnarrangedOverdraft 28%, unarranged-overdraft-fee 50. Trading date 2026-10-05.
| Step | Current | Facility used | Available | Excess |
|---|---|---|---|---|
| Opening | 4 200.00 | 0 | 6 200.00 | 0 |
| Hotel authorises 5 000 (ADR-836): hold placed | 4 200.00 | 0 | 1 200.00 | 0 |
| Hold released; clearing posts 5 000 | −800.00 | 800 | 1 200.00 | 0 |
Clerk tries 1 500: guard Current + FacilityAvailable >= 1 500 → −800 + 2 000 = 1 200 ≥ 1 500 false, refused |
−800.00 | 800 | 1 200.00 | 0 |
| Fuel clears 2 300 (no hold; offline) | −3 100.00 | 3 100 | 0 | 1 100.00 |
| Day-end 2026-10-05 | ||||
DebitInterestAccrued: min(3 100, 2 000) × 18% / 365 |
0.99 | |||
ExcessInterestAccrued: 1 100 × 28% / 365 |
0.84 | |||
UnarrangedOverdraftFeeCharged: 50 |
−3 150.00 | 3 150 | 0 | 1 150.00 |
| Salary 10 000 posts | 6 850.00 | 0 | 8 850.00 | 0 |
GL at the clearing post: Dr the deposit liability 5 000, Cr card settlement payable 5 000 (ADR-836). The liability is now a debit balance of 800, which the bank reports as an asset; the chart’s reclassification of debit-balance deposits is the financial director’s month-end question, named in Consequences.
Model
Generated from docs/model/model.json (ADR-773 D8): the shape the model knows today, <<new>> for what
## Contracts declares and the model does not know, relies-on for ## Relies on. Regenerate with
python3 scripts/model/adr_model.py ADR-NNN --write; frozen at Shipped.
classDiagram
class Facility {
<<aggregate>>
Decimal Amount
Decimal Available
FacilityId Id
Decimal UsageByAccount
Decimal Utilisation
Double UtilisationPercent
Decimal UtilisationRatio
CounterpartyId CounterpartyId
CurrencyId CurrencyId
LookupValueId FacilityTypeId
SetUsage()
}
Facility --> Counterparty : CounterpartyId
Facility ..> FacilityUsageSet : SetUsage
class FacilityUsageSet {
<<event>>
}
class FacilityReadModel {
<<read-model>>
Decimal Amount
Decimal Available
FacilityId Id
Decimal Utilisation
Double UtilisationPercent
}
Facility ..> FacilityReadModel : FacilityCreated (Inline)
Facility ..> FacilityReadModel : FacilityDecreased (Inline)
Facility ..> FacilityReadModel : FacilityFrozen (Inline)
Facility ..> FacilityReadModel : FacilityIncreased (Inline)
Facility ..> FacilityReadModel : FacilityUsageSet (Inline)
class BelowZero {
<<new>>
}
Facility ..> BelowZero : declared
class CurrentAccount {
<<new>>
}
Facility ..> CurrentAccount : declared
class Direction {
<<new>>
}
Facility ..> Direction : declared
class FacilityAvailable {
<<new>>
}
Facility ..> FacilityAvailable : declared
class Overdraft {
<<new>>
}
Facility ..> Overdraft : declared
class Raise {
<<new>>
}
Facility ..> Raise : declared
class SetUsageTo {
<<new>>
}
Facility ..> SetUsageTo : declared
class AccountValuation {
<<relies-on>>
}
class AvailableBalance {
<<relies-on>>
}
class CostOfCreditValidator {
<<relies-on>>
}
class GrantFacilityCommand {
<<relies-on>>
}
class LimitExposure {
<<relies-on>>
}
class ProcessStandingOrderPaymentCommand {
<<relies-on>>
}
class UpdateLimitsOnPositionChangedHandler {
<<relies-on>>
}
Consequences
Positive
- An overdraft is two lines of YAML and a facility grant. No code names a product; the guard change and the wire are the configuration surface the salesperson points at.
- One available figure everywhere. The button, the execution guard and the oracle read the same facility available through one reader.
- The unarranged overdraft is visible and priced on the day it happens, on the account the customer sees, and the auditor finds it in the facility’s usage trail.
- The customer’s credit limit sees the overdraft, so the overall exposure the bank agreed holds across loans and the current account.
Negative / Trade-offs
- A debit-balance deposit liability sits in a liability GL account until reclassified; the posting rules here do not move it. A month-end reclassification is a Books question for the financial director and is not in this ADR.
- The guard reads the facility, then the posting happens: two tellers on one account can both pass the guard. The exposure is one withdrawal; payouts reserve and are safe.
- A hold reserves nothing on the facility, so two cards on two accounts sharing one overdraft can both be held into it; the clearing posts then record the usage. A consequence of D9.
- The teller guard reads the facility, not the customer’s credit limit. The credit limit
records the overdraft’s usage and refuses payouts and activations past it (ADR-794), as it
does for every type today; a teller withdrawal is not gated by it. A
CreditLimitAvailablesymbol is one line when a tenant asks. - One facility read per current account per day-end, and one per guard evaluation on a wired type. Measured in the plan’s first bite.
- The daily fee charges every day in excess, including a weekend the customer cannot act on. That is the configured practice; a grace day is a condition on the row.
Neutral
Raiseis the default direction, so every existing wire reads exactly as before.- The corporate package is untouched; a second current account row exists by design (D1).
Implementation Plan (Bites)
Six bites, one land; reseed: true. Bite 4 waits for ADR-836’s decider on main; the lane
takes it after a bite-boundary merge.
Bites, acceptance criteria, files touched, and status live in ADR-837-plan.md.
Changed during the grill
Phase A (the cold author’s questions, 2026-10-02): Decision 1’s conformance test is
struck — the two rows never shared transaction names, and a holder role joins the retail
vocabulary; Decision 2 wires the facility only on the retail template, and SetUsage floors
an account’s usage at zero; Decision 7 fixes the order within the day and names the GL legs;
Decision 11 floors the shown available and shows a zero limit for a wired type with no
facility; bites 2 and 3 swap so the guard can be the act that draws the overdraft.
Plan grill (14 press points, 2026-10-02): Decision 2 sets usage from the balance rather
than adding deltas, and the asked amount is the net growth across an operation’s lines;
Decision 3’s Excess is computed live where Current is bound, and the reader carries the
tenant; Decision 7 names the day count and lets a back-dated reversal take the fee with it;
payout operations carry the availability guard only. Bites 4 and 5 wait for ADR-836’s land.
Phase B (six authors): the day count lives on the rate rows; the current account carries the
call deposit’s required properties; the outbound recurring act is the standing order, not the
debit order (inbound here); the limit formula clamps a sibling’s usage at zero and caps at the
amount, and reads the owner’s facility only; asks land on the lines that cross zero; a hold never
reserves on the facility and the three available figures agree; the detail shows a frozen
facility as frozen; the revaluation seam gains the closed day and the external-source cascade;
the rates are named rate types beside Call, not properties, and the day count is the calendar’s.
Grilled 2026-10-02 by the author against the proposal, the code and the press; the operator’s standing instruction was to take the recommendations.
- Decision 3 — the headroom formula. The draft read
Current + FacilityAvailablewithFacilityAvailableas the facility’s own available. Below zero that subtracts the draw twice (−800 + 1 200 = 400 against a true 1 200). Now both facility symbols add this account’s own usage back and subtract the other accounts’ usage, so one formula is right for one account, two accounts, and a frozen facility. The worked example’s refused withdrawal changed from 1 000 to 1 500 to stay refused. - Decision 9 — shared facility. The draft accepted that two overdrawn accounts each read their excess against the whole limit. With Decision 3’s symbols each reads its share; the acceptance is withdrawn.
- Decision 7 — frozen, no facility, limit cut, reversal after fee. Four silences closed: frozen reads 0 on both symbols, so the draw is excess; no facility means the whole negative balance is excess; the day-end prices from the facility as it stands when the step runs; the daily fee stands through a later reversal — superseded at the plan grill: a back-dated reversal re-walks the day and takes the fee with it.
- Decision 11 — which available the screen shows. The guard’s figure, so screen and refusal agree.
- Decision 2 — which limit is the overdraft pressed against the corporate proposal’s
reading (
CreditLimitis an overdraft) and held: the facility is the priced product limit, the credit limit the customer’s cap, and both are wired. The teller guard reads only the facility; recorded under Consequences. - Decision 1 — one type promoted pressed against the package model and changed from “promoted to the shared vocabulary” to “a second package row, one shape” before the draft was committed; recorded in Notes.
- Decision 8 — NCA classification pressed on the user seat (the clerk must answer
regulatoryRegimeon every current account; no lookup property defaults today) and held: the question is the law’s, and the answer is one click.
Contradiction press: 9 pairs, resolved as the headroom double count (Decision 3, changed),
per-account excess on a shared facility (Decision 9, changed), a frozen facility’s excess
(Decisions 7 and 9, closed), the teller guard and the credit limit (Consequences), the zero
boundary (the existing > 0 reading, held), excess with no facility (Decision 7, closed), a
same-day limit cut (Decision 7, closed), the fee after a reversal (Decision 7, closed), and the
header’s available (Decision 11, closed).
- Current −800, limit 2 000: the guard computes 400 while the example shows 1 200 — the formula double-counts the draw below zero. Real.
- Two accounts at −1 500 on one 2 000 facility: each reads
Excess0 against the full limit while the facility is 1 000 over. Real.- A frozen facility:
FacilityAvailable0 blocks the teller,FacilityLimit2 000 still prices a card draw as arranged. Gap.- A teller withdrawal inside the facility but past the credit limit: D2 claims overall exposure, the guard reads only the facility. Wording gap.
- Balance 0, no facility:
> 0hides the button,>= $amountwould pass 0. Boundary.- No facility, card post below zero: the whole negative balance prices at 28%. Silent.
- A same-day limit cut: which
FacilityLimitthe accrual uses. Silent.- A reversal after the daily fee posted: whether the fee reverses. Silent.
- D11’s “available” inherits pair 1’s ambiguity. Gap. Pairs: 9
Notes
- Deviation from the proposal, recorded: “promoted to the shared vocabulary” becomes “a
second package row, one shape” (D1); “the abnormal state
AccountNaturealready names” becomes a derivedExcessfigure (D6). Both are facts of the code the proposal did not have. - The collections hook.
Excessis the input a later ADR ages into days past due for the collections router (CollectionSettings.routingRules). Without it an account in excess is visible on its own page and on the facility, and nowhere else. - A per-item honouring fee needs the pre-posting ledger in a
whenConditionstep; the step bag binds available after claims. When a product needs it, the step bag grows, not the fee. - Depends on ADR-820 and ADR-835 (Shipped) and ADR-836 (Accepted): the card integrations
on the type, the funding rule and
AccountAvailability. Bites 4 and 5 start after ADR-836 has landed; the rest can start now.
Outcome
Landed in six bites; the full box suite passed at 5a1c1ae92. Bite 5 also fixed F-1791 (a post back-valued to the closed day now accrues). The same land carried four fixes found by later ADRs’ design reads: F-1802 (a redelivered forward-dated payout raised two instructions), F-1806 (two taps could pass a ceiling), F-1807 and F-1808 (tenant-wide hold reads).