Skip to main content
Reconciliation Pattern

Platform Settlement

Reconcile OTA, marketplace, and aggregator settlements against booking records

Request Demo Product Overview

What this pattern solves

Platform and aggregator businesses disburse settlements on a weekly or bi-weekly cycle, bundling hundreds of individual transactions into a single bank credit. The settlement file lists individual transactions with platform fees, returns, and TDS deducted — but the identifiers used by the platform rarely match the identifiers in your accounting system. The Platform Settlement pattern handles this in three stages: ingestion of the settlement file with format normalisation, ID mapping from platform identifiers to internal records, and multi-item matching within the settlement batch.

Use this pattern when:

  • You receive revenue through OTAs (MakeMyTrip, Booking.com, Goibibo, Expedia)
  • You sell on marketplaces (Amazon, Flipkart, Meesho)
  • You use food/delivery aggregators (Zomato, Swiggy, Dunzo, Blinkit)
  • You use logistics platforms (Delhivery, Porter, Shiprocket)
  • Platform settlements arrive in weekly batches with commission and TDS pre-deducted

How it works in TransactIG

01

Ingest settlement file

TransactIG ingests the platform's settlement report using a pre-built format template. Each line item is parsed — booking/order ID, gross amount, commission, TDS, net payout.

02

Map identifiers

Platform booking IDs or order IDs are mapped to your internal records using the configured ID mapping rule. Unmapped IDs are flagged for review.

03

Match net payout to bank credit

The sum of net payouts in the settlement batch is matched against the actual bank credit amount. Discrepancies are classified as settlement shortfall or timing difference.

04

Classify variances

Unmatched items are classified: commission rate change, disputed order, return clawback, TDS deduction, or unidentified. Each variance type has a configured workflow.

Matching rules

Batch sum match
Sum of all net payouts in settlement file = bank credit amount. Tolerance: ₹1.
Line-item match
Each settlement line matches to an internal record by mapped ID.
Partial settlement
Platform settles a subset of the period; remaining items carried forward.

Variance taxonomy

V
Commission deduction
Platform fee deducted at agreed rate. Expected variance.
V
TDS deduction (194H)
TDS on commission income. Logged for 26AS.
V
Return clawback
Order returned; platform reversed the payout.
V
Rate change variance
Commission rate changed mid-period without notice.
V
Unidentified deduction
Deduction not explained in settlement notes. Escalate to platform.

Frequently asked questions

Which platform settlement formats does TransactIG support?

TransactIG ships with ingestion templates for MakeMyTrip, Goibibo, Booking.com, Expedia, Agoda, Amazon Seller Central, Flipkart, Zomato, Swiggy, Delhivery, Porter, Dunzo, and Shiprocket. New formats can be added without code changes.

What happens when a platform changes their settlement report format?

Column mapping templates are updated in the TransactIG admin console. No engineering work is required. Terra Insight monitors major platform format changes and releases updates proactively.

Can I reconcile multiple platforms in the same run?

Yes. TransactIG processes multiple platform settlement files in a single reconciliation run with unified output and cross-platform variance reporting.

See the Platform Settlement pattern in action

Terra Insight will run a live TransactIG demo using this matching pattern on data from your industry vertical.

Request Demo All Patterns