Nykaa Marketplace Reconciliation Using OMS

Nykaa marketplace reconciliation using OMS helps finance teams compare internal order records with marketplace reports, settlements, and payout data in a structured way. Instead of working through spreadsheets and ad hoc checks, teams can map the required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in one report.

For eCommerce and marketplace finance teams, the main challenge is that OMS data and marketplace data often do not line up exactly. Orders may be split across reports, settlement values may include deductions or adjustments, and some records may appear in one system but not the other. Cointab is built to handle this kind of reconciliation workflow with reusable setup, clear exception handling, and audit-ready reporting.

Why Nykaa marketplace reconciliation becomes complex

Nykaa marketplace reconciliation usually involves more than just comparing two totals. Finance teams often need to account for:

• Order-level differences between the OMS and marketplace reports
• SKU-level splits or merged records
• Payout timing differences
• Settlement deductions, fees, or adjustments
• Returns, cancellations, and reversals
• Missing or incomplete identifiers
• Late-arriving files from the marketplace or internal systems

When these items are reviewed manually, reconciliation becomes repetitive and difficult to audit. Cointab replaces that process with a structured workflow where the team uploads files, maps fields, runs reconciliation, and reviews clear exception buckets.

Typical reports used in the reconciliation

A Nykaa marketplace reconciliation workflow can use one or more of the following reports:

• Nykaa all order report
• Nykaa sales report
• Nykaa payout report
• Bank statement
• Client OMS export such as Increff, Unicommerce, EasyEcom, or another internal order system

Depending on the workflow, supporting files can also be uploaded to enrich the primary reports before reconciliation. Common examples include product masters, SKU mapping files, tax mapping files, or reference files used for lookup and calculation.

How Cointab structures the reconciliation

Cointab uses a Side A and Side B model so finance teams can clearly define what they expect to be correct and what they are comparing it against.

Side A: your OMS records

Side A usually contains the business's internal source-of-truth records, such as:

• OMS order data
• Internal sales working
• ERP exports
• Order-level finance records
• SKU-level shipment or invoicing data

Side B: Nykaa marketplace records

Side B usually contains the external marketplace reports, such as:

• Nykaa sales report
• Nykaa order report
• Nykaa payout or settlement data
• Marketplace adjustments or deduction reports

Users upload CSV, XLS, or XLSX files, then map the relevant fields such as date, amount, and identifier columns. Identifiers may include order ID, transaction ID, invoice number, settlement ID, SKU, or other business references.

If the same report format is used every month, the setup can be reused for future runs instead of being rebuilt from scratch.

Matching logic for Nykaa marketplace reconciliation

Cointab's reconciliation engine uses structured matching logic to compare records across both sides. This is useful when marketplace reporting does not follow a simple one-to-one pattern.

The platform supports scenarios such as:

• One OMS order matched to one Nykaa record
• One OMS record matched to multiple marketplace records
• Multiple OMS records matched to one marketplace record
• Net-to-net comparisons
• Partial matches where identifiers align but amounts differ
• Contra entries or adjustment-style records
• Cross-side matching when supporting references appear in different fields

This matters in marketplace reconciliation because a single order may move through multiple operational states before it settles. For example, the order may appear in the OMS at the time of booking, then later show deductions, returns, or settlement differences in Nykaa reports.

What finance teams see after the run

Once reconciliation is complete, the report dashboard shows transaction-level results with clear buckets.

Fully matched

These are records where the identifiers and amounts match according to the configured rules. For example, an OMS order matches the Nykaa sales record with the expected amount.

Partially matched

These are records where the transaction is related, but the amounts do not fully match. This is useful when the order ID or reference is present on both sides, but the settlement amount differs because of fees, deductions, returns, or adjustments.

Unmatched

These are records present on one side but not found on the other. For example:

• An OMS order that does not appear in Nykaa reports
• A Nykaa record that does not appear in the OMS
• A payout or settlement record that is not tied back to the internal books

Skipped

Skipped records are rows that were excluded from reconciliation because they were incomplete, invalid, duplicated, or missing required data. Showing skipped records is important because finance teams need to know what was left out and why.

The report also supports filters and detailed transaction views so teams can investigate exceptions without reviewing every row manually.

Supporting data and derived columns

Marketplace reconciliation often needs more than direct row matching. Cointab supports supporting data and derived columns to make the comparison more complete.

Supporting data can be used to:

• Enrich missing order details
• Merge reports before reconciliation
• Add product or SKU information
• Apply tax or fee lookups
• Normalize marketplace-specific identifiers

Derived columns can be created from existing data and used as amount fields, identifier fields, or comparison fields. This is especially useful when teams need a clean order ID, a normalized transaction reference, or a net amount calculated from multiple columns.

AI can help finance users create these formulas in a simpler way by describing the logic in natural language and generating an Excel-style formula.

Handling open items and exceptions

Not every discrepancy should be forced into a match. After structured matching is complete, Cointab can analyze remaining open items and help teams understand why they remain unresolved.

Common reasons include:

• Missing file from the marketplace or internal system
• Late settlement or delayed payout
• Return or cancellation not yet reflected everywhere
• Fee or deduction differences
• Inconsistent identifiers across reports
• Records that need manual review before closing

If the evidence is not strong enough, the transaction remains unmatched rather than being weakly matched. That makes the output more suitable for finance review and audit follow-up.

Users can also manually match transactions when business context is known and the totals tally, which is helpful for one-off exceptions or incomplete partner data.

Reuse for recurring marketplace close processes

Nykaa marketplace reconciliation is often a recurring workflow, not a one-time exercise. Once a reconciliation is configured, teams can reuse it for the next period by selecting the reconciliation, choosing the period, uploading the files, and running the report again.

This makes it easier to handle:

• Monthly close
• Quarterly review
• Custom settlement periods
• Ongoing open items that need to be carried forward

For recurring operations, Cointab can also automate data input and scheduled runs through email, SFTP, or API integrations. After reconciliation is completed, the output can be delivered to internal systems by email, SFTP, or API as well.

What this helps finance teams control

A structured Nykaa marketplace reconciliation workflow helps teams maintain visibility over:

• Orders that were paid, pending, or missing
• Settlement differences and deductions
• Records that need follow-up with the marketplace
• Internal OMS entries that require correction
• Audit-ready reporting for review and period close

For finance leaders, the key benefit is not just faster matching. It is having a transparent process that shows what matched, what did not, what was skipped, and what action is needed next.

FAQs

What files are usually needed for Nykaa marketplace reconciliation?

A typical workflow uses Nykaa order or sales reports, payout or settlement reports, a bank statement, and OMS exports. Supporting files such as SKU mapping or product master files can also be used when enrichment is needed.

Can Cointab handle order-level and SKU-level matching?

Yes. The reconciliation setup can be mapped at the order level, SKU level, or another business reference level depending on how the reports are structured.

What happens if the amounts match but the identifiers differ slightly?

Cointab supports structured matching logic and comparison methods that can handle partial references, similar descriptions, and other controlled matching scenarios. If the evidence is not strong enough, the record remains open for review.

Can the same Nykaa reconciliation setup be reused every month?

Yes. Once the workflow is configured, it can be reused for future periods instead of being rebuilt each time. That helps reduce repeated setup work and keeps the process consistent.

What if a report was missed during the first run?

The missed file can be uploaded under the same reconciliation and the report can be refreshed so the new data is included in the output.