Reconciled recovery population

Figure 01 / 12

One purchase, several independent states

This case concerns recover with a reconciled population. A success response, a completed capture, and settlement evidence are different observations. The sequence gives each event its own record instead of forcing all of them into one status field.

Figure data and text version

Event	Time	Recorded fact
Order accepted	09:00	Commercial promise exists
Payment instruction	09:01	A stable payment identifier is assigned
Capture record	09:02	USD 1,319,200.00 captured across this batch
Settlement evidence	Later	USD 1,240,048.00 observed as settled
Availability decision	After reconciliation	USD 941,908.80 available under the stated policy

Recovery must classify every affected financial action and resolve unknown outcomes before replay. Restoring throughput does not repair duplicate or missing postings.

Join original action identifiers to external and ledger evidence and repair only the supported exceptions.

All amounts, rates, capacity limits, and outcomes in this case are synthetic. The three conditions are separate assumptions for comparison. A better result in the response condition is not measured proof that the proposed control causes that improvement. The figures expose the calculation and its limits; a real deployment needs its own evidence.

Read the result

The batch begins with $1,360,000 of instructions and $1,319,200.00 of captured value. At the observation cutoff, $79,152.00 remains pending. After the stated refunds, fees, and restrictions, $941,908.80 is available for payout. The unresolved instruction count is 4; an unknown external result is handled separately from a known decline.

Figure 02 / 12

From captured value to available payout

Captured value of $1,319,200.00 becomes $941,908.80 available after pending settlement, refunds, fees, and eligible restrictions. This is a financial bridge: the bars display each component’s amount, not a cumulative balance. Reserves are restrictions on availability, not an additional fee.

Figure data and text version

Component	USD
Captured value	1,319,200
Still pending	-79,152
Refunds	-59,364
Fees	-27,703.2
Restricted cover	-211,072
Available payout	941,908.8

Figure 03 / 12

Balanced postings are necessary but not sufficient

The first entry records a settlement receivable and a merchant obligation for $1,319,200.00. Later entries move the observed settled amount to cash and record fees and refunds. Debits equal credits within each posting; external evidence is still required to establish that settlement occurred.

Figure data and text version

Entry	Debit account	Credit account	USD
Capture	Settlement receivable	Merchant payable	1,319,200
Settle	Bank cash	Settlement receivable	1,240,048
Refund	Merchant payable	Bank cash	59,364
Fee paid	Merchant payable	Bank cash	27,703.2

Figure 04 / 12

Recorded value and usable value differ

Gross instructions total $1,360,000, but only $1,319,200.00 has been captured. Pending value cannot be counted as settled cash in this illustration. The final availability decision also includes the stated restriction. These amounts are different views of one batch, so do not add the bars together.

Figure data and text version

View	USD
Instructed	1,360,000
Captured	1,319,200
Settled	1,240,048
Cash after refunds and fees	1,152,980.8
Available for payout	941,908.8

Figure 05 / 12

Timing of receipts and uses

The synthetic ladder stages both receipts and uses over five days. Its purpose is to make timing explicit. The fractions are illustrative scheduling assumptions, not observed payment-rail behavior. A positive total over the full period does not prove that funds are available at every earlier cutoff. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version

Period	Cumulative receipts	Cumulative uses
Day 0	124,004.8	102,897.6
Day 1	496,019.2	411,590.4
Day 2	868,033.6	720,283.2
Day 3	1,116,043.2	926,078.4
Day 4	1,240,048	1,028,976

Figure 06 / 12

A reconciliation identity with explicit components

The identity is capture = pending + refunds + fees + restricted cover + available payout, provided cash after fees and refunds is nonnegative. Here both sides equal $1,319,200.00. The identity locates differences; it cannot validate an incorrect input source.

Figure data and text version

Component	USD	Evidence
Captured	1,319,200	Batch records
Pending settlement	79,152	Batch records
Settled	1,240,048	Batch records
Refunds	59,364	Journal and availability policy
Fees	27,703.2	Journal and availability policy
Restricted cover	211,072	Journal and availability policy
Available payout	941,908.8	Journal and availability policy

Figure 07 / 12

One business action can produce several messages

The batch contains 12,300 intended actions and 0 duplicate attempts in this teaching trace. A stable action key identifies the business instruction. A transport identifier identifies one delivery attempt. Treating both identifiers as interchangeable is the route to duplicate financial effects.

Figure data and text version

Step	Contract
Receive	12300 intended actions; 0 repeated deliveries
Match	Look up the business action key and request fingerprint
Commit	Create one journal effect within the approved transaction boundary
Reply	Return the stored result or a controlled conflict

Figure 08 / 12

Unknown outcomes need their own queue

4 of the 12300 instructions have an unknown external outcome at the cutoff. They are not automatically failed. The remaining counts are constructed disjoint states for this example and sum to the total number of intended actions.

Figure data and text version

State	Count
Known complete	11,312
Known declined	984
Unknown external outcome	4

Figure 09 / 12

A money record carries units and identity

An integer amount is meaningful only with its currency and exponent convention. A provider identifier is meaningful only with its namespace. The data contract keeps the action identity, financial amount, and external observation separate so they can be reconciled.

Figure data and text version

Field	Example	Purpose
batch_ref	Reconciled recovery population	Stable cohort identity
currency	USD	No mixed-currency addition
gross_minor	136,000,000	Two decimal places in this USD example
availability_minor	94,190,880	Derived usable amount
settlement_state	reconciled	Financial evidence state

Figure 10 / 12

Pending settlement changes available cash

This sensitivity calculation holds capture, refunds, fees, and reserve fixed, then varies the pending share. Available payout is floored at zero. The curve describes the stated formula, not a recommended payout hold or a forecast of return timing. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version

Pending share	Available USD
0%	1,021,060.8
5%	955,100.8
10%	889,140.8
20%	757,220.8
30%	625,300.8
40%	493,380.8

Figure 11 / 12

Economic claims after the event

The edges label obligations or evidence relationships. They do not assert that the named firm performs every legal role in every payment arrangement. The purpose is to keep the commercial promise, settlement evidence, and payout obligation visible at the same time.

Figure data and text version

From	To	Relationship
Reconciled recovery population	Merchant	Fulfillment promise
Processor	Platform ledger	Settlement evidence
Platform ledger	Merchant	Payout obligation
Platform ledger	Review queue	4 unresolved

Figure 12 / 12

The close record preserves unresolved differences

Available payout is $941,908.80; restricted cover is $211,072.00. The illustration also keeps 4 unresolved outcomes and $0.00 of any reserve shortfall visible. A close process should not hide unresolved items merely to force a report to balance.

Figure data and text version

Measure	Value	Owner
Available payout	USD 941,908.80	Treasury
Restricted cover	USD 211,072.00	Merchant risk
Unresolved instructions	4	Payment operations
Reserve shortfall	USD 0.00	Exposure owner

Connect the result to the system

Join original action identifiers to external and ledger evidence and repair only the supported exceptions.

Check the population, evidence, permitted action, and actual effect together. A balanced calculation can still use the wrong population; a successful response can still leave an unknown financial outcome. The case’s numerical result applies only to its stated assumptions.