WEIMI INSIGHTS / REPORTING ACCURACY
Align transaction times, reporting cut-offs and payment settlement periods before comparing daily performance.
CLOCK
Know the time zone attached to each record.
CUT-OFF
Use the same start and end boundaries.
STATUS
Separate sale time from upload and settlement time.
Before investigating a difference in daily totals, confirm that the reports cover the same transactions, time zone and status.
01 / BUYER NOTES
A vending record may show purchase time, server receipt time or another event timestamp. The payment provider may use its own reporting zone. Ask what each field means and whether the displayed time is converted for the account user.
Record those definitions in the reporting procedure. A label reading “today” is not precise enough for a fleet operating in several regions. The person exporting the file should know which date boundary the system applies.
02 / BUYER NOTES
Choose the reporting basis that fits the business and keep it explicit. A local trading day may be useful for site operations, while finance may need another consolidated period. Neither should be silently substituted for the other during reconciliation.
When comparing two systems, use matching start and end times and understand whether the endpoint is included. Pay attention to overnight activity. A purchase near midnight can appear on different calendar dates without either system having lost it.
03 / BUYER NOTES
Some systems may upload records after connectivity returns. Confirm whether a delayed transaction is assigned to the original purchase date or the upload date in each report. A report exported too early may not contain every record for the period.
Check how the system handles local clock changes and time-zone updates. Do not manually shift timestamps in a spreadsheet without retaining the original data and documenting the conversion. For a persistent discrepancy, give support specific transaction references rather than only two totals.
04 / BUYER NOTES
The bank deposit is not necessarily the total of the same calendar day’s purchases. Settlement timing, fees, refunds and adjustments can affect the amount and period. Use the payment provider’s definitions and reports to reconcile these movements.
Build a small test using known transactions around the reporting boundary. Confirm where each one appears and record the result. This gives the team a reference when a future daily report looks different, without assuming every mismatch is a machine fault.
Describes: When the customer transaction occurred.
Check: The time zone and transaction status used in the sales report.
Describes: When a record reached a connected service.
Check: How delayed records are assigned to reporting periods.
Describes: When the payment provider processes or remits funds.
Check: Fees, refunds, adjustments and the provider’s settlement rules.
PRACTICAL ANSWERS
The systems may use different time zones or reporting cut-offs. Confirm the timestamp definitions before treating the difference as missing revenue.
Only through a documented conversion that correctly handles the relevant zones and dates. A fixed offset may not be appropriate where clock changes apply.
Not necessarily. Settlement periods, fees and adjustments need to be reconciled separately from gross sales.
YOUR NEXT STEP
Request sample exports and explanations of time zones, statuses and settlement links. Use the information to build a reporting routine that remains consistent as more sites are added.
Explore equipment →Discuss your requirements →