Booking vs PG Reconciliation: A Complete Guide for Finance Teams

Booking vs PG reconciliation is the process of comparing booking records with payment gateway transactions.

For businesses that accept online payments for bookings, this reconciliation is an important finance control. A booking system may show that a customer has paid for a booking, while the payment gateway report may show a different amount, missing transaction, failed payment, or unmatched merchant transaction ID.

This reconciliation helps finance teams confirm whether every paid booking has a corresponding payment gateway transaction.

It answers questions such as:

• Are all paid bookings present in the PG file?
• Are all payment gateway transactions linked to valid bookings?
• Do booking payment amounts match PG amounts?
• Are gateway payment IDs mapped correctly?
• Are booking dates and PG transaction dates aligned?
• Which bookings or payments need review?

For travel companies, ticketing platforms, appointment-based businesses, hospitality businesses, and any booking-led platform, Booking vs PG reconciliation helps ensure that collections are complete and accurately recorded.

What Is Booking vs PG Reconciliation?

Booking vs PG reconciliation compares two sides of data.

Side A: Booking File
This represents the internal booking records. It contains the booking date, gateway payment amount, and gateway payment ID.

Side B: PG File
This represents the external payment gateway report. It contains the payment amount, merchant transaction ID, and transaction date.

The goal is to match the booking-side payment record with the payment gateway-side transaction record.

In this workflow, matching is mainly based on:

• Gateway payment ID
• Merchant transaction ID
• Booking payment amount
• PG amount
• Booking date
• PG transaction date

The booking file uses GatewayPaymentId, while the PG file uses merchantTranID. These fields are used to connect internal bookings with payment gateway transactions.

Why Booking vs PG Reconciliation Matters

A booking is not financially complete until the payment is confirmed, captured, and correctly reflected in the payment gateway report.

When booking data and PG data do not match, finance and operations teams may face issues such as:

• Booking marked paid internally but missing in the gateway
• PG payment received but booking not found
• Amount mismatch between booking and payment gateway
• Duplicate payment entries
• Failed or reversed payments treated as successful
• Payment captured against the wrong booking
• Delayed settlement visibility
• Customer support disputes
• Month-end closing delays

Booking vs PG reconciliation helps finance teams identify these differences before they affect revenue reporting or customer operations.

Reports Involved

Side A: Booking File

The booking file represents the internal transaction view.

Important fields include:

• Booking Date
• Gateway Payment Amount
• Gateway Payment ID

The booking date shows when the booking was created or recorded. The gateway payment amount shows the payment value expected for the booking. The gateway payment ID acts as the payment reference used to match with the PG file.

This report shows what the business expects to have collected.

Side B: PG File

The PG file represents the payment gateway’s transaction view.

Important fields include:

• Transaction date
• Amount
• Merchant transaction ID

The amount shows the transaction value recorded by the gateway. The merchant transaction ID is the external reference used to connect the PG transaction to the booking record.

This report shows what the payment gateway has actually recorded.

How Matching Typically Works

Booking vs PG reconciliation usually works by comparing reference, amount, and date.

A typical matching process looks like this:

1. Booking file is uploaded.
2. PG file is uploaded.
3. Booking GatewayPaymentId is compared with PG merchantTranID.
4. Booking GatewayPaymentAmount is compared with PG amount.
5. Booking Date is compared with PG transaction date.
6. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• Booking file shows a gateway payment amount of ₹3,500 with a gateway payment ID.
• PG file shows an amount of ₹3,500 with the same merchant transaction ID.
• The transaction is treated as matched.

If the reference matches but the amount differs, it becomes an amount mismatch.

If a booking exists but no PG transaction is found, it becomes a booking-only exception.

If a PG transaction exists but no booking is found, it becomes a PG-only exception.

Common Exceptions in Booking vs PG Reconciliation

1. Booking Missing in PG File

This happens when the booking file shows a payment, but the PG file does not contain a matching transaction.

Possible reasons include:

• Payment failed after booking creation
• Booking was incorrectly marked as paid
• Gateway report is incomplete
• Wrong PG report period was used
• Gateway payment ID is missing or incorrect
• Transaction was processed through another gateway

This exception is important because the business may believe payment was collected when the gateway does not confirm it.

2. PG Transaction Missing in Booking File

This happens when the PG file contains a transaction, but the booking file does not have a matching booking.

Possible reasons include:

• Booking creation failed after payment
• Callback or webhook failed
• Payment was captured manually
• Transaction belongs to another booking system
• Duplicate PG record exists
• Booking report is incomplete

This can create customer support and accounting issues because money may have been received without a valid booking record.

3. Amount Mismatch

