Splitting a hotel bill: routing, split folios and the company that pays only for the room

A split folio is one stay billed to two or more accounts. Routing is the rule, set before or at check-in, that decides which account each charge lands on when it is posted: room and tax to the company, extras to the guest. The rule is fixed once; charges are not sorted by hand at checkout.

The company booked room only. The guest had three drinks, a spa treatment and a late checkout. At 11:40 the desk holds one bill for everything, a guest who is sure the company covers it, and a queue behind him. This article shows how to reach that morning with two clean bills instead: the four cases the desk actually meets, what must be agreed before arrival, how to set the rule at check-in, how to fix a charge that lands on the wrong account, and which invoice questions belong to the accountant. The front office terms behind it are simple once they are named.

What is a split folio, and what does routing do?#

A folio is the running bill for one stay. A split folio is that stay divided across two or more accounts, and routing is the rule that decides, charge by charge, which account receives what.

Four working terms cover the whole subject. A folio is the bill itself: the list of charges and payments for one stay. A posting is the act of adding a charge to it, whether from the restaurant terminal, the minibar count or the nightly room charge. A window is the date range a routing rule applies to. A master account is the account held for a payer who is not the guest, such as a company, an agency or a group.

The key point is timing. Routing is evaluated when the charge is posted, not when the guest arrives. A bar charge posted at 23:00 goes wherever the rule points at 23:00. If no rule exists at 23:00, the charge lands on the guest folio by default and stays there until someone moves it by hand.

Rules are usually written by department or charge type: room, restaurant, minibar, telephone, laundry. They can be limited to specific nights, and a rule with no window runs to the end of the stay. One stay, several accounts, one room: the room is not duplicated, only the money is divided.

The classic failure is timing of a different kind. Routing set at checkout, with the guest at the desk and a queue behind, is a negotiation under pressure. Routing set at booking is a decision. Hotel systems differ in how far a rule can be narrowed, so check what your own system can express before you promise a payer a rule it cannot hold.

Which four cases does the front desk actually meet?#

Four patterns cover almost every split folio hotel situation: a company paying for the room, an agency paying against a voucher, two guests sharing one room, and a group with its own master account.

In the company case, the company covers room and tax, or room only, and the guest covers everything else. In the agency case, the voucher names what is covered, for example bed and breakfast, and everything above the voucher stays with the guest. For two guests in one room, open two folios and divide the room by an agreement written on the reservation and confirmed at check-in. For groups, the contract names what the master account covers, usually room, and incidentals stay on the individual folio.

The fifth case that causes trouble is the employee who assumes the employer covers the bar. The written scope answers that, not the guest's expectation. In every case, the same three things must be known before the first posting: who the payer is, what the payer covers, and for which nights.

What must be agreed before the guest arrives?#

The scope of who pays what must be written before arrival, because at the desk it becomes a negotiation and before arrival it is a decision.

Answer three questions in writing: who the payer is, exactly what the payer covers, and for which nights. "Exactly" means room only, room and tax, room and breakfast, or a fixed allowance per night. A booking note that says only that the company pays is not an instruction, it is a question. Treat it as unfinished work, not as authority.

Make sure the agreement reaches the desk. That means a payer name on the reservation, a routing instruction in the booking, a flag on the arrival list, and a copy of the authorization filed where the desk can see it without leaving the counter. The check-in procedure then starts from a decision instead of a guess.

Name two people: the person at the company who may widen the scope, and the person at the hotel who may accept that change. A guest saying the company will cover it is not authority. For vouchers, read the inclusions and the dates before the guest arrives: a half-board voucher that covers six nights does not cover the seventh, and the seventh is where the argument starts.

Company rates and company credit are commercial decisions that belong to sales and finance. The desk applies the rule; it does not create it.

How do you set the rule at check-in?#

Identify the payer, open the accounts, set the routing before the first posting, and say the split out loud to the guest.

