Build the evidence pack around the exact disputed obligation. Link the agreed scope, dated submissions, version-specific feedback, acceptance decision, approved changes, invoice, and payment attempts. Separate a disagreement about work from a missing or failed transfer and from a card dispute. State what is agreed, what remains contested, and what evidence would resolve the next question before escalating.
A creator says the brand has not paid. The brand says the work was incomplete. The agency has a folder of screenshots, but no one can identify which version was accepted or whether a later request changed the original scope. The dispute becomes harder because each side's account is organized differently.
A useful evidence pack does not guarantee a favorable legal or payment-provider outcome. It makes the underlying events understandable and supports an informed conversation or qualified review. This guide is an operational framework, not legal advice. Contract rights, dispute procedures, card rules, and applicable law must be assessed for the actual arrangement.
Define the dispute before gathering every message
Write the specific question in neutral terms. Is the disagreement about whether a deliverable meets scope, whether an additional fee was approved, whether payment is due, or whether a transfer arrived? These questions require different evidence. A broad statement that the collaboration failed can hide an accepted asset and a separate unresolved request.
Use the creator contract dispute process to identify the agreed notice and escalation route. Do not invent a new remedy or threat from frustration. The operational record should show the relevant clause or commercial term, the parties involved, and the next evidence needed. Qualified advice may be appropriate when the parties interpret the agreement differently.
Assign a person to organize the record without making them the final judge of contested rights. Separate established facts, each party's position, unresolved questions, and proposed actions. That structure is more useful than a chronological dump of every message because it shows what the evidence does and does not establish.
Reconstruct the agreed scope and amendments
Start with the executed agreement or other relevant written acceptance, the approved brief, deliverables, deadlines, revision allowance, rights, and payment terms. Identify the version in effect when work began. If the commercial scope exists across several documents, explain their relationship and flag inconsistencies rather than silently choosing the interpretation most favorable to one party.
Add approved changes with the date, requester, agreed work, additional cost, and effect on deadlines. A later request for another language, location, or paid-media license may be a separate scope change rather than evidence that the original deliverable was deficient. Conversely, a correction to an agreed requirement may already be included. Preserve the actual exchange and avoid labeling it prematurely.
The creator quote normalization record can help explain which production, posting, rights, and expense lines were purchased. It is supporting context, not a replacement for the agreement. Use it to identify why two parties may be discussing different totals or deliverables and to separate a price misunderstanding from a dispute about actual performance.
| Evidence group | Useful record | Question it supports |
|---|---|---|
| Scope | Executed terms, brief version, approved changes | What work and payment were agreed? |
| Performance | Dated submissions and exact asset versions | What was delivered and when? |
| Review | Feedback, revision history, acceptance record | Which requirements were accepted or contested? |
| Payment | Invoice, authorization, provider references | What remains owed and what was attempted? |
Connect feedback and acceptance to specific versions
Identify the submitted files, their timestamps, and the review outcomes. A message saying looks good may have referred to a concept, rough cut, or final export. Preserve its context. Do not present a brief acknowledgment as definitive final acceptance unless the agreed process and surrounding evidence support that interpretation.
Use creator asset version control to connect feedback to the file the reviewer actually saw. If the disputed change was requested after acceptance, record that sequence. If the creator submitted a replacement, show whether it addressed the relevant feedback. The pack should let a new reviewer understand the versions without relying on one participant's memory of a shared link.
Include the stated reason for any rejection and the requirement it relates to. Distinguish a scope defect from a new preference or an outcome the creator did not promise. A campaign that generated fewer sales than hoped does not automatically establish incomplete production. The contractual implications require review, but the factual distinction should be visible in the evidence.
Reconcile the amount rather than argue over one headline total
Build a ledger view of the original fee, approved additions, reimbursable expenses, payments already received, and amounts currently contested. State the currency for every line. Do not subtract an unagreed refund, penalty, or future credit merely to reach a desired balance. Each adjustment needs an identifiable basis and the appropriate review.
For an illustrative case, assume an original fee of eighteen hundred dollars, an approved license extension of three hundred, and a six-hundred-dollar payment already received. The recorded remaining balance is fifteen hundred dollars before any disputed adjustment. If the brand contests two hundred of additional work, identify that line separately instead of describing the whole collaboration as unpaid or invalid.
Use a creator invoice record to connect the billed amount with the agreed scope and amendments. If a charge is missing supporting approval, mark the question and request evidence. If the invoice is simply addressed to the wrong payer entity, correct that operational issue without pretending it resolves a separate disagreement about whether the work was accepted.
Distinguish commercial disputes from transfer exceptions
A missing transfer can occur even when both parties agree on the amount owed. Record the provider reference, amount, currency, beneficiary identifier, creation time, and current verified state. Limit sensitive information to the reviewers who need it. A redacted trace record can support the discussion without exposing full bank details to every campaign participant.
Airwallex's transfer status documentation is a provider-specific reference for interpreting that service's states. Use the actual provider's definitions and evidence rather than assuming a general completed label proves receipt. The evidence pack should distinguish payment authorization, transfer creation, provider processing, and the recipient outcome that can actually be verified.[2]
If the exception is a failed payment, follow a controlled recovery path instead of starting another transfer during a scope argument. A payer's acknowledgment of an obligation and the service's ability to route funds are separate facts. Keep both visible so that a technical problem is not mistaken for commercial rejection, and a commercial dispute is not disguised as indefinite payment processing.
Treat card disputes as a separate procedure
Stripe's dispute documentation explains cardholder disputes through the card-payment process. That procedure is distinct from the creator's commercial agreement and does not by itself determine what work was delivered or what remains owed. Use the current provider requirements for any relevant card case and qualified advice for the contractual questions.[1]
If a brand funded an agency or platform by card and then contests that funding charge, identify the transaction being disputed. It may not be the same transaction as the payout to the creator. Record the funding and payout chain separately. Avoid telling the creator that a funding dispute automatically cancels an accepted obligation without reviewing the actual arrangement.
The creator refund and chargeback process can help map these distinct events. Preserve evidence deadlines and communication ownership for the relevant provider case, but do not overload that case with unrelated campaign history. Supply the evidence appropriate to the stated issue while keeping the broader commercial record available for separate review.
- Define the contested obligation
- Connect scope and asset evidence
- Reconcile charges and transfers
- Use the appropriate escalation path
Make the pack readable enough for the other side to respond
Start with a short summary, the agreed facts, the contested items, and an indexed timeline. Link to the underlying records rather than paste dozens of screenshots without context. Preserve originals and avoid selective cropping that changes meaning. A credible pack should help a reviewer understand both the evidence supporting a position and the material uncertainty that remains.
Give the other party a specific request: confirm the relevant version, provide the missing approval, identify the disputed requirement, or verify the transfer outcome. Include an appropriate response window consistent with the agreement and circumstances. Do not substitute threats, unsupported legal claims, or public pressure for a clear evidence request.
After resolution, record the agreed outcome and the operational change that would prevent the same ambiguity. That might be a better acceptance record, clearer payer identity, a more precise revision allowance, or a controlled payment trace. The goal is not to produce the largest archive. It is to make the collaboration's scope, work, and money understandable enough for a fair next decision.
- State the exact contested obligation and currency.
- Preserve the scope version and approved amendments.
- Tie submissions, feedback, and acceptance to exact assets.
- Separate commercial issues from transfer and card procedures.
- Index the records and ask for the evidence needed next.