Every Hong Kong hotel supplier invoice gets coded to a USALI department before posting to the GL — line items mapped across Schedule 1 (Rooms), Schedule 2 (Food and Beverage), Schedule 3 (Other Operated Departments), Schedule 5 (Administrative and General), Schedule 6 (Information and Telecommunications), Schedule 7 (Sales and Marketing), Schedule 8 (Property Operation and Maintenance) and the new Schedule 9 (Energy, Water and Waste). The USALI 12th Revised Edition takes effect for accounting periods beginning 1 January 2026, with new dedicated schedules for Full-Time Equivalents, Executive Lounge, Loyalty Programs, and Brand and Operator costs. That is why HK hotel finance teams are now re-mapping AP coding workflows before each weekly Angliss, DCH, Wismettac, CLP, HK Electric or Diversey invoice hits the night-audit posting cycle.
Hong Kong hotel supplier invoice USALI department coding is not a nice-to-have. The departmental P&L is the entire control surface — rooms-department margin, F&B-department margin, OOD margin, undistributed-expense ratios, GOP and GOPPAR all derive from how cleanly the supplier invoice is coded at the AP step. Miss the coding and the departmental story is fiction: the rooms team wears back-of-house cleaning chemicals, the F&B GP is propped up by misallocated banquet linens, and ownership makes decisions on numbers that look right and aren't.
The audience is the financial controller, director of finance or AP supervisor at an independent boutique hotel, mid-tier business hotel, lifestyle or design hotel, serviced-apartment operator, or a small hotel group of 2 to 10 properties below the international flag-brand tier — the band that runs on USALI departmental discipline but does not have corporate finance in head office maintaining the chart of accounts on its behalf. The work runs in HKD on a Sage 300, SUN Systems, Oracle Financials Cloud or NetSuite stack at the upper end and on Xero, MYOB or QBO at the boutique end, and the AP coder is dealing with the actual invoice on the actual day it arrives.
What follows walks the workflow end to end — from the 12th edition transition through the departmental coding map, the splitting discipline on shared-cost suppliers, the multi-property roll-up pattern, the night-audit cadence and the HK-specific supplier overlay, to the three concrete posting routes available in 2026.
What Changed for AP Coding in USALI 12th Edition
According to Antravia Advisory's USALI 12th edition transition briefing, USALI 12th Revised Edition is effective for accounting periods beginning 1 January 2026 and replaces the Utility Department with a new Energy, Water, and Waste (Schedule 9), while introducing dedicated schedules for Full-Time Equivalent (FTE) labour, Executive Lounge, Loyalty Programs, and Brand and Operator costs. Each of those changes lands on the AP coding sheet in a specific way.
The Utility Department is retired and replaced by Energy, Water and Waste. Schedule 9 — Energy, Water and Waste — replaces the old Utility Department and broadens the scope: the monthly CLP, HK Electric, Towngas and WSD bills still code here, but the waste-removal contractor invoices that used to scatter into P&M (or, less defensibly, into A&G) move into EWW alongside them. The dedicated Schedule 9 walk-through is in section 5.
The new FTE schedule changes labour reporting, not labour coding. Outsourced-labour supplier invoices — contracted housekeeping, contracted security, contracted F&B casual labour through agencies — still code to the operating or undistributed department where the labour was deployed. The supplier invoice attaches to a department before it attaches to an FTE roll-up.
Executive Lounge is pulled out of Rooms. Where the property runs an Executive Lounge or Club Lounge (common at the upper-tier HK boutiques and lifestyle properties), the supplier costs that previously coded to Schedule 1 Rooms — F&B for the lounge, lounge amenities, lounge-only laundry — now code to the Executive Lounge schedule. The chart of accounts needs a clean lounge code series before the first 2026 invoice posts; otherwise lounge costs default back into Rooms and the rooms-department margin overstates.
Loyalty Programs has its own schedule. Loyalty-fulfilment partners, points-redemption billbacks and loyalty-event suppliers that previously scattered through Sales and Marketing now consolidate into a Loyalty Programs schedule. The OTA invoice itself stays in S&M; the loyalty-tier amenity supplier moves.
Brand and Operator consolidates operator costs. Where a HK boutique runs under an operator agreement — a serviced-apartment operator on a management contract, a small group operating under a soft brand, a third-party management company — the operator's monthly fees, brand-licence fees, central-services charge-backs and shared-services allocations consolidate into a single Brand and Operator schedule rather than being split by hand each month across A&G, S&M and Rooms.
Refined OOD definitions and the all-inclusive section. The 12th edition tightens what qualifies as an Other Operated Department (Schedule 3) and adds an all-inclusive section. The practical AP implication is at the edges — a parking-operator pass-through that previously sat in OOD by habit may belong in undistributed under the refined definition; a spa run as a tenant concession is treated differently from a spa run as a hotel department. Re-check the OOD inclusions before locking the chart of accounts.
This article covers the AP-coding-relevant changes only; for the full edition walk-through across every schedule, line and reporting requirement, refer to the HFTP USALI documentation. The 12th edition transition modifies but does not replace the broader USALI departmental-coding workflow for hotel AP teams — the principles of departmental allocation, splitting on shared-cost suppliers and audit-trail discipline carry over from 11th edition, with the schedule numbering and the new dedicated schedules layered on top.
Operating Departments — Where Rooms, F&B and OOD Supplier Invoices Land
The operating departments are where supplier-invoice volume concentrates and where coding errors do the most visible damage to the departmental P&L. Schedule 1, Schedule 2 and Schedule 3 between them carry most of the weekly invoice traffic at any HK hotel.
Schedule 1 (Rooms). The Rooms schedule absorbs everything that touches the guest room or the rooms-side guest experience. On the AP coding sheet that means in-room amenities (toiletries, slippers, robes, in-room stationery), guest supplies (turn-down items, in-room packaging), in-room dining minibar restocks billed by the F&B supplier but consumed against the rooms occupancy line, third-party guest-linen laundry where the property does not run its own laundry, channel-content licensing for in-room TV (the monthly bill from the IPTV or pay-TV content aggregator), guest transportation supplier invoices for hotel-arranged airport transfers where the cost is not recharged at full margin, and any complimentary food and beverage tied directly to a room booking (welcome drinks delivered to the room, complimentary breakfast where it is contractually part of a rate plan rather than an F&B sale). Under 12th edition the Executive Lounge slice that previously sat in Rooms is now its own schedule, and the AP coder has to redirect lounge-amenity invoices accordingly. Room-cleaning chemicals are a perennial Rooms-versus-P&M splitting decision, and that decision is worked through in the splitting-discipline section below.
Schedule 2 (Food and Beverage). Schedule 2 carries the heaviest weekly volume at most HK hotels because the F&B supplier base delivers daily. Hong Kong hotel F&B supplier invoice USALI coding is mostly a question of recognising the supplier and routing the line items appropriately. On the food side that means Angliss for protein and broadline frozen, DCH for dry goods and broadline ambient, Foodgears for produce, Wismettac for Japanese and broadline Asian product, Chef's Garden for hydroponic and specialty produce, ETAK for niche specialty ingredients, and Eugina alongside the smaller specialty importers the chef has on rotation. On the beverage side it is the wine importers (typically two to four across the consolidated programme), the beer distributors, the spirits importers, the soft-drinks distributor, the coffee supplier and the tea supplier.
Around those, Schedule 2 picks up F&B uniforms billed by the contracted uniform supplier, kitchen smallwares replacement, banquet linens where the hotel maintains its own pool rather than renting, F&B china, glass and silverware breakage replacement, and F&B-allocated music licensing. Where the property runs banquet and conference as part of F&B (most do at the boutique tier), the banquet linen and beverage coding flows through Schedule 2 rather than splitting into a separate Conference treatment.
Schedule 3 (Other Operated Departments). Schedule 3 is the home for departments that the hotel operates as standalone profit centres beyond Rooms and F&B. At a typical HK boutique that means the spa, the gym, any retail outlet the hotel runs in-house, the business centre where it still operates as a standalone department, and parking where it is hotel-operated. On the AP side that translates to spa supplies through the local distributors of Comfort Zone, Aromatherapy Associates, ESPA, SHISEIDO Professional and Thalgo HK (each property's spa carries one or two product partnerships rather than the full list), gym towels and supplies, gym equipment maintenance where the cost is treatable as supplies rather than capitalised, retail-outlet COGS where the hotel buys its retail stock from local distributors or specialty wholesalers, business-centre supplies, and the parking-operator pass-through where the hotel runs the car park itself rather than leasing it to an operator. Under the 12th edition refined OOD definitions, anything operated as a tenant concession (a spa run by a third-party operator on a concession agreement, retail outlets leased to a tenant) is no longer an OOD by default — the rental income comes through Miscellaneous Income and the concession's own supplier invoices do not hit the hotel's AP at all. Re-check the OOD inclusions against the new definitions before a spa-supplies invoice is auto-coded to Schedule 3 by AP-recurring-coding habit; the spa may not be an OOD anymore at all.
A note on the operating-department flag at line level: the same Wismettac order can include both general F&B inventory (Schedule 2) and a loyalty-tier welcome basket (Loyalty Programs under 12th edition, per section 2). The supplier does not change; the line-level coding does.
Undistributed Departments — A&G, IT&T, S&M and P&M Supplier Invoices
The undistributed schedules sit between the operating departments and the fixed charges. Coding accuracy here is what produces an honest GOP — a P&M expense miscoded into A&G distorts both lines, and the undistributed-margin story stops being usable for benchmarking against STR or HFTP peer data.
Schedule 5 (Administrative and General). A&G carries the corporate-overhead supplier base at the property level. On the AP coding sheet that means office supplies (the print-and-paper stream from the local stationery supplier), printing and stationery (letterhead, business cards, in-room collateral where it is corporate-branded rather than rooms-amenity), audit and accounting fees (the annual statutory audit invoice and any interim accounting support), legal fees (HK lawyer invoices for ad-hoc work — license renewals, contract review, disputes), bank charges excluding interest (the monthly account fees and FX charges from HSBC, BOCHK, Hang Seng or Standard Chartered), credit-card commissions on the merchant-acquirer side (the monthly statement from the acquirer netting commissions across cards), and owner's representative fees where the property pays an owner-rep separately from the operator. The cluster-services and shared-services concept the 12th edition treats more explicitly is relevant here: where a small group's head office allocates a monthly cluster-services charge across properties (shared finance, shared HR, shared IT support), that allocation typically codes to A&G at each property under the 11th edition habit but may be a candidate for the new Brand and Operator schedule depending on how the group structures the allocation. Document the policy choice once and apply it consistently across properties.
Schedule 6 (Information and Telecommunications). IT&T is where the HK hotel technology stack codes — the PMS (Opera at the upper tier, Mews and Cloudbeds at the boutique and serviced-apartment end, with Cloudbeds also doubling as channel manager at the smaller end), the POS (Micros, Toast where the property has gone with a newer F&B POS), any RMS treated as IT&T rather than allocated to Rooms (IDeaS being the most common decision point — the policy choice between coding RMS to Rooms or to IT&T should be settled at the chart-of-accounts level and stuck to), internet and WAN (the leased line plus any backup circuit, often two suppliers), telephone exchange (the in-house PBX maintenance contract or the cloud-PBX subscription), IT consulting (the local managed-services partner doing day-to-day IT support at the property), and cybersecurity tooling (endpoint protection, SIEM where the property runs one, the email-security gateway). The 12th edition's clearer treatment of cybersecurity costs is relevant here — costs that previously sat ambiguously between IT&T and A&G now land more cleanly in IT&T, and the AP coder can stop fielding ad-hoc questions about where a CrowdStrike or Microsoft Defender invoice should sit.
Schedule 7 (Sales and Marketing). S&M at a HK hotel is dominated by OTA commission billbacks and channel costs. The OTA commission flow — Booking.com, Agoda, Expedia, Trip.com (significant given the inbound mainland mix), Klook (significant where the property has packaged offers or experiential add-ons distributed through Klook) — codes to Schedule 7 as commission expense, with the underlying room revenue still flowing through Schedule 1. Around the OTAs the AP coder processes digital-marketing agency fees, photography, channel-manager subscriptions (SiteMinder at the upper boutique tier; RoomRaccoon at the serviced-apartment end), in-house sales-driven signage and collateral, and FAM-trip costs for hosted agents, journalists or corporate buyers. Loyalty-programme costs move to the new Loyalty Programs schedule per section 2; the OTA commission itself stays in S&M.
Schedule 8 (Property Operation and Maintenance). P&M carries the contractor base that keeps the building functioning. On the AP coding sheet that translates to preventive maintenance contracts on lifts (the LIFT/EMSD-required regular inspection contract — typically a single annual or quarterly invoice from KONE, Schindler, Otis or Mitsubishi Electric), AC (the contracted maintenance on the chiller plant and the FCU service rounds), plumbing (the on-call contract plus scheduled rounds), fire-suppression (the annual sprinkler and fire-pump inspection driven by Fire Services Department requirements), kitchen-extraction cleaning (the quarterly or six-monthly extraction-duct deep clean — a known kitchen-fire-prevention expense), back-of-house cleaning chemicals (the share of the Diversey or Ecolab delivery that does not code to Rooms — covered properly in section 6), repairs and maintenance materials (the trickle of plumbing fittings, electrical components, paint and sundry materials from the local trade suppliers), and contracted security where the property's security spend sits in P&M rather than A&G (the policy choice differs by property; document it and stick to it).
Brand and Operator (new schedule). Where the property runs under an operator agreement, the operator's monthly invoice now routes to the Brand and Operator schedule per section 2 rather than being split each month across A&G, S&M and Rooms. Re-point the supplier-recurring-coding rule before the first 2026 operator invoice arrives.
The New Schedule 9 — Energy, Water and Waste in HK
Schedule 9 is the biggest single AP-coding change in the 12th edition for HK hotels. Under 11th edition the Utility Department covered electricity, water, gas and fuel. Under 12th edition Schedule 9 — Energy, Water and Waste (EWW) — replaces it and broadens the scope to include waste removal, recycling, food-waste handling and the related sustainability-disclosure supplier costs alongside the traditional utilities. Every recurring-coding rule pointed at the old Utility Department needs re-pointing to EWW, and a clean set of supplier-to-EWW mappings needs to be in place before the first January 2026 utility cycle.
The energy and water side is straightforward once the supplier-to-territory mapping is locked. CLP supplies Kowloon and the New Territories. HK Electric supplies Hong Kong Island and Lamma. Towngas supplies piped town gas across the city. WSD bills for water and sewerage. Around those, fuel oil suppliers and LPG suppliers code to EWW where the property uses them — fuel oil for any back-up generator that runs on diesel, LPG for any kitchen burner not on town gas (less common in HK than in mainland or southeast-Asia hotels but not unheard of at the boutique tier). The property's geography drives whether CLP or HK Electric is the electricity counterparty for each property; a small group with a Tsim Sha Tsui property and a Sheung Wan property will see CLP and HK Electric invoices arriving each month and both code to EWW Schedule 9 at the relevant property's level. On bilingual handling: the WSD bill in particular carries both Chinese and English fields, and the AP coder needs to recognise both — supplier identification by the Chinese name as much as the English one is normal for HK utility coding.
The waste side is where the change takes effect most visibly on the AP coding sheet. General waste removal contractors (the licensed waste collector contracted to the building management or directly to the property), recycling contractors (paper, cardboard, glass, metal where the contractor handles them separately), food-waste contractors (where a HK hotel composts or processes kitchen waste through a dedicated food-waste collector — this has expanded under EPD waste-charging policy), confidential-waste shredding for back-office records and any contractor handling waste cooking oil from F&B all move into EWW under 12th edition. Under 11th edition these typically coded into P&M (the defensible choice) or into A&G (the lazy choice that distorted both lines). Under 12th edition they belong with the energy and water suppliers, and the chart of accounts needs the EWW department code populated to receive them.
The multi-property pattern adds a wrinkle that small groups need to think through once. A group operating one property on Hong Kong Island and one in Kowloon will have HK Electric invoices for the first property and CLP invoices for the second, both coding to EWW Schedule 9 at each property's level before the cross-property roll-up. The roll-up needs to consolidate at the EWW schedule level (not at the supplier level), so the group EWW line shows total energy-water-waste spend across the portfolio while each property's departmental P&L shows only its own EWW costs. The chart-of-accounts pattern that supports this cleanly is covered in the multi-property section below.
The extraction work on HK utility bills themselves — line-level meter reads, billing periods, kWh and unit consumption, the demand-charge versus consumption-charge split, fuel-clause adjustments where they apply, the bilingual fields on WSD — is its own walk-through. For the detail on extracting CLP, HK Electric, Towngas, and WSD bills for the new EWW Schedule 9, the dedicated utility-bills article carries the line-level treatment that the AP coding step then maps into Schedule 9.
Splitting-Discipline Examples on Shared-Cost Suppliers
USALI departmental P&L discipline only holds when shared-cost supplier invoices are split across the departments that actually consumed the cost, not coded to a single catch-all account. The principle is straightforward; the practice is where most departmental margin distortion enters HK hotel financials. Three named scenarios cover most of the splitting work an AP team does on a typical week.
Diversey HK or Ecolab cleaning chemicals — Rooms versus P&M
A weekly Diversey HK or Ecolab delivery shows up as one invoice with twenty or thirty product lines. Some of those lines are housekeeping product — bathroom cleaner, glass cleaner, surface disinfectant, bed-linen detergent (where the property runs its own laundry), bathroom amenities consumables tied to the housekeeping cart. Those code to Schedule 1 Rooms, because the cost was consumed inside guest rooms or on the housekeeping operation that exists for the rooms department. Other lines on the same invoice are back-of-house product — kitchen-extraction degreaser, public-area floor cleaner for the lobby and corridors, back-of-house disinfection for staff areas, dishwasher detergent and rinse aid for the kitchen, drain-clearing chemicals. Those code to Schedule 8 P&M, because they are consumed on the building and back-of-house operation rather than on the rooms inventory.
The AP coder reads the delivery note alongside the invoice. Two methods work for the actual split: a usage-driven percentage agreed with the executive housekeeper and the chief engineer at the start of the year (typical splits at HK boutiques run something like 60-65% Rooms, 35-40% P&M, with the policy reviewed quarterly), or a line-by-line product attribution where each product line is coded to the schedule it physically supports. The line-by-line method is more accurate and is the recommended approach where the AP throughput supports it; the percentage method is a defensible fallback where it does not. Whichever method is used, the audit trail needs to capture both the split percentages applied and the documented source of those percentages — a signed-off split agreement on file from the executive housekeeper and chief engineer, refreshed annually, plus the AP coding sheet field carrying the multi-coding decision per invoice. An auditor sampling Diversey invoices needs to be able to reproduce the decision without re-asking how the split was set.
Bottled water — Rooms versus F&B versus Conference
The bottled water supplier delivers one invoice covering multiple consumption points: in-room turn-down water (Schedule 1 Rooms), banquet and restaurant table-service water (Schedule 2 F&B), and meeting-room water for the conference and event spaces. The conference share is the policy decision point. Where the property runs Conference and Banquet as a standalone operated department under Schedule 3 OOD (less common at the HK boutique tier), the conference water codes there. Where Conference is run inside F&B (the more common HK boutique pattern), the conference share simply codes back into Schedule 2.
The split on a typical weekly bottled-water invoice runs by case count rather than by line value — the in-room programme has predictable per-occupied-room consumption, the restaurant service has predictable per-cover consumption, and the meeting-room consumption is event-driven. The AP coder splits the invoice using the case-count breakdown supplied by the F&B receiving point, with the split recorded on the AP coding sheet and the receiving documentation attached for retention. The chart-of-accounts decision on whether Conference sits in OOD or in F&B should be settled at the controller level once and not re-litigated invoice by invoice; if the decision changes mid-year, document the change date and apply it consistently from that date.
Linen rental — Rooms versus F&B versus Spa
Where the hotel rents linen rather than owning it (a common pattern at HK boutiques to keep working capital out of inventory), the monthly linen-rental invoice from the contracted linen-services provider covers guest bed linens and bath linens (Schedule 1 Rooms), restaurant table linens and napery (Schedule 2 F&B), and spa treatment linens — towels, robes, treatment-bed sheets — where the property runs an in-house spa (Schedule 3 OOD spa, subject to the OOD-eligibility check from section 3 against the 12th edition refined OOD definitions).
The split follows the contract: the linen-rental contract enumerates piece counts and rates by linen type, and each linen type maps to one department. The AP coder applies the contract-driven mapping line by line. The spa portion can be material at properties running busy day-spas — where the spa is heavily booked, the spa-treatment-linen rental can run 10-15% of the total monthly linen invoice, large enough to distort the rooms-department margin if it is not split out. The audit trail is the linen-rental contract on file, the monthly piece-count statement from the linen-services provider attached to the invoice, and the AP coding sheet showing the multi-coding decision against the contract mapping.
Multi-Property Roll-Up for Boutique Groups and Serviced Apartments
The pattern that holds at the 2-to-10-property tier is property-level USALI integrity with group-level consolidation by property and by department. Each property maintains its own USALI departmental P&L at the property level — Schedules 1 through 9 plus the new dedicated schedules where applicable — and the group consolidates upward by preserving both the property identity and the departmental identity. A consolidated GOP line that loses the property breakdown is no use to ownership; a property breakdown that loses the departmental detail is no use to the operator. The roll-up has to keep both.
In practice the chart-of-accounts pattern that supports this is property-prefix department codes against a USALI-aligned numeric range. Each property has its own department code series — a property-prefix on a numeric range that matches the USALI schedule numbering, so property A's Schedule 2 F&B code is a different ledger account from property B's Schedule 2 F&B code, but both roll up cleanly to a group F&B line. Supplier records carry the property dimension at AP entry rather than at consolidation, and the group consolidation maps property codes upward to a common USALI schedule. The small ERPs at the boutique end — Xero, MYOB, QBO — handle this through tracking categories or location dimensions, with the property as one dimension and the USALI department as the account itself; the upper-end ERPs (Sage 300, SUN Systems, Oracle Financials Cloud, NetSuite) carry native multi-entity structures that handle this without needing to lean on tracking dimensions. Hong Kong boutique hotel multi-property USALI roll-up works in either pattern; the choice is driven by what the group already runs rather than by anything specific to USALI. This sits inside the broader picture of hotel accounts payable automation across single and multi-property operations, where the AP-tooling decision and the multi-property structure decision interact.
A single Wismettac invoice covering deliveries to three boutique properties in the group needs splitting at AP entry into three property-specific coding lines, each then coded to Schedule 2 F&B at the relevant property — not coded to a single group-level F&B account that loses the property attribution. The same applies to any consolidated supplier billing across the group: a Diversey HK monthly statement covering deliveries to multiple properties, a corporate IT services invoice charging across properties, an audit fee billed at the group level but allocated to each property. The splitting discipline from the previous section carries directly into the multi-property layer — the same discipline, applied first across properties and then across departments within each property.
Hong Kong serviced apartment supplier invoice department allocation has a slightly different shape from the hotel pattern. Serviced apartments typically have a thinner OOD layer (most have no spa, often no F&B beyond a breakfast offering or a small grab-and-go), heavier IT&T allocation per door for the booking-engine and channel-manager stack (the technology cost is spread across fewer revenue-generating departments than at a full-service hotel), and a different operating cadence — guests are longer-stay so the housekeeping-supplies consumption per occupied night is lower than at a transient hotel, but the in-unit kitchen-supply consumption (where units have kitchenettes) shifts cost into Rooms that would otherwise be in F&B. USALI 12th edition applies cleanly to serviced-apartment operators despite the different mix; the schedules are the same, the weight on each schedule is just different. The Brand and Operator schedule introduced in 12th edition is particularly relevant for the operator-managed serviced-apartment model, where the operator's monthly fee structure is often a material undistributed line.
Operationally the consolidation step runs in two layers. Monthly close runs at each property — USALI departmental P&L produced for that property using its own AP coding work over the month. Then the group accountant consolidates by property and by department, producing the group view ownership receives. The AP coding step at each property is what makes the consolidation reliable. Coding errors at the property level — a P&M expense miscoded into A&G at one property, a Schedule 2 F&B line miscoded into Schedule 3 OOD at another — surface as departmental-margin distortions at the group level, where they are harder to spot and harder to unwind. Discipline at the AP step is what protects the whole reporting chain.
The Night-Audit Cadence and Same-Day Posting
HK hotels run night audit nightly: revenue, occupancy and cost transactions for the day post into the GL within the same 24-hour cycle, and the morning report lands on the GM and controller's desk before the next day's operating meetings. Supplier invoices belong inside that cycle on the day they arrive and code — not held for a weekly batch. The AP team extracts each invoice (header plus line-level detail), codes each line to the relevant USALI department per sections 3 to 5, applies the splitting discipline from section 6 where the invoice covers shared costs, and queues the coded invoice for that night's audit posting alongside the day's PMS and POS feeds. By morning the controller has departmental cost-to-date that genuinely matches departmental revenue-to-date.
The cost-velocity argument is concrete. A Wismettac F&B delivery on Monday morning that posts in Tuesday's morning report shows up in the Schedule 2 F&B cost-to-date for Tuesday's revenue meeting — GP for the period under review reflects the cost that produced the revenue. The same delivery held until Friday for batch posting distorts the F&B cost story for four days; the Tuesday and Wednesday morning reports show F&B revenue without the corresponding cost. For a property running 70%-plus occupancy on tight F&B margins, that gap is enough to move the GOPPAR conversation in the wrong direction — the GM and the F&B director make mid-week operating decisions on a margin picture that materially overstates, and the Friday batch correction lands too late to course-correct.
The cadence forces specific AP-coding decisions. The AP team needs same-day extraction throughput at the receive-and-code step — the four-hour, six-hour or eight-hour window between invoice arrival and the night-audit cut-off is the operating constraint. The shared-cost splitting decisions on Diversey, bottled water and linen rental cannot be deferred to a later batch; the split needs to land in the same posting cycle as the underlying invoice, or the audit trail breaks across cycles. The multi-property splits at small-group operators need to land before each property's individual night-audit cut-off, which means the group AP team is working against multiple cut-off times rather than a single end-of-day deadline.
The honest failure mode is throughput. Where the AP team is undersized relative to invoice volume — a common pattern at boutiques running lean on back-office headcount — or where the extraction tooling is slow on bilingual invoices and on the line-level F&B detail, supplier invoices accumulate in a queue and the night-audit posting falls behind. Cost-to-date stops matching revenue-to-date, the morning report becomes a polite fiction, and the value of running night audit at all starts to erode. The fix is not to relax the night-audit cycle — that is the whole control structure — but to lift throughput at the extraction-and-coding step. The posting routes covered next are the practical ways HK hotel AP teams do that.
HK Supplier-Mix Overlap with Restaurant AP, Bilingual Invoices and Section 51C Retention
Three things travel with HK hotel AP that no US-shaped USALI explainer carries: the supplier-mix overlap with the local restaurant chain base, the bilingual handling on most F&B and utility supplier invoices, and the IRD Section 51C retention discipline that audit-readiness depends on.
The F&B supplier base for a HK hotel — Angliss, DCH, Foodgears, Wismettac, Chef's Garden — is the same supplier base a HK restaurant chain works with daily. The hotel codes those invoices to USALI Schedule 2 F&B, with the splitting and sub-departmental detail covered in sections 3 and 6. A chain restaurant codes the same invoices to outlet-level cost centres, often through Xero tracking categories or an equivalent dimension on a different ERP. The extraction-and-coding work upstream is identical — same suppliers, same line-item layouts, same bilingual fields, same delivery-note matching (the HK restaurant three-way match across PO, delivery note and supplier invoice walks the validation step the hotel performs in the same way before department coding), same throughput pressure on the receiving operation — and only the framework downstream differs. For the controller running both a hotel and a small chain F&B operation in the same group, or for the consultant supporting both kinds of HK F&B client, the restaurant-chain variant of supplier-invoice allocation in Xero tracking categories walks the same supplier base into the chain-restaurant chart-of-accounts framework.
Bilingual handling is daily work, not an edge case. HK F&B suppliers commonly issue invoices with the supplier name and address in Traditional Chinese alongside English line descriptions, or with the supplier name in English and Traditional Chinese line descriptions on local product lines (the produce supplier's mainland-import lines often carry only the Chinese product description, even when the rest of the invoice is in English). Utility bills — WSD in particular — carry bilingual fields throughout. The AP coding step has to read both, because supplier identification often relies on the Chinese name where the English name is generic or absent, BR Number / 商業登記號碼 verification cross-references the IRD record that itself carries both Chinese and English names, and line-item coding to the right F&B sub-department often relies on the Chinese description (the line "鮮豬腩" is unambiguous; an English-only "fresh pork" description would not tell the kitchen whether it codes to banquet, restaurant or staff canteen). Treating bilingual handling as a normal AP requirement rather than as a foreign-language exception is the right operating posture. The mechanics of handling Traditional Chinese and English bilingual supplier invoices at the extraction step is its own walk-through.
IRD Section 51C is YMYL territory and deserves stating cleanly. Inland Revenue Ordinance Cap. 112 Section 51C requires every business carrying on a trade or profession in Hong Kong to retain sufficient records to enable the assessable profits to be readily ascertained, for not less than 7 years from the date of the transaction (subject to the exceptions the Ordinance specifies). For a HK hotel that means every supplier invoice, every coding sheet showing the USALI department allocation including the splitting decisions documented in section 6, every supplier-statement reconciliation, and every supporting document attached to the AP file (delivery notes, executive housekeeper sign-offs, banqueting BEOs supporting bottled-water splits, linen-rental contracts supporting linen splits) must remain retrievable for 7 years. AP retention discipline has to back the rule up at the document-management layer, with backups, off-site replication and clear retrieval paths in place for the full retention window.
The audit-readiness payback is concrete. HK hotels are audited annually under HKFRS or HKFRS for SMEs depending on size and ownership structure. The auditors test AP coding samples against the underlying supplier invoice and against the USALI departmental allocation — they pull a sample of invoices, trace each to its coding decision, and check whether the supporting documentation justifies the coding (especially on the splitting decisions, where the absence of a documented split source is a finding). Hong Kong's statutory audit documentation checklist for hotel AP records walks the documentation auditors look for. Strong coding discipline at AP entry — split percentages with documented sources, AP coding sheet fields carrying the multi-coding decision per invoice, supporting references attached for retention — pays back at audit time as a clean sample-testing pass. Weak discipline pays out as findings, management points and a longer audit cycle.
Three Posting Routes — Manual Entry, Built-In OCR and AI Extraction
The AP team gets the supplier invoice from receipt to a coded line in the GL one of three concrete ways at a HK hotel in 2026. The right choice depends on volume, on the night-audit-cadence pressure from section 8, on the splitting-discipline requirement from section 6, and on whether the property sits inside a multi-property roll-up.
Route 1: Manual entry into the ERP. The AP clerk reads each supplier invoice, types in the header data (supplier, invoice number, date, total, tax), and codes each line by hand to the relevant USALI department in whichever ERP the property runs — Sage 300, SUN Systems, Oracle Financials Cloud or NetSuite at the upper end, Xero, MYOB or QBO at the boutique end. This is honest work and it does the job at low volume. At a small boutique with thirty supplier invoices a week and a stable supplier base, an experienced AP clerk who knows the chart of accounts and the split policies can keep up with the night-audit cadence on this route. It breaks down at higher volume, on bilingual invoices that slow the keying step, on shared-cost suppliers where the splitting decision adds keystrokes, and at multi-property operators where the same invoice needs splitting across properties before any property's coding can land.
Route 2: Built-in OCR or in-ERP capture. Most ERPs and most third-party AP-bolt-on tools now offer OCR at the receive step — the invoice image is processed, header data is extracted into the entry form, and the AP clerk reviews and posts. Header capture (supplier, invoice number, date, total, tax) is generally reliable on standard layouts; line-level extraction is patchy on the bilingual layouts the HK F&B and utility supplier base produces, and the USALI-coding suggestion is typically absent — the coding decision still sits with the clerk. Practically this lifts the manual-entry throughput on the header but leaves the line-level coding work where it was, which is where most of the time on a multi-line F&B invoice or a shared-cost cleaning-chemicals invoice is actually spent.
Route 3: Pre-accounting AI extraction with USALI-department suggestion. The third route handles the extraction-and-coding-suggestion step before the data reaches the ERP. The supplier invoice is processed end to end — full line-level parsing, bilingual handling on Traditional Chinese and English fields, supplier identification by either Chinese or English name, and a USALI-department suggestion at the line level driven by the supplier name plus the line content. The output is structured data (Excel, CSV or JSON) that loads into the property's ERP through standard import or through API. The AI suggests the department; the controller still owns the call, especially on the splitting decisions covered in section 6, and the audit trail still lives in the AP coding sheet at the property — what the AI route changes is the throughput on the receive-and-code step, not the accountability for the coding decision.
What makes this route fit the HK hotel pattern specifically is the combination of features. Bilingual handling is built in rather than bolted on, so Wismettac invoices with mixed Chinese product descriptions and English line totals process the same way as the all-English layouts. Line-level extraction supports the splitting discipline rather than breaking it — each line carries its own department suggestion, and a Diversey delivery line for kitchen-extraction degreaser comes through suggesting Schedule 8 P&M while the next line for bathroom disinfectant comes through suggesting Schedule 1 Rooms, leaving the AP supervisor to confirm or override rather than build the split from scratch. Batch throughput supports the night-audit cadence — same-day extraction across the day's invoice arrivals is the operating mode rather than an aspirational target. And the property dimension carries through into the structured output for multi-property operators, so a single Wismettac invoice covering three properties produces three property-coded outputs rather than collapsing to a single line. AI supplier invoice extraction with USALI department-coding suggestions is the concrete way HK hotel AP teams running 12th edition workflows are tooling the route in 2026; the prompt at the extraction step carries the USALI-department logic (named schedules, supplier-name hints, splitting flags on the known shared-cost suppliers) and the structured output is the input to the ERP posting.
A note on scope. Revenue management and channel management sit upstream of this work; departmental P&L analysis — reading the GOP, GOPPAR and undistributed-margin story across periods — sits downstream of it, with the controller and the GM. Payroll and MPF on the labour-cost side sit alongside, not inside; extracting MPF remittance statements for the labour-cost line below GOP is the sibling workflow with its own retention and reporting discipline.
Extract invoice data to Excel with natural language prompts
Upload your invoices, describe what you need in plain language, and download clean, structured spreadsheets. No templates, no complex configuration.
Related Articles
Explore adjacent guides and reference articles on this topic.
Hotel Invoice Coding: A Practical Guide for Finance Teams
Learn how hotel finance teams code invoices by property, department, and GL account so month-end reporting stays clean and recoding drops to a minimum.
Hong Kong Restaurant Chain Supplier Invoice Extraction by Outlet
How HK F&B chains extract supplier invoices and code them by outlet and cost type — Xero Tracking Categories, IRD Section 51C retention, posting routes.
Hong Kong Restaurant Three-Way Match: PO, Delivery Note, Invoice
Three-way match for Hong Kong restaurants — align PO, delivery note, and supplier invoice to catch short delivery, price variance, and missing credit notes.