Commission Matching

Last updated September 12, 2026

Every commission payment that comes in has one job: find the booking it paid for, so the advisor gets paid and the money lands in the right year. Most of the time JourneyFuse does that on its own. This article explains what it is looking at when it matches, the daily routine agency owners use to keep everything moving, and what to check on the rare payment that says no match when you know the booking is in your account.

The goal is always the same: move everything to Payouts. Imports and the Inbox are where the work happens. Payouts is where it ends.

The daily routine

Start at Imports, every time. That is where anything you send or upload lands first, and it is the screen that does the most matching for you.

1. Bring the statement in

Three ways, best first:

  • Forward the supplier's email to your workspace's commissions address (shown with a Copy button on the Inbox and Imports tabs). Every line on the statement is read automatically.
  • Upload the file — click Import statement (AI) and drop in a PDF, spreadsheet, or a screenshot. A screenshot works well for a payment advice you only have on screen. You review what was read, then confirm.
  • Record payment by hand — for a check or ACH that never came with a statement. Pick the payer, the amount, the date, and the reference. See Which number goes in Reference below, because this is where most hand-recorded payments go wrong.

2. Read the match detail

Open Match detail on the statement. For each line you see what the supplier said next to what your advisor entered on the booking, with a dot for each thing that agrees:

  • Reservation number — the strongest signal by far
  • Guest name
  • Advisor
  • Amount — a match within a few percent still counts, so a $252.05 payment on a $252.00 expectation shows green
  • Dates — travel and booking dates

All green means the advisor's booking and the supplier's statement agree. That is the ideal case, and it needs nothing from you.

Long statements: three piles

A statement with four or more lines opens already sorted, so you are not reading twenty rows to find the three that need you:

  • ■ Exact — the reservation number and the amount agree. Collapsed; its menu sets all of them at once.
  • ◆ Needs a decision — a commission was found, but the amount, the reservation number or the traveler disagrees. Open by default, and never offered "To payouts" in bulk: each of these is decided on its own row.
  • □ No match — nobody has filed a commission for these. Its menu can record them all as one advisor's commission. A line whose reservation an advisor has filed, but which is still waiting for your approval, says so and offers Approve claim on its row.

Recording a line as an advisor's commission never records a sale twice. Before it creates a commission, JourneyFuse checks the reservation number against the commissions you already have. If a trip's booking already expects that reservation and hasn't been paid, or any commission expects exactly that amount, the line is not recorded. It comes back in the list of lines that need you, with a note like "Reservation 1466550 already has a commission on a trip's booking, expecting $273.60". Match the payment to that commission instead. A different-amount claim on the same number does not stop it, because two suppliers sometimes share a number (an insurance policy filed under the number of the cruise it covers).

The payouts screen has the same protection. A claim is held from payout when a booking with the same reservation and the same commission amount has already been paid, or is about to be, even if the two were set up at different advisor splits. Review it there: cancel the duplicate claim, or record why it is a separate commission.

The bar under the statement's title shows the same split at a glance. Each line marks the reservation number with a ★ when the supplier's number agrees, or ☆ Reservation differs when it names a different one, and shows the payout arithmetic — expected, paid, the advisor's share of what actually arrived, and the agency's remainder.

The top of the Imports page counts the whole queue in lines rather than statements: waiting, exact, need you, no match, and — when QuickBooks is connected — how many statements already have their cash in your books.

When a match is approved over a different reservation number, JourneyFuse records it quietly: which supplier, the number the supplier used, and the numbers on the booking. Disney is the usual case — it often pays against a different number than the confirmation an advisor saved. Nothing about the payment changes; the record is there so matching can learn which numbers each supplier really uses.

When a supplier pays a commission in a different currency than the advisor filed — a Canadian hotel paying C$120.00 that lands as $87.60 — the line says converted, not short, and shows the rate. On Imports, click Converted — to payouts with note: when you press Process the commission closes at what arrived and the advisor gets an email saying it was the same commission converted at that rate, with their share and when it pays. In the Inbox the same case appears under Gaps to answer with Close & send conversion note, which lets you read the email before it sends.

