Docs
Setup
- Open the app from the apaleo Store or click Connect with apaleo and sign in with your apaleo account.
- Choose the property. Set the start date and the opening balance, the cash in the drawer at the start of that day. Cash payments before the start date are not taken over. Both stay fixed.
- The app imports all cash payments since the start date and registers itself in apaleo: in the property menu as Kassenbuch and as a dashboard tile.
Daily work
- Deposit: cash goes into the drawer, for example change from the bank.
- Withdrawal: cash leaves the drawer, for example to the bank.
- Expense: something paid in cash, with description and receipt number.
- Cancel: a wrong booking gets a counter-entry. Nothing is edited, the journal stays complete.
- Refresh reconciles with apaleo. Webhooks normally do this by themselves.
- Excel and PDF export: Excel for accounting, PDF with a signature line so staff can sign off the shift.
- Language: English or German under Settings, saved per user. Without a choice the app follows apaleo.
Who may do what
| Admin | Staff (default) | |
|---|---|---|
| Deposit, withdrawal, expense | yes | yes, for themselves |
| Cancel bookings | all | own bookings |
| Book for others | yes | no |
| Change rights, delete | yes | no |
Admins are the account admins and the property admins of apaleo. Under Settings → Rights they change the default for staff or give single people their own rights. Booking for others, changing rights and deleting need a login confirmed once via apaleo.
A user only sees the properties they may open in apaleo.
Permissions the app asks for
folios.readandlogs.read: read cash paymentsidentity:account-users.read: staff names, admin flag and property accessintegration:ui-integrations.manage: the menu entry and dashboard tileopenid,profile,offline_access: login
Guest names are not imported from apaleo, only technical payment IDs. If staff type a name into the description or receipt field, that text is stored. Please avoid that; the hotel is responsible for what is typed.
Support
Questions, ideas or a bug? Open a ticket or write to team@agi-research.de.