Defined review inputs
An agreed list of selected counters, available information sources, relevant checks and technical or visibility limitations.
Counter & POS exception verification
Give counter exceptions the context they deserve.
A transaction exception is a question to investigate, not a conclusion about an employee. CoreVision can discuss an agreed review process that connects observable counter activity with authorized reference information where available. The scope must distinguish what a camera shows from what a transaction record can establish.
Two different sources
Counter footage and POS data answer different questions.
A counter camera may show a customer interaction, an exchange of items or a cash drawer opening. It may not show the amount entered, a payment authorization, the reason for a refund or the final status of a transaction. Screen text within footage may be obscured or unreadable.
POS records can provide transaction details where access is authorized and a supported workflow is separately agreed. That might involve owner-provided exception information or a validated integration, but neither is assumed to be available. A camera connection is not a connection to the store's sales system.
The purpose of combining sources is to add relevant context and identify what remains uncertain. A visual mismatch may reflect timing, a legitimate process or missing information. It should not be described as fraud without an appropriate investigation.
- Visual observation: what is reasonably visible at the counter.
- Transaction information: what an authorized record actually states.
- Management review: the explanation, context and decision that follow.
Review prerequisites
Make the records comparable before relying on them.
Useful exception review needs relevant camera angles, usable footage, clear counter or register labels and sufficiently aligned timestamps. If a store has several registers, a transaction reference must identify the correct location. A timestamp alone may not resolve which interaction is relevant.
Provide the rules that explain the exception being reviewed: for example, which owner-supplied void or refund entries require context and what management expects staff to do. A written reference reduces ambiguity and helps avoid inconsistent judgments across shifts.
Access to playback, transaction information or supporting exports must be specifically authorized and technically confirmed. Public contact channels are not a place to send footage, customer records or login details. Data access and handling requirements should be settled during onboarding.
- Can the counter view show the activity being reviewed?
- Are camera and POS times comparable, including the time zone?
- Who can explain legitimate exceptions and approve follow-up?
- What source material is available through an authorized process?
Evidence & decisions
Report the observation without turning uncertainty into an accusation.
An exception note should identify the reference supplied, the camera and time reviewed, the visible sequence and any limitation. It should distinguish a confirmed observation from an interpretation or an unanswered question. If the relevant action is outside the view, that gap belongs in the report.
Where agreed and available, supporting material can help an authorized manager review the context. Delivery method, access permissions and handling must be specified; a website dashboard illustration does not establish that a customer portal or evidence archive is included.
This service does not reconcile accounts, certify a forensic investigation, determine disciplinary action or guarantee loss recovery. The owner remains responsible for checking the full circumstances and using the appropriate internal or professional process.
Define the deliverables
A useful scope ends with clear outputs.
Traceable exception notes
Site, register or reference details where supplied, reviewed times and a factual description of the observable activity.
A management follow-up
Questions needing explanation, actions taken under the agreed brief and any additional context the owner needs to obtain.
Common questions
A few things worth knowing.
Will CoreVision automatically connect to my POS system?
No. POS data access is separate from CCTV access. The platform, permissions, technical method and exact workflow must be assessed and expressly agreed before any integration can be represented as available.
Does a void or refund mean someone has done something wrong?
No. Exceptions can have legitimate explanations. Reporting should record the available information and visible context, leaving conclusions to a properly informed review.
Can you confirm cash totals from video?
Do not assume so. Camera angles and image detail may not support reliable amounts, and an apparent exchange does not establish the recorded payment outcome. Cash reconciliation requires the appropriate records and controls.
Your next step
Request a Free Risk Review ↗
Start with the exception you need to understand.
Describe your counter setup, POS platform if known and the review questions that matter. We can discuss the information and access a useful scope would require.