Confirm the payer and the scope against the written authorization, not against what the guest remembers being agreed. Open the company or agency master account and keep the guest folio separate from the first minute, not after the first charge. Set routing by department: room and tax to the payer, every other department to the guest, narrowed further only if the authorization says so. Limit the rule to the nights the payer covers, because a rule with no window keeps paying after the authorization ends.

Check the first room charge has landed on the payer's account before the guest walks away from the desk. One check at check-in saves the whole argument at checkout. Tell the guest what is covered and what is not, and write down that you told them and when. Record who set the rule and at what time in the folio notes, so the next shift inherits a decision rather than a guess.

A charge landed on the wrong account. What now?#

Void the charge and post a reversing entry to the correct account. Never delete it: the record of the mistake is part of the audit trail.

Deletion is the wrong fix because a deleted charge leaves a bill nobody can explain and a report that no longer reconciles with the day's postings. The correction is a pair: a void on the wrong account and a fresh posting on the right one, each carrying a short reason and the name of the person who made it. Set a supervisor threshold in writing; the agent who made the error should not be the only signature on its correction.

Know the difference between a transfer and a void with a repost. A transfer moves the money; a void and repost leaves both sides visible. Pick the one your system and your auditor expect, and use it every time. The same discipline applies when you void a folio charge for other reasons: the method matters more than the speed.

Errors surface at the night audit, when the day's postings are checked against the routing rules. A wrong-account charge found at 02:00 costs minutes; found at checkout it costs a queue. Fix the rule, not only the charge: if the routing was wrong, every charge posted after it is wrong too.

AI Otel's hotel operating system handles billing this way, and it is built: financial records are never deleted, corrections are voided and reversed, and the night audit closes the business day. It is built and working, ahead of launch, and the platform page describes the module.

What does checkout look like with two bills?#

Two folios, two payments, one room: settle the guest's bill first, then close the payer's account, and check that nothing is left sitting on the room.

Order matters. Settle the guest's extras, then close the payer's account. A guest who leaves with an open company account leaves a balance nobody owns. Read the split before printing anything: room charges on the payer, extras on the guest, and no charge appearing on both.

The payment routes differ. The guest pays at the desk by card or cash; the payer is invoiced, and the balance moves to the city ledger with its own ageing and its own follow-up. Ask the guest to sign the guest folio and to acknowledge that the remaining balance belongs to the payer. That signature is what ends the argument later.

One room, one departure, one housekeeping status. Splitting the bill does not split the room, and the room must still be released once. When the authorization covered fewer nights than the stay, the extra nights go to the guest, and that conversation belongs at check-in or the night before, never at checkout. The rest of the checkout process runs as usual.

Who receives which invoice?#

The front desk prepares the accounts; the accountant decides which fiscal document each payer receives and in what form.

In Türkiye, every stay involves a payment, a fiscal document (an invoice or e-document), a guest identity notification (KBS) and personal data (KVKK). A split changes who pays, not whether those steps happen. The buyer named on the document must match the payer: a company that pays needs a document in its own name, and that is an accounting decision with tax consequences, not a desk decision.

Whether one stay can be documented as two, and how the room and the extras are described on each, is a question for the accountant and, where relevant, for the licensed integrator that issues the e-documents. Do not promise a same-day invoice at the counter; documents are issued within the legal period, and the period is a matter for your accountant. Rules on e-Fatura and e-Arşiv depend on the taxpayer's own scope, so confirm your case with your accountant rather than applying a rule you heard at another hotel.

The hotel's real job is to hand over a clean pair of folios: payer named, scope documented, corrections visible, totals reconciled.

What to do next#

Add a payer field, a scope field and a named authorizer to your reservation flow. Then walk one company booking from reservation to checkout at the desk and see where the split breaks. Routing set before arrival turns the four cases into routine work; routing left to checkout turns each one into an argument. If you want to see how a built system handles voids, reversals and night audit, you can request a briefing.