Reconciliation Configuration Guide

Overview

Reconciliation ensures that transactions recorded in your internal systems match those reported by the payment gateway. This config setup automates the matching of records between:

• System A: Your internal transaction table.

• System B: Gateway transaction reports.

• System C: Bank settlement reports (Optional)

Once configured, the system automatically identifies matched and unmatched records, aiding in dispute resolution, settlement validation, and financial accuracy.

This guide explains how to create and manage reconciliation configurations using the Juspay Dashboard.

Creating a Reconciliation Configuration

To set up a reconciliation process:

Recon Config on Juspay Dashboard

Configuration Breakdown

1. Historical Check

historical_check :Defines the time window (in days) for which historical transactions will be considered during reconciliation.

This "historical_check": "30 days"instructs the system to only consider transactions from the last 30 days during the reconciliation run. Any transactions outside this window will be ignored. This is useful for avoiding unnecessary comparisons with very old data and improving performance.

2. Probable Match

probable_match :Indicates whether the system should attempt fuzzy/probable matching for transactions that don’t exactly align on deciders.

Here "probable_match": false indicates only transactions with exact matches (based on both the primary lookup and decider values) will be marked as matched.

If "probable_match": true, the system would try to find likely matches (e.g., slightly differing amounts within a buffer), but this is turned false here to avoid ambiguity.

3. Primary Lookup

primary_lookup: Defines the first condition for identifying a match between two systems.

This means the system first tries to match each record from System A and System B based on a common "payment_entity_txn_id". Only when these IDs match will deciders be applied.

4. Deciders

These define the rules for validating if two matched records (via primary lookup) are truly reconciled.

After a primary lookup match, the system compares the txn_amount field from both systems. If the values match exactly (because buffer is 0), the records are marked as reconciled.

5. Recon Trigger

"recon_trigger":Determines how the reconciliation process is initiated.

Here, "recon_trigger": "AUTOMATED"means reconciliation starts automatically once both System A (Merchant File) and System B (PSP File) are uploaded.

If this were "recon_trigger": "MANUAL", you would need to manually trigger "Run Recon" from Juspay Dashboard