To compare late-night sales fairly, give each service a consistent reporting window. If dinner starts Friday evening and ends early Saturday, a cutoff after the last orders can keep that service under Friday’s business date. A midnight cutoff instead splits it across two calendar dates. Neither changes the sales; the choice changes where they appear.
Start with the hours your restaurant actually operates, then check whether your POS, online ordering reports, and exports can use the same definition. A useful cutoff leaves enough room for late orders and closing adjustments without grouping the next service into the wrong day.
Map the service before choosing a cutoff
Write down when orders normally begin, when the last order can be placed, and when staff usually finish closing checks. Include weekends, late events, and delivery orders that may arrive after the dining room closes. Your reporting period needs to reflect the full operation, not just the hours printed on the door.
Next, decide what the business date should mean to your team. Many operators will want “Friday” to describe the service that began Friday, even when some guests paid after midnight. That makes it easier to compare one Friday service with another. A calendar-day view can still be useful when a bank statement or another system uses dates from midnight to midnight.
For example, a restaurant that stops taking orders at 2 a.m. might consider a 4 a.m. cutoff. The gap gives staff time to close checks and handle ordinary adjustments. But that choice needs another check: if breakfast orders can start before 4 a.m., those orders could land on the previous business date. Choose a boundary between services, not simply a convenient round hour.
Clarify which event assigns an order to a date. Is it the time the order was placed, accepted, paid, completed, or closed? A check opened at 11:45 p.m. and paid at 12:20 a.m. can move between dates depending on that rule. Split payments, refunds, voids, and tips can add further differences. Ask the vendor to show how each appears rather than assuming every report uses the same timestamp.
A restaurant POS system is one place to start the conversation. Bring an example of a check that crosses midnight and ask which date appears on the order detail, daily summary, and payment report.
Compare two reporting windows
Hypothetical example: A Friday dinner service runs from 6 p.m. Friday until 2 a.m. Saturday. Three orders total $180: $80 at 8 p.m., $40 at 11:30 p.m., and $60 at 12:30 a.m. All three are assigned by order time. The amounts are order sales before discounts, refunds, tips, and taxes; there are no such adjustments in this example. Fixed, variable, and exception costs are excluded, so these figures are not profit or an all-in operating cost.
The table compares the same orders under a midnight cutoff and a 4 a.m. cutoff. A business date begins at its stated cutoff and ends immediately before that cutoff the following day.
| Reporting choice | Friday business date | Saturday business date | What the numbers show |
|---|---|---|---|
| Midnight cutoff | $120 | $60 | The after-midnight order moves to Saturday. |
| 4 a.m. cutoff | $180 | $0 | All three orders stay with Friday service. |
These are totals for the three listed orders only, not the restaurant’s full Saturday sales. Both rows add to $180. The difference is the date label, not a change in demand.
For this schedule, 4 a.m. is a reasonable starting choice if no next-service orders arrive before then and the system assigns the relevant reports consistently. It preserves the complete dinner service for a Friday-to-Friday comparison. Confirm those conditions before adopting it. If the restaurant also sells breakfast at 3:30 a.m., a different boundary or a separate shift report may be more useful.
A cutoff alone does not define the sales measure. Decide whether the comparison uses gross order sales, net sales after discounts and refunds, or another figure. Record the treatment of tips, taxes, and delivery charges too. A consistent date window cannot fix a comparison in which one report includes items that another excludes.
Align reports, exports, and managers
Make a short list of everyone who uses the daily number: the closing manager, the person reviewing online orders, the bookkeeper, and any owner checking weekly performance. Ask each person which report they use and what they expect “Friday” to include. Two correct reports can disagree because they answer different questions.
Document the definition in plain language. For the hypothetical schedule above, that might read: “Friday business day runs from Friday at 4 a.m. up to Saturday at 4 a.m.; orders are grouped by order time.” Add the restaurant time zone, the sales measure, and the handling of refunds. If a system uses another timestamp, note that difference rather than giving both reports the same label.
Check these places together:
- Order and sales summaries: Does the selected date use the business-day boundary or calendar midnight? Can staff open an order detail to see why it was included?
- Payment reports: Is the date based on payment activity rather than order time? Can a payment or refund appear on a different day from the original sale?
- Online channels: Do direct online orders and other order sources follow the same date rule? Keep order source separate from dining option, such as pickup or dine-in.
- Exports and connected tools: Does an export carry the business date, the event timestamp, the time zone, or all three? Ask how receiving systems interpret those fields.
- Manager handoffs: Which number is used for the closing note, and who explains a correction made after the cutoff?
Fleksa’s partner portal shows sales and order summaries for a selected period, along with order-status views; available views and configuration can vary. Ask for a demonstration of the date and timestamp behavior you need. Review any integrations separately, including whether another provider’s reporting period can be changed to match.
Do not expect a sales summary to reconcile automatically with a bank deposit. Sales and deposits measure different things, and payment timing, refunds, and fees can affect the comparison. Ask how the reports connect, and consult a qualified adviser when you need accounting or tax treatment.
Once the reporting period is settled, you can use it as a foundation for other comparisons. The guide to comparing labor hours with sales by shift covers a different decision: relating staffing to sales within a defined shift.
Test a date change before relying on it
Ask the vendor to walk through the proposed cutoff using the restaurant’s local time zone. Confirm whether the setting is per location and what happens if a business has locations in different time zones. Ask whether reports show local time, another time zone, or a converted timestamp in exports.
Daylight saving time deserves a specific check. On a clock-change night, an hour can be skipped or repeated in places that observe the change. Ask how the system distinguishes events in a repeated hour, which time zone information is retained, and how the daily total is assigned. Also ask what happens in locations that do not change clocks. The answer should cover both the on-screen report and any export you depend on.
Before making a live change, request a simulated walkthrough in a sandbox or other non-production environment. Use sample orders just before and after midnight and just before and after the proposed cutoff. Include a check opened on one side of the boundary and closed on the other, plus a sample refund. Simulation should not create a real card payment, guest message, or courier dispatch.
Compare the sample order details with the daily summary and any available export. The acceptance criteria should be written before the walkthrough: each sample must appear on the expected date under the agreed timestamp rule, and the listed sales must reconcile to the sample orders under the agreed sales definition. If a payment report intentionally uses payment time, label and check it against that separate rule rather than expecting it to match the order-date report.
Then ask how a setting change affects historical reports. Does it recalculate past dates, apply only going forward, or differ by report? Record the effective date and preserve the old definition alongside any prior exports you need. Avoid comparing an old midnight-based Friday with a new 4 a.m.-based Friday as if they covered the same hours.
If you proceed to a live service pilot, agree on the start date, responsible manager, reports to review, and a way to revert if the results are confusing. Review normal service activity after closing; do not create a real payment, guest message, or courier dispatch merely to test the setting. Investigate differences before using the new daily number for decisions.
Bring your proposed cutoff, timestamp rule, and sample checks to a restaurant management software evaluation. Ask the provider to show the workflow and identify any report or connected tool that needs a different definition.
Frequently asked questions
Should every restaurant use a 4 a.m. cutoff?
No. Choose a quiet boundary between services. A 4 a.m. cutoff may suit a late dinner service, but it can misclassify early breakfast orders or fail to accommodate unusually late closing activity.
Does changing the cutoff change total sales?
It changes which business date receives an included order, not the order’s value. Totals for individual dates can change even when the combined sales over the full period stay the same, provided the same transactions and sales definition are included.
Why might a payment report still show a different date?
A payment report may group activity by payment time while an order report uses order time. Ask the provider which timestamp each report uses and how refunds and split payments are shown.
