Reading the payout audit

The four numbers across the top

• Files parsed — statements on record. It is the denominator for everything below.
• Open leaks — differences found and not yet resolved.
• Claims queue — leaks that have been gathered into something you could actually send a partner.
• Banked — money that reached your bank because of a claim. Nothing else counts here, ever.

That last one is the number the whole screen exists for, and it is the one that is hardest to move. It is not a total of what you are owed, or of what you have asked for; it counts credits that were independently recorded as having arrived. Beside it sits at stake in claims, which is what you have asked for and not yet received. Keeping the two apart is the point.

How a difference is found

For every settled row, the payout that should have landed is recomputed from the row's own parts — gross, less commission, less GST on that commission, less TDS, TCS, advertising, penalties and refunds — and compared against the net the statement says it paid. When the recomputed figure is higher, you were short paid, and the gap becomes a variance.

The reverse is never flagged. If a statement paid you more than the arithmetic says it should, nothing appears. A clean file producing no leaks at all is a result, not a failure of the audit.

The five classes

• Double deduction — the same order settled more than once, with fees taken again on the repeat. Exact, and the most straightforwardly recoverable thing on this screen.
• Fee math — the components on the row do not add up to the net the row claims.
• Missing order — an order you have that the statement does not.
• Refund mismatch — a refund on the statement that does not agree with what you recorded.
• Unknown — a real difference the engine will not put a name to.

The first three can be attributed to an exact order, so they become claim drafts on their own. The last two go to the review queue instead, because a claim you cannot point at an order for is a claim you will lose.

What an audit with no contract can and cannot say

This matters more than any other line here. Unless your own negotiated fee schedule for a platform has been recorded, the audit checks each statement against itself — its stated components against its stated net. That finds double deductions and broken arithmetic, and it needs no rate at all.

What it cannot do is tell you that a commission rate was too high, because it does not know what you agreed to. So it says nothing rather than guessing, and a quiet commission column means *not measured*, not *correct*. Substituting a typical market rate would produce a figure you might put in front of a partner, and a wrong accusation costs you more than a missing one.

A claim's life

A claim moves in one direction: draft → approved → filed → acknowledged → credited. A partner who pays without ever acknowledging is common, so filed can go straight to credited. From any live state a claim can be rejected — by them, or by you deciding not to pursue it — or expired when it has sat past its window. Those three are the end; nothing moves out of them.

Each claim carries how long it has been open and whether it is overdue, which is what tells you when to escalate rather than wait.

Marking a claim credited

Mark credited does not create money. It consumes a bank credit that was already recorded against that claim, and if none exists there is nothing for it to consume. The amount that lands may be smaller than the amount you asked for; the smaller figure is what gets counted, because that is what arrived.

This is the reason the banked figure can be trusted. There is no path anywhere in the product from "I claimed this" to "this is banked" that does not pass through evidence that the money turned up.

The evidence behind a figure

Open any claim's details and every rupee is traceable: the variances it is built from, the settlement rows those came from, and where your own order records exist, those too. The total claimed is shown beside a figure recomputed from the same rows, so a claim whose parts no longer add up is visible rather than hidden. You can download the bundle and attach it to a dispute.

The recovery report in the reports section is the same story over time — what was found, what was filed and what came back — rather than the working queue this screen is.