On this page

A funding instruction can be valid while the money is not yet available for awards. The bank may show a transfer sent, the provider may show a received credit under review, and the release team may still lack the availability confirmation required by the program.

The operational task is to identify what each record proves and use the authoritative state for the decision being made. A matching amount across systems is helpful, but it does not erase the difference between initiation, receipt, and availability.

Identify the authoritative funding status

Begin with one transfer reference and trace its related bank and provider records. Record the amount, currency, program, and state at each source. If references differ between organizations, preserve the mapping rather than assuming one shared identifier exists everywhere.

For a hypothetical program, the merchant initiates a $1,000 USD transfer under FI-62. The bank records it as sent under BT-62. The provider later confirms receipt but places $200 in an unresolved review category, leaving $800 available under the example’s approved arrangement.

These states and amounts are illustrative. RebateCardX’s program disclosures should be read with the actual funding agreement to establish which source controls availability and what any held or restricted amount means.

Funding stage Evidence reference Amount represented What is established Release implication in the example
Initiated FI-62 $1,000 Authorized transfer instruction exists No program availability established
Sent by bank BT-62 $1,000 Bank-stage transfer evidence exists Provider availability still unconfirmed
Received by provider RC-62 $1,000 Credit received under the provider record Need the applicable availability finding
Available AV-62 $800 Provider confirms this amount available Only this confirmed amount enters the availability comparison
Under review HR-62 $200 Received amount not yet available under the example terms Exclude from available funding until resolved

The $800 and $200 are parts of the $1,000 received amount, not additional money. Adding all three would count the same transfer twice. The state table describes how the received amount is classified.

Separate expected cash from available cash

Suppose the release team has $900 of approved awards awaiting the next action. The transfer instruction is $1,000, but only $800 is confirmed available in the example. The team should not treat the intended amount as proof that the full $900 release is funded.

The unresolved $200 may later become available, but the next decision should use the actual program’s release prerequisite. If the program permits a particular arrangement involving pending funds, that permission must be explicit and applicable. Operations should not invent it merely because the transfer is expected to clear.

The record should also distinguish available program funds from amounts already committed to other awards. An $800 available figure may have a provider-specific definition. Before relying on it, confirm whether existing commitments are included or excluded and apply the definition consistently.

A receipt confirmation is still useful evidence. It narrows the question from whether the transfer arrived to how the provider classified it. The next inquiry can then focus on HR-62 and the condition needed for availability rather than asking the merchant to resend the entire transfer.

Do not use a bank screenshot as the final answer to a provider availability dispute. It may establish that the merchant sent money, but the provider’s applicable record must explain whether that money supports the intended program release. Both records matter, with different roles.

Resolve state disagreements before award release

A completed reconciliation note could read: “FI-62 and BT-62 identify the $1,000 USD transfer received under RC-62. Provider record AV-62 confirms $800 available and HR-62 identifies $200 under review. The received amount reconciles to those two categories. Operations will use the confirmed availability definition and obtain the required resolution before treating the additional $200 as available.”

If the merchant’s dashboard still shows $1,000 available, record the discrepancy and identify which source governs the actual release decision. Do not average the figures or choose the larger one. Determine whether the views represent different times, different programs, or different balance definitions.

A difficult case is a provider confirming availability after a transfer was previously shown as returned by the bank. The records may refer to different events or a correction. Preserve both references and obtain a reconciled explanation before using the disputed amount. One recent label should not erase contradictory evidence without investigation.

Another case is a transfer split across several provider credits. The total may reconcile even when no single credit equals the original instruction. Match the components with their references and availability states. Do not treat the smaller individual credits as repeated shortfalls requiring additional full transfers.

Use the same discipline when the unresolved $200 is released. Record the actual availability confirmation and its date. Preserve the balance snapshot time as well, especially when later award releases have already consumed part of the newly available amount. An expected future release should not be entered as a completed current movement simply because the team has been told it is likely.

The finished table shows one transfer through its observed states, with the source that supports each finding. It gives the release team a defensible funding position and prevents expected, sent, received, and available money from being treated as interchangeable balances.

Discuss how funding availability should be confirmed before awards are released.

Discuss your program

Source references

Back to contents

General information only

This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.