These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Cloud Kitchen Management
- Features
- Folio and payments
Folio and payments
Review stay charges against confirmed payment records.
OverviewDraft folio charges×
Cloud Kitchen Management · Folio and payments
New
Draft folio charges
Posting waits for the finance officer
| Folio charge number | Reservation | Service date | Description | Amount | Status | |
|---|---|---|---|---|---|---|
| RL-92752 | FB-14413 | 26 Oct | Draft rl-572 | 40 | Draft | |
| RL-28719 | FB-77572 | 23 Oct | Draft rl-512 | 560 | Draft | |
| RL-24527 | FB-30836 | 10 Oct | Draft rl-981 | 920 | Draft | |
| RL-39056 | FB-39155 | 04 Oct | Draft rl-150 | 120 | Draft | |
| RL-73888 | FB-80622 | 26 Oct | Draft rl-967 | 590 | Draft |
6 of 6 records
Draft rl-572Recipe lines · RL-92752
DraftReservationFB-14413
Service date26 Oct
Amount40
What you can do
Make the departure amount explainable
A folio charge has a service date, description, amount, posting state and linked reservation. A payment record has its own amount, receipt time, reference and confirmation state. Finance Officer reviews those sources separately before explaining the account at departure. A draft or voided charge does not carry the same meaning as a posted one, and a pending payment is not confirmed money.
How the work is organized
- Charges. Prepare dated folio entries against the correct stay and review posting state.
- Receipts. Keep payment confirmation and refund state with the reservation.
- Reconciliation. Compare posted charges with confirmed receipts before check-out.
What to agree during setup
Decide who may prepare a charge, who reviews a correction and how a void is documented. Define the payment service or manual receipt evidence that establishes confirmation. Finance Officer needs a way to distinguish a pending provider response from a successful receipt. Agree who acknowledges an outstanding account when departure proceeds with money still due. The reviewer should see the specific charges and receipts supporting that decision.
Check the handoff on an actual case
A checked-in stay has a posted nightly charge and a second draft service charge. A payment arrives with a reference but is still pending. Finance Officer excludes the draft charge from the posted total and does not call the pending payment collected. When the charge is reviewed and posted and the provider confirms the payment, the officer reconciles the amounts. If a balance remains, Operations Reviewer examines the evidence and authorizes the eligible departure outcome with that balance explicit. A later refund changes net collection and must be traceable to the same stay.
Before releasing that stay, compare the payment reference and receipt time with the provider result. If the provider has not confirmed the receipt, leave it pending and explain the open amount to the reviewer. Keep a voided charge in the history so the team can see why the current total differs from an earlier draft. This gives the front desk a specific account decision to use at departure rather than a balance that changed without explanation.
For each departure, Finance Officer should open the reservation before comparing amounts. A charge with the right amount but the wrong stay is still an account error. Check the service date and description, then follow the payment reference back to its confirmed result. Operations Reviewer can use that linked evidence to decide whether the guest leaves with a settled or acknowledged outstanding account. Front Desk Agent should see that decision before changing the stay status. Keep later refunds tied to the original reservation so the next review explains why the collected amount changed.
What your team sees
- Draft folio charges — Charges that still need review before posting.
- Pending payments — Receipts awaiting confirmation or investigation.
- Departure review — Checked-in stays ready for financial review.
Follow the work through
What it keeps track of
Data model- Recipe lines
- Recipe line records for Cloud Kitchen Management.
- Ingredient lots
- Ingredient lot records for Cloud Kitchen Management.
- Food batches
- Food batch production records for Cloud Kitchen Management.
- Kitchen tickets
- Kitchen ticket records for Cloud Kitchen Management.
Who uses it
Permissions- Finance Officer
- Prepares and reconciles financial records.
- Operations Reviewer
- Examines the decision evidence.
- Property Manager
- And Front Desk Agent use the reviewed result for departure work.
Set up Cloud Kitchen Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.