Agent Commission Submissions: Full Lifecycle

When an agent logs a booking in the agent portal (Commissions → New Submission), it becomes a commission submission the agency reviews. This article covers exactly what each side can do at every stage — useful for training agents and for agencies setting expectations.

Roles in this article. "Agent" means an advisor working in the agent portal (myatlasgo.com-style host-agency portal). "Agency" means an owner or admin working in the full app at journeyfuse.com.

The stages

A submission moves through these states:

• Pending — submitted, waiting for agency review.
• Needs attention — the agency sent it back with a note.
• Approved — the agency accepted it into commission tracking.
• Cancelled — terminal; the booking won't pay.

What the AGENT can do

Action	Pending	Needs attention	Approved
Edit fields (supplier, guest, dates, amount)	✅ Yes	Via "Respond"	❌ Locked
Withdraw it	✅ Yes (before it's sent)	❌	❌
Respond & resubmit	—	✅ Yes	—
Request a change	✅	✅	✅
Request cancellation	✅	✅	✅

Editing before approval. While a submission is pending, the agent can edit it directly — supplier, reservation number, guest, dates, and gross commission (their share recalculates from their split automatically).

Once approved, it's locked to the agency. This is by design — the approved record is the agency's to manage. The agent can't silently change an approved commission. Instead they use Request a change (below).

Withdrawing. An agent can withdraw a submission only while it's still pending and hasn't been sent. Withdrawals are recoverable — see Recovering a withdrawn submission below.

Request a change. When a booking changes after it's logged (cabin upgrade, reprice, added guest), the agent clicks Request a change on the submission, describes what's different, and the agency gets notified. The agency makes the edit and marks it done. This works at any stage, including approved.

Request cancellation. If a trip cancels, the agent clicks Request cancellation with a reason. This does not cancel it outright — the agency confirms or declines.

What the AGENCY can do

From Commissions → Inbox → Pending submissions, the agency works a set of cards:

• Pending submissions — review, then Approve or Send back with a note.
• Cancellation requests — confirm (→ Cancelled) or dismiss (stays active).
• Change requests — an advisor flagged a needed edit; make the change, then Mark done.
• Needs clawback — see Clawback below.
• Recently withdrawn — restore a submission removed by mistake.

Reassigning the agent of record. Open a submission's Review panel and use Agent of record → Reassign. This moves the booking — and its payout/1099 attribution — to a different advisor, and makes it appear in that advisor's portal. Owners and admins only; agents cannot reassign.

Wrong client or guest

Guest names on a submission are free-text (first/last name) — there's no separate "client record" to move it between. So a wrong name is simply corrected, not deleted and re-entered:

• While pending, the agent can edit it directly.
• At any stage, an owner/admin can fix it from the submission's Review panel → Guest → Edit guest (logged to the history).
• An agent on a locked submission uses Request a change to ask the agency to fix it.

Duplicate submissions

If the same booking is submitted twice while the first is still a draft, JourneyFuse updates the existing draft rather than creating a second row — so accidental duplicates don't pile up. (Once the first has been sent to the agency, a re-submit does create a new record.)

Cancellations and clawback

When a submission is cancelled after the advisor was already paid (agencies pay agent-portal advisors outside JourneyFuse), JourneyFuse raises a Needs clawback flag on the commission inbox. JourneyFuse never silently reverses a payout — it flags the commission so the agency can recover the funds and then click Mark resolved.

On the full-app side, cancelling a booking automatically writes off any unpaid commission and flags any already-paid commission for clawback the same way.

Policy and activity records

A submission's type (Trip / Policy / Activity) is chosen at submit time, and each is its own standalone record. An insurance policy or an excursion is edited or cancelled independently — there's no parent booking to touch.

Audit trail and recovery

Every submission keeps a history: created, edited, withdrawn, resubmitted, change requested, cancellation requested/confirmed, reassigned, guest edited, and restored. Nothing is silently lost. The agency can see the full timeline under History in a submission's Review panel (who did what, and when).

Recovering a withdrawn submission

Withdrawing is a soft delete — the record is hidden from active lists but kept. The agency sees it under Commissions → Inbox → Recently withdrawn and can click Restore to bring it back in its prior state. (Owners/admins only.)

Gotchas worth training on

• Approved = locked for agents. Agents use Request a change, not direct editing, on an approved submission.
• Cancellation is a request, not an instant action. The agency confirms it.
• Reassigning changes who gets paid. It updates payout and 1099 attribution, so it's owner/admin-only.
• Editing a pending submission doesn't re-notify the agency — it stays pending; the agency sees the updated values on next review.
• Editing an approved submission does not re-trigger review or any downstream automation (e.g. ID verification / payment-setup webhooks fire once, on the first booking only).

Related

• Commissions Workflows by Role
• When Clients Change Their Mind
• Commission Reconciliation