Store Cash Close
Compare complete register sessions, counted cash, approved differences and unresolved late source activity in each drawer currency.
Close a store shift
Reconcile register cash with actual source activity and an independently reviewed close.
5 stages · 1 approval
Roles and responsibilities
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Identify the session
Match the source namespace, register, store, currency and actual start time. Link the opening float to existing cash custody instead of recognizing revenue. Only one active original source session is allowed. Imported checkout evidence retains its actual occurrence even while local accounting review is unresolved.
Reconcile the source activity
Verify the acknowledged event watermark and all source identities through the cutoff. Confirmed cash receipts, actual cash refunds and signed custody movements explain expected cash once. Card collections and processor payouts remain separate. Missing, contradictory or late evidence keeps the close open for investigation.
Count and submit
Record denominations and quantities in the drawer currency. A recount preserves the earlier count and explicitly selects one complete replacement set. The packet retains expected cash, actual counted cash and the difference. Staff cannot edit a total to conceal a variance or use an incomplete source manifest.
Approval required
Approve the closing packet
An independent Finance Manager reviews the frozen count, source completeness, custody movements and proposed variance accounting. The approver cannot be a counter, preparer or material editor. A zero difference still requires the same completeness and review. Changing any material evidence invalidates the decision.
Record the close
Execute only the approved difference or actual transfer against an eligible accounting period. Closing turnover never posts another sale, receipt or tax amount. The shift becomes Closed only when its exact required effects are confirmed. Later source facts create visible exceptions and linked correction work; closed counts remain intact.
Approvals and exception handling
1 approval required in this process
-
Approve the closing packet
Finance Manager signs · record the close waits
POSShifts, ApprovalDecisions, JournalEntries - Preserve original eventsExact revisions and independent decisions when a source changes.
- Recheck current entityCustomer and monetary or unit scope at execution.
- Keep failed, partialUncertain outcomes visible without releasing a claim prematurely.
- Use linked corrections after actual effects; never erase settled history to make a new request fit.
When the process needs attention
-
variance
Count and submit
Staff cannot edit a total to conceal a variance or use an incomplete source manifest.
-
variance
Approve the closing packet
An independent Finance Manager reviews the frozen count, source completeness, custody movements and proposed variance accounting.
-
late
Record the close
Later source facts create visible exceptions and linked correction work; closed counts remain intact.
Start with the evidence
Reconcile register cash with actual source activity and an independently reviewed close. Use the original source identities, retained policy versions and named decision owners. Connector acknowledgments and current status labels do not establish cash, completed work or permission. Verify this behavior during implementation before relying on it in a running store.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Identify the session | POSRegistersPOSShifts | Establish the original register session |
| 2 Reconcile the source activity | POSShiftsCashReceiptsRefundsPOSCashEvents | Freeze the complete source manifest |
| 3 Count and submit | POSTenderCountsPOSShifts | Submit one immutable count set |
| 4 Approve the closing packet | POSShiftsApprovalDecisionsJournalEntries | Authorize the exact closing variance |
| 5 Record the close | POSShiftsPOSCashEventsJournalEntries | Close after verified accounting |
Process reports
All reportsReceivables and Payables Aging
Review outstanding customer and supplier amounts by entity, currency and due-date bucket after actual allocations and corrections.
Run by an agent
Agent support
An assistant cannot provide a required independent human approval, invent customer acceptance or treat an uncertain provider response as confirmed money. It cannot promise goods already held or committed to another order, receive the same finished kit twice, or release a refund without its eligible source and decision.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› close a store shift · identify the session on POSRegisters, POSShifts
✓ Match the source namespace, register, store, currency and actual start time.
› close a store shift · reconcile the source activity on POSShifts, CashReceipts, Refunds, POSCashEvents
✓ Verify the acknowledged event watermark and all source identities through the cutoff.
› close a store shift · count and submit on POSTenderCounts, POSShifts
✓ Record denominations and quantities in the drawer currency.
› close a store shift · approve the closing packet on POSShifts, ApprovalDecisions, JournalEntries
⏸ approval · waiting for the finance manager
# 1 more stage after approval: record the close
Other processes
5 moreOrder to cash
Carry the accepted order through shipment, invoice approval and cash application.
5 stages · 2 approvals
Collect and reconcile
Connect actual collections, invoice applications and processor payouts without counting the money twice.
7 stages · 2 approvals
Procure to pay
Purchase needed supply, accept the goods received and settle the right supplier balance.
7 stages · 3 approvals
Return and refund
Connect returned goods, customer credit and the actual refund without losing the original purchase.
9 stages · 4 approvals
Manage customer rewards
Keep earning, redemption, returns and expiry tied to the original customer purchase.
6 stages · 2 approvals