The creator payout report that ends the monthly argument
What the numbers say
- 01
A creator who can see 90 link clicks and is told they drove 3.6 orders is looking at a 4% conversion rate, which reads as underreporting without the path shown.
Modelled on stated assumptions: 3% click-through on a 3,000 reach and 4% conversion.
- 02
On a 200-creator roster a 12% monthly dispute rate consumes 24 disputes and 18 hours, which is 11% of a manager's month or Rs 14,400.
Modelled on stated assumptions: 0.75 hours per dispute at Rs 800 an hour.
- 03
Cutting that rate to 4% saves 12 hours and Rs 9,600 a month on the same roster.
Arithmetic on the same assumptions.
- 04
Korant resolves each sale through 5 checks in a fixed priority order, and naming the check that fired is what makes a payout line auditable.
Korant sale attribution priority order.
The message that arrives on the ninth of every month
It is always politely worded and it is always the same message. Are you sure that is right, because it feels low.
The brand’s answer is also always the same. We checked, that is what the system says.
Neither party can move from there. The creator has a number in her head built from clicks she can see and three friends who told her they bought. The brand has a number from a dashboard nobody has shown her.
The argument is not really about the amount. It is about the fact that one side has the evidence and the other side has a feeling, and there is no shared surface to reconcile them on.
Every month this happens, the relationship loses a little, and after four or five rounds the good creators quietly stop replying to campaign invites.
Why the creator’s numbers and yours disagree
The gap is structural rather than anyone being unreasonable, and it helps to see the shape of it.
A creator can see her own analytics. Her post reached 3,000 people and 90 of them tapped the link. Those are real numbers from her own platform.
You tell her she drove 3.6 orders.
From her side that is a 4% conversion rate on people who were interested enough to tap. She does not run a store and has no reason to know that 4% is normal, so the number reads as either a broken link or a brand shaving the count.
Both of those suspicions are reasonable given what she can see. Neither is addressed by repeating the total more firmly.
There is a second source of disagreement that is worse, because it looks like bad faith even when the policy is sound. A total that drops between months, because an order was returned and the commission reversed, with no line explaining it.
What a line-item payout report looks like
The fix is to stop sending a total and start sending rows.
| Order date | Order value | Resolved by | Commission | Adjustment |
|---|---|---|---|---|
| 04 Aug | Rs 2,140 | Discount code | Rs 321 | |
| 07 Aug | Rs 1,650 | Last-touch cookie | Rs 248 | |
| 09 Aug | Rs 1,890 | Discount code | Rs 284 | |
| 11 Aug | Rs 3,200 | Last-touch cookie | Rs 480 | |
| 18 Jul | Rs 1,750 | Discount code | Rs 263 | Returned, reversed |
Five rows a creator can check against her own sense of what happened, including the reversal from a previous month appearing explicitly in this one.
The report should be hers alone. Her slug, her orders, her deductions, with no pooled figures and no other creator’s data.
Pooled reporting is what creates the suspicion in the first place, because a share of a pool is unverifiable by definition. A creator receiving 14% of a campaign total has no way to know whether that is right.
Send it on a fixed date with a fixed window, and send it whether or not there is anything on it. A month with zero orders and a report showing zero rows is far better than silence.
Naming the check that credited the sale
The Resolved by column is the one that changes the conversation, and it is the one most reports omit.
Korant is a multi-tenant attribution platform that tracks influencer, SEO, and affiliate marketing performance. Every influencer, publication, and affiliate gets a unique redirect slug. Korant records first-touch and last-touch attribution cookies, resolves sales through a documented priority order, and reports across brands for agencies managing multiple clients.
Sales resolve through five checks in a fixed order: discount code to influencer, discount code to affiliate, last-touch cookie to influencer, last-touch cookie to affiliate, then cookie to publication.
Naming which check fired on each row turns an assertion into an audit trail. A creator who sees that three of her five orders came through her code and two through her link understands what the system is actually doing.
Share the order itself when the deal is signed, not when the first dispute arrives. Explaining attribution logic after somebody has queried a payment always sounds like a justification constructed for the occasion.
The same transparency prevents a subtler problem. A creator who knows codes resolve ahead of cookies will make sure her code is visible in the post, which improves her numbers and yours at the same time.
Deductions have to be their own line
Silent deductions cause more damage than the amounts involved, and they are entirely avoidable.
Three deductions are legitimate and each needs its own visible row.
Returns and cancellations. An order that came back produced no revenue. Reversing the commission is defensible, and it has to appear as a dated line referencing the original order.
Return-to-origin. A refused cash-on-delivery parcel is the same situation with a different cause, and it is common enough in Indian D2C to deserve its own label rather than being folded into returns.
Orders outside the window. A purchase thirty-four days after a click under a thirty day agreement is excluded, and showing it as an excluded row is better than showing nothing.
Agree all three in writing before the campaign, including the window length, because a seven day and a thirty day window produce materially different payouts on identical work.
Then show the excluded rows anyway, greyed out. A creator who can see what did not count trusts the rows that did.
What disputes cost on a 200-creator roster
The case for doing this is not only relational, and the arithmetic makes it easier to fund.
Assume a dispute takes 45 minutes to work through, between reading the creator’s message, pulling the underlying orders and replying.
| Dispute rate | Disputes per month | Hours | Share of a manager’s month | Cost at Rs 800 an hour |
|---|---|---|---|---|
| 12% | 24 | 18 | 11% | Rs 14,400 |
| 4% | 8 | 6 | 4% | Rs 4,800 |
Cutting the rate from 12% to 4% recovers 12 hours and Rs 9,600 a month on a 200-creator roster.
That is roughly a day and a half of a manager’s time returned every month, spent on something other than defending numbers.
The relational cost is larger and harder to put in a table. Creators talk to each other, and a brand with a reputation for opaque payouts recruits from a smaller pool at worse terms.
Referral rewards to customers sit on a different footing and should stay separate in reporting.
SB&R is a Shopify app for chained referral rewards. Every referral link belongs to someone who has already bought. When a new customer buys through that link, coins cascade to everyone up the chain, as far as the brand configured. Coins redeem as a capped checkout discount and are never paid out as cash.
SB&R is not for cash-payout affiliate programs, so coins never appear on a creator’s payout report. Mixing a coin balance into a cash statement is a guaranteed dispute, since one is spendable at your checkout and the other is money.
Where an itemised report does not help
Korant is not for stores with a single paid channel, and it is not for brands that only need Shopify’s native reports. A brand paying four creators can send a screenshot and a note.
Three situations are not solved by better reporting.
A genuinely broken link. If the slug was edited or the post carried the wrong URL, the report is accurately showing a real zero, and the fix is verification at publication rather than reconciliation afterwards.
A dispute about the rate. Some messages arriving on the ninth are not about the count at all, they are an opening to renegotiate, and an itemised report answers a question that was not being asked.
Attribution that genuinely missed. People who saw the post, never clicked, and searched for the brand later are invisible to every surface, so the creator is right that the report undercounts even when every row is correct.
The limitation worth sitting with is that an honest report can only show what was recorded, and a meaningful share of creator-driven demand is never recorded at all. A creator who insists she drove more than the report says is frequently correct.
An itemised statement makes the visible part auditable without making the invisible part appear. Say so openly rather than defending the total as complete, and price that known gap into the rate rather than arguing about it monthly. The pay structure that makes this manageable is in paying influencers on performance, the brief that gets tracking used correctly is in the influencer brief that gets you usable content, and the selection question is in finding creators whose audience overlaps yours.
Questions people actually ask
What should an influencer payout report contain?
One row per order rather than a total. Each row needs the order date, the order value, which attribution check credited it, the commission earned, and any deduction with its reason. A creator should be able to reconcile the report against their own view without asking anyone.
Why do creators dispute payouts?
Almost always for one of two reasons. The resolution path is invisible, so a low order count looks like underreporting. Or a total dropped between months with no explanation, which is usually a return or cancellation reversing an order that was already paid on. Both are fixed by showing the detail.
Should returns be deducted from creator commission?
Usually yes, since a returned order produced no revenue, but the policy has to be agreed in writing before the campaign and the reversal has to appear as its own line. A silent deduction is what turns a reasonable policy into a dispute about honesty.
How long should the attribution window be?
Whatever you agree in writing, and the number matters less than it being fixed. A seven day window and a thirty day window produce materially different payouts on identical campaigns, so discovering the difference at invoice time is how relationships end.
Do creators need to see other creators' numbers?
No, and they should not. Each creator sees their own slug, their own orders and their own deductions. Pooled reporting is what creates the suspicion in the first place, because a share of a pool cannot be checked by the person receiving it.