Data Effica Digital

Client stories

Specific engagements — what was mismatched, what we traced, and what the property did next.

“They traced three months of Agoda remittances against our night audit packs. Two commission rows were wrong; the rest simply arrived late. The brief was long, but every exception had a folio number.”

— Mei Ling, finance controller, boutique hotel, Georgetown

“We asked only for a channel analytics review before peak season. The memo showed our booking app was filling midweek rooms while one OTA contributed almost nothing after commission. Useful, though I wished they had included breakfast-package stays in the first pass — we added those later.”

— Arif, revenue manager, beach resort, north Penang

“A disputed Booking.com batch had sat in my inbox for weeks. Their reconciliation schedule separated currency rounding from three genuine missing stays. I still had to chase the channel myself, but I finally had a clean schedule to send.”

— Soft spoken owner-operator, serviced residence, Jelutong

Extended story: 68-room city hotel, three OTAs

The general manager noticed February cash lagging occupancy. Night audits looked complete; bank credits for two OTAs arrived in irregular clumps. We scoped a booking revenue audit for January–March across three OTAs and one consumer booking app.

Intake took four days while the property rebuilt missing remittance PDFs. Matching showed eleven stays posted under “direct” that originated on an OTA — a front-office source coding habit — and one remittance that credited a sister property by mistake. Net cash impact was modest, but the coding habit was distorting channel reports used for contracting.

The findings brief recommended a weekly source-code check at night audit close. Six weeks later the finance controller confirmed OTA-coded stays aligned with remittances for the following month. No miracle recovery — just cleaner books and fewer false alarms.

Extended story: Langkawi resort, single-app dispute

A resort contacted us for a reconciliation assessment on one booking-app batch covering Chinese New Year departures. Folio totals and the app’s remittance differed by a mid-five-figure ringgit amount.

Our schedule found early checkouts billed at full rate on the folio but refunded inside the app after the remittance freeze date, plus two no-shows the app still treated as completed stays. Once those lines were isolated, the residual gap fell inside the channel’s documented rounding rules.

The property used the schedule in its merchant ticket. The episode reinforced why we keep reconciliation assessments narrow: when only one batch is contested, a full multi-month audit would have delayed the answer.

Request a similar review