Control the retail audit day, from transaction validation and store close to payment reconciliation, approved corrections, and confirmed financial posting.
Cybex Sales Audit brings transaction controls, reconciliation, and exception handling into the retail operating routine. Auditors investigate and document findings, store teams provide local evidence, and finance approves the changes that affect the books.
The module uses connected data from the Sales Audit Data Platform. Its focus is the work people perform: what is missing, what differs, who owns the next action, and whether the result has been accepted downstream.
Deployment scope is configured around your source systems, policies, roles, and operating schedule. Confirm connector coverage and enabled automation during discovery.
Apply configurable controls to the transactions received from stores and digital channels.
Track the status of each store and business date, with a clear owner for outstanding work.
Follow customer payments through processor settlement and bank receipt.
Move from a finding to an evidenced resolution in one operational queue.
Control corrections and preserve the original evidence behind each decision.
Release approved activity through configured accounting mappings and verify the result.
Connect the order, fulfillment, payment and return across retail channels.
Focus review on unusual patterns while mandatory controls remain in force.
Organize the queue by business date, financial exposure, severity, age, and ownership. Open a finding to inspect linked evidence, distinguish a source-data error from an operating issue, and record a correction or an explained exception.
| Finding | Evidence to review | Next action | Owner |
|---|---|---|---|
| Missing register feed | Expected register list, source totals and last received batch | Request recovery; keep completeness blocker visible. | Data operations |
| Settlement difference | Payment events, fee schedule, refund records and bank receipt | Explain or escalate the remaining amount; record matching evidence. | Reconciliation analyst |
| Unusual override pattern | Source receipts, promotion context and prior findings | Review the supporting transactions and record the outcome. | Audit analyst |
| Rejected journal | Approved adjustment, account mapping and ERP response | Correct through the authorized process and confirm accepted delivery. | Finance |
Cases can group related findings without losing their individual rule history. A proposed adjustment remains distinguishable from an approved change, and closing a case requires a documented outcome.
Identify expected stores, registers and feeds. Surface missing or rejected activity before approval.
Reconcile cash and tenders, investigate blocking findings, and obtain supporting evidence.
Apply authorized corrections, revalidate, and release the approved posting units.
Track receiving-system acceptance, unresolved settlement items, and controlled retries.
Store close and bank settlement have different completion dates. Keep pending receipts visible after the store-day is approved. Reopening a closed day records who authorized it, why, and which adjustments followed.
Rank unusual returns, overrides, discounts, and recurring variances against relevant store, channel, season, and promotion context. Present the contributing factors and linked transactions so the auditor can assess the finding.
Mandatory validation, balancing, and approval checks stay in force regardless of a score. A high score is a reason to investigate. Reviewer dispositions feed a controlled evaluation process before rule or model changes are released.
| System | Purpose in the module | Confirm during scoping |
|---|---|---|
| POS and order management | Transaction detail, sales lifecycle, returns and expected activity. | Source identifiers, business dates, channel coverage and delivery schedule. |
| Payment processors and banks | Settlement detail, adjustments and received funds. | Merchant/account scope, fee data and settlement calendars. |
| Merchandising and customer liabilities | Pricing references, inventory movements, gift cards and loyalty activity. | Reference ownership, effective dates and correction responsibilities. |
| ERP and finance | Account mappings, approved postings and receiving documents. | Posting ownership, approval rules and acknowledgment handling. |
| BI and AI Data Platform | Governed audit datasets, shared measures and contextual features. | Data quality, lineage, source freshness and version history. |
Batch or intraday processing is agreed per source. Near-real-time availability depends on the connected systems and deployment; the workbench should show freshness and completeness rather than imply a universal refresh rate.
Explore the warehouse model, BI measures, and AI feature foundation.
| Role | Primary responsibility |
|---|---|
| Audit analyst | Investigate cases, document evidence and propose corrective action. |
| Store manager | Confirm counts, explain local activity and provide supporting records. |
| Audit manager | Own control policy, assignments, escalations and audit-team performance. |
| Finance approver | Approve sensitive accounting changes and verify posting acceptance. |
| Data operations | Monitor source delivery, data quality and recovery of failed processing. |
| Analytics and model owner | Evaluate features, reviewed labels and model performance before release. |
Establish baselines for the stores, channels, and tenders in scope. Assess improvement using on-time store close, aged unresolved value, case resolution time, accepted postings, and actionable findings among reviewed ML alerts.
Report confirmed recoveries and measured staff time separately. Validate processing capacity on representative volumes and infrastructure. Targets are agreed for the deployment rather than presented as universal accuracy, throughput, or ROI promises.
Agree on stores, tenders, source coverage, roles, controls, and success criteria.
Map source data and reconcile representative periods with existing records.
Run alongside current practice and verify approvals, exceptions, posting, and recovery.
Evaluate ML in observation mode, review outcomes, and authorize the next scope.
Schedule and rollout readiness depend on source access, integration gaps, and control requirements. The data-platform acceptance plan defines the technical evidence needed before operational rollout.