Marketplace settlement reconciliation is the process of matching every Amazon, Flipkart, and Meesho order with the corresponding sale value, marketplace fees, shipping deductions, refunds, returns, tax deductions, compensation credits, settlement statement, and bank deposit.

Sales shown in a marketplace dashboard are not the same as the final amount received in the seller's bank account. The difference may include referral or service fees, fixed or closing fees, logistics charges, fulfilment costs, reverse shipping, advertising deductions, customer refunds, cancellation adjustments, TCS, TDS, GST on marketplace services, claims, recoveries, reserves, and corrections from earlier settlement periods.

This guide explains how sellers can build an order-level and settlement-level reconciliation workflow across Amazon, Flipkart, and Meesho without assuming one universal fee rate or payment cycle. Current account-specific agreements, rate cards, seller-panel reports, invoices, and transaction statements should always be treated as the final source.

What Is Marketplace Settlement Reconciliation?

Settlement reconciliation confirms that:

  • Every eligible order has been included in a settlement
  • The correct order value has been considered
  • Marketplace fees match the applicable commercial terms
  • Shipping and fulfilment charges are correct
  • Refunds and returns are adjusted only once
  • Compensation or claim credits have been received
  • Tax deductions are recorded separately
  • The net payout matches the bank deposit
  • Unmatched or disputed amounts are tracked until closure

Why Sales and Bank Deposits Do Not Match

A seller may compare gross sales directly with the bank credit and assume that the remaining amount is a marketplace commission. This approach is incomplete because a settlement can contain many transaction types.

Transaction type Possible effect on payout
Product sale Increases seller receivable
Referral or service fee Reduces payout
Closing or fixed fee Reduces payout
Forward logistics Reduces payout
Reverse logistics Reduces payout after return or failed delivery
Fulfilment and storage fee Reduces payout where applicable
Customer refund Reverses part or all of the sale
Marketplace compensation Increases payout
Advertising deduction Reduces payout when ads are billed through the seller account
TCS or TDS Reduces bank payout but may be available as a tax credit subject to law
GST on marketplace fee Reduces payout and should be supported by a tax invoice
Previous-period adjustment May increase or reduce the current settlement

Three Levels of Reconciliation

1. Order-Level Reconciliation

Match each order or order item with:

  • Order ID
  • Order-item ID
  • SKU
  • Quantity
  • Selling price
  • Discount
  • Shipping charge collected from the customer
  • Order status
  • Delivery date
  • Return or refund status
  • Expected receivable

2. Settlement-Level Reconciliation

Match all order transactions, fees, refunds, recoveries, claims, and tax entries included in one payout or settlement batch.

3. Bank-Level Reconciliation

Match the net settlement amount with the actual bank credit using the payout reference, UTR, settlement ID, deposit date, and bank narration.

Core Reconciliation Formula

Expected Net Settlement = Gross Seller Receivable + Credits - Marketplace Fees - Logistics Charges - Fulfilment Charges - Refunds - Return Adjustments - Advertising Deductions - Tax on Fees - Statutory Deductions - Other Recoveries

Settlement Variance = Actual Net Settlement - Expected Net Settlement

Bank Variance = Bank Credit - Marketplace Settlement Amount

A zero variance is ideal, but small differences may occur because of rounding, timing, tax treatment, or transactions carried forward to another cycle. Every difference should still have a documented explanation.

Reports Required for Reconciliation

Amazon

Depending on account access and report availability, collect:

  • Settlement or transaction reports
  • Payments dashboard data
  • Order reports
  • Returns and refunds reports
  • FBA inventory adjustment and reimbursement reports
  • Advertising invoices or transaction data
  • Fee invoices
  • TCS and TDS certificates or tax reports
  • Bank statements

Flipkart

Collect the available seller-panel reports for:

  • Orders and order items
  • Settlements and payment transactions
  • Commission and marketplace fees
  • Forward and reverse shipping
  • Returns and cancellations
  • Protection or claim credits
  • Tax invoices and tax deductions
  • Advertising or promotional deductions
  • Bank deposits

Meesho

Collect the available supplier-panel reports for:

  • Orders and delivered orders
  • Payment or settlement details
  • Shipping charges
  • Returns and reverse shipping
  • Refund or cancellation adjustments
  • Claims, recoveries, or compensation
  • Tax reports
  • Bank credits

Report names and fields can change. Build the reconciliation logic around stable business concepts rather than one fixed file name.

