To raise a payment discrepancy ticket with Myntra, first confirm the gap by comparing your settlement report against order, return and fee data and your agreed terms. Then open the support or ticketing section of your seller portal, pick the closest payment category, and submit one ticket per issue with order IDs, expected versus received amounts, the rate card reference and report extracts. Track it to closure.
Step 1: Confirm it is a real discrepancy
Many apparent shortfalls are timing or netting differences, not errors. Before you raise anything, rule these out:
- Settlement cycle: the order may simply not have reached its payout date yet. Check the cycle in your seller agreement or onboarding documents.
- Returns and RTOs: a return can reverse earlier revenue and show up as a deduction in a later settlement.
- Netting: penalties, ad charges or other adjustments may be deducted from a payout covering many orders.
- Tax deductions: deductions at source depend on current rules. Confirm the latest position with your tax adviser and the settlement report, not from memory.
Only when the amount received differs from what your agreed terms say you should receive, after these checks, do you have a discrepancy worth a ticket.
Step 2: Classify the type of discrepancy
Marketplaces route tickets by category, and a clearly classified ticket is easier to act on. Most cases fall into one of these:
| Type | What to compare | Typical evidence |
|---|---|---|
| Short or missing payout | Expected settlement vs amount credited | Settlement report row, bank credit entry |
| Wrong commission or fee | Charged amount vs rate card or agreement | Rate card, fee lines in report |
| Duplicate charge | Same fee or deduction appearing twice | Both report rows with order IDs |
| Return not credited or wrongly debited | Return status vs reversal amount | Return ID, receipt or QC status, report rows |
If one settlement has three different problems, treat them as three issues.
Step 3: Build the evidence pack
Prepare this before opening the ticket, so you do not have to answer follow-up questions one at a time:
- Order IDs, SKU or style codes, and order, dispatch and delivery dates.
- The settlement report extract showing the affected rows, plus the settlement ID or date.
- Your calculation of the expected amount, with the formula visible.
- The agreement clause or rate card page that supports your calculation.
- Return or RTO status evidence, if relevant.
- The bank statement line showing what was actually credited.
Keep a one-sheet Excel summary with one row per order: expected, received, difference, reason. It becomes your master list for follow-up.
Step 4: Raise and write the ticket
Menu names and categories in the Myntra seller portal can change, so follow the current support or ticketing section in your account and any process note shared by your account manager. In general:
- Log in to the seller portal and open the support or ticket section.
- Choose the category closest to your issue, such as payments or settlements.
- Write a short subject: issue type, settlement date or ID, number of orders.
- In the body, state the facts: what was expected, what was received, the difference, and the clause or rate that supports your figure.
- List order IDs in a table or attach the Excel sheet.
- State the action you want: reverse the extra deduction, release the shortfall, or explain the calculation.
- Submit and save the ticket number with a screenshot.
Avoid long narratives. Raise one ticket per issue type, and do not reopen the same issue in a new ticket unless asked, since duplicates can slow resolution.
Step 5: Follow up and escalate
Log every ticket with its number, date raised, amount claimed, status and next follow-up date. Check the response timelines in your seller agreement or support guidelines rather than assuming them.
- If Myntra asks for more information, reply on the same ticket with the exact documents requested.
- If it is closed without an adjustment you can verify, ask for the calculation behind the decision.
- If it stalls beyond the stated timeline, escalate to your account manager or category contact, quoting the ticket number and the amount.
- When a credit arrives, match it to the claim in your master list. Partial credits are common, and the balance should stay open.
Step 6: Catch discrepancies earlier
The costliest discrepancies are the ones found months later, when evidence is harder to assemble and ageing disputes are harder to pursue. A monthly check of settlements against orders, returns and agreed fees is the minimum. Doing this by hand across thousands of rows is slow, which is where a tool such as MarketplaceMetrics by Fundle helps: it reconciles sales and settlements, checks commissions and fees against agreed terms, and tracks returns and recovery cases. Myntra Excel reports are reviewed today, and other marketplaces are in scope discussion.
Worked example
Illustrative example only. Figures are not Myntra rates.
Suppose one order has a sale value of ₹1,499. Your agreed commission for this style, per your rate card, works out to ₹300, and the agreed fixed fee is ₹60. Expected payout: ₹1,499 − ₹300 − ₹60 = ₹1,139.
The settlement report shows ₹1,079 credited. The difference is ₹60, and the report shows the ₹60 fee on two separate rows for the same order ID.
- Ticket subject: Duplicate fee deduction, settlement dated [date], 1 order
- Body: Expected ₹1,139, received ₹1,079, difference ₹60. The fixed fee appears twice for order [ID]. Rate card page [x] shows it applies once. Please reverse the duplicate.
- Attachments: report extract with both rows highlighted, rate card page, bank credit line.
Repeated across many orders, small duplicates like this add up, which is why a master list matters.
Questions and answers
Where do I raise a payment discrepancy ticket on Myntra?
Use the support or ticketing section of your Myntra seller portal and choose the payments or settlements category. Menu names can change, so check your current portal view and any process note from your account manager before relying on a fixed path.
How long does Myntra take to resolve a payment ticket?
Resolution time varies by issue and evidence quality, so do not assume a fixed number. Check the timelines in your seller agreement or support guidelines, record the date you raised the ticket, and escalate with the ticket number if that period passes.
Should I raise one ticket or many for multiple mismatches?
Raise one ticket per issue type, such as duplicate fees or missing return credits, and list all affected order IDs within it. Mixing different problems in one ticket makes it harder to review, and duplicate tickets for the same issue can cause delays.
What if the discrepancy is old?
Raise it anyway, with the settlement date, order IDs and calculations. Check your agreement for any claim window, since time limits may apply. Older cases need stronger evidence, so keep settlement reports and bank statements archived and reconcile regularly to catch issues sooner.