When the statement prints its own commission and revenue in that currency, the rate bars use them. A Canadian hotel line reads, for example, "paid 10% of CAD 575.04 revenue · filed 10% of the $192.48 sale". Both bars then show the supplier's real rate. If the two rates are the same, the gap comes from the amount the commission was paid on (often a longer stay or a later rate) or from the exchange rate, not from a different commission rate.

3. Process

Click Process. Each line goes one of three places:

What happenedWhere it goesWhat you do
Everything matchedPayoutsNothing. If you pay after travel, it sits as pending until the trip ends, then becomes payable.
Matched, but the amount is offInbox → Variance flagsPick a reason (short-pay, rate was wrong, client cancelled) or send the advisor a one-click note asking them to confirm the supplier's terms.
No booking foundInbox → Unmatched paymentsEither an advisor hasn't entered the booking yet, or the number on the statement doesn't line up with the number on the booking. See below.

4. Work the Inbox

The Inbox is where you make decisions. Every morning, open it and clear the buckets:

  • Unmatched payments — click Review. Search by the booking number or the traveler's last name. When the right booking appears, review the match and confirm. If the advisor booked it outside JourneyFuse, use Advisor booked this directly to create the commission and link the payment in one step.
  • Variance flags — resolve the difference. Most are advisor typos on the expected amount; the rest are real short-pays you follow up with the supplier.
  • Awaiting supplier — expected money that hasn't arrived. The Suppliers tab shows each supplier's typical pay lag, so you can see who is late and chase from there.

The top of the Inbox is four lanes — Match payments, Gaps to answer, Advisor claims and Late from supplier — each marked You or Supplier for whose move it is, with the next step written underneath. Needs filing only appears when there is something to file.

Late from supplier counts only commissions 30 or more days past their expected date; the rest are not late yet and sit behind their own chip. A bar shows the ageing, and anything over 180 days is called out as a write-off decision rather than a chase. The By supplier table groups what is late, and says whether each supplier has an email on file — a chase can only go to a supplier JourneyFuse has an address for. Select picks every late commission for that supplier, ready for Chase.

On Gaps to answer, each row shows the reservation star, and under the received amount what the advisor and the agency would take if you close at what arrived. When the supplier paid more, the menu offers Close & send "paid more" note as well as closing without an email.

5. Payouts

Once a payment is matched and the hold period has passed (for most agencies, when the trip ends), it appears in Payouts grouped by advisor. Pay through DOTS, or export a file for your bank. The Forecast view shows what is coming due by month.

Optional: Deposits

Some agencies want to confirm the money actually hit the bank before paying advisors, not just that the statement arrived. The Deposits tab groups payments by the check or deposit they arrived on so you can tick them off against your bank feed, and it can sync with QuickBooks. It is entirely optional.

Each bank line on Deposits is labelled:

  • Exact / Close / Unclear — a statement you haven't confirmed yet matches this line exactly, nearly, or in more than one way.
  • Already confirmed — this money was already confirmed, usually because the same credit came in twice (an uploaded file, then QuickBooks). It can't be matched a second time. Open it and choose Same deposit — set aside. Set-aside lines stay under Dismissed with the reason, so you can undo it.
  • No match — no statement covers this amount. When the bank line names a supplier, the row says so ("No statement from Carnival covers this amount"). That means the supplier's remittance never arrived: ask them for it, import it, and the line will match.

What a booking needs to be matchable

A payment can only match a booking that JourneyFuse can see. Three things have to be true:

  1. The booking exists in JourneyFuse, on a trip, with the advisor assigned.
  2. The booking carries the supplier's reservation number — exactly as it appears on the supplier's statement. Not the invoice number, not the client's trip name.
  3. There is a commission to match against — either a commission amount on the booking, or a commission the advisor submitted.