Master Reconciliation Table

Field Purpose
Marketplace Amazon, Flipkart, or Meesho
Seller account Identifies the legal entity and marketplace account
Order ID Primary order reference
Order-item ID Supports item-level matching
Settlement ID Identifies the payout batch
Transaction ID Identifies individual fee, refund, or credit entries
SKU Supports product-level profitability
Quantity Confirms unit-level sale and return
Order date Supports sales-period reporting
Delivery date Supports payout eligibility calculations
Settlement date Supports payment-cycle monitoring
Gross sale value Starting transaction value
Customer discount Tracks discount impact
Marketplace-funded discount Separates marketplace contribution
Seller-funded discount Reduces seller receivable
Marketplace fees Tracks commission, referral, closing, or service charges
Forward shipping Tracks outbound logistics
Reverse shipping Tracks return logistics
Fulfilment fees Tracks storage, pick-pack, or handling charges
Tax on fees Tracks GST or similar service tax
TCS Tracks tax collected at source
TDS Tracks tax deducted at source
Refund Tracks customer-value reversal
Claim or compensation Tracks seller credits
Expected payout Calculated amount
Actual payout Marketplace settlement amount
Bank credit Actual amount received
Variance Difference requiring explanation

Step-by-Step Settlement Reconciliation Workflow

Step 1: Define the Reconciliation Period

Choose a fixed daily, weekly, or monthly period. Use separate date fields for order, delivery, return, settlement, and bank deposit because these events may occur in different periods.

Step 2: Download Raw Reports

Save reports without changing the original file. Keep a dated folder for each marketplace and seller account.

Step 3: Standardize Column Names

Map marketplace-specific fields to one common structure.

Examples:

  • Order reference -> order_id
  • Item reference -> order_item_id
  • Merchant SKU -> seller_sku
  • Net remittance -> actual_payout
  • Transaction type -> transaction_type
  • Fee amount -> marketplace_fee

Step 4: Preserve Transaction Signs

Do not convert every value to a positive number. Sales, deductions, reversals, and credits need consistent debit and credit signs.

Step 5: Create Unique Matching Keys

Useful keys include:

  • Marketplace + seller account + order-item ID
  • Marketplace + transaction ID
  • Settlement ID + order-item ID + transaction type
  • Bank account + settlement ID + deposit date

Step 6: Classify Every Transaction

Create standardized transaction groups:

  • Sale
  • Refund
  • Return
  • Marketplace fee
  • Shipping fee
  • Fulfilment fee
  • Advertising
  • Tax on fee
  • TCS
  • TDS
  • Claim credit
  • Compensation
  • Recovery
  • Reserve or hold
  • Other adjustment

Step 7: Calculate Expected Settlement

Apply account-specific rates and rules at order-item level. Do not rely on a single flat commission percentage.

Step 8: Compare Expected and Actual Entries

Flag:

  • Missing sale transactions
  • Duplicate fee deductions
  • Incorrect shipping weight
  • Wrong commission category
  • Refund deducted twice
  • Return fee without corresponding return
  • Missing claim credit
  • Tax mismatch
  • Unexplained recovery
  • Settlement amount not received in bank

Step 9: Match Settlement to Bank

Use settlement ID, payout reference, UTR, amount, and date. One bank credit may represent one or several settlement components depending on the marketplace process.

Step 10: Raise and Track Disputes

Create a dispute register containing:

  • Marketplace
  • Case ID
  • Order ID
  • Settlement ID
  • Disputed amount
  • Expected calculation
  • Supporting report
  • Date raised
  • Owner
  • Status
  • Expected resolution date
  • Credit received date

Amazon Settlement Reconciliation

Amazon seller settlements may contain sale proceeds, referral fees, closing fees, weight-handling charges, fulfilment fees, storage charges, refunds, reimbursements, advertising charges, tax entries, reserves, and other adjustments.

Amazon Matching Process

  1. Import order and order-item data.
  2. Import the settlement or transaction report.
  3. Group transactions by order-item ID and transaction type.
  4. Separate FBA, Easy Ship, Self-Ship, and programme-specific charges.
  5. Calculate expected referral and closing fees using the applicable category and price band.
  6. Validate shipping or weight-handling charges.
  7. Match refunds and return-related charges.
  8. Match FBA reimbursements and inventory adjustments.
  9. Separate advertising deductions.
  10. Match the net settlement with the bank deposit.

