Introducing Terrace Accounts Receivable: Stop profit leakage in your hotel — Read more →
terrace
Travel Agent Commissions

Onyx CenterSource Reconciliation for Hotels

Terrace AI helps hotel accounting teams reconcile Onyx CenterSource commission claims against PMS data, rate codes, agency details, prior payments, and dispute records so exceptions are easier to catch and resolve.

less manual commission review
75%less manual commission review
faster TA payout close
4xfaster TA payout close
more commissions recovered
40%more commissions recovered
The unified Onyx CenterSource workflow

Every Onyx commission payout matched to the PMS reservation.

Terrace ingests Onyx CenterSource remittance and commission statements, matches each payout to the PMS reservation, validates the commission rate against your contracted terms, and surfaces underpayments for dispute.

  • Native Onyx CenterSource statement ingestion
  • Per-reservation commission rate validation
  • Underpayments and discrepancies surfaced for recovery
Terrace Onyx CenterSource reconciliation overview dashboard

What is Onyx CenterSource reconciliation?

Onyx CenterSource is a commission processing platform used by hotels and travel agencies globally. Onyx reconciliation is the process of validating commission claims submitted through the platform against your PMS data before approving payment. Hotel accounting teams need to confirm each claim matches a real commissionable stay, the agency details are correct, and the claim has not already been paid or disputed.

What teams check
  • Claim matched to a real PMS stay record
  • Rate code confirmed commissionable
  • IATA number verified against PMS booking source
  • Room nights and revenue match PMS
  • No duplicate or prior payment found
  • Dispute documentation ready for invalid claims

Why Onyx reconciliation is time-consuming for hotel accounting teams

Onyx processes claims from hundreds of agencies at once

Claim volume can be high for multi-property operators, and each claim must be individually verified against the PMS rather than reviewed in aggregate.

Each claim requires a cross-system PMS lookup

Validating an Onyx claim means pulling the corresponding PMS record, checking the rate code, and comparing room nights and revenue — steps that cannot be short-circuited at scale.

Non-commissionable rates are a frequent source of invalid claims

Rate codes vary by property, and non-commissionable rates are not always clearly flagged in Onyx claim data, making per-claim rate checking essential.

Duplicates and prior-paid claims are not auto-flagged by the platform

Onyx does not always prevent re-submission of previously paid claims, so hotels must maintain their own payment history and check each claim against it.

Dispute documentation must be submitted through Onyx with evidence

Disputing a claim requires preparing PMS evidence and submitting it through the Onyx platform within a dispute window, which adds time pressure to the manual process.

Backlogs grow quickly without automation

When claim validation falls behind, backlogs accumulate and the risk of approving invalid claims by mistake increases — especially for teams covering multiple properties.

What data needs to be matched for Onyx reconciliation?

Onyx CenterSource claim files
Commission claim exports
  • Claim ID
  • Agency name
  • IATA number
PMS reservation records
Opera, Mews, Cloudbeds, etc.
  • Confirmation number
  • Stay dates
  • Rate code
Rate code schedules
Commissionable vs non-commissionable
  • Rate code
  • Commission eligibility
  • Property
Payment history records
Prior Onyx payments
  • Payment date
  • Claim ID
  • Amount paid
Agency and IATA records
PMS booking source
  • IATA number
  • ARC number
  • Agency name
Accounting postings
GL ledger
  • Posted amount
  • Account code
  • Period

Common Onyx CenterSource reconciliation exceptions

Onyx claim cannot be matched to a PMS stay

The claim ID or stay details cannot be matched to any reservation record in the PMS.

Commission claimed on a cancelled or no-show stay

The claim references a reservation that was cancelled or a no-show and is therefore not eligible for commission.

Commission claimed on a non-commissionable rate code

The rate code for the stay does not qualify for commission under this property's commission schedule.

Duplicate claim or previously paid claim

The same claim or a near-duplicate has already been paid, creating a duplicate payment risk if approved again.

Claimed room revenue or nights do not match PMS

The number of room nights or room revenue on the claim differs from the PMS record for the same stay.

IATA or agency mismatch

The agency name or IATA number on the Onyx claim does not match the booking source recorded in the PMS.

Manual Onyx reconciliation workflow

  1. 1

    Export Onyx CenterSource claim file for the period.

  2. 2

    Look up each claim in the PMS to confirm the stay record exists.

  3. 3

    Verify rate code commissionability for each matched stay.

  4. 4

    Check IATA number and agency name against PMS booking source.

  5. 5

    Compare claimed room nights and revenue against PMS records.

  6. 6

    Review payment history for duplicate or prior-paid claims.

  7. 7

    Prepare dispute documentation for invalid claims.

  8. 8

    Approve valid claims and file the audit trail.

Automated Onyx CenterSource reconciliation with Terrace AI

