Brokerage Confirmation Reconciliation
Reconcile brokerage and custody confirmations with ledger holdings.
Description
Holdings reconciliation compares broker/custodian confirmations with a ledger value.
Holdings reconciliation compares broker/custodian confirmations with a ledger value. Confirmation spread is a separate comparison.1
Reconcile brokerage and custody confirmations with ledger holdings.
When to use Brokerage Confirmation Reconciliation
Use this tool to reconcile brokerage and custody confirmations with ledger holdings.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Brokerage Confirmation Reconciliation and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter ledgerHoldingsValue, brokerConfirmedValue, custodianConfirmedValue, tolerance using the field table and calculation rules, then run the tool.
- Read brokerDifference, custodianDifference, confirmationSpread, reconciled. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| ledgerHoldingsValue | Ledger holdings value | number; minimum: 0 | Required |
| brokerConfirmedValue | Broker-confirmed value | number; minimum: 0 | Required |
| custodianConfirmedValue | Custodian-confirmed value | number; minimum: 0 | Required |
| tolerance | Allowed difference | number; minimum: 0 | Required |
Enter nonnegative values/tolerance; return differences/spread. Reconciled requires both ledger differences within tolerance.
differences=confirmed−ledger; spread=abs(broker−custodian) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| brokerDifference | Broker minus ledger difference | number |
| custodianDifference | Custodian minus ledger difference | number |
| confirmationSpread | Broker-custodian spread | number; minimum: 0 |
| reconciled | Confirmations reconcile | boolean |
{
"input": {
"ledgerHoldingsValue": 1000,
"brokerConfirmedValue": 1002,
"custodianConfirmedValue": 999,
"tolerance": 3
},
"output": {
"brokerDifference": 2,
"custodianDifference": -1,
"confirmationSpread": 3,
"reconciled": true
}
}Limitations and assumptions
Spread does not separately gate the result and can exceed tolerance even when reconciled. No ownership, valuation or external confirmation is obtained.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Proof-of-Reserves Coverage: Measure proof-of-reserves asset ratio and customer-account inclusion. For a complementary task, use Record Count Reconciliation: Reconcile source and target record counts within a caller-supplied tolerance.
References
-
Brokerage Confirmation Reconciliation — tool.io
Similar or alternative tools
- Proof-of-Reserves Coverage
Measure proof-of-reserves asset ratio and customer-account inclusion.
- Record Count Reconciliation
Reconcile source and target record counts within a caller-supplied tolerance.