Amount mismatches occur when the gateway payment ID and merchant transaction ID match, but the payment amount is different.

Possible causes include:

• Partial payment
• Discount or coupon treatment difference
• Convenience fee included on one side
• Refund or reversal impact
• Rounding difference
• Incorrect booking amount
• Gateway-side adjustment

Amount mismatches should be reviewed carefully because they directly affect collections and revenue reporting.

4. Date Difference

The booking file uses Booking Date, while the PG file uses transaction date.

These dates may differ due to:

• Late-night bookings
• Payment processing delay
• Gateway reporting cutoff
• Booking created before payment capture
• Time zone differences
• Transaction updated after booking creation

A date difference is not always an error, but it should be visible during reconciliation.

5. Duplicate Transactions

Duplicates may occur in either the booking file or PG file.

Examples include:

• Same booking appearing twice
• Same merchant transaction ID appearing twice
• Duplicate PG export
• Retry payment captured more than once
• Multiple payments attempted for one booking

Duplicate transactions can overstate collections or create false mismatches.

6. Incorrect Payment Reference

Booking vs PG reconciliation depends heavily on the quality of the payment reference.

Reference issues may happen when:

• Gateway payment ID is blank
• Merchant transaction ID is stored differently
• Prefixes or suffixes are added
• Payment ID is truncated
• Different systems use different reference formats
• Manual edits change the reference

A good reconciliation process should clean and compare references consistently.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile booking files and PG files manually in Excel.

The typical process includes:

1. Exporting the booking file.
2. Downloading the PG transaction file.
3. Cleaning payment IDs.
4. Standardizing dates and amounts.
5. Running lookup formulas.
6. Comparing booking amounts with PG amounts.
7. Identifying missing and mismatched records.
8. Preparing an exception report.

This becomes difficult as transaction volume increases.

Common Excel challenges include:

• Broken lookup formulas
• Wrong reference column selected
• Date format issues
• Duplicate records missed
• Manual copy-paste errors
• Amount mismatches not categorized clearly
• No clear audit trail
• Repeated effort every reconciliation cycle

A structured reconciliation workflow reduces these risks and improves consistency.

What a Good Booking vs PG Reconciliation Process Should Include

A reliable Booking vs PG reconciliation process should include:

• Correct booking file selection
• Correct PG file selection
• Clean gateway payment ID mapping
• Standardized amount comparison
• Date comparison between booking and PG records
• Fully matched transaction reporting
• Partial match or amount mismatch reporting
• Booking-only exception reporting
• PG-only exception reporting
• Duplicate detection
• Audit-ready output

The output should help finance teams quickly understand which transactions are correct and which need action.

How Cointab Helps

Cointab can help finance teams automate Booking vs PG reconciliation by comparing internal booking records with payment gateway transactions.

Finance teams can map the required payment ID, transaction ID, amount, and date fields once and reuse the same setup for future periods.

Cointab helps teams:

• Upload booking and PG files
• Match Gateway Payment ID with Merchant Transaction ID
• Compare booking payment amount with PG amount
• Identify fully matched records
• Highlight amount mismatches
• Show booking-only and PG-only exceptions
• Review skipped or invalid records
• Download audit-ready Excel reports
• Reuse the workflow for recurring reconciliation

This reduces manual Excel effort and helps finance teams focus on unresolved exceptions.

Business Value

Booking vs PG reconciliation helps finance teams:

• Validate booking-level collections
• Identify missing or failed payments
• Detect payments without bookings
• Improve revenue accuracy
• Reduce customer payment disputes
• Speed up month-end close
• Improve audit readiness
• Reduce manual reconciliation work

It also helps operations and customer support teams resolve payment-related booking issues faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile bookings and PG transactions regularly
• Use gateway payment ID as the main matching reference
• Validate merchant transaction IDs carefully
• Review amount mismatches separately
• Track date differences across periods
• Check for duplicate payment IDs
• Investigate PG-only transactions quickly
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

Booking vs PG reconciliation helps finance teams confirm whether internal booking records match payment gateway transactions.

Because this reconciliation depends on gateway payment IDs, merchant transaction IDs, payment amounts, booking dates, and transaction dates, manual reconciliation can become slow and error-prone as volumes grow.

A structured process helps identify matched payments, missing bookings, missing PG transactions, amount mismatches, duplicate records, and timing differences.

With Cointab, finance teams can automate Booking vs PG reconciliation, reduce manual Excel work, and generate audit-ready reports for review.

Start your 14-day free trial with Cointab and automate Booking vs PG reconciliation without relying on manual Excel work. No credit card required.

Visit: https://www.cointab.net/