Scenario map
Follow the operating track, open a scenario, and see where responsibility changes hands.
1 tracks6 scenarios
PY
Money in
Every channel ends in the same validation: client, register, and invoices confirmed together.
When money arrives on its own
Payment emails and card payments arrive with a suggested place.
When SettleWise cannot place it
A person assigns, credits, or rejects.
Shared operating concept
SettleWise
Alerts connected to this scope
These alerts depend on records in this scope. The responsible person corrects the trusted source before the next step in the money loop.
A name in this matrix documents operating coverage; it does not grant application access by itself.
| Alert | When | Source scope | Trigger summary | Responsibility | Coverage | Status |
|---|---|---|---|---|---|---|
| Payment cannot be matched | Now | Payments | Money arrived by email or manual entry but no open invoice fits the amount. | Primary: Accounting assigns or investigatesEscalation: Admin when register rules block assignment | Primary: AccountingBackup: Admin | Needs review |
| Register balance unexpected | Close | Payments | Assigned payments no longer match the register the lodge expects to hold. | Primary: Accounting reconciles the registerEscalation: Owner when cash sales or transfers are involved | Primary: AccountingBackup: Admin | Needs review |