Common Amazon Variances

  • Wrong referral-fee category
  • Weight or volumetric-weight difference
  • Closing fee based on another price band
  • FBA storage or fulfilment charge not included in expected calculation
  • Refund processed in a later settlement
  • Reimbursement pending
  • Reserve held
  • Advertising charge deducted separately
  • GST on seller fees not separated

Flipkart Settlement Reconciliation

Flipkart reconciliation should match order-item values with applicable commission, fixed or collection charges, shipping, reverse shipping, promotions, taxes, returns, cancellations, protection claims, and settlement deposits shown in the seller account.

Flipkart Matching Process

  1. Import order-item and delivery-status reports.
  2. Import settlement and transaction-level payment data.
  3. Map seller SKU and Flipkart listing identifiers.
  4. Separate marketplace fees, collection charges, and logistics deductions.
  5. Match return and cancellation entries.
  6. Track SPF or other approved protection credits separately.
  7. Validate tax invoices and statutory deductions.
  8. Match settlement IDs to bank credits.

Common Flipkart Variances

  • Commission based on incorrect category mapping
  • Fixed-fee or collection-fee difference
  • Forward shipping based on unexpected weight slab
  • Reverse shipping after customer return
  • Cancellation adjustment in a later cycle
  • Protection claim approved but not credited
  • Promotion contribution misunderstood
  • Multiple order items combined into one payout

Meesho Settlement Reconciliation

Meesho publicly promotes a zero-commission seller model, but sellers should still reconcile shipping, returns, taxes, adjustments, and any account-specific services or deductions shown in the supplier panel.

Meesho Matching Process

  1. Import order and delivered-order data.
  2. Import payment details and settlement entries.
  3. Map supplier SKU and catalogue or product identifiers.
  4. Separate product receivable and logistics deductions.
  5. Match returns, reverse shipping, and refunds.
  6. Track claims, recoveries, and compensation credits.
  7. Separate tax deductions.
  8. Match net payment with bank deposits.

Common Meesho Variances

  • Delivered date and payout eligibility date mismatch
  • Return adjustment posted after original payout
  • Reverse-shipping charge not included in expected amount
  • Bank or KYC issue delaying payout
  • Incorrect catalogue or SKU mapping
  • Claim credit pending
  • Tax deduction not separated from operating fees

Marketplace Comparison Table

Area Amazon Flipkart Meesho
Primary matching level Order item and transaction Order item and settlement transaction Order, catalogue or sub-order, and payment entry
Common fee categories Referral, closing, shipping, fulfilment, storage, programmes Commission, fixed or collection, shipping, reverse shipping, services Shipping, reverse shipping, tax, and account-specific adjustments
Return impact Refund, return fees, reimbursement, inventory adjustment Refund, reverse shipping, claim or protection credit Refund, reverse logistics, claim or compensation
Bank matching Settlement or deposit reference Settlement and payment reference Payment reference and bank credit
Final source Current Seller Central report and agreement Current Seller Hub report and agreement Current Supplier Panel report and terms

Returns and Refund Reconciliation

Returns create some of the most complex settlement differences because the original sale and later reversal may appear in different payout periods.

Return Reconciliation Fields

  • Original order ID
  • Original order-item ID
  • Delivery date
  • Return requested date
  • Return received date
  • Refund date
  • Return reason
  • Product-value refund
  • Forward shipping adjustment
  • Reverse shipping charge
  • Marketplace fee reversal
  • Tax adjustment
  • Inventory disposition
  • Claim or compensation amount

Return Matching Formula

Net Return Loss = Refunded Product Value + Non-Reversed Fees + Forward Logistics + Reverse Logistics + Product Damage Loss - Compensation Credit

TCS, TDS, GST, and Fee Invoices

Tax deductions should not be mixed with marketplace operating fees.

Recommended Accounting Separation

  • Gross product sale
  • Marketplace service fee
  • GST on service fee
  • TCS receivable
  • TDS receivable
  • Shipping expense
  • Advertising expense
  • Customer refund
  • Claim income
  • Net bank receipt

Tax treatment should be reviewed using current law, marketplace reports, invoices, certificates, and advice from a qualified tax professional.

Settlement Timing and Cut-Off Differences

An order can be:

  • Placed in one month
  • Delivered in another month
  • Settled later
  • Returned after settlement
  • Refunded in a future period
  • Compensated in a different cycle

