Creator Sponsorship Settlement Auditor

How to use Creator Sponsorship Settlement Auditor

Two attribution signals can disagree. Keep conflicting orders unallocated and separate fixed commitments from bounty calculations before reviewing a creator settlement.

1. Enter agreed creator terms and permitted anonymized order totals.
2. Leave conflicting coupon/UTM identities unallocated for human review.
3. Compare payout with source orders and contracts; attribution does not prove incremental sales.

Good to know

• Attribution is not causation.
• Tax, attribution windows and contractual exceptions remain external.
• Independent local review of supplied records. No account/API access, AI, publication, outreach, source-truth verification, legal certification or income forecast.
• Each field is limited to 8,000 UTF-16 characters and each CSV to 100 data rows with the exact displayed header. Quoted commas/newlines and doubled quotes are accepted. Unsupported controls, unpaired surrogates, duplicate identities and invalid records are refused rather than silently removed. Ordinary decimal inputs have magnitude at most 999,999,999; the smallest supported nonzero magnitude is 0.000000001. Exponents are refused; whole counts use exact integer checks before numeric conversion. Results use exact rational arithmetic, with at most 18 decimal digits and an ellipsis when further fractional digits remain.
• Markdown and CSV are editable review exports. CSV retains unresolved records and apostrophe-prefixes spreadsheet-like formula text; review your real import settings. Tool outputs can contain your entered pseudonymous records, so inspect them before sharing.
• Independent deterministic ToolJovia workflow. Inputs stay in this browser. No vendor account, model call, upload, publication, outreach, payment, saved input or outside service is used. A local reconciliation does not validate source truth, customers, income or legal compliance.