Commission Statement Check Agent · Use case
How can a hotel group or an airline use an AI agent to check a travel agency's commission statement on its own infrastructure?
A commission statement check agent reads one commission statement from a travel agency or a sales channel, sets each line against the booking it names and the commission rate in the contract, and lists each difference, with the line and the record behind it. Accounts payable approves or disputes the statement. The agent approves nothing, pays nothing, changes no booking and sends nothing to the partner.
The statement says one thing.
The bookings may say another.
- ✗ 01A statement arrives each month from every agency and channel, in the partner's own format, with thousands of lines to set against bookings that were changed, shortened, cancelled or never stayed.
- ✗ 02Rates differ by partner, by contract period and by rate type, and a line claimed twice or at the wrong rate is easy to miss when many statements fall due together.
Where it stops for a person
Always. Accounts payable approves or disputes the statement.Always. It compares figures, it does not settle them: it gives no view on what is owed where the contract is unclear, and none on the partner. Approval, any dispute and what the partner is told are accounts payable's, and payment follows your own approval process.
It lists each difference.
Accounts payable approves or disputes.
Step · 01
An accounts payable clerk uploads the statement and names the partner.
Step · 02
The agent reads the statement: each booking reference, the dates, the amount the commission is charged on and the commission claimed.
Step · 03
It reads each booking through your own APIs, as it finally stood, and the commission terms in the partner's contract.
Step · 04
It lists each difference: a booking cancelled or not found, an amount that is not the booking's, a rate that is not the contract's, a line claimed before.
Step · 05
Accounts payable checks the list and approves or disputes the statement.
Reads from · connectors
Your own APIs
The statement, as an uploaded file; the bookings it names, read through your own APIs with the operations that change something left out; and the partner's contract and its commission terms, indexed as a knowledge source. No card numbers.
Acts through · MCP servers
Nothing. It approves no statement, releases no payment, raises no dispute, changes no booking and sends nothing to a partner.
What you set up
- Index the partner contracts and their commission terms as a knowledge source.
- Import the description of the API that holds bookings and keep only the operations that read.
- Build the agent in Katonic Studio and test it on statements your team has already checked by hand.
- Publish it to accounts payable, one partner first.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. Partner contracts, commission rates and booking records stay inside the company.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does it approve or pay the statement?
No. It lists where the statement and the records disagree. Accounts payable approves or disputes, and payment follows your own approval process.
Does it raise the dispute with the agency?
No. It has no tool that sends anything. Any dispute is written and sent by your finance team.
What does it do with a line it cannot match?
It lists the line as not found, with the reference as the statement gives it. It does not guess at a booking.