Quick Troubleshooting for
End Of Reporting Periods
About
H&L’s reporting periods include Shift, Day, Week, Month and Year. These periods are finalised using corresponding End Of functions, such as End of Day or End of Week. While the periods typically reflect their calendar names, their actual duration depends on when they are processed. You can process these periods manually using the Processing application or automate them using a TimeSwitch.
This guide provides troubleshooting, mitigation and next-step advice to help resolve common issues encountered when processing reporting periods. This includes:
If the steps in this guide do not resolve your issue, or if the issue occurs regularly, please contact the H&L Support team for further assistance. You can log a support ticket via:
Phone: 1800 778 340
Email: support@hlpos.com
Chat: Live Chat
Client Portal: Click the Submit a Ticket button above.
For more information on processing End Of periods, see:
Verifying if End Ofs processed
Several symptoms may indicate an issue with processing reporting periods. These include:
- Processing Last Run dates are older than expected
- End of period reports failed to print or email
- Reports are blank (show $0 totals)
- Report totals are inflated (appear to combine multiple days, weeks, etc.)
The first step in troubleshooting End Of issues is to confirm whether the period processed. If it hasn’t, there’s no need to check email or printer issues, as no reports will be available to print or email.
Checking the Last Run times via Processing.exe
- Upon opening Processing, a “(Last Run: Day, Date)” appears below the End of Day, Week, Month and Year buttons.
- Greater detail, including End of Shift locations, is available under Options > View the dates of most recent runs.
Checking historical run times via Reports.exe
- In Reports, double-click a period-based report (e.g. Processing > Cash Balance) to open the report filter window.
- Select a Period Type radio button (Day, Week, Month or Year).
- Use the Period selection dropdown menu to check when periods have processed. Periods are displayed in the format “Date Time to Date Time [Period#]”. The first date and time indicate when the period started (i.e. when the previous period was finalised), and the second indicates when the current period was finalised. The top entry, shown as “Date Time to Today”, represents the current (unprocessed) period.
Note: Syswan troubleshooting is outside the scope of this guide. If reporting periods for a specific site are missing from Head Office, confirm the period processed at the site, run an UpdateHO, and contact the H&L Support team if further assistance is needed.
Issue: Period processing failed or didn’t run
The following causes can prevent reporting periods from processing.
Problem | Solution or workaround |
Server not running |
|
Windows updates on server |
|
End Of TimeSwitches |
|
TransServer or PosController stuck on “Locked: True" |
|
Forgot to run manually |
|
If your end of period failed to process and you believe the cause has been resolved, you can choose to rerun it or allow it to combine with the next scheduled run. For guidance on making this decision, see: Decision: Reprocess or consolidate a missed period.
Issues: End of period report printing
The following problems can prevent end of period reports from printing, even if the End Of period has successfully processed.
Problem | Solution or workaround |
Report printer issues |
|
Default printer |
|
Configuration |
|
Processing > Print Last |
|
If you need to reprint reports, you can:
- Use Print Last in Processing – This attempts to reprint reports using the configuration in place when the period was finalised. It uses the then-default printer. If that printer is no longer available, this option will not work.
- Regenerate reports via Reports.exe – Open the required report for the relevant period and print it manually. These reports can be sent to any currently available printer, but each one must be selected and printed individually.
Issues: End of period report emailing
The following problems can prevent end of period reports from being emailed, even if the End Of period was successfully processed.
Problem | Solution or workaround |
Internet Access |
|
Email Service |
|
Configuration |
|
Junk or spam folders |
|
Default printer |
|
If the emailing issue has been resolved and reports need to be re-sent, you must manually attach the PDF files to an email and send them to the intended recipients. There is no automated option to re-send reports.
You can obtain the reports from:
- The PDF export directory – Confirm the directory in Processing > Options > End Of > Exports
- Reports.exe – Regenerate the required reports for the relevant period and save them as PDF files
If needed, you can confirm recipient email addresses from:
Utilities > Company Info > Mail Server Settings > Email Template > End of Reports
[Reference Visual]
Issues: Report figures
This section covers issues with totals and values shown on end of period reports.
Problem | Solution or workaround |
Combined periods |
|
Blank / $0 totals on reports |
|
Reporting variances |
|
If blank figures were caused by End of Shift not being run, you can either rerun End of Shift followed by End of Day, or allow the data to combine with the next scheduled period. For guidance on this decision, see: Decision: Reprocess or consolidate a missed period.
If data has been combined in a single processed period, it cannot be separated within H&L. However, your bookkeeper or accountant may be able to split the data in your accounting software. Printed Y-Reads may provide approximate totals for individual days within the combined period.
Decision: Reprocess or consolidate a missed period
If an End Of period was not processed or did not process correctly, and the cause has been identified and resolved, you have two options for how to proceed. The same applies if End of Shift was not run before End of Day, resulting in $0 totals.
- Reprocess the missed or problem period now, making sure to run End of Shift first if it was also missed before End of Day.
- Leave the missed period to be processed together with the next run of the same period type, consolidating the figures into a single reporting period.
The best approach may depend on when the issue was detected (e.g. before or after trade resumed) or the preference of your bookkeeper or accountant.
Here are some points to consider when deciding which option is best for your venue:
- For End of Shift and End of Day, if the issue is caught before trade begins, it is usually preferable to reprocess both immediately. This will re-finalise the period and produce the reporting figures you would expect if nothing had gone wrong.
- Similarly, for End of Week, Month or Year, reprocessing immediately, if caught before the next EOS or End of Day runs, will result in clean period totals that reflect expected trading data.
- If the issue is caught later (e.g. mid-trade or the mid-week), the current or following days’ sales will be included in the current trading period when it is processed. In such cases, it may be simpler to allow one combined period rather than splitting the data into two uneven periods.
- Example: End of Shift and End of Day did not run and the issue wasn't noticed until midday the next day. Reprocessing both immediately would create a day period with 1.5 days of sales figures and the next with only 0.5 days. In this situation, it may be preferable to allow the period to roll forward and process as a single two-day period at the next scheduled time.
- Sometimes, having uneven periods is still preferable to skipping the period entirely. For example, processing End of Year with 380 days one year and 350 the next is likely better than waiting with no approximate yearly reporting until the following year.
Reference Visuals
- Windows Update > Update History
- Processing > Print Last
- Utilities > Company Info > Mail Server Settings > Email Templates
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article