# Counter Sale to Reconciled Work Period

This workflow follows a counter sale from the cashier’s cart through tender, receipt, inventory review, operating reports, and work-period close. It shows why checkout is only the first control point: the business must still explain stock movement, tender totals, deposits, payouts, returns, and material differences.

> **Demonstration notice:** All displayed names, identifiers, amounts, contact information, and transactions are fictional. Tender results are seeded test states; no live card, ACH, or EMV request is made.

<h2 id="bkmrk-glance">Workflow at a glance</h2>

| | |
|---|---|
| **Outcome** | A completed sale reviewed within its work-period cutoff |
| **Starts with** | An open workstation, drawer, warehouse, and work period |
| **Ends with** | Close evidence and reports traced to source transactions |
| **Primary roles** | Cashier, shift lead, accounting reviewer |
| **Brisk areas involved** | POS, Sales, Inventory, Cash Drawers, Accounting, Reports |
| **Common businesses** | Retail, parts counters, farm stores, service counters |
| **Approximate handoffs** | Two |

<h2 id="bkmrk-why">Why this workflow matters</h2>

A receipt confirms what the cashier finalized, but it does not explain the whole period. Supervisors still need to compare tender types, deposits, payouts, returns, cash activity, and over/short entries with the saved sales.

Brisk keeps those records available under one operating cutoff. That lets staff investigate a difference at its source instead of changing a close total to make it look correct.

<h2 id="bkmrk-prerequisites">Before you begin</h2>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/sales-point-of-sale-workspace.png" alt="Brisk Point of Sale workspace prepared for a fictional counter transaction." loading="lazy" style="max-width:100%;height:auto;"><figcaption>The cashier confirms workstation, drawer, customer, and warehouse context before scanning items.</figcaption></figure>

- Required: configured workstation, cash drawer, warehouse, open work period, saleable items, tax setup, and cashier permissions.
- Required: an approved walk-in customer or the correct named customer.
- Optional: barcode scanner, receipt printer, and sandbox terminal.
- The [Offline POS Queue](https://help.brisksystems.us/link/2952#bkmrk-overview) is a recovery tool, not the normal successful path.

<h2 id="bkmrk-steps">End-to-end steps</h2>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/sales-customer-order-draft.png" alt="Fictional sale DOC-SALE-1001 showing item rows and transaction totals." loading="lazy" style="max-width:100%;height:auto;"><figcaption>A saved sale preserves lines, pricing, tax, payment, and fulfillment context after checkout.</figcaption></figure>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/article-modelsalescashdrawer-list-cash-drawers.png" alt="Cash Drawers list used to identify the drawer assigned to the fictional register." loading="lazy" style="max-width:100%;height:auto;"><figcaption>Drawer identity matters because tender activity must be reviewed against the correct physical till.</figcaption></figure>

1. **Cashier — confirm operating context.** Open [Point of Sale](https://help.brisksystems.us/link/2953#bkmrk-sale). Verify workstation, warehouse, open work period, and the [Cash Drawer](https://help.brisksystems.us/link/2736#bkmrk-overview) that matches the physical till.
2. **Cashier — build the cart.** Select the authorized walk-in or named customer. Scan or search two or three stocked items, then confirm quantity, unit, price, discount authorization, tax, fulfillment, and total.
3. **Cashier — accept the actual tender.** Select cash or the supported test tender, verify references, and finalize once. Do not retry an uncertain processor attempt until the sale and provider history have been checked.
4. **Cashier — verify completion.** Review the completed [Sale](https://help.brisksystems.us/link/2746#bkmrk-detail) and receipt. Confirm the displayed payment and fulfillment states match what happened, then review item history for the processed inventory effect.
5. **Shift lead — review the period.** Compare sales, tenders, cash, deposits, payouts, returns, and over/short activity. Use [Work Period Reports](https://help.brisksystems.us/link/2951#bkmrk-report) with one deliberate cutoff.
6. **Shift lead or accounting — close after exceptions are resolved.** Use [Close Accounting Periods](https://help.brisksystems.us/link/2965#bkmrk-day) to close the intended work period. A closed period is not automatically reconciled; retain the report and explanation for any approved variance.

<h2 id="bkmrk-connected">What Brisk keeps connected</h2>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/article-screenreportswork-period-report-date-range-report.png" alt="Work Period Reports date-range screen for the deterministic documentation period." loading="lazy" style="max-width:100%;height:auto;"><figcaption>Apply one defined cutoff before comparing sales, tenders, deposits, and exception totals.</figcaption></figure>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/article-modelsalessale-list-pos-sale-list.png" alt="Sales list containing fictional documentation transactions for work-period review." loading="lazy" style="max-width:100%;height:auto;"><figcaption>The sales register supplies detail behind the period totals.</figcaption></figure>

| Action | Result or downstream record | Where to verify it |
|---|---|---|
| Finalize the cart | Saved sale, lines, totals, tender and receipt context | Sale detail and receipt |
| Process fulfillment | Item movement for qualifying rows | Item inventory history |
| Record cash, deposit, payout, or return | Period activity with its own source record | Drawer and period reports |
| Close the work period | Saved cutoff and close detail | Work Period detail and close reports |

<h2 id="bkmrk-handoffs">Handoffs and controls</h2>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/article-workflowaccountingperiod-close-day-close-workperiod.png" alt="Close Work Period screen for a fictional documentation work period." loading="lazy" style="max-width:100%;height:auto;"><figcaption>Closing creates a boundary after staff resolve material differences; it does not reconcile inaccurate source records.</figcaption></figure>

The cashier supplies completed sales and physical tender evidence. The shift lead reviews the drawer and exceptions; accounting relies on the saved cutoff and source records. Supervisory overrides require the authorized user—never shared credentials. The sale stays authoritative for checkout while the work period supplies the cutoff.

<h2 id="bkmrk-exceptions">Exceptions and safe corrections</h2>

- Wrong item before finalization: correct the cart.
- Duplicate-submission uncertainty: search Sales and provider history before retrying.
- Completed sales error: use the supported return or void tied to the original transaction.
- Offline ticket: inspect each queued item and live Sales before retrying; do not use **Retry All** without individual verification.
- Drawer difference: trace deposits, payouts, returns, tender selection, and timestamps. Closing does not repair missing activity.

<h2 id="bkmrk-related">Related documentation</h2>

### Start here

- [Point of Sale](https://help.brisksystems.us/link/2953#bkmrk-overview)

### Continue with

- [Sales](https://help.brisksystems.us/link/2746#bkmrk-overview)
- [Cash Drawers](https://help.brisksystems.us/link/2736#bkmrk-overview)
- [Work Periods](https://help.brisksystems.us/link/2595#bkmrk-overview)

### Related controls and reports

- [Work Period Reports](https://help.brisksystems.us/link/2951#bkmrk-overview)
- [Offline POS Queue](https://help.brisksystems.us/link/2952#bkmrk-overview)
- [Close Accounting Periods](https://help.brisksystems.us/link/2965#bkmrk-day)

<aside class="brisk-workflow-cta" aria-label="Brisk demonstration">
<h2>Could Brisk Simplify This Process for Your Team?</h2>
<p>See how this workflow could be configured around your records, permissions, approvals, and reporting requirements.</p>
<p><a href="https://brisksystems.us/point-of-sale-software/">Request a focused Brisk demonstration</a></p>
</aside>