Terrace AI validates Onyx commission claims against your PMS automatically and presents your accounting team with a prioritized exception queue instead of a full claim review backlog.

Claim matching

Automatic Onyx claim-to-PMS matching

Terrace matches Onyx claim IDs to PMS stay records automatically across reference formats and date ranges.

Onyx batch · 2026-04-22
Claim ↔ PMS reservation
112 claims
OX
ONX-388401
BCD Travel · IATA 10-548121
Matched
OX
ONX-388512
American Express GBT · IATA 10-298104
Matched
OX
ONX-388621
FCM Travel · IATA 10-441208
Matched
OX
ONX-388754
Direct Travel · IATA 10-771840
Fuzzy
OX
ONX-408120
Travel Leaders · IATA 10-882190
No PMS
109 auto-matched · 3 reviewProcess queue →

Rate check

Rate code commissionability check

Every claim is validated against your property's commission schedule to flag claims on non-commissionable rates.

Rate schedule · Hilton Garden Inn DTW
Commissionability matrix
Live
RAC
Rack rate
Commissionable
BAR1
Best Available
Commissionable
GOV
Government
Non-comm.
AAA
AAA Member
10% comm.
CORP-IBM
IBM Corporate
Negotiated
STAFF
Staff rate
Non-comm.
ONX-441200 claims commission on rate GOV — auto-flagged for dispute.
2 invalid rate codes todaySend to disputes →

IATA validation

IATA and agency validation

Agency name and IATA number on each claim are checked against PMS booking source records.

IATA verification · ONX-399041
Onyx claim ↔ PMS booking source
Mar 14-16
On Onyx claim
AgencyCarlson Wagonlit
IATA10-882210
ARC
On PMS folio
AgencyCWT
IATA10-558827
ARC33-8211
IATA mismatch · same agency family
Both records resolve to CWT but use different IATA codes. Suggest merging to 10-558827.
Auto-resolves 4 of 6 mismatchesApprove match →

Stay comparison

Room night and revenue comparison

Claimed room nights and revenue are compared against PMS records and discrepancies surfaced for review.

Stay comparison · ONX-394812
Onyx claim ↔ PMS folio
Apr 8-12
MetricClaimPMS
Nights43
Room revenue$1,196$897
Commission %10%10%
Commission $$119.60$89.70
Claim over-states by 1 night · $29.90 commission. Auto-dispute drafted.
Saves $29.90 on this claimSend dispute →

Duplicate check

Duplicate and prior-payment detection

Terrace checks each claim against payment history to identify duplicates and re-submitted prior payments.

Prior-payment scan · ONX-441820
Payment history check
24mo lookback
ONX-441820 · Stay Feb 14 · CONF-58102
Current submission · $84.20
Duplicate
ONX-441820 · Stay Feb 14
Paid 2026-03-14 · Batch ONX-B-0341
$84.20
Already paid 38 days ago
Identical claim reference and stay window. Reject through Onyx dispute portal with prior payment evidence.
9 duplicates caught this monthReject claim →

Dispute queue

Dispute-ready documentation for invalid claims

Invalid claims surface with supporting PMS evidence attached for submission through the Onyx dispute process.

Dispute package · ONX-412889
Evidence ready for Onyx portal
3-day SLA
Claim
ONX-412889
Agency
HRG Worldwide
Reason
Cancelled stay
At stake
$94.50
PMS reservation export · CONF-61100
Attached
Cancellation log · Feb 18 13:22 UTC
Attached
Onyx claim PDF
Attached
Property rate schedule
Attached
Exception review queue
Sample data — illustrative only
Records reviewed
5
Auto-matched
1
Exceptions surfaced
4
Source recordPMS recordIssue detectedTerrace status
Onyx Claim #OX-441200 — Stay Mar 5-7CONF-69812 — Mar 5-7Rate code GOV is non-commissionableDispute-ready
Onyx Claim #OX-388401 — Stay Mar 10-12CONF-72010 — Mar 10-12Commission rate and revenue matchAuto-matched
Onyx Claim #OX-412889 — Stay Feb 19CONF-61100 — Cancelled Feb 18Claim for cancelled stayDispute-ready
Onyx Claim #OX-399041 — Stay Mar 14-16CONF-73920 — Mar 14-16IATA #88221 does not match PMS booking sourceNeeds review
Onyx Claim #OX-408120 — Stay Mar 8No match foundStay record not found in PMSMissing PMS match
Get started

Put hotel revenue on autopilot

From OTA statement to GL posting — faster cash, accurate books, and less manual reconciliation.

Frequently asked questions

Onyx CenterSource reconciliation is the process of validating commission claims submitted through the Onyx platform against your PMS stay records, rate codes, agency details, prior payments, and dispute history to confirm each claim is valid before it is paid.