If any of these is missing, the payment will show no match even though "the booking is right there." Fixing the booking fixes the match.

Which number goes in Reference

When you record a payment by hand, the Reference field is what the matcher compares against your bookings. Put the supplier's reservation or booking number for that line — the same one your advisor typed on the booking.

Do not put the check number, the document number, or the statement number there. On a payment advice those are usually at the top of the page and they identify the payment, not the booking. A reference filled with a document number will never match anything, and it is the single most common reason a hand-recorded payment sits in Unmatched.

If one check covers several bookings, record one line per booking, each with its own reservation number. The Record payment form has a separate Check / statement # field for the document number; it is kept in the payment's notes so the paper trail survives without confusing the matcher.

Lines that arrive together stay together. The Inbox shows one card per statement, with the check or statement number in its header and every open line beneath it, so a five-booking check reads as one check.

Import statement does this for you. A screenshot is enlarged before it is read, which is what stops an 0 turning into an 8; a supplier's own CSV, when it offers one, is read column by column with no reading step at all, so prefer it over a screenshot when you have both. When it reads a payment advice it separates the two numbers itself: each line's reservation number becomes the Reference, and the statement number is noted as statement 2000429938 on every payment from that document. Check the Reservation # column on the review screen before you import; if the supplier printed it in a way the reader misread, fix it there.

Spreadsheets with more than one sheet. When a workbook has several sheets, the import reads the one that holds the payments and tells you which it read, for example Read the "Commission_by_PayoutDate" sheet. A sheet that lists your bookings or the commission a supplier expects to pay is never read as money. Dates are read the way the file writes them, so a day-first date such as 05-10-2026 comes in as 5 October, not May 10. The guest, the advisor, and the travel and booked dates are brought across wherever the sheet has them.

Virgin Voyages. Upload the Commission report you download from the Virgin agent portal as it is. It has two sheets, and only Commission_by_PayoutDate is money. Each payout comes in with its booking number, the sailor's name, the First Mate (advisor), the booked and sail dates, and the date Virgin calculated it. Two things are corrected for you. Rows the export repeats word for word are counted once. Payouts dated after today are left out until they're paid, and the next report picks them up.

Allianz: the plan sets the rate. Allianz's AgentMax report prints each policy's plan, premium, and rate, and those come in with the payment. Allianz pays a fixed rate per plan, for example 36% on a single-trip Premier Plan and 20% on every annual plan. Because both have "Premier" in the name, the most common Allianz gap is an annual plan filed at the single-trip rate. When that happens the line says so and shows both calculations, for example Allianz Travel Insurance paid 20% of $715.00, its rate for the Annual Premier $5K. The claim used 36%. Close and tell sends the advisor an email that names the plan and the rate to use next time.

Advisor notes stand apart. Anything an advisor typed when filing is shown in a blue quote with their name on it, so you can always tell their words from JourneyFuse's explanation.

Already recorded. The review screen also checks every line against the payments you already have. A line with the same supplier, reservation number, amount and payment date is marked Already recorded, unticked, and linked to the payment on file. This is what catches the same statement arriving twice, for example forwarded to your commissions inbox and then uploaded by hand. A different guest name on the two lines means they are different bookings, so they are not flagged, and a recalled payment never counts. If a supplier really did pay the same line twice, tick the row again and it imports anyway. Lines without a reservation number are never flagged, because there is nothing to tell a repeat from a second real payment.

Why didn't my payment match?

Work down this list. Almost every unmatched payment is one of these.

The reservation number differs. Compare the number on the statement with the number on the booking, character for character. Suppliers sometimes print a shortened or differently formatted version. If the booking has the wrong number, fix it on the booking, then open the payment and search for it.

The reference on the payment is the check or document number. Open the payment, click Edit, and replace it with the reservation number. Then review again.

