> ## Documentation Index
> Fetch the complete documentation index at: https://guide.garde.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Close out the day

> Finish the day and review closing reports.

Every downstream number (sales journals, labor cost, the P\&L) assumes each business day was actually finished. **End of Day** is where that happens. Two pages in the sidebar: **Close Out Day** and **Closing Reports**.

## Close out the day

When the store is done:

1. Open **End of Day → Close Out Day**.
2. Walk the closeout: confirm the day's sales, payments, and totals against what the register says.
3. Resolve anything flagged before you finish. A mismatch caught tonight is a two-minute fix; the same mismatch found at month-end is an archaeology project.

Do it the same night. A close done at 11pm takes five minutes; a close reconstructed a week later takes an hour.

## Review closing reports

**Closing Reports** holds the reports for past days. Use it to:

* Confirm a specific day's numbers when accounting asks.
* Compare closes across days when something looks off.
* Verify the close actually happened. Unclosed days are how books drift.

## Know-how

* The business day boundary follows your location's closeout hour, so a 1 AM check lands on the right day. Late-night store with days splitting wrong? Get the closeout hour fixed in settings.
* Closes feed the [sales journals](/accounting/overview). An unbalanced journal often traces back to a day that closed with an unresolved flag.
* Rule of thumb: every business day gets closed before the next one starts. No exceptions, no batching Sundays.