Why do my batch numbers look different?
We have standardized batch numbers to a unified format (MID-Date-BatchID) to ensure consistency across all reporting regions. This makes it easier to track specific batches across the Transaction Manager, Settlement, and Settlement Detail reports.
What is a "Settlement ID" and how do I use it?
The Settlement ID is a unique identifier provided by Global Payments that appears in both your Transaction Manager and Settlement Detail reports. You can use this ID to quickly reconcile your Lighthouse reports with your bank payout. Because one batch can be paid out across multiple deposits—and a single deposit can include transactions from multiple batches—the Settlement ID allows you to accurately map every transaction to its specific batch and corresponding bank deposit.
Why don't the transaction counts in my reports match?
With this update, they should match perfectly. The Settlement Report now pulls data directly from the Settlement Detail Report, which in turn sources 100% of its data from the Transaction Manager. This creates a single "source of truth" for all your financial data.
Can I see which transactions make up a specific settlement total?
Yes. In the Settlement Report, you can now select on the transaction count. This will automatically redirect you to the Transaction Manager with the correct filters applied, showing you the exact list of transactions included in that settlement.
What if I am missing historical batch data?
As part of this redesign, we are automatically backfilling any incomplete or missing batch entries identified during the reconciliation process to ensure your historical records are complete.
Why might a transaction status update be delayed in Lighthouse Business Manager (LBM)?
Transactions that are captured more than 7 days after they were originally created may not immediately reflect updated statuses in LBM. This is due to our standard 7-day data refresh cycle. Our data team performs a proactive monthly reconciliation to ensure these older transactions are synchronized.
What’s next?
This limitation will be resolved in Q2 2026 with the rollout of Near Real-Time data for all Canadian merchants.
Why doesn’t LBM show the updated status for some chip transactions?
In some cases, a bank may request a security upgrade during checkout. For example, if a customer initially taps or swipes their card and is then prompted to insert the chip (SCA: Security Card Authentications).
When this happens:
- The processor creates a new transaction record
- Settlement is tied to the new record (not the original attempt)
- LBM may not reflect the updated status of the initial transaction
We are actively working with the processor to resolve this issue.
How many transactions are affected by these limitations?
These limitations are estimated to impact less than 1% of total transactions.
Comments
0 comments
Please sign in to leave a comment.