Use separate reporting views for:

  • Order-date sales
  • Delivery-date sales
  • Settlement-date cash flow
  • Bank-date receipts
  • Return-date losses

Settlement Variance Categories

Variance category Example Action
Timing variance Refund included in next cycle Carry forward and monitor
Rate variance Commission differs from expected rate Verify category, price band, and agreement
Quantity variance Two units sold but one unit settled Check item-level records
Logistics variance Higher weight slab charged Check dimensions, weight, and service zone
Tax variance GST, TCS, or TDS differs Check invoice and tax report
Duplicate deduction Refund or shipping deducted twice Raise dispute with evidence
Missing credit Approved claim not received Track case and settlement
Bank variance Settlement recorded but bank credit missing Check payout status, bank details, and UTR

Common Reconciliation Errors

Using Only the Order Report

An order report does not contain the complete fee and settlement picture.

Using Only the Bank Statement

A bank credit does not explain which orders, fees, and refunds created the amount.

Matching Only by Order ID

One order can contain several items, quantities, returns, and transaction entries.

Ignoring Negative Transactions

Refunds, fee reversals, recoveries, and credits require correct signs.

Hardcoding Old Marketplace Rates

Fee structures can change by date, category, price, weight, fulfilment, and programme.

Mixing Tax with Fees

TCS, TDS, GST on services, and marketplace charges need separate accounting treatment.

Ignoring Previous-Period Adjustments

A current payout may include transactions from older orders.

Closing Disputes Before Credit Receipt

A dispute should remain open until the correction appears in a settlement and bank deposit.

Illustrative Reconciliation Example

The following amounts are illustrative and do not represent an official marketplace rate card.

Component Illustrative amount
Gross product value INR 1,500
Seller-funded discount INR 100
Marketplace and fixed fees INR 165
Forward shipping INR 80
GST on marketplace services INR 44
TCS and TDS INR 20
Claim credit INR 25
Expected payout INR 1,116
Actual marketplace settlement INR 1,106
Variance requiring review INR -10

Automated Reconciliation Logic

A spreadsheet, database, business-intelligence system, or accounting integration can automate much of the workflow.

Recommended Processing Stages

  1. Import raw files.
  2. Validate required columns.
  3. Standardize dates and numbers.
  4. Normalize SKU and order references.
  5. Classify transaction types.
  6. Apply effective-dated fee rules.
  7. Aggregate at order-item level.
  8. Aggregate at settlement level.
  9. Match bank credits.
  10. Generate variance and exception reports.

Effective-Dated Fee Master

Field Purpose
Marketplace Identifies platform
Category Identifies fee category
Price-from and price-to Identifies price band
Weight-from and weight-to Identifies shipping slab
Fulfilment channel Identifies FBA, Easy Ship, seller fulfilment, or equivalent
Fee type Referral, closing, shipping, or service fee
Rate or fixed amount Calculation input
Effective-from date Start of fee version
Effective-to date End of fee version

Settlement Reconciliation KPIs

KPI Formula
Order reconciliation rate Fully matched order items / eligible order items x 100
Settlement reconciliation rate Matched settlement amount / total settlement amount x 100
Bank matching rate Matched bank credits / expected deposits x 100
Variance percentage Absolute variance / expected payout x 100
Missing credit value Total approved but unreceived credits
Average dispute age Total open-dispute days / open disputes
Recovery rate Recovered disputed amount / valid disputed amount x 100
Settlement delay Actual deposit date - expected deposit date

Daily, Weekly, and Monthly Workflow

Daily

  • Download new settlement transactions
  • Match new bank credits
  • Flag missing or duplicate transactions
  • Check high-value refunds and recoveries
  • Track overdue payouts
  • Update open disputes

Weekly

  • Complete order-item reconciliation
  • Review fee and logistics variances
  • Review return-related deductions
  • Review missing claims and compensation
  • Review tax and invoice mismatches
  • Raise supported marketplace cases

Monthly

  • Close settlement-to-bank reconciliation
  • Reconcile TCS and TDS reports
  • Reconcile GST fee invoices
  • Calculate SKU-level profitability
  • Review marketplace-wise deduction trends
  • Review unresolved dispute ageing
  • Update fee masters

30-Day Settlement Reconciliation Plan

Days 1-7: Report Mapping

  • List all seller accounts
  • Collect order, settlement, return, fee, tax, and bank reports
  • Map marketplace columns
  • Create the common transaction structure
  • Document payout references

Days 8-14: Historical Reconciliation

  • Import one complete settlement period
  • Classify all transaction types
  • Match orders and settlements
  • Match settlements and bank credits
  • Identify recurring differences

Days 15-21: Rule and Exception Setup

  • Create effective-dated fee masters
  • Create shipping and weight rules
  • Create return and refund rules
  • Create tax classifications
  • Create variance thresholds

Days 22-30: Automation and Governance

  • Automate data imports where possible
  • Create the exception dashboard
  • Create the dispute register
  • Assign finance and operations owners
  • Schedule weekly and monthly reviews
  • Document marketplace policy changes

How DigiCommerce Supports Settlement Reconciliation

DigiCommerce helps marketplace sellers, brands, manufacturers, and online retailers build reliable Amazon, Flipkart, and Meesho finance operations.

  • Order-to-settlement reconciliation
  • Settlement-to-bank matching
  • Marketplace fee validation
  • Shipping and weight variance analysis
  • Return and refund reconciliation
  • Claim and reimbursement tracking
  • TCS, TDS, and fee-tax report organization
  • SKU-level profitability
  • Dispute registers and ageing reports
  • Automated dashboards
  • Multi-account and multi-marketplace reporting
  • Monthly finance-control workflows

Related DigiCommerce resources include SKU-level marketplace profitability, multi-marketplace inventory reconciliation, Amazon business reports, and ecommerce service provider agency.

Frequently Asked Questions

1. What is marketplace settlement reconciliation?

It is the process of matching orders, fees, shipping, returns, refunds, taxes, claims, marketplace payouts, and bank deposits.

2. Why does marketplace sales value differ from bank payment?

The marketplace payout may include fees, logistics, taxes, refunds, previous adjustments, advertising deductions, and compensation credits.

3. Should reconciliation be done by order or settlement?

Both are required. Order-level matching explains transactions, settlement-level matching confirms the payout batch, and bank matching confirms cash receipt.

4. Can I use one flat commission rate?

No. Fees may vary by marketplace, category, price band, weight, fulfilment channel, date, and programme.

5. How should returns be reconciled?

Match the original sale, refund, fee reversal, forward shipping, reverse shipping, inventory result, and compensation credit using the original order-item ID.

6. How are TCS and TDS handled?

Track them separately from marketplace fees and reconcile them with applicable tax reports and certificates.

7. What is the best matching key?

Order-item ID plus marketplace, seller account, settlement ID, and transaction type is usually more reliable than order ID alone.

8. How often should sellers reconcile settlements?

High-volume sellers should monitor daily and close formal reconciliation weekly or monthly according to finance controls.

9. What if a marketplace approves a claim but payment is missing?

Keep the dispute open until the credit appears in the settlement report and bank deposit.

10. Can payment cycles change?

Yes. Eligibility, seller programme, account status, order lifecycle, and marketplace policy may affect payout timing. Check the live seller account and current agreement.

11. Can settlement reconciliation be automated?

Yes. Report imports, transaction classification, fee calculations, order matching, bank matching, and exception reporting can be automated.

12. Can DigiCommerce reconcile Amazon, Flipkart, and Meesho payments?

Yes. DigiCommerce can build order-level reconciliation, fee validation, return matching, bank reconciliation, dispute tracking, and profitability dashboards.

Conclusion

Amazon, Flipkart, and Meesho settlement reconciliation should connect every order item with every related fee, logistics charge, return, refund, claim, tax entry, payout, and bank deposit. Gross sales alone cannot explain marketplace cash flow.

A reliable system uses standardized transaction classifications, stable matching keys, effective-dated fee masters, order-level calculations, settlement-level controls, bank matching, and an open-dispute register. Current seller-panel data and account-specific terms should always override old or generic fee assumptions.

For Amazon, Flipkart, and Meesho settlement reconciliation, fee audits, return matching, tax-report organization, bank reconciliation, and marketplace finance dashboards, connect with DigiCommerce Solutions.

Ready to Grow Your Business?

Let's turn your e-commerce challenges into success stories. Fill out the form below to connect with one of our experts for a free consultation and strategic analysis.

Send Us a Message

7797f380

Direct Contact

Get in touch with our team of experts directly.



WhatsApp Call Now Carrers

Quick Enquiry

Fill out the form and we will contact you shortly.

7797f380