Reserved, Committed and Loaded: Build a Reward Funding Balance Bridge

Reserved, committed, and loaded can sound like three balances that should be added together. In practice, they may describe different stages of the same value, and an internal reservation may already sit inside an available balance. Adding every label can overstate the money the program has.

A funding bridge should define each category from its source records and show movements between them. This is an operational explanation, not a prescribed accounting treatment. Provider terminology and legal ownership must be established separately through the actual program documents.

Define each money category from source records

For a hypothetical model, use three operational measures. Available funds are not yet moved into the model’s approved-unloaded commitment category. Approved-unloaded commitments are value assigned to approved awards but not confirmed loaded. Cumulative loaded value records confirmed historical loads during the tracked period and is not treated as currently available program cash.

The merchant also keeps a provisional internal reservation for a possible future batch. In this example, that reservation is a subset of available funds, not an additional provider balance. Its purpose is internal planning and it must not be added to the provider total.

RebateCardX’s reporting capability page is a starting point for discussing available records. The categories and calculations below are an original illustration; a real bridge must follow the actual source definitions.

At the opening point, the example has $2,000 available, $400 approved but not loaded, and $1,500 of cumulative confirmed loads. The last figure describes historical loaded value and should not be interpreted as an unused card balance.

Reconcile movements between categories

During the period, the provider confirms $1,000 of new funding. Operations moves $700 from available funds into approved-unloaded commitments. The provider confirms $600 of loads from commitments. A separately authorized $100 commitment release returns to available funds.

The available calculation is $2,000 plus $1,000 minus $700 plus $100, giving $2,400. Approved-unloaded commitments are $400 plus $700 minus $600 minus $100, leaving $400. Cumulative confirmed loads rise from $1,500 to $2,100.

The operational funds still available or committed but not loaded total $2,800 at the close: $2,400 plus $400. The same total follows from the opening $2,400, plus $1,000 of new funding, minus $600 loaded. This cross-check confirms the illustrated movements without adding historical loaded value back into current funding.

Now add the internal provisional reservation of $300. Because it sits within the $2,400 available category in this model, the merchant’s unearmarked internal view is $2,100. The provider available amount remains $2,400. The reservation changes the merchant’s intended use, not the amount received from the provider. If that provisional batch later becomes an approved commitment, remove its provisional earmark when recording the commitment movement so the same intended use is not deducted twice.

Every movement needs a reference and authority appropriate to its type. New funding needs provider confirmation. A commitment needs its approved award relationship. A load needs the authoritative provider outcome. A release needs evidence that the commitment was actually released, not merely a request to do so.

Explain differences without double counting value

A filled bridge note could read: “Closing operational funds are $2,800 across available and approved-unloaded categories. The $2,100 cumulative loaded measure is tracked separately and is not added to current funds. A $300 internal provisional reservation is included within available funds, leaving $2,100 unearmarked in the merchant planning view. Source definitions and movement references are retained.”

The note explains why two reports might display $2,400 and $2,100 without either being arithmetically wrong. One shows provider-defined availability in the example; the other subtracts an internal earmark. The reports must label their definitions so users do not mistake the difference for missing money.

A difficult case is a provider whose available balance already excludes approved commitments differently from this model. Do not force the provider’s numbers into the example’s categories. Map the actual definitions first, identify overlaps, and then build a bridge that reconciles the real source records.

Another case is a failed issuance attempt with an unreleased reservation. The award may show failure while money remains unavailable. The bridge should retain the reservation until the appropriate release evidence exists. The failed-issuance funding review addresses that distinct reconciliation question.

Also avoid using cumulative loads as proof of current card balances. Recipients may have spent value, cards may have provider-specific adjustments, and the bridge may not contain that information. Its scope is movement into confirmed loads, not a complete cardholder balance report.

If a difference remains unexplained, record it as a reconciling item with an owner and source references. Do not balance the sheet by inserting an unlabeled adjustment. A bridge is useful because it exposes missing explanations, not because every column can be made to match by changing a number.

The completed bridge defines the categories, shows actual movements, and identifies which measures overlap. It gives the merchant an operational funding position that can be checked without counting reservations, commitments, and loaded value as though each were separate new money.

Discuss the funding categories your team needs to reconcile across the award process.

Discuss your program

Source references

• reporting capability page

Back to contents