The advisor filed it, but nobody has approved the claim yet. A claim becomes a commission only when it is approved, and only commissions can be matched. When a statement line has no match but an advisor has filed that exact reservation number, the Imports row says so — "Pat filed FM0G23 on Sep 27 — it is waiting for your approval" — and offers Approve Pat's claim. That is the same Approve as on the claim itself (your usual rules still apply, and the advisor is notified). Once approved, the line re-checks and matches by its reservation number; the payment itself is still only recorded when you press Process.

The advisor hasn't entered the booking yet. Nothing to match against. Send them the payment details from the Inbox, or wait for their submission. If your agency uses Unclaimed commissions, the payment appears there and the advisor can claim it themselves.

The booking is there but has no commission on it. Open the payment, search for the booking number. It will appear marked No commission recorded yet. Click Record & match to create the commission from the payment amount and link them in one step.

The booking is there but nobody recorded a commission for it. The Inbox still names the booking ("→ Pauline True — True/Europe/Aug26 · no commission recorded yet") and the payment's match page says so in words. Click Record & match there, or open Review and choose the booking: the commission is recorded from the statement's figure and the payment is matched in one step. Nothing is ever recorded automatically.

The supplier's payer name doesn't match the booking's supplier. A parent company pays for several brands (ALG pays for Funjet and Apple Vacations; Disney pays for its parks and cruise line). Searching by reservation number finds the booking regardless of the brand name. If it keeps happening for one supplier, add the brand under the payer in Suppliers.

Amounts differ. That is a variance, not a failed match. Resolve it in the Variance flags bucket.

One check arrived as several lines. That is expected: each line matches its own booking. If a line is unmatched, review that line alone. The Deposits tab shows the whole check together.

Several lines pay one booking. The Inbox adds them up for you and offers one row with one Accept when the lines together equal a claim to the cent. It looks for three shapes:

  • the same guest on one statement (two Viator lines for one tour);
  • a group block paid one line per attendee. Hilton prints the group's number on every attendee line, so file the group once under that number and all its lines match it together;
  • the same guest across separate statements (a long hotel stay paid in two parts).

If the lines add up to less than the claim, nothing is proposed. Open one and match it by hand, choosing More is coming or That's the final amount.

The advisor cancelled the claim, and the supplier paid anyway. The row says who cancelled it, when and why, instead of Not submitted yet. Ask the advisor whether the client kept the booking. If they did, reinstate the claim and match the payment. If not, hold the money, because the supplier may take it back.

The supplier name has a typo. A payment under a misspelt supplier ("Vacatino Creations") can never match, because nobody filed a claim under that name. When an open payment's supplier is one or two letters away from a supplier you already work with, the Inbox shows a banner with Change to …, which renames every open payment under the typo in one step.

A supplier login is your shared agency account. Statements name the advisor by their supplier login, such as an Allianz agent code. Open Supplier logins on open lines at the top of the Inbox to say what each login means: one advisor, or Shared agency login. A shared login is never read as one person, so its lines are not assigned to anyone in bulk, and you choose the advisor line by line.

An advisor's own booking. When a statement names an advisor on your team and nobody has filed a claim, the line waits with the other unfiled lines, tagged with who the statement names. Record for … is still there if you want to record it for them. An owner's or admin's own booking gets its own line, because they have nobody to file to.

Closing at what the supplier paid. When you close a short-paid claim at the supplier's figure, or answer That's the final amount, it is settled. It does not come back as a gap to answer, and the advisor's payout is not held.

After a migration

If your bookings came over from another system, the reservation numbers and commission amounts came with them, but the history of what you were already paid usually did not. For the first few months, expect some statements to pay commissions the old system already recorded as received. Match them anyway; the ledger stays accurate, and the payout hold keeps anything from going out twice.

This is part of JourneyFuse’s travel commission tracking: expected commissions, supplier statements and payouts.