Expedia bookings can arrive under two different payment models, and reconciling what you're owed means knowing which one applied to a given reservation before you start checking numbers.
A property running Expedia bookings for any length of time eventually finds a reservation where the payment doesn't behave the way they expected, and usually the first question to answer isn't whether the number is wrong — it's which of Expedia's two payment models that specific booking was under. Collect and Hotel Collect reconcile against completely different records, and mixing them up is the most common reason the math looks off.
Under the model commonly called Expedia Collect, Expedia takes payment from the guest at the time of booking and later pays the property the room revenue minus its commission, meaning you reconcile against a payout from Expedia rather than against anything the guest paid you directly. Under Hotel Collect, the property takes payment from the guest directly — typically at check-in or during the stay — and Expedia separately invoices the property for its commission afterward, meaning you reconcile against your own folio and a commission invoice rather than a payout.
Both are normal, contracted arrangements, and a single property can run bookings under both models at once depending on the rate plan or arrangement each reservation falls under.
Which model applies is usually set at the rate plan or contract level rather than chosen booking by booking, so a property can have one set of rate plans configured under Collect and another under Hotel Collect, often without anyone on the day-to-day team thinking about which is which until a reconciliation question comes up. A rate plan added later, or a renegotiated contract term, can also introduce a second model into a property that previously only ran one, which is when the two getting mixed up in reconciliation becomes a real risk rather than a theoretical one.
For a Collect booking, start from Expedia's payout report for the relevant period and match the specific reservation's line to the commission deducted and the net amount paid, rather than trying to recreate the number from the extranet's displayed rate alone. For a Hotel Collect booking, start from your own folio for what was actually charged to the guest at the property, then separately check Expedia's commission invoice for that reservation to confirm the commission amount and rate applied match your contract. Reconciling the wrong document against the wrong booking — a payout report against a Hotel Collect reservation, or a folio against a Collect one — is the single most common way this goes wrong.
Prime Shield compares the rate you sent, the rate you intended, and what the guest actually paid, and flags any gap worth more than 5% in plain money, which helps regardless of which payment model a specific booking falls under, since the underlying question — did this reservation net what it should have — is the same either way. Bank-level reconciliation adds the payout side for channels it covers, matching batches and computing expected payment dates so a Collect-style payout isn't reconstructed by hand each period. If reconciling two payment models has been eating time every cycle, that's the structural fix — the public demo at try.primehostpartners.com is open to try without signing up.