Exception Queue
Nothing is silently written off. Every item here is owned, aged, and resolved with an audit trail.
Unresolved payment variances by marketplace
A nickel alone is noise — a month of them is a phone call. Each packet lists every transaction behind the total, ready to send for resolution.
What is this — and what do Resolve / Dismiss actually do?
What happened: Inventory has sat unsold long enough to flag.
Resolve: Closes it once the team acted (repriced, moved marketplaces, wrote off).
Dismiss: Closes it if it's intentional (e.g. holding for playoffs).
Normally: A pricing decision for the team, not a bookkeeping one.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: Card charges with no purchase record close enough in amount and date. Common causes: several charges funding ONE purchase (the matcher only pairs 1-to-1 — Match manually handles combos), a PO that isn't in Skybox, or spend that simply isn't tickets.
Resolve: Closes the group with your note. The charges stay recorded — nothing is deleted. If the charges ARE ticket spend, prefer Match manually: that links them to the purchase AND clears this automatically.
Dismiss: Closes it without a real note. For recurring non-ticket merchants (subscriptions, utilities), use "Not ticket-related — never ask again" instead so the merchant stops raising exceptions forever.
Normally: Tickets → Match manually. Personal/recurring spend → Not ticket-related. Genuinely unknown → ask Reed's card statements, then decide.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: Card charges with no purchase record close enough in amount and date. Common causes: several charges funding ONE purchase (the matcher only pairs 1-to-1 — Match manually handles combos), a PO that isn't in Skybox, or spend that simply isn't tickets.
Resolve: Closes the group with your note. The charges stay recorded — nothing is deleted. If the charges ARE ticket spend, prefer Match manually: that links them to the purchase AND clears this automatically.
Dismiss: Closes it without a real note. For recurring non-ticket merchants (subscriptions, utilities), use "Not ticket-related — never ask again" instead so the merchant stops raising exceptions forever.
Normally: Tickets → Match manually. Personal/recurring spend → Not ticket-related. Genuinely unknown → ask Reed's card statements, then decide.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: Card charges with no purchase record close enough in amount and date. Common causes: several charges funding ONE purchase (the matcher only pairs 1-to-1 — Match manually handles combos), a PO that isn't in Skybox, or spend that simply isn't tickets.
Resolve: Closes the group with your note. The charges stay recorded — nothing is deleted. If the charges ARE ticket spend, prefer Match manually: that links them to the purchase AND clears this automatically.
Dismiss: Closes it without a real note. For recurring non-ticket merchants (subscriptions, utilities), use "Not ticket-related — never ask again" instead so the merchant stops raising exceptions forever.
Normally: Tickets → Match manually. Personal/recurring spend → Not ticket-related. Genuinely unknown → ask Reed's card statements, then decide.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: Card charges with no purchase record close enough in amount and date. Common causes: several charges funding ONE purchase (the matcher only pairs 1-to-1 — Match manually handles combos), a PO that isn't in Skybox, or spend that simply isn't tickets.
Resolve: Closes the group with your note. The charges stay recorded — nothing is deleted. If the charges ARE ticket spend, prefer Match manually: that links them to the purchase AND clears this automatically.
Dismiss: Closes it without a real note. For recurring non-ticket merchants (subscriptions, utilities), use "Not ticket-related — never ask again" instead so the merchant stops raising exceptions forever.
Normally: Tickets → Match manually. Personal/recurring spend → Not ticket-related. Genuinely unknown → ask Reed's card statements, then decide.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: Card charges with no purchase record close enough in amount and date. Common causes: several charges funding ONE purchase (the matcher only pairs 1-to-1 — Match manually handles combos), a PO that isn't in Skybox, or spend that simply isn't tickets.
Resolve: Closes the group with your note. The charges stay recorded — nothing is deleted. If the charges ARE ticket spend, prefer Match manually: that links them to the purchase AND clears this automatically.
Dismiss: Closes it without a real note. For recurring non-ticket merchants (subscriptions, utilities), use "Not ticket-related — never ask again" instead so the merchant stops raising exceptions forever.
Normally: Tickets → Match manually. Personal/recurring spend → Not ticket-related. Genuinely unknown → ask Reed's card statements, then decide.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: Money landed in the bank that doesn't line up with any marketplace payout on record.
Resolve: Closes it with your note once you know what the deposit was (e.g. a payout the marketplace never emailed about, a transfer, a refund).
Dismiss: Closes it if it's not marketplace money (owner transfer, interest, etc.).
Normally: Identify the sender in the bank feed, note it, Resolve.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: A marketplace paid a different amount than the invoices it covered — fees, short-pays, or clawbacks TicketLedgers couldn't fully explain.
Resolve: Closes it with your note once the gap is explained (expected fee) or recovered (dispute won).
Dismiss: Closes it if the variance is too small to chase.
Normally: Small and fee-shaped → note it and Resolve. Large or wrong → open a dispute packet from this page first.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.
What is this — and what do Resolve / Dismiss actually do?
What happened: A marketplace paid a different amount than the invoices it covered — fees, short-pays, or clawbacks TicketLedgers couldn't fully explain.
Resolve: Closes it with your note once the gap is explained (expected fee) or recovered (dispute won).
Dismiss: Closes it if the variance is too small to chase.
Normally: Small and fee-shaped → note it and Resolve. Large or wrong → open a dispute packet from this page first.
Both buttons only close this item with a note in the audit trail — neither deletes data, changes Skybox, or moves money.