At a glance
- A folio can balance and still be wrong: the leaks that matter are the ones no balance check can see.
- The leak-type table lists each pattern, why it passes a normal check, and what a continuous agent check would list for review.
- Group billing adds a second failure point: charges that never reach the master folio, or need to be moved by hand.
- A periodic spot-check samples folios; an agent can read every folio each day, but a person resolves each exception.
- The agent reads your property management system (PMS) and ledger exports; you keep both systems.
Why do group and master folios drift from the GL without tripping a normal check?
A folio can balance while the rate, period, account or routing posted to the ledger is wrong. A group and folio billing audit is the review of group, master and guest folios against the contract, the rate code and what actually posted to the general ledger (GL). A master folio is the single account that collects the charges a group has agreed to pay centrally, such as rooms, tax or meeting-room food and beverage.
In its published article, Docyt, a vendor of hotel accounting automation software, writes that "a folio can be internally consistent (it balances, it prints cleanly, the guest signs it)"[1]. It lists several kinds of exception and adds that "none of them trips an obvious error"[1], and that such exceptions "do not surface through normal exception reporting."[1] That is the core reason for drift: the folio agrees with itself, so the check that looks only at the folio passes.
The GL is a different test. It asks whether the revenue, period and account are right, not just whether the folio foots. Docyt says such exceptions show up as "unexplained revenue variance at month-end"[1]. Expect a suspense balance or reconciling item on one property's books, and a cut-off question on which period a correction belongs to. Four places to look:
- Rate: the posted amount against the rate code and the contract.
- Period: the date the folio was closed against the departure date.
- Account: charges sitting in suspense instead of a revenue line.
- Routing: room, tax and event charges on the master folio instead of on individual rooms.
What causes revenue leakage that normal checks miss? The leak-type table
Folio exception detection starts from a list of what to detect. The table below uses the four exception types Docyt published on August 4, 2026. The columns show why each one escapes a standard check, how a continuous agent check would list it, and who decides. Copy it into your audit procedures.
| Leak type | Why it passes a normal check | How an agent flags it each day | Who decides |
|---|---|---|---|
| Rate Code vs. Posted Rate Mismatch | The folio can still balance. Docyt describes the case where "the amount that actually posts to the room revenue account does not match what that rate code should produce."[1] One cause it names is a front desk agent who "manually overrides a rate at check-in"[1] | Compares posted room revenue for each reservation with the rate code and the contract rate you load; lists every difference with both amounts. | Income auditor: correct the posting or accept the override. |
| Missing folio close | An open folio is not an out-of-balance folio. Docyt: "A guest checks out, but the folio never gets formally closed in the PMS."[1] | Compares each reservation's departure status with its folio status; lists open folios past departure and open group folios past the contract end date. | Income auditor: close, or hold open for a stated reason. |
| Out-of-policy adjustment | Docyt: a comp, discount or override "gets applied by someone without the authority level"[1]. Docyt adds "This is usually not fraud."[1] | Compares each adjustment with the approval limits you load for the user's role; lists adjustments above the limit, grouped by user and property. | Property finance lead: approve, reverse or retrain. Intent is a human judgment. |
| Orphaned charge | Docyt: "A charge posts to a folio (an outlet charge routed from the POS, a spa charge, a parking fee)"[1]. One cause: "the folio it was intended for has already closed"[1]. Another: the reference "does not match any active folio"[1]. A balance check on the guest's folio passes because the charge never reaches an active folio for that guest; it sits in suspense or is written off. | Matches every outlet, spa and parking charge to an active folio; lists charges sitting in suspense with the candidate folios, dates and room numbers. | Income auditor: reroute, bill or write off. Guest disputes stay with income-audit and finance staff. |
How do hotels catch billing errors in group and conference folios before checkout?
Group and conference billing adds routing risk to the four leaks above. A master folio gathers charges from many rooms and events, so one wrong routing instruction repeats across all of them. Whether charges land there depends on setup and order of operations. Two PMS vendors' documentation shows the pattern; read your own PMS's help pages.
The Visual Matrix Desktop help page for group check-in says that if the Group Master is not checked in before the individual rooms, under the conditions it lists, "the charges will post on each individual room and will not be transferred to the Group Master folio."[2] Infor's HMS documentation says "When auto transfer is used, the charge is routed to another account at the time of posting."[4] It also says "Transactions posted before the maintenance of the instructions must be moved manually if they are required on another folio."[4]
Timing matters at checkout too. The Visual Matrix Cloud group checkout page says "Visual Matrix does not prevent the night audit from running if a group master folio still has a balance."[3] It also says "Once the group folio is checked out, it cannot be reinstated."[3] So we recommend a review before the final checkout, not after it.
- Load the billing instructions
Put the signed contract terms, rooming list, event orders and routing instructions into one checklist per group, so each folio has something to be compared with.
- Check routing at the first posting
Confirm that room, tax and agreed incidentals reach the master folio, and list any that posted to individual rooms.
- Compare daily during the stay
Match master and room charges with the contract rate, the event orders and the adjustment limits; list differences the same day.
- Review the day before departure
Work through the exception list while corrections are still possible: unrouted charges, missing event lines, open adjustments.
- Close only after a person signs off
Check out the master folio once the income auditor confirms the balance and the routing are right.
How long should an income audit take, and how do manual and continuous checks compare?
We found no independent benchmark for how long a hotel income or night audit should take, so this article gives none. We recommend timing your own audit for a few nights at two or three properties, including the time spent chasing differences, and using that as the baseline.
On automation, Docyt states that "each of these four checks can run automatically, on every folio, rather than depending on a manual spot-check"[1]. That is a vendor statement, not a measured result. The comparison below has no time or savings figures.
| Question | Periodic spot-check (as defined here) | Continuous agent check | What stays human |
|---|---|---|---|
| Coverage | If review is by sample, only sampled folios | Every folio in the export, every run | Choosing which rules to load |
| When an exception appears | At the audit, or at month-end close | On the next run after the posting | Acting on it before departure |
| Evidence | If notes are kept per reviewer, evidence sits with that person | The folio line, the rule and the compared amount, stored with the exception | Approving the correction |
| Repeat patterns | If each review stands alone, a repeat shows only when someone recalls it | Grouped by user, property, rate code or outlet | Deciding whether a pattern needs training or a policy change |
Who is responsible for auditing group folios across a management company's portfolio?
This is your own operating choice; we recommend writing it down. One workable split is for each property's income auditor to resolve exceptions on its own folios, while a portfolio-level controller owns the rules, the approval limits and the cross-property view. Each exception needs a named owner and a due date.
- Property income auditor or night auditor: resolves exceptions on that property's folios, handles guest-facing disputes with finance staff and records the decision.
- Property finance lead: approves adjustments above the posted limit.
- Portfolio controller: owns the rule set, the limits and the monthly view of repeat exceptions across properties.
- Shared-services accounting: clears suspense items and confirms the ledger ties to the folios at close.
When this doesn't apply
- Your PMS already stops the leak at entry (for example, adjustments above a set limit need approval), so few exceptions reach audit.
- With one or two hotels, one income auditor can read every folio each night; a written checklist may be all you need.
- If contract rates, rate codes and adjustment limits exist only in people's heads, record them first: the agent compares folios against those rules.
- You want software that decides guest disputes, sets rates or corrects folios on its own. This workflow prepares cases for your staff and decides nothing.
Starting with one rule on one property
We recommend starting with a single leak type at one property, for example open folios past departure. Run it beside your current audit for a closed month, compare what each finds, and expand once the list is trusted. AI agent implementation covers how a single workflow is scoped, and the document review with human approval pattern describes how unreadable or ambiguous items go to a person instead of being guessed. The financial reconciliation automation page describes the matching pattern behind the ledger tie-out.
Frequently asked questions
Why do group/master folios show different totals than what posts to the GL?
A folio can balance and still differ from the ledger, so a check on the folio alone passes. The differences sit in the rate code, the posting period, the routing to the master account or a charge held in suspense.
How do hotels catch billing errors in group and conference folios before checkout?
Compare each group folio with its contract, event orders and routing instructions during the stay, not only at checkout. List unrouted charges, rate differences and open adjustments the day before departure, and let the income auditor sign off before the master folio is closed.
What causes revenue leakage in multi-property folio audits that normal checks miss?
Docyt names four patterns that balance cleanly: rate code vs. posted rate mismatches, missing folio closes, out-of-policy adjustments and orphaned charges. Each posts without an obvious error, so only a comparison with the rate code, the departure status, the approval limit or an active folio exposes it.
How long should a hotel income or night audit take and can it be automated?
We found no independent benchmark, so we give no duration. Time your own audit over several nights, including the time spent chasing differences. Docyt states that these checks can run automatically on every folio; a person still resolves each exception the checks list.
Who is responsible for auditing group folios across a hotel management company's portfolio?
That is your own operating choice. We recommend property income auditors resolve exceptions on their folios, property finance leads approve adjustments above the limit, and a portfolio controller owns the rules and the cross-property view. Each exception needs a named owner and a due date.
Related reading
- Hospitality operations for hotel management companies places folio audit beside the other back-office workflows of a hotel management company.
- Approval-gated document review covers the approve-before-it-posts pattern used for exceptions.
- Reconciliation and exception matching covers the matching-and-exception pattern behind the ledger tie-out.
- Scoping one agent workflow covers how a single workflow is built.
Sources
- [1] Docyt, Hotel Folio Exceptions: The Revenue Leak Multi-Property Owners Rarely See (August 4, 2026) (accessed 2026-10-29)
- [2] Visual Matrix, Check In "Room & Tax"/"All Charges" Group Reservations (Desktop) (accessed 2026-10-29)
- [3] Visual Matrix, Check Out Group Master Folio (Cloud) (accessed 2026-10-29)
- [4] Infor, Maintaining group auto transfers (HMS documentation) (accessed 2026-10-29)
More in Finance operations
Deal Jacket and Title/Registration Automation for Multi-Rooftop Dealer Groups
Deal jacket and title/registration automation for multi-rooftop dealer groups: a completeness checklist table, audit-gap handling and cross-store standards.
Auto DealershipsFranchise Brand-Standards Audit Documentation: Automating the Paper Trail Behind the Inspection
Franchise brand-standards audit documentation: how an agent turns photos, PDFs, forms and emailed fixes into one packet per location, ready when asked.
Multi-Unit Franchise OperatorsMulti-Brand AP Automation for Home Services Roll-Ups: Consolidating Vendor Invoices Across ServiceTitan, Housecall Pro and FieldEdge
Multi-brand AP automation for home services roll-ups: what an AI agent normalizes across ServiceTitan, Housecall Pro and FieldEdge, and what stays human.
Home Services Companies