OpenChainGraph Suite · ART-507 · Deposit Insurance · 12 CFR Part 370

Deposit Insurance Coverage Determination

Part 370 asks an institution's system to say, for every deposit account, how much is insured and how much is not, grouped by ownership right and capacity. This page does that arithmetic on the records you give it, and it is equally explicit about the accounts it cannot do it for.

The insurance amount is something you supply. No statutory figure is held anywhere in this page or in the kernel behind it, because a maintained number goes quietly wrong the moment it moves. Supply none and nothing is estimated: every account is returned as undeterminable naming smdia, and the totals report zero insured rather than a guess.

Insurance amount is an input, never baked in Every undeterminable account names its missing field Fixed point money, no clock
Balances combine within an ownership right and capacity for the same holder, and they combine before an allowance is applied, and a group takes the largest allowance count stated for it rather than the sum across its accounts. · Ownership right and capacity codes are opaque strings used for grouping and reporting only: nothing here branches on the text of a code and no part 330 rule table is held.
What this is, and what it is not

This computes insured and uninsured amounts from the records you supply. It carries no claim that the FDIC would accept the result, it does not serve as a filing, it does not produce the submission format §370.10 prescribes, and it offers no deposit insurance advice. Whether coverage is correct for any particular depositor is decided under 12 CFR part 330 by the institution and its counsel, never here.

It does not tell you whether part 370 applies to you. Whether an institution has the two million or more deposit accounts that make it a covered institution under §370.2 is a declaration you make; no account census is performed and no covered status is asserted on this surface.

The §370.10 certification confirming that the IT system was tested during the preceding twelve months is your own assertion carrying your own date. It is echoed unchanged, it is never computed from a clock, and nothing here verifies that any testing occurred. The signature over that certification is evaluated as a §27 approval record at threshold one by the dual control certification surface; no second certification surface exists here.

How many separate insurance allowances a group is entitled to is a part 330 determination that arrives as a per-record input. This page never makes that determination for you.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data – use synthetic or anonymised inputs only.
⚠ Account and holder references are opaque strings and should stay that way. Use internal identifiers, never names, addresses, account numbers or tax identifiers. All amounts are integer minor units, so 250000.00 is entered as 25000000.
Determination frame
Certification assertion (§370.10, yours and never verified here)
Account records (opaque refs, zero PII)

The default set carries the four shapes that matter. Two accounts held by one holder aggregate before the allowance applies. A pass-through account with five beneficiaries clears; the same shape without a beneficiary count does not. An account under alternative recordkeeping and an account flagged as an exception are each undeterminable, and each says which field is missing rather than being quietly treated as insured.

Coverage summary
By ownership right and capacity
Aggregation groups
Accounts that could not be calculated
Certification and covered status
Execution Hash (SHA-256)
Related

The §370.10 certification signature is evaluated at threshold one by the dual control certification surface, which serves this regime and others without a node per statute. Where the certified subject needs sealing first, bind it with the attested artifact subject binder. The accountability vocabulary is described at §27 of the OpenChainGraph specification.