Settlement reconciliation procedures are essential to merchant acquiring because they confirm that approved, captured, refunded, and reversed transactions are accurately reflected in processor settlements. By comparing transaction records with gross sales, fees, reserves, and net settlement amounts, financial teams can identify errors before they affect merchants or reporting.
A structured reconciliation process also provides a clear method for investigating discrepancies, including partial captures, split settlements, delayed postings, and unexpected adjustments. Reliable controls, complete documentation, and timely communication with processors help protect settlement accuracy and strengthen confidence in the acquiring operation.
Establishing the Settlement Reconciliation Process
A settlement reconciliation process begins by defining its purpose, scope, and accountable owners. In merchant acquiring, it should cover the complete transaction lifecycle, from authorization and capture through settlement, refunds, reversals, chargebacks, and adjustments.
Document the reconciliation frequency, cut-off times, settlement currencies, and systems included in the review. Specify whether reconciliation will occur daily, per settlement batch, or according to contractual requirements with each payment processor and merchant.
Clear control rules should identify the records to compare, acceptable timing differences, approval requirements, and escalation periods. Access to reconciliation files and adjustment functions should be restricted according to defined responsibilities.
The procedures should also establish how exceptions are recorded, investigated, approved, and resolved. This framework provides a consistent basis for the detailed matching of transaction records, fees, reserves, and net settlement amounts in subsequent stages.
Mapping Settlement Data Sources and Transaction Records
Map each settlement data source to the transaction records it represents. Typical sources include the merchant acquirer’s settlement files, payment gateway reports, processor messages, card-network records, merchant statements, and the general ledger. Document the file owner, delivery frequency, time zone, currency, and reporting period for each source.
Transaction records should retain identifiers that support traceability, such as the transaction ID, authorization code, retrieval reference number, batch number, and settlement date. Where identifiers differ between systems, create a documented cross-reference between gateway, processor, and ledger values.
The mapping should also show how transaction statuses move through the payment lifecycle, from approval and capture to settlement, refund, or reversal. Record the fields used to compare transaction amounts, fees, reserves, chargebacks, and net proceeds.
Clear data lineage supports settlement reconciliation procedures by identifying the authoritative source for each field and showing how records flow into reconciliation files. Any unavailable, manually maintained, or inconsistently defined data should be documented before matching begins.
Preparing Data for Settlement Reconciliation
Data preparation begins by collecting settlement files, transaction-level records, and adjustment reports from the acquirer, payment processor, gateway, merchant system, and relevant banking platforms. Each source should be assigned a reporting period and retained in its original format for auditability.
Standardise key fields before matching records. Dates and time zones should follow an agreed convention, while transaction identifiers, currencies, decimal places, and status values require consistent formatting. Common preparation tasks include:
- Removing duplicate file imports without deleting legitimate repeated transactions
- Converting amounts into a consistent currency and number format
- Normalising approved, captured, refunded, and reversed status codes
- Preserving processor fees, reserves, chargebacks, and other deductions as separate fields
Missing or invalid values should be logged rather than silently corrected. Data should then be validated through record counts, control totals, and file completeness checks. These prepared datasets provide a reliable basis for applying settlement reconciliation procedures and identifying differences during transaction matching.
Matching Transactions and Settlement Entries
Matching begins by linking each approved, captured, refunded, or reversed transaction in the merchant’s records with its corresponding settlement entry. Matching keys may include transaction identifiers, authorization codes, capture dates, currency, and settlement batch references. Status changes must be evaluated to prevent duplicate or incomplete matches.
The comparison should cover gross sales, interchange and processor fees, chargebacks, reserves, adjustments, and the final net settlement amount. Timing differences between transaction capture and processor funding dates should be documented rather than automatically treated as exceptions.
Partial captures require reconciliation against the captured amount, not the original authorization. Split settlements should be traced across all related entries, including separate funding dates, currencies, or accounts. A transaction is considered fully matched only when its aggregated settlement components agree with the underlying records.
These matching rules form a central part of settlement reconciliation procedures because they create a consistent basis for identifying missing transactions, duplicated entries, incorrect fees, and unexplained variances. Thresholds for acceptable rounding or currency conversion differences should be defined in advance.
Matching approved, captured, refunded, and reversed transactions
Approved transactions represent authorization, while captured transactions confirm that funds should be included in settlement. Reconciliation procedures should link each capture to its original approval using transaction identifiers, merchant references, timestamps, and amounts, while recognizing that an approval may expire or remain uncaptured.
Refunds must be matched to the related captured transaction, not merely to the original authorization. The review should verify the refund amount, processing date, currency, and refund reference, including cases involving multiple partial refunds.
Reversed transactions require separate treatment because they cancel or release an authorization before, or sometimes around, capture. They should not be counted as completed sales. Matching should confirm the reversal status and ensure no corresponding amount enters the merchant’s receivable or settlement total.
Where identifiers differ between the merchant, processor, and acquirer, controlled cross-reference fields can support matching. Unmatched approvals, captures, refunds, and reversals should remain in an exception queue for investigation rather than being forced into a presumed match.
Comparing gross sales, fees, reserves, and net settlement amounts
Reconciliation should compare the processor’s gross sales with approved and captured transaction records for the same settlement period. The comparison must use consistent dates, currencies, merchant identifiers, and treatment of refunds, reversals, and chargebacks.
Calculate the expected net settlement by applying documented deductions:
- Gross captured sales minus refunds, reversals, and chargebacks
- Processing, scheme, interchange, and other disclosed fees
- Reserve or rolling-reserve amounts withheld
- Approved credits, adjustments, and prior-period corrections
The resulting figure should agree with the amount deposited into the merchant’s designated account, subject to documented timing differences. Fees and reserves should be validated against the applicable pricing schedule and settlement report rather than inferred from the deposit alone.
Settlement reconciliation procedures should record each variance separately. A difference may arise from a fee change, reserve release, currency conversion, rounding, or a transaction posted in another cycle. Each variance should be supported by processor reports, transaction records, and adjustment references before it is cleared.
Handling partial captures and split settlements
Partial captures occur when a merchant captures only part of an authorised transaction, often because items are shipped separately or inventory changes. Reconciliation should link each capture to the original authorisation and confirm that the cumulative captured amount does not exceed the approved amount.
Split settlements arise when one transaction is distributed across multiple settlement batches, funding dates, currencies, or merchant accounts. Each settlement entry should retain a shared transaction reference, capture identifier, or processor-assigned trace number to support accurate matching.
Settlement reconciliation procedures should compare every component with the processor report, including gross captured value, interchange and processing fees, reserves, adjustments, and net amounts. Timing differences must be distinguished from genuine discrepancies, particularly when captures settle on different business days.
Unmatched partial captures or split entries should be classified and investigated before adjustments are posted. Supporting records should show the original authorisation, each capture, settlement batch, applicable fees, and any refund or reversal associated with the transaction.
Detecting and Classifying Settlement Discrepancies
Settlement reconciliation procedures should compare expected transaction outcomes with processor settlement records and the amounts posted to the merchant account. A discrepancy exists when transaction status, settlement date, currency, amount, or accounting entry does not agree across approved records.
Discrepancies can be classified by their source and financial effect. Common categories include missing settlements, duplicate entries, amount variances, fee differences, timing mismatches, currency conversion variances, and transactions settled under an incorrect merchant or account.
Status-related exceptions require careful review of approved, captured, refunded, reversed, and declined transactions. For example, a captured payment absent from a settlement file may indicate a missing settlement, while a refunded payment included as a positive credit may represent an incorrect sign or transaction status.
Classification should also distinguish processor errors from internal recording issues and legitimate timing differences. Assigning a category, value, transaction identifier, settlement batch, and ageing status allows teams to prioritise investigation and maintain consistent Settlement reconciliation procedures.
Investigating and Resolving Reconciliation Exceptions
Investigating reconciliation exceptions begins by tracing the discrepancy through the acquiring platform, payment gateway, processor file, and merchant ledger. Review transaction identifiers, timestamps, statuses, currencies, and settlement dates to determine where recorded values diverged.
For each case, verify whether the variance resulted from a processing delay, duplicate entry, failed capture, refund, chargeback, fee, reserve, or currency conversion. Comparing source records with processor reports helps distinguish operational errors from timing differences.
Resolution should be coordinated with the relevant processor and merchant when external confirmation is required. Maintain an exception record containing:
- The affected transaction and discrepancy type
- Investigation findings and responsible system
- Approved correction, adjustment, or follow-up action
- Supporting reports, correspondence, and approval evidence
Adjustments must be posted through authorized procedures rather than altering historical transaction data. Once resolved, the exception should be independently reviewed where controls require it, and the outcome retained for audit purposes and future Settlement reconciliation procedures.
Tracing discrepancies to source systems
Trace each discrepancy from the settlement report to the processor record, payment gateway, acquiring platform, and merchant order or ledger system. Use stable identifiers, such as transaction IDs, authorization codes, retrieval reference numbers, and settlement batch numbers, to maintain an auditable link between records.
Compare event timestamps and processing statuses across systems. This helps distinguish timing differences from genuine errors, such as a capture recorded after a batch cutoff, a refund omitted from the settlement file, or a reversal posted in a later cycle. Reconciliation logs should preserve the relevant file names, batch dates, and processing versions.
Access controls and system-generated audit trails should support the investigation without altering original records. Where source data is unavailable, incomplete, or retained under a different identifier, document the limitation and obtain corroborating evidence from approved reports or processor documentation. These practices make Settlement reconciliation procedures more consistent and defensible.
Coordinating with payment processors and merchants
Effective coordination requires a documented communication process between the acquiring institution, payment processor, and merchant. Reconciliation teams should provide transaction identifiers, settlement dates, currency, disputed amounts, and relevant batch references when reporting an exception.
Payment processors can confirm processing status, scheme adjustments, interchange fees, reserves, chargebacks, and settlement timing. Merchants should validate order records, capture details, refunds, cancellations, and expected net amounts against the processor’s information.
Each discrepancy should have an assigned owner, response deadline, and audit trail. Teams should use secure channels and consistent case references, while avoiding the transmission of unnecessary cardholder data. Processor reports, merchant confirmations, and correspondence should be retained with the reconciliation record.
When the investigation identifies a processor or merchant error, the responsible party should confirm the corrective action and effective settlement date. Any manual adjustment must be approved under established controls and supported by evidence before it is posted.
Recording adjustments and supporting documentation
Adjustments should be recorded in a controlled reconciliation log that identifies the affected merchant, settlement date, transaction reference, amount, currency, adjustment type, and reason. Entries should distinguish processor corrections, fee changes, chargebacks, reserves, refunds, and internal posting errors.
Each adjustment should link to the original transaction and the corresponding settlement report or ledger entry. The record should state whether the amount increases or decreases the merchant balance and identify the employee or system that authorized and posted the change.
Supporting documentation may include processor correspondence, transaction-level reports, approval records, refund confirmations, chargeback notices, and calculation worksheets. Documents should be stored in a secure, searchable location with consistent naming and retention rules.
Within settlement reconciliation procedures, adjustments should follow segregation-of-duties controls. A preparer can investigate and propose the correction, while an authorized reviewer approves it before posting. The reconciliation record should preserve the original discrepancy, corrective action, approval evidence, and final resolution date.
Documenting Controls and Reporting Reconciliation Results
Settlement reconciliation procedures should be supported by documented controls that define responsibilities, approval requirements, reconciliation frequency, and escalation thresholds. Records should identify the staff or system performing each review, the reporting period covered, and the evidence retained for audit purposes.
Reconciliation reports should present transaction volumes, gross sales, processing fees, reserves, adjustments, chargebacks, refunds, and net settlement amounts. They should also distinguish matched entries from unresolved exceptions, allowing acquiring teams to assess financial exposure and settlement status accurately.
Each exception should have a unique reference, documented cause, assigned owner, resolution date, and supporting evidence, such as processor files, merchant records, or adjustment approvals. Any manual corrections should include an audit trail showing the original value, revised value, authorisation, and reason for change.
Management reporting may use defined metrics, including exception rates, ageing, recurring discrepancy types, and recovery amounts. Consistent formats and retention periods make Settlement reconciliation procedures easier to review, compare across periods, and demonstrate compliance with internal policies and applicable regulatory requirements.
Strengthening Ongoing Settlement Reconciliation Procedures
Review settlement reconciliation procedures at defined intervals to reflect changes in processor agreements, fee schedules, reserve policies, currencies, and payment channels. A controlled change-management process helps ensure updated rules are approved, documented, and applied consistently.
Automation can improve reliability by importing settlement files, validating required fields, applying matching rules, and flagging unusual variances. Automated controls should remain subject to periodic testing, access reviews, and manual oversight for complex cases or system failures.
Performance should be monitored through measures such as unreconciled transaction volume, exception aging, adjustment frequency, and reconciliation completion time. Trend analysis can reveal recurring issues, including delayed files, incorrect fee configurations, or failures in transaction-status updates.
Settlement reconciliation procedures should also include regular training, clear ownership, backup responsibilities, and documented escalation thresholds. Periodic reviews by compliance, finance, or internal audit teams can assess whether controls remain effective and whether supporting evidence is complete and traceable.