An expense system that receives a hotel folio usually does one thing with it: it finds the total at the bottom, attaches the image to a lodging line, and moves on. The folio looked like a receipt, so it was treated as one. That is the mistake. A receipt records one purchase. A folio is the hotel’s account for the stay: a dated list of charges posted night by night, credits applied against them, and a balance that ends at zero when someone has paid. The total at the bottom is the one number on the page that no expense policy actually uses.
Every rule that decides what gets reimbursed is applied below the total. The room is compared with a nightly limit. The tax on the room follows the room. A dinner charged to the room is a meal, not lodging. A minibar line may be personal. A deposit is not an expense at all. None of those decisions can be made from a total, and all of them can be made from the lines, if the extraction keeps the lines intact.
This piece walks through a folio the way a policy engine has to read it. The rules quoted come from two primary sources: IRS Publication 463 (2025), on the records that support travel expenses, and Part 301-11 of the Federal Travel Regulation, as revised by FTR Case 2025-05 (90 FR 56893, December 8, 2025). The FTR binds federal travelers, not private companies, but it is the most precise public statement of how lodging lines are treated, and many private policies use the same per diem tables or a table of the same shape. Nothing here is tax advice or a recommendation for any particular policy.
A folio is an account, not a purchase
Publication 463 is specific about what makes a hotel receipt adequate evidence of business travel. It has to show the name and location of the hotel, the dates of the stay, and separate amounts for charges such as lodging, meals and telephone calls. The last condition is the one that matters for extraction. The IRS is not asking for a total. It is asking for the lines, kept apart, because different lines are treated differently.
A folio is the document that carries those separate amounts. It has three regions, and each one feeds a different part of the expense decision:
| Folio region | What it holds | Why the expense system needs it |
|---|---|---|
| Header | Property name and address, guest name, room number, arrival and departure dates, folio number, quoted rate | Ties the stay to a traveler and a trip, and sets the location that decides the applicable limit |
| Posting lines | One row per posting: date, description, charge or credit, sometimes a reference | Carries the separate amounts that each policy rule is applied to |
| Balance | Total charges, total credits, balance due | Proves the lines were read completely; does not decide anything by itself |
The balance is a control, not a value. If the extracted charges minus the extracted credits do not equal the balance printed on the page, a line was missed or misread, and nothing computed from the lines can be trusted until the difference is explained. That check is cheap and should run on every folio before any policy rule does.
Every line belongs to a category
Once the lines are read, each one needs a category before a rule can be applied to it. The category is not a guess from the amount. It comes from the description the hotel printed, and the description should be kept verbatim beside the category so a reviewer can see why the line was placed where it was.
| Folio line | Category | The rule that applies |
|---|---|---|
| Room charge, one per night | Lodging | Compared with the lodging limit for the location. FTR §301-11.19 reimburses actual and necessary lodging up to the applicable lodging per diem rate, and §301-11.7 reimburses conventional lodging at the single occupancy rate. |
| Room tax, occupancy tax, city tax | Lodging tax | Reimbursed separately in the US, limited to the tax on reimbursable lodging (§301-11.16(a)). Not claimed separately in foreign areas (§301-11.16(b)). |
| Restaurant or room service charged to the room | Meal | Belongs to meals, not lodging. Under the actual expense method each meal is itemized separately (§301-11.23). |
| Complimentary breakfast | Meal provided | A complimentary meal provided by a hotel does not need to be deducted from the meal allowance (§301-11.21(c)). |
| Telephone, internet | Communication | Listed by Publication 463 as one of the amounts a hotel receipt should show separately. |
| Laundry | Miscellaneous | Publication 463 states that incidental expenses do not include laundry, lodging taxes or telephone calls, so none of them belongs in that bucket. |
| Minibar, in-room entertainment, spa | Personal unless the policy says otherwise | Decided by the company’s own policy; the extraction only has to keep the line separate. |
| Deposit, card payment, direct bill transfer | Credit | Not an expense. Offsets charges and explains the balance. |
Two things in this table are easy to lose. The first is that the rule source is part of the output. A line placed in “personal” because the company excludes minibars and a line placed in “lodging tax” because a federal regulation says so are different kinds of decision, and a reviewer needs to know which one was made. The second is that the categories are about the line, not the merchant. Everything on the folio was sold by the same hotel. The merchant category code on the card transaction will say “lodging” for the whole amount, which is exactly why the card statement cannot replace the folio.
The general argument, that a receipt can be read perfectly and still leave the expense undecided, is made at length in the receipt and expense policy article. The folio is the sharpest case of it, because a single document carries lines that land in four or five different rules.
The tax follows the room, and so does the cap
Lodging tax is where a folio read as a total does the most damage. FTR §301-11.16(a) says that, for the continental US and non-foreign areas outside it, lodging taxes are reimbursable as a miscellaneous travel expense, limited to the taxes on reimbursable lodging costs. Read plainly, the tax that can be claimed is the tax on the part of the room that is itself reimbursable, not the tax on whatever the room cost.
A small illustration, with invented figures rather than any published rate. A traveler stays three nights at 240.00 a night, and the folio posts a 15 percent room tax of 36.00 each night. The lodging limit for the location, in this example, is 180.00 a night.
| Line | On the folio | Reimbursable | Why |
|---|---|---|---|
| Room, 3 nights | 720.00 | 540.00 | Capped at 180.00 per night |
| Room tax, 3 nights | 108.00 | 81.00 | Tax on the reimbursable 540.00, not on the 720.00 |
An extraction that captured “tax 108.00” as a single figure can still get this right, provided it also kept the nightly room lines and knows which tax line belongs to which room charge. An extraction that captured only the total of 828.00 cannot. It has no way to separate the room from the tax, so it either reimburses tax on the excess or refuses the whole stay for review.
Real folios make this harder in three ways. Tax is often split across several lines, a state tax, a city tax, a tourism assessment, each posted separately against the same night. Some lines labeled as fees are not taxes, and whether a given fee belongs to lodging is a decision the policy owner has to make, not one the extraction should make by pattern. And outside the US the rule flips: §301-11.16(b) says separate claims for lodging taxes are not allowed in foreign areas, because those taxes were never removed from the foreign per diem rates. The same tax line is a separate claim in Chicago and part of the room in Lisbon. The extraction should read both the same way and leave the location to decide.
Dates are nights, not posting times
A folio dates every line, and the date means different things on different lines. A room charge is dated with the night it pays for. A restaurant charge is dated with the meal. A late checkout fee posts on the departure date. A charge discovered after the guest left, a minibar item counted by housekeeping, can post later still, and the hotel may issue a revised folio that includes it. Two folios for one stay can both be genuine, and the later one is the complete account.
Matching those dates to the trip is where most lodging exceptions are actually found. A room night outside the authorized travel dates is either an extension that needs approval or a personal night attached to a business trip. The FTR has one specific rule worth knowing here: under §301-11.4, a traveler who arrives at the lodging after midnight may claim the lodging cost for the preceding calendar day. A system that compares night dates with arrival times without that rule will flag a correct claim as a night that did not happen.
Long stays change the arithmetic again. When lodging is taken on a weekly or monthly basis, §301-11.8 computes a daily rate by dividing the total lodging cost by the number of days of occupancy, and that daily rate may not exceed the daily per diem. A folio that posts one weekly room charge instead of seven nightly ones is not wrong; it needs a different calculation before the comparison with the limit means anything.
Credits are not expenses
Half of a folio’s lines can be credits, and each kind tells the expense system something different.
- Advance deposit — paid before the stay to secure the room. FTR §301-11.18 allows an agency to reimburse a required advance deposit, so the deposit may already have been claimed. Claiming the full folio again counts it twice.
- Card payment at checkout — should equal the card transaction on the traveler’s or the company’s statement. When it does not, the usual reasons are a currency conversion, a later adjustment, or a charge that posted after checkout.
- Direct bill or company account — the company paid the hotel directly. The traveler has nothing to claim for those lines, even though they appear on the folio the traveler submitted.
- Adjustment or allowance — a correction posted by the hotel, often a reversed charge. It should be paired with the line it reverses, not counted as a separate credit.
Split folios are the common case that breaks naive matching. A company that pays room and tax directly will often have the hotel open a second folio for the guest’s incidentals. The traveler submits one; the company’s accounts payable receives the other. Each has its own payer and its own balance, and the expense claim should contain only the lines on the folio the traveler paid. Pairing reversals with the charges they cancel is the same discipline described for bank data in the bank statement categorization article: an unpaired reversal looks like income, and an unpaired charge looks like spend.
The folio checked against the record that produced it
So far the reader has been the traveler’s company. The folio has a second audience: the hotel itself, and travel programs that negotiate rates with hotels. For them the comparison runs in the other direction. The folio is an output of the property’s own system, and the question is whether the document a guest received says what that system recorded and what the contract promised.
| Folio field | Checked against | Divergence | Action |
|---|---|---|---|
| Nightly room rate | The negotiated or quoted rate for that stay | Rate above the agreed figure on one or more nights | Raise with the property, citing the night and the agreement |
| Number of room nights | Arrival and departure in the reservation | An extra night, or a night charged twice | Hold the claim and request a corrected folio |
| Tax lines | The room lines they belong to | Tax posted with no matching room night, or at a different rate on one night | Flag for review; do not recompute the tax |
| Payments and balance | The card transaction or the direct bill invoice | Paid amount differs from the balance or the statement | Reconcile before the claim is approved |
This is the reconciliation the hospitality solution describes as folio-to-PMS reconciliation: itemized charges and their tax breakdown, read from the document, compared with the record that should have produced them. The extraction is the same in both directions. What changes is which side is treated as the source.
What the extraction should deliver
A folio extraction that serves both audiences has a short, specific contract. For every folio it should return:
- Header fields — property name and location, guest name, room number, arrival and departure, folio number and currency, each with the place on the page it was read from.
- Every posting line — date, description verbatim, amount, and whether it is a charge or a credit, in the order printed.
- A category per line — with the source of the rule that assigned it, so a policy decision and a regulation are never confused.
- Tax linked to its room night — so a cap applied to the room can be applied to its tax.
- The balance check — charges minus credits against the printed balance, with the difference reported, not hidden.
- The folio’s relation to others — a revised folio for the same stay, or a split folio with another payer, identified rather than counted twice.
None of this asks the extraction to decide whether a minibar is reimbursable. It asks the extraction to make that decision possible, and to keep enough evidence that the decision can be checked later. That is the same boundary drawn for receipts generally: extraction is a precondition for the expense decision, not the decision.
Not a policy, not tax advice
The rules quoted here are the federal rules for federal travelers and the IRS description of adequate records. A company’s own policy can be stricter or looser on almost every line: it can reimburse the minibar, refuse the parking, or set its own nightly limits. The point is not that every company should follow the FTR. It is that any lodging policy, whatever its content, is applied line by line, and a folio read as a total gives it nothing to apply.
Read the lines, then apply the rule
A hotel folio arrives looking like a receipt and behaves like a small ledger. Its total is a control. Its lines are the evidence, and each one is decided by a different rule: the room by a nightly limit, the tax by the room, the dinner by the meal allowance, the deposit by whether it was already claimed. An extraction that keeps the lines, their dates, their categories and their links to each other turns a folio into a set of decisions a reviewer can check. One that keeps only the total turns it into a single number nobody can approve.