How to Consolidate Restaurant Reports With Different Day Cutoffs

When locations use different business-day cutoffs, combine their reports by assigning each transaction to the same defined comparison period. Keep each location’s own business-day report for closing and reconciliation, but do not add those daily totals together and assume they cover the same hours.

The practical choice is whether your reporting tools can produce a consistent period directly, whether someone must rebuild it from transaction-level records, or whether the locations need to keep separate totals. Test that choice with transactions around each cutoff before relying on a combined number.

Decide what the combined report needs to answer

Start with the decision the owner wants to make. A calendar-day view can answer how much was sold across the group on a particular date. A business-day view can help a manager close a late shift. Both can be useful, but they may include different transactions even when the reports carry the same date label.

Assign one person, such as the operations manager or bookkeeper, to own the combined report. That person should document the period, collect the location reports, check exceptions, and explain differences to the owner. Each location manager should remain responsible for checking their own close and flagging corrections.

Service patterns matter. A location that serves late may need a cutoff after midnight to keep one service together. An earlier-closing location may use a different boundary. Changing either cutoff just to make a report look consistent could make local closing harder. First ask whether the reporting process can translate both locations into a common window without changing how staff close.

Also agree on what the total measures. For example, decide whether sales are assigned by order creation, payment, or another timestamp, and apply that choice consistently. Keep deposits and fees separate from sales. Record how refunds, voids, and adjustments are handled rather than assuming every report treats them alike.

Build a common-period worksheet

The following is a hypothetical example. Both locations are in the same time zone. Location A closes its business day at 4:00 a.m.; Location B closes at 2:00 a.m. Each labels its business day by the date on which that period begins. The owner wants a calendar-day comparison for January 10: midnight at the start of January 10 up to, but not including, midnight at the start of January 11.

The table shows four sales around the end of that comparison period. Amounts are sales only; they do not include fixed operating costs, variable fees, or exception costs. Those costs are not part of this sales-total example.

For these four sales, the January 10 calendar total is $60: $40 plus $20. The other $55 belongs to January 11. Adding the displayed January 10 business-day amounts would give $115, but that is not the January 10 calendar total. The two local business-day windows also start and end at different times, so their full daily totals are not directly comparable to each other as equal time windows.

The owner’s decision in this example is to retain the local cutoffs for closing and use the midnight-to-midnight window for the group’s calendar-day report. The location managers check their local records. The operations manager assigns each sale to the agreed window and checks the combined total. If the tools cannot provide the necessary detail, the manager should not present the business-day sum as a calendar-day result.

For locations in different time zones, write down whether the group report uses each location’s local midnight or one shared time-zone boundary. Either choice can answer a useful question, but the report label must make the choice clear. A shared instant and a local calendar day are not the same comparison.

Choose how to consolidate the reports

There are three practical approaches. Ask each provider to demonstrate the exact period and fields you need before deciding which one fits.

Use a common-period report

Ask whether the system can show each location’s sales for the same start and end times, independently of its local business-day setting. Check which timestamp drives inclusion, whether locations can be combined, and whether the resulting detail can be reviewed. A selected-period summary is useful only if its boundaries and definitions match the question.

This approach may require less recurring staff work, but setup or additional access may affect the quote. Ask whether changing report settings affects local operations or guest-facing workflows; do not assume it does or does not.

Rebuild the total from transaction detail

If a common-period summary is unavailable, ask whether transaction-level records can be obtained with a unique identifier, location, timestamp, amount, and relevant status or adjustment. An authorized staff member can assign records to the agreed window and total them in a worksheet.

Budget for staff time to prepare, review, and correct that worksheet. Ask about any export, setup, or support charges, as well as recurring software charges. This method need not change the guest experience, but confirm that obtaining records will not interrupt service. It also depends on getting sufficient detail from every location; a daily total alone cannot reliably be split at midnight.

Keep local reports separate

If the necessary detail is unavailable or the manual work is too risky, keep the local business-day totals separate and label their different windows. This is a valid operating choice, but it does not produce a consistent calendar-day total. Use it for local close reviews, not as a precise group comparison.

Compare written quotes on the same basis: recurring charges, setup, staff effort, support, and the work needed when an exception occurs. A quoted processing fee is not the all-in cost of operating the reporting process. Ask a qualified adviser about contract or accounting treatment where needed.

Run a boundary check before relying on the total

Use a simulated set of records in a practice environment or a worksheet. The simulation must not create a real payment, guest message, or courier dispatch. If a provider cannot demonstrate in a safe environment, use existing records with suitable access controls or ask for a demonstration using the provider’s test data.

For the hypothetical worksheet above, the pass condition is that each of the four sales appears once in the combined two-day detail, with $60 assigned to January 10 and $55 to January 11. A sale immediately before the boundary must not also appear after it; a sale immediately after it must not be pulled into the earlier calendar day. Check records around both local cutoffs as well as midnight.

Ask the person running the check to retain the period settings, transaction identifiers, timestamps, amounts, and resulting totals. Check that the group result can be traced back to the location records. If a summary differs, identify whether the cause is a boundary, timestamp choice, status, refund, or another adjustment before changing the number.

Fail the check if a record is missing or duplicated, the time boundary is unclear, or the report cannot show enough detail to explain the result. Also flag a comparison as incomparable when two totals cover different windows or use different sales definitions, even if their arithmetic is correct.

For the manual fallback, have the report owner use available transaction detail to assign records to the agreed period, then have a second authorized person review the boundary items and totals. If detail is not available, publish separate labeled local totals instead of estimating a combined calendar figure. Document any correction and rerun the check after a configuration change.

Put ownership and access into the routine

Write a short reporting rule that names the time zone, start and end boundaries, timestamp, included sales and adjustments, and person responsible for review. Give the report a label such as “local calendar day” or “business day by location,” rather than relying on the date alone.

Decide who can view detailed transactions and who can change reporting settings. Review permissions with the people who administer access, and ask each vendor how its available roles fit the job. Keep a record of changes so a new cutoff or report setting does not quietly alter a comparison.

During a live service pilot, continue the existing close routine while the report owner checks the new output against normal records. Resolve discrepancies before using the new report for an owner decision. A simulation checks the boundary logic; a live pilot checks whether staff can maintain the process under actual service conditions.

Review the fields and period options in your current sales report, then compare the workflow with Fleksa’s restaurant management software. Ask Fleksa to demonstrate the applicable capabilities with your locations’ cutoffs and your chosen comparison period.

Frequently asked questions

Should every location use the same business-day cutoff?

Not necessarily. Different service hours may justify different local cutoffs. Use a consistent reporting window for group comparisons if the available records support it, while keeping local closing needs in view.

Can I add daily sales totals from two locations?

Only if the totals use compatible time windows and definitions for the question you are answering. A date label alone does not establish that the reports cover the same hours.

What if a vendor cannot split a daily total at midnight?

Ask for transaction-level detail that supports the split. If it is unavailable, keep the local totals separate and label their boundaries rather than presenting their sum as a calendar-day total.