On this page

A reward approved on the last day of a month may be issued during the next month using funding transferred earlier. Each date can be correct. A month-end reconciliation fails when it expects those different events to belong to one reporting period without a bridge explaining their sequence.

The operational close should tell finance what happened, when it happened and which records remain unresolved. It should not silently choose an accounting recognition policy. Approval dates, provider issuance dates and funding dates are useful evidence, but finance must determine how those events enter the organization’s formal accounts.

Choose the operational reporting cutoff

Write the cutoff as a date, time and timezone. “September month end” can mean different moments to a merchant team, an export generated in UTC and a provider using another reporting zone. Choose one operational reporting convention and document how source timestamps are translated or interpreted for that convention.

Keep both the event time and the time the record became available where they differ. A provider may confirm on October 2 that an issuance occurred on September 30. That is a late-arriving record of an earlier event, not necessarily an October issuance. The distinction determines which bridge line explains the change between the provisional and final reports.

For a hypothetical close, suppose approved but unissued rewards totaled $800 at the start of September. During September, another $5,000 was approved. Confirmed issuance removed $4,200 from that queue, and supported corrections removed $100 under the applicable decisions. The unissued closing queue is therefore $1,500: $800 plus $5,000, less $4,200 and $100.

Label the $100 carefully. It represents specifically supported corrections in this example, not an assumption that any approved award may be canceled at month end. Attach the decision references so finance can distinguish a valid state change from a reporting omission or an unresolved customer obligation.

Bridge awards and cash events across periods

Use separate schedules for award states and funding movements. They should connect through references without being forced to share a single event date. The following example illustrates the award schedule.

Movement September amount Evidence Period-boundary explanation
Opening approved unissued awards $800 Prior closing queue Approved before September
New approvals $5,000 Dated approval records September approval events
Confirmed issuance ($4,200) Issuance references Issued by reporting cutoff
Supported corrections ($100) Authorized decision records Removed under documented decisions
Closing approved unissued awards $1,500 Reconciled closing queue May require later issuance

Now build the funding schedule. Assume $2,000 confirmed opening funding, $4,000 received during September and $4,200 used for the confirmed issuance above. Under this simplified example, with no other movements, closing funding is $1,800. That $1,800 is not supposed to equal the $1,500 unissued queue. One describes a funding position; the other describes a set of awards at a particular stage.

Keep any fee, reservation or restriction outside the simplified calculation until it has been identified from the applicable records. The worksheet should show additional lines when the real arrangement requires them. An unexplained difference should not be absorbed into a generic adjustment merely to produce an attractive month-end total.

For every cross-period award, retain the approval reference, approval timestamp, issuance status at cutoff and eventual issuance reference. A reward approved September 29 and issued October 3 appears in September’s closing queue and October’s issuance movement. Its history is continuous even though the events occupy different columns and months.

A late confirmation needs a clear report-version decision. Suppose the provisional report lists a $60 award as unissued, then a confirmed provider record establishes September 30 issuance. The operational report can either issue a documented revised close or show a prior-period correction in the next report, according to the agreed close procedure. It should not make an invisible edit after finance has used the original schedule.

Hand unresolved timing differences to finance

An unresolved timing register should describe the evidence still needed. “Pending” is too vague on its own. Write “funding sender debit confirmed September 30; receiving availability unconfirmed at cutoff” or “issuance event dated September 30 received October 2; report version decision required.” Each description identifies a next action.

Give finance an amount, owner, expected source of confirmation and relationship to the reported totals. If the difference is excluded from confirmed cash, say so. If it remains in the approved unissued queue, identify the award references. This allows finance to evaluate the information without guessing whether a line has already been counted elsewhere.

Avoid mixing reporting incompleteness with operational nonperformance. A missing confirmation could indicate an event that happened but has not been reported, or an event that has not happened at all. Until the evidence resolves that distinction, the schedule should preserve both the known state and the uncertainty rather than claim a successful issuance.

The close pack should contain the source extracts, calculation bridge, unresolved register and version history. A short cover note can state: “The award queue reconciles to $1,500 at the agreed cutoff. Confirmed funding is $1,800 before the separately listed unresolved items. This is an operational movement schedule for finance review.” That description is more useful than calling every number a liability, asset or expense without the necessary accounting assessment.

Finish by carrying forward unresolved references, not merely their aggregate amount. A $200 opening difference that disappears into a $200 closing difference may conceal two unrelated problems. Maintaining item-level continuity makes the next month’s reconciliation a continuation of the same evidence trail, and gives finance a supported explanation of movements that cross dates.

Discuss the source records available for your monthly reward reconciliation.

Discuss your program

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.