What reconciliation is
Data reconciliation is the habit of comparing two sets of figures that should match, and explaining every difference. In iGaming, the usual pair is a total in your warehouse against the same total in the system of record, such as the PAM or a payment provider.
Why it matters
A report can be wrong without looking wrong. A game provider’s feed arrives half complete. A payment file is late. A change in a source system shifts a field. Nothing fails loudly, and the first person to notice is finance at month end, or a regulator reading a submitted figure.
Three kinds of check
- Source to warehouse. Does the total deposited for yesterday in the warehouse equal the total in the PAM?
- Warehouse to report. Does the report show the same total the warehouse holds?
- System to system. Does the PAM agree with the payment provider on settled deposits?
A simple daily routine
| Check | Example | Compare against |
|---|---|---|
| Control totals | Deposits, withdrawals, bets, wins per brand | The source system’s own totals |
| Record counts | Transactions loaded for the day | The count the source reports |
| Freshness | Time since the latest record per source | The agreed target |
| Duplicates | Repeated transaction IDs | Zero |
| Drift | A total that changed after it was reported | The previous run |
Run these automatically after every load, set a tolerance for each, and alert someone when a check fails.
What to do when a check fails
- Pause the reports that depend on the figure. A late correction is better than a wrong submission.
- Fix the cause, not the number. Find the missing feed or the changed field.
- Replay. Rebuild the affected reports from the raw data once the source is right.
- Keep the record. Note what failed, what you changed and when, so you can show it later.
Around migrations
Reconciliation matters most when you move platforms. Run the old and new systems side by side, compare balances and totals daily, and explain every difference before you cut over. Our guide to a data warehouse migration strategy walks through the steps.
How Dejta+ approaches it
Dejta+ reconciles totals against source, flags drift with a daily check, and can pause the reports that use a figure that does not match. Dejta Reporting keeps versions of each report and a catch-up queue for missed runs, and fingerprints every run so you can show what was produced. If you are planning a move, see data warehouse migration for iGaming.
