Inventory, POS, and Money Reconciliation

Reconcile Before Trusting The Result

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, Inventory, POS, and Money Reconciliation narrows that work to how to reconcile LAN inventory stock, POS transactions, POS items, and finance follow-up. Because this is a reconciliation page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What Must Match

This page is for proving that two views of the event agree. Read it after imports, exports, offline operation, or manual fixes so the dashboard can be trusted again. The intended readers are Logistics staff and Finance staff. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/inventory-tracking?id=:eventId and /rego/events/manage/point-of-sales?id=:eventId.
• Records or contracts involved: Inventory stock rows, POS transactions, and POS transaction items.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Compare Counts, Records, And Proof

1. Choose the two sources being compared: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Inventory, POS, and Money Reconciliation.
2. Check counts before individual records: Use /rego/events/manage/inventory-tracking?id=:eventId and /rego/events/manage/point-of-sales?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Investigate every mismatch before closing it: Keep Inventory stock rows, POS transactions, and POS transaction items in view so the work stays tied to the records or contracts it can affect.
4. Save the summary and owner for unresolved items: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

Reconciliation Is Credible When

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook after LAN import touched inventory or POS.

1. Step 1 - Tie the check to one import. Confirm the import summary includes inventory or POS counts. This proves this reconciliation page applies.
2. Step 2 - Gather real-world notes. Gather starting stock, ending physical stock, POS totals, payment notes, and known exceptions. This sets comparison data.
3. Step 3 - Compare imported records with physical evidence. Compare dashboard inventory and POS surfaces with onsite totals. This verifies imported stock and sales.
4. Step 4 - Explain every mismatch. Investigate negative stock, missing transaction items, unexpected totals, or payment evidence gaps. This protects finance review.
5. Step 5 - Mark the dashboard trustworthy or unresolved. Record final stock and POS totals with notes for finance or settlements. This makes the numbers auditable.
6. Step 6 - Store the reconciliation note for audit. Assign unresolved money-adjacent issues to finance before event closeout. This prevents lost obligations.

What to compare

Area	Compare against
Stock rows	Physical count and onsite adjustment notes.
POS transactions	Device totals and payment notes.
POS items	Item-level sales and inventory movement.
Finance follow-up	Settlements, refunds, and payment evidence where relevant.