Tata Cliq Marketplace Reconciliation Using OMS Data
Tata Cliq sellers often manage order data in an internal order management system while receiving sales, settlement, payment, return, and fee details from the marketplace. When those records are reviewed in Excel, the process can become slow, repetitive, and difficult to audit.
Cointab helps finance teams reconcile Tata Cliq marketplace data against OMS data in a structured workflow. Users upload files, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in a clear report.
Why Tata Cliq reconciliation becomes difficult
Marketplace reconciliation usually involves more than comparing one report to another. Finance teams may need to review:
- Internal order data from the OMS
- Marketplace sales records
- Settlement or payout data
- Refunds, returns, deductions, and fees
- Supporting files such as product masters, mapping files, or rate files
When these records are handled manually, teams often rely on formulas, VLOOKUPs, copy-paste checks, and multiple spreadsheet versions. That can make month-end review, exception management, and audit preparation harder than it needs to be.
Reconcile Tata Cliq records with a Side A / Side B model
Cointab uses a simple reconciliation structure:
- Side A contains the records your business expects to be correct, such as OMS data or internal order reports.
- Side B contains the external records received from Tata Cliq, such as marketplace sales or settlement data.
This makes the reconciliation setup transparent for finance teams. Users know which source is being treated as the internal record and which source is being compared against it.
What teams typically compare
A Tata Cliq marketplace reconciliation workflow can include the following data sources:
| Data source | Role in reconciliation |
|---|---|
| OMS order report | Internal order, payment, and status data |
| Tata Cliq sales report | Marketplace order and sales information |
| Tata Cliq settlement or payment report | Payouts, deductions, and settlement details |
| Supporting data | Product master, fee rate file, return report, SKU mapping, or reference file |
Supporting data is optional. It is used to enrich or prepare the primary files before reconciliation, not to replace them.
How Cointab runs the reconciliation
Once the files are uploaded, the workflow is straightforward:
- Upload the OMS file and Tata Cliq marketplace file or files.
- Map the required fields such as date, amount, and identifiers.
- Add supporting data if enrichment, lookup, or calculation is needed.
- Create derived columns if business logic needs to be normalized.
- Run reconciliation manually or on a schedule.
- Review the report once processing is complete.
- Export the Excel report or keep the run available on the dashboard for future reference.
Derived columns can help teams prepare fields such as clean order IDs, normalized references, net amounts, or calculated settlement values before matching begins.
What the reconciliation engine can match
Cointab uses structured matching logic to compare records across the two sides. This can include:
- One-to-one matching
- One-to-many matching
- Many-to-one matching
- Many-to-many matching
- Net-to-net matching
- Contra matching
- Partial matching
This is useful for marketplace workflows where one order may appear across several records, where fees and deductions affect the final amount, or where references appear in different formats.
Common reconciliation outcomes for Tata Cliq sellers
The report separates records into clear categories so finance teams can focus on the exceptions.
| Outcome | What it means |
|---|---|
| Fully matched | The order or settlement lines match according to the configured logic |
| Partially matched | The records are linked, but the amounts do not fully tally |
| Unmatched | The record appears on one side but not on the other |
| Skipped | The record was excluded because of missing, invalid, duplicate, or incomplete data |
Typical differences that Tata Cliq sellers may review include:
- Less settlement in OMS: the amount recorded internally is lower than the marketplace record.
- More settlement in OMS: the amount recorded internally is higher than the marketplace record.
- Payment not received: the OMS contains the order, but the payment or settlement record is missing.
- Not recorded in OMS: Tata Cliq shows the transaction, but the internal record is missing.
- Partial match: the order reference matches, but the amount differs because of fees, refunds, deductions, or returns.
How open items are handled
After structured matching is complete, Cointab can help analyze remaining open transactions using AI-assisted review. This is useful when references are inconsistent, descriptions differ, or the evidence is not strong enough for deterministic matching.
AI can also assist finance teams by helping identify:
- Possible reasons a record remains unmatched
- Whether a file may be missing
- Whether refunds, returns, fees, or deductions explain the difference
- Whether the item should be reviewed manually
If the system cannot confidently match a record, it should remain open rather than forcing a weak match.
Manual review and missed files
Finance teams often receive late files from marketplaces or discover that one report was not uploaded on time. Cointab supports this reality by allowing users to:
- Manually match transactions that need human review
- Undo manual matches when needed
- Upload a missed file under the same reconciliation
- Refresh the report after the file is added
That keeps the reconciliation setup practical for recurring marketplace operations.
Reuse the same setup for future periods
A major advantage of Cointab is reuse. Once a Tata Cliq reconciliation is configured, the same setup can be used again for monthly, quarterly, yearly, or custom periods.
Users do not need to rebuild the workflow every time. They can simply select the reconciliation, choose the period, upload or receive the required files, and run the process again.
For recurring workflows, automation can also be set up through email, SFTP, or API so that files are received and reconciled without repeated manual upload.
Reporting for finance, audit, and follow-up
Once the reconciliation is complete, teams can review the report dashboard and download Excel outputs for internal review, audit preparation, or partner follow-up.
The report view helps users see:
- Total summary
- Fully matched records
- Partially matched records
- Unmatched records
- Skipped records
- Transaction-level detail
- Filtered views for deeper analysis
This makes it easier to close exceptions, prepare month-end reporting, and keep a clear audit trail of what was matched and what still needs attention.
When a custom reconciliation is a better fit
If your Tata Cliq workflow uses business-specific fields, extra supporting files, or unique matching rules, a custom reconciliation may be a better fit than a standard template.
Custom reconciliation is useful when you need to define:
- Which files belong on Side A and Side B
- Which columns should be used as identifiers
- How amounts should be compared
- Which supporting files should be added for enrichment
- Which derived columns should be created before matching
That flexibility helps finance teams handle real-world marketplace data without rebuilding spreadsheets every period.
Why finance teams use a structured reconciliation workflow
A structured platform is helpful when teams want more control over marketplace reporting and exception review. Instead of comparing spreadsheets line by line, finance teams can:
- Map fields once and reuse the setup
- Match transactions consistently across periods
- Review open items separately from matched records
- Keep skipped records visible for transparency
- Share work inside a team workspace
- Maintain reconciliation history for future reference
For Tata Cliq sellers, that means less spreadsheet dependency and a clearer process for transaction matching, settlement review, and reconciliation reporting.
