Two sources of truth.
Zero copies in between.
Sabre knows what was booked. Central Command knows what was settled. Queue Zero is the live layer that keeps them agreeing — from PNR creation to ARC/BSP settlement to the advisor’s statement.
Most host agency stacks keep three, four, or five copies of every booking
The GDS, a mid-office tool, a commission tracker, the accounting system — and a spreadsheet reconciling the other four. Every copy is a place for the truth to drift.
Two systems of record. One live layer keeping them in agreement.
Both databases are already the industry-standard pairing, already trusted by large host agencies. Queue Zero becomes the middleware that pieces together front, mid, and back office — not another database, but the end of extra databases.
It already knows how to settle. What it consumes is files.
Central Command is a travel-industry ERP built on Unit4 — strong at exactly the back-office work host agencies need. What it lacks is a live conversation with the GDS side.
ARC/BSP reconciliation
Imports the BSP HOT file / IAR data and compares what the GDS sent to BSP against what it sent to Central Command — auto-updating matches and producing coded exception reports for voids, refunds, and discrepancies.
Commission reconciliation
Handles clearing houses beyond ARC — formats including TACS (Onyx CenterSource), NPC, and Pegasus — plus supplier-direct formats. It already knows how to close the loop on the money.
A file-based GDS interface
The GDS print manager drops message files into a parser folder; the IFP Parser processes them into the back office. It works — but it's batch, one-directional, and file-system-dependent. A missing message file goes unnoticed until reconciliation.
No live view for front-line teams
Batch windows and parser folders mean an advisor can't see “ticket issued” and “ticket settled” on one screen. The cleaner and more complete the GDS feed, the shorter the exception report — that's Queue Zero's whole job.
What the API-native integration enables
Integrate Queue Zero against Unit4’s API layer and Central Command becomes a live endpoint rather than a folder of parsed files. Data moves both ways — closing the loop from PNR creation to advisor payout.
Downstream — Queue Zero → Central Command
Upstream — Central Command → Queue Zero
Roadmap & forward-looking statement. The Unit4 / Agresso API integration described here is a planned, future capability — not a shipped product — subject to change and dependent on third-party API availability and partnership terms. Unit4, Agresso, ServeVita Central Command, ARC, BSP, IATA, TACS, and Onyx CenterSource are third-party names/trademarks referenced descriptively; no partnership, certification, or endorsement is implied.
Already on the Sabre + Agresso pairing?
See where the pairing is headed — and how Queue Zero fits in today as the real-time layer between them.
Talk to us about your setup