AP use case · Order-to-cash

Every settlement, decoded
to the exact order.

Marketplaces settle in cycles, gateways in batches, each with its own fee logic and file format. Finnoto matches every payout line to the order it belongs to, validates every commission against your rate card, and ties the whole thing to your bank credit.

Settlement console

Payout ↔ orders ↔ bank,
matched three ways.

Settlement run · Amazon T+7 · Cycle 42 Live
₹18.4L
Settlement received · 4,118 orders
99.2%
Auto-matched to order ID
₹41,300
Short-paid - disputes raised
OrderExpectedSettledStatus
402-8812345₹1,249₹1,249Matched · fees valid
402-8812399₹2,140₹1,890! Excess commission · disputed
402-8812410₹899-✕ Missing from settlement · chasing
Bank tie-out
Settlement UTR AXIS-9921 credited ₹18,41,207 = payout file total. Books posted - commission, TCS & TDS split to ledgers.
Fee guard
Referral fee charged 18% vs rate-card 15.5% on 12 orders - auto-disputed with evidence.
4,084 matched · 22 fee disputes · 12 missing-settlement chases · next cycle in 3 days

Illustrative product behaviour - values shown are examples.

Why it's hard today

The settlement file is where
margins quietly die.

Every channel settles differently - commissions, storage, ads, TCS, TDS, returns offsets - and the only version of truth is a file designed to be hard to read.

Formats built for machines, read by humans

Amazon settlement reports, Flipkart SPF files, gateway MIS, QC payout sheets - each cycle lands as thousands of rows that Excel recon can sample, not cover.

Fees drift, nobody notices

Commission slabs change, weight disputes reclassify, ad spend offsets - a 1-2% fee drift across lakhs of orders is invisible per order and enormous per quarter.

Missing settlements age silently

Orders delivered but never settled don't announce themselves. Without order-level tracking they surface months later - past the dispute window.

The Finnoto difference: recon tools flag the mismatch; Finnoto raises the dispute with evidence, chases it to credit, and posts the reconciled outcome to your books.
How Finnoto runs it

From payout file to
closed books.

1
Ingest every cycle
Settlement files pulled automatically from every channel and gateway - parsed, normalised, deduplicated.
2
Match to the order
Payout lines matched to order, return and replacement events; bank credit tied to the payout total.
3
Validate every fee
Commissions, logistics, storage, ads, TCS/TDS checked against your rate card and slab history.
4
Dispute & post
Short-payments and excess fees disputed with evidence; reconciled entries posted to ERP with fee splits.
FAQ

Frequently asked questions

Which channels are covered?

Amazon, Flipkart, Myntra, Nykaa, quick commerce (Blinkit, Zepto, Instamart), D2C gateways (Razorpay, PhonePe, Paytm) and COD remittances from 3PLs - normalised into one reconciliation.

How do disputes actually get raised?

Finnoto packages the evidence - order, rate card, settlement line - and files through the channel's dispute mechanism (e.g., SPF for Flipkart, SAFE-T for Amazon), then tracks each case to credit or rejection.

Do reconciled settlements post to our ERP?

Yes - with commission, TCS, TDS and logistics split to the right ledgers, so your books carry the true net revenue per order.

Find what your settlements aren't telling you.

One cycle of your own data is usually enough to see the leak.

Talk to us