How issuer banks can reconcile Mastercard dispute fund movements – A practical guide

Every chargeback an issuing bank files through Mastercard triggers a chain of fund movements (credits, debits, fees, and settlement adjustments) that must be tracked, matched, and closed on the bank's ledger. Get it right and your books balance cleanly at end-of-day. Get it wrong and your reconciliation team spends hours chasing discrepancies across Mastercom reports, Dual Message Clearing system clearing files, and internal GL entries.

Despite how critical this process is, most issuing banks piece it together from fragments of Mastercard documentation, tribal knowledge, and manual spreadsheets. There is no single reference that maps the full dispute lifecycle, from first chargeback through arbitration to the exact fund movements and reconciliation touchpoints at each stage.

This guide changes that. Drawing on the Mastercard Dual Message Clearing System Guide and the Mastercom User Guide, it walks through the three core reconciliation scenarios every issuer faces, explains the newer Collaboration and Fee Collection flows that many teams still struggle with, and provides a practical framework for closing your books with confidence.

The reconciliation challenge for issuers

Mastercard processes all dispute-related clearing messages through the Dual Message Clearing system. Each message carries a Message Type Indicator (MTI) and a Function Code that together define what the message does and how it affects your financial position.

The core message types that drive fund movements in disputes are straightforward in isolation. A 1442 message with Function Code 450 is a First Chargeback – a credit to the issuer. A 1240 message with Function Code 205 or 282 is a Second Presentment from the acquirer – a debit that reverses the original credit.

The complexity arises because these messages don't arrive in neat, predictable sequences. Chargebacks can be partial (FC 453 instead of 450). Second Presentments can carry additional data (FC 282 alongside 205). Pre-Arbitration outcomes are tracked primarily through Mastercom's case reporting rather than through a clearly documented, scheme-defined recovery message in the Mastercard manuals. And Collaboration (the pre-chargeback window where acquirers can resolve disputes before they enter the clearing system) can resolve either through a Fee Collection message (typically 1740 with FC 700/MRC 7800) or through a TC-20 refund, with the original chargeback often showing as a 5000/5001 reject rather than as a standard cleared chargeback.

Each of these scenarios requires the reconciliation team to look in a different place, match against a different report, and apply a different set of validation rules.

Scenario 1: Filing a first chargeback

When a cardholder dispute is valid and the issuer files a First Chargeback, a 1442 message enters the Mastercard clearing system. Before it reaches clearing, Mastercard holds it in a Collaboration queue for up to 72 hours, giving the merchant's acquirer a window to resolve the dispute directly.

If Collaboration closes without resolution, the 1442 message is released and cleared to the acquirer. At this point, the issuer receives a credit.

What to reconcile

At the transaction level, each successfully cleared First Chargeback appears as a row in the TQR4 reconciliation report (or the enhanced T5G2 report for institutions that have migrated). The key fields to validate are the MTI (1442), Function Code (450 for full, 453 for partial), Transaction Status (must be SUCCESS – a FAILURE status means Dual Message Clearing system rejected the message and no funds moved), and the Amount Reconciliation field, which shows the clearing amount in the issuer's reconciliation currency excluding fees.

At the file level, the Dual Message Clearing system system generates a 1644 Financial Position Detail message (Function Code 685) after each clearing processing window. The issuer's outgoing chargeback credits accumulate in PDS 0391 (Credits – Transaction Amount). The sum of all TQR4/TG52 Amount Reconciliation values for chargebacks cleared in that window should match PDS 0391 in the corresponding 1644 message.

At the settlement level, the 1644 Settlement Position Detail (Function Code 688) consolidates all intraday processing windows into a single net position. PDS 0396 (Net Total Amount) is the figure that flows to the actual settlement wire between the issuer and Mastercard.

The critical check most teams miss: Always verify the Transaction Status field before including a row in your reconciliation totals. A status of FAILURE means the message was rejected by Dual Message Clearing system's edit rules – there is no fund movement for that row, and the chargeback will need to be re-filed. Similarly, rows with a Reversal Flag of 'R' offset a prior message and must be matched to their originals before netting.

Scenario 2: Receiving a second presentment

When the acquirer contests the chargeback by filing a Second Presentment (1240 message, FC 205 or 282), the issuer is debited. The credit from the original First Chargeback is effectively reversed.

This is where reconciliation gets more involved, because the Second Presentment arrives in the issuer's incoming clearing file – a different direction from the outgoing chargeback. In the 1644 Financial Position Detail, Second Presentments appear in the Notification message (DE 25 = 6862), not the Acknowledgement message (DE 25 = 6861) that covers outgoing chargebacks.

What to reconcile

In the TQR4/TG52 report, match the Second Presentment row using Claim ID/Event ID (which links it to the same Mastercom claim as the original chargeback) and the ARN (DE 31), which ties all messages back to the original transaction. The Amount Reconciliation on the 1240 row represents the debit to the issuer.

In the 1644 message, the Second Presentment amount feeds into PDS 0390 (Debits – Transaction Amount). If second presentments in a given clearing window exceed chargebacks, PDS 0394 (Net Transaction Amount) will flip to a debit position, and PDS 0396 (Net Total) will reflect a net amount payable by the issuer rather than receivable.

The issuer then has two choices: accept the Second Presentment (absorb the loss and close the case) or contest it by filing a Pre-Arbitration case in Mastercom.

Scenario 3: Winning through pre-arbitration or arbitration

This is where reconciliation becomes genuinely tricky, because the fund flow depends on how the issuer wins, and some winning outcomes don't generate a new clearing message at all.

Pre-Arbitration Win (Acquirer Accepts): When the acquirer accepts the issuer's Pre-Arbitration case, the outcome is confirmed in Mastercom's case-filing reports. Reconciliation teams should validate the financial outcome against the entries that actually appear in clearing and settlement.

In practice, reconciliation teams should confirm acceptance in the Case Accepted Report, use the Case Billing Reconciliation Report and Case Year-to-Date Billing Report to review associated case fees, and cross-check the previously cleared 1442-450/453 credit and 1240-205/282 debit against any actual scheme-generated refund or adjustment entry that appears for the case. If a case decision appears in the Case Ruling Report, note that Status = S means ruled for sender and Status = R means ruled for receiver.

Arbitration Win (Mastercard Rules for Issuer): If the acquirer rejects the Pre-Arbitration and the case escalates to full Arbitration, a sender-favoured decision appears in the Case Ruling Report with Status = S. The Case Billing Reconciliation Report can be used to review the dispute amount and any associated case fees.

The hidden complexity: Collaboration fees & good faith collections

Beyond the standard chargeback-to-arbitration path, two fund recovery mechanisms increasingly appear in issuer reconciliation workflows, and both bypass the traditional clearing channel, making them easy to miss.

Collaboration (Pre-Dispute Resolution): During the Mastercom Collaboration window (the 72 hours before a chargeback is released to Dual Message Clearing system) the acquirer may resolve the dispute directly. The issuer can receive that resolution either as a Fee Collection message or as a TC-20 refund. For response code A (Funds Movement Request), the issuer sees a 1740 with Function Code 700 and Message Reason Code 7800, and the original chargeback is typically rejected with reason code 5000. For other refund/reversal responses, the issuer may need to identify a TC-20 Refund. These outcomes are not ordinary cleared chargeback rows, but they are still traceable through TQR4/T5G2, the Acquirer Collaboration Responses-Issuer Report, and bulk/operational report outputs such as T112 and IP142110-AA.

Good Faith Acceptance Settlement: The Dual Message Clearing system guide also defines fee collection reason codes for Good-Faith Acceptance Settlement (DE 25 = 7606). Because these are fee collection messages rather than standard chargeback events, they should be tracked separately from the 1442/1240 dispute-clearing flow and reconciled against the actual fee collection records that appear in clearing.

Both of these flows represent real money recovered for the issuer, but because they arrive through a non-standard channel, they are frequently omitted from reconciliation totals, leading to unexplained variances between what the dispute management system reports as recovered and what the ledger actually shows.

A Three-Layer Reconciliation Framework

Every fund movement in the Mastercard chargeback cycle must reconcile across three layers before the books can be closed for a given processing date:

• Layer 1 – Transaction Level (TQR4/T5G2 Report): One row per cleared dispute event. This is where you validate each individual chargeback, second presentment, or arbitration chargeback. Filter by MTI, Function Code, and Transaction Status. Sum Amount Reconciliation values by type to build your expected credit and debit totals.

• Layer 2 – File/Window Level (1644 FC 685): One message per clearing processing window per file direction. PDS 0391 (credits) must equal the sum of your TQR4 chargeback and arbitration amounts for that window. PDS 0390 (debits) must equal the sum of your TQR4 second presentment amounts. Multiple processing windows occur each business day.

• Layer 3 – Settlement Level (1644 FC 688): One message per business day. PDS 0396 (Net Total Amount) consolidates all intraday processing windows and is the amount Mastercard will include in the day's settlement wire. Your treasury team should reconcile this figure against the actual settlement entry received from Mastercard.

When all three layers agree (transaction details match file totals, file totals match settlement) the reconciliation is complete.

Why this matters for dispute operations

Reconciliation isn't just an accounting exercise. For issuer banks running active dispute operations, accurate fund movement tracking directly impacts recovery rates, financial reporting, and audit readiness.

When reconciliation teams can confidently trace every dispute from case creation through to settlement, they can identify stuck cases faster (a chargeback showing as filed in the dispute management system but missing from TG52 likely failed Dual Message Clearing system edit rules and needs re-submission), catch fee leakage (Collaboration credits and Good Faith collections that arrived but were never booked), and provide auditors with end-to-end documentation linking each fund movement to its clearing message and settlement entry.

The banks we work with at Rivero increasingly tell us that reconciliation complexity is one of the biggest operational pain points as their dispute volumes grow. It's one of the reasons we're building deeper reconciliation visibility directly into our dispute management platform – giving operations teams a single place to track not just the dispute workflow but the corresponding fund movements and clearing data, without having to manually cross-reference Mastercom reports, Dual Message Clearing system files, and internal ledgers.

If you're navigating these reconciliation challenges and want to see how an integrated approach can reduce the manual effort, we'd be happy to show you.

Frequently Asked Questions

How do I reconcile a Pre-Arbitration win when no new clearing message is generated?

When the acquirer accepts the Pre-Arbitration, confirm the outcome in the Case Accepted Report. If a case decision also appears in the Case Ruling Report, Status = S means ruled for sender and Status = R means ruled for receiver. The Mastercard manuals do not define a standard automatic recovery message for every accepted Pre-Arbitration outcome, so reconcile the case against the actual clearing or settlement entries that appear for it and review associated fees in the Case Billing Reconciliation Report.

What's the difference between TQR4 and the T5G2 Enhanced Reconciliation Report?

T5G2 is the enhanced version of TQR4. In the February 24, 2026 Mastercom User Guide, TQR4/TQR6 has 28 fields and T5G2/T5G4/TS7F has 47 fields. The additional fields include the Clearing Date, Clearing Cycle ID, transaction status, more detailed currency-conversion data, a fee detail structure, and an extended Reason for Rejection field of up to 5,000 characters.

Why do some chargebacks show as filed but don't appear in my reconciliation reports?

This typically means the 1442 message failed Dual Message Clearing system's edit rules. Check the Transaction Status field in TQR4 – a FAILURE status means no funds moved. The extended Reason for Rejection field (up to 5000 characters in T5G2) will explain why. The chargeback needs to be corrected and re-submitted before it will clear.

How should I handle Collaboration credits in my reconciliation?

Successful Collaboration resolutions can surface either as a 1740 fee collection message or as a TC-20 refund, depending on how the acquirer responds. For response code A, the manuals point to a 1740 with FC 700 and MRC 7800, while the original chargeback is typically rejected with reason code 5000. Reconcile these items using TQR4/T5G2, the Acquirer Collaboration Responses-Issuer Report, and the relevant bulk/report outputs such as T112 or IP142110-AA/T140 rather than treating them as ordinary cleared chargeback rows.

Where does the settlement wire amount come from?

The settlement wire is based on PDS 0396 (Net Total Amount) in the 1644 Settlement Position Detail message (FC 688), which consolidates all intraday processing windows. Your treasury team should reconcile PDS 0396 against the actual settlement entry received from Mastercard daily.