Last night's card payments
Every payment checked against the processor and the terminal
Register · invoiceAmountPOSProcessorTerminal
CybexAI SALES AUDIT
Sales audit and revenue integrity
for specialty retail
Cybex Retail Data Platform · AI Insights
Every card payment should match. Not all of them do.
Measured on live data at a 17-store specialty retailer, one month of card payments.
49,601
card payments in the month, across 17 stores
99.7%
matched to the processor automatically
152
exceptions left, 3.1 for every 1,000 payments
$6,505
charged with no sale, never paid, or sales rung twice
Found by hand, each one takes spreadsheets and phone calls. Most are never found at all.
From data to decisions, automatically.
One platform carries every payment from the till to the general ledger.
1
Data platform

POS, processor, terminal logs and bank in one model

2
BI analytics

Tickets, tenders, deposits and settlements by day

3
Statistical extract

Match keys, tolerances and exception patterns

4
Insight datasets

Card match, cash, returns and the GL journal

5
AI Insights viewer

Findings, exceptions and actions in plain language

6
Applications

Card reconciliation
Cash and deposits
Exception queue
GL journal

Starting with Sales Audit
Every fix tightens tomorrow's match
Fully automated: every payment matched every night, auditors work the exceptions
01 · Three-way match
POS, processor and terminal, matched.
Each card tender is matched to its processor charge on invoice, auth code or amount, with the terminal log as the tie-breaker.
Card match · 26 OctAll stores · 1,912 payments
Register · invoiceAmountPOSProcessorTerminalResult
49,399 one to one84 split tenders51 on register, date and amount
02 · Exceptions classified
Every exception gets a cause, and a fix.
The orders on either side, the tender used and the terminal log tell the system what happened. Auditors get the fix, not a mystery.
152 exceptions by cause, one month
Rows · amount at stake · the fix
03 · Root cause
Fix the process, not just the row.
Patterns by store, register and cashier show where coaching or a setup change stops tomorrow's exceptions.
Sales rung twice
58 times · 39 cashiers · 11 stores
Fix: void the first order, coach keyed card tenders
Sale abandoned after approval

27 customers were charged with no POS payment: the terminal approved, then the sale was left. 13 at one store.

Fix: find the sale or refund the customer
Two registers set up wrong

Their terminals send a counter instead of the POS invoice, so their payments can only match on auth code.

Fix: send the POS invoice to the terminal
04 · Close and post
The books post themselves.
Once a store's day is reconciled and approved, the journal is built and posted to the general ledger, balanced to the cent.
GL journal · Store 19 · 26 OctBuilt from the reconciled day
AccountDebitCredit
ReconciledApprovedPosted to GL
05 · AI Insights
Insights that explain themselves.
Payments, cash, returns and store close, reviewed and written up in plain language every morning.
Cybex AI Insights · Sales Audit
Insights
Card reconciliation
Exceptions by cause
Cash over and short
Returns and voids
Store close status
GL journal

Payments reconciliation · Oct 1 to 26

All stores · refreshed 06:00 · exceptions by cause
Matched to processor
99.69%
Open exceptions
152
Per 1,000 payments
3.1
AI insight
Automation and Optimization.
Every night it matches every payment, classifies every exception and prepares the journal. Your auditors start the day on the exceptions.
↑
Revenue integrity

Every card dollar accounted for

↓
Audit effort

From days of spreadsheets to a morning queue

↓
Customer disputes

Double charges refunded before the customer calls

→
Faster close

Month end on reconciled, posted numbers

CybexAI SALES AUDIT
Every sale. Every payment. Reconciled automatically.
cybexai.ca
cybexai.ca