Travel Ledger
  • Welcome to Travel Ledger Help
  • Registering on the Platform
    • Registering as a New Company
    • Two-Factor Authentication (2FA) Setup Guide
    • Registering as a User
    • Updating User Profile
  • Managing Transactions
    • Bookings Organisation and Management
    • Updating Bookings (Accept/Reject)
      • Updating Booking (Accept/Reject) Manually
      • Updating Booking (Accept/Reject) through Buyer Download & Upload File
      • Reviewing Completed Settlements and Remittance Advice
    • Duplication Checks
    • Reviewing Remittances
    • Payment History Page
    • Uploading Bookings
      • Upload Manually
      • Upload by Data Delivery Methods
        • FTP setup guide
      • Reviewing Data Delivery
    • File Formats for Upload
      • Extended File Format (Full Version)
      • Extend File Format (Lite Version)
    • Seller returns file (Rec)
    • Scheduling payments
  • Exporting Data & Reconciliation
    • Reconciliation Best Practice
    • Exporting Data from Grid Displays
    • Scheduling Reports in Task Scheduler
  • Notifications
    • Notifications Overview
    • Configuring Notifications
  • Managing your Partners
    • Company List
    • Invite Partners to the Platform
      • Sending Individual Partner Invites
      • Sending Bulk Partner Invites
    • Commercial Link Creation
      • Payments Overview
        • Payment Profiles
        • Business Terms
        • Settlement Schedules
    • Managing Commercial Links
  • TL Pay Account
    • Registration Process - Revolut Grow
    • Registration Process - Nium/Clearbank
      • UK Application (KYB/KYC)
      • EU Application (KYC/KYB)
      • Step-by-Step Guide: KYB/KYC Form Completion
    • Funding your TL Pay Account
    • Commercial Links required
    • Settling via your TL Pay Account
    • Viewing TL PAY Activity
    • Withdrawals
    • Suppliers not cutover to TL PAY
  • Billing
  • Managing your Companies and Users
    • Managing your Companies
    • Suspending and Archiving Head Office and Branches
    • User Creation
    • User Management
  • Processing Entity Schemes
    • Refunds on the ABTA Scheme
  • Help and Support
    • Public Holiday Schedules
    • FAQs
      • FAQs - General Platform Queries
      • FAQs - Registration and Initial Set Up
      • FAQs - Transactions Area
      • FAQs - Uploading Files
      • FAQs - Payments and Commercial Links
      • FAQs - Admin
    • Glossary of Terms
    • Glossary of Notifications
    • Testing with Travel Ledger
    • Release Notes
      • Release 1.26.0 (12/10/2023)
        • Release 1.26.1 (19/10/2023)
        • Release 1.26.2 (26/10/2023)
          • Release 1.26.3 (03/11/2023)
          • Release 1.26.4(18/11/2023)
      • Release 1.25.0 (31/08/2023)
      • Release 1.24.0 (27/07/2023)
      • Release 1.23.0 (06/07/2023)
      • Release 1.22.0 (28/06/2023)
      • Release 1.21.0 (08/06/2023)
      • Release 1.20.0 (25/05/2023)
      • Release 1.19.0 (11/05/2023)
      • Release 1.18.0 (13/04/2023)
      • Release 1.17.0 (23/03/2023)
      • Release 1.16.0 (09/03/2023)
      • Release 1.15.0 (23/02/2023)
      • Release 1.14.0 (09/02/2023)
      • Release 1.13.0 (16/11/2022)
      • Release 1.12.0 (07/09/2022)
      • Release 1.11.0 (25/07/2022)
      • Release 1.10.0 (02/05/2022)
      • Release 1.9.0 (17/03/2022)
      • Release 1.8.0 (02/03/2022)
      • Release 1.7.0 (27/01/2022)
      • Release 1.6.0 (09/12/2021)
      • Release 1.5.0 (29/10/2021)
      • Release 1.4.0 (07/10/2021)
      • Release 1.3.0 (04/10/2021)
      • Known Issues
    • Still Need Help?
Powered by GitBook
On this page

Was this helpful?

  1. Managing Transactions

Duplication Checks

Travel Ledger supports the flagging of potential duplicate transactions in the Transactions>Bookings grid, prompting you to check if transactions are valid for payment.

Transactions will be flagged and highlighted in orange for partial matches and red where it looks to be a full match for a previously loaded transaction. Details as below:

  • When more than one transactions exists anywhere on the platform for the same combination of Booking Ref, Buyer, Seller, Trans type, currency code and Original Amount, TL will underline the transaction in Red

  • When more than one transactions exists anywhere on the platform for the same combination of Booking Ref, Buyer, Seller, Trans type and currency code, but with a different Original Amount, TL will underline the transaction in Orange

To validate the highlighted items, hover over text on red/orange underlined items will read:

Red = 'Duplicate(s) invoices with same Booking Ref/Amount exist(s)

Orange = 'Duplicate(s) invoices with same Booking Ref but different Amount exist(s)'

If a transaction has been previously rejected or ignored (voided) by a Buyer, it will not be flagged as a duplicate when reloaded by the Seller as no previous payment has been lodged against the previous iteration of the booking. However, if a booking is loaded in duplicate in the same cycle (review window) and the Buyer has rejected it, the duplicate versions will still be flagged to ensure the Buyer is aware of the potential conflict.

If there is any concern that the underline is in fact a duplicate, users should undertake further investigation with the Seller.

PreviousReviewing Completed Settlements and Remittance AdviceNextReviewing Remittances

Last updated 1 year ago

Was this helpful?