← All templates
Reconciliation workflow

Expected Payment Tracker: Know What Every Marketplace Owes You

Compute the exact expected payment for every invoice after mapped debit notes, then flag each short or missing payment automatically — so revenue leakage surfaces the day a settlement lands, not at month-end.

Blinkit logoBlinkitZepto logoZeptoSwiggy Instamart logoSwiggy InstamartBigBasket logoBigBasketAmazon logoAmazonFlipkart logoFlipkartNykaa logoNykaaMyntra logoMyntraNoon logoNoonNamshi logoNamshiTrendyol logoTrendyolZalando logoZalandoReliance Retail logoReliance RetailDMart logoDMartMetro logoMetro
Expected Payment Tracker: Know What Every Marketplace Owes You workflow diagram

The outcome

Finance stops reconstructing payments by hand. For every invoice the workflow knows what should have been paid after valid debit notes, compares it to what arrived, and surfaces every gap as a specific, chaseable line.

How teams use it

Expected vs actual, per invoice

Invoice value minus mapped line-item and overall debit notes gives the expected figure, checked against every payment received.

Short payments surface instantly

Any variance from expected is flagged the moment the settlement lands, keeping claims inside the dispute window.

Handles many-to-many payments

Splits one payment across multiple invoices and accumulates multiple payments against one invoice automatically.

Follow-up ready

Each unexplained gap carries its invoice, DN mapping and amount, so collection is a filing task, not an investigation.

How the workflow runs

  1. Ingest settlement. Payments and debit notes are pulled from each marketplace as settlements post.
  2. Compute expected. Valid line-item and overall DNs are netted against invoice value to derive the expected payment.
  3. Flag variance. Actual received is compared to expected; unexplained shortfalls are raised for follow-up.

Bikaji. Bikaji reached 99% reconciliation accuracy and recovered 60+ hours a week by automating PO, invoice and payment matching into SAP.

Where customers use it

Customers run this template across Blinkit, Zepto, Swiggy Instamart, BigBasket, Amazon, Flipkart, Nykaa, Myntra, Noon, Namshi, Trendyol, Zalando, Reliance Retail, DMart and Metro, spanning India, the Middle East and Southeast Asia. Additional channels and systems can be added to the workflow on request.

Questions we get asked

How is expected payment calculated?

Invoice value minus valid line-item debit notes (quantity, price, tax) mapped to its lines, minus valid overall debit notes (promo, RTV) allocated to it. The actual received amount is then compared to flag variances.

Which marketplaces does it cover?

Every connected channel across quick commerce, ecommerce and modern trade, including Blinkit, Zepto, Swiggy Instamart, BigBasket, Amazon, Flipkart, Nykaa, Myntra, Noon, Namshi, Trendyol, Zalando, Reliance Retail, DMart and Metro.

Can one payment cover multiple invoices?

Yes. The workflow splits a single settlement across the invoices it covers and accumulates multiple payments against one invoice, so the true received amount per invoice is always known.

Track expected payment on every invoice

See expected-versus-actual payment computed across all your marketplaces, with short payments flagged automatically.

Book a demo →
More templates

Related workflows