Nykaa Fashion Marketplace Reconciliation with OMS

Cointab helps Nykaa Fashion sellers reconcile marketplace data with their internal OMS records in a structured, reusable workflow. Finance and operations teams can compare orders, sales, payouts, returns, and settlement values, then review matched, partially matched, unmatched, and skipped transactions in one place.

Why Nykaa Fashion marketplace reconciliation matters

For marketplace sellers, the OMS is often the internal source of truth for order processing, while Nykaa Fashion provides external reports for order activity, sales, payouts, deductions, and settlement updates. These records do not always line up perfectly.

Common reasons for differences include:

• cancellations that appear at different times in each system
• returns or replacements processed after the original order
• settlement deductions, fees, or adjustments
• partial shipments or split fulfilment
• file format changes across periods
• missing or delayed reports from the marketplace

A structured reconciliation workflow helps teams avoid repeated Excel checks and gives them a clearer view of what is matched, what is pending review, and what needs follow-up.

Side A and Side B in this reconciliation

Cointab uses a simple Side A and Side B model.

Side A: your OMS records

Side A contains the records your business expects to be correct. For Nykaa Fashion reconciliation, this usually includes:

• OMS order data
• internal sales records
• SKU-level order details
• invoice or fulfilment references
• return or cancellation details

Side B: Nykaa Fashion marketplace records

Side B contains the external records received from the marketplace. Depending on the workflow, this may include:

• order reports
• sales reports
• payout or settlement reports
• return reports
• deduction or adjustment reports

Cointab lets you map the required fields on both sides so the reconciliation can compare order IDs, reference numbers, dates, amounts, and other identifiers consistently.

What teams typically reconcile

A Nykaa Fashion marketplace reconciliation workflow can cover more than just order totals. Finance teams often compare multiple fields, such as:

• order ID or transaction reference
• SKU or item-level information
• order date and transaction date
• quantity and item value
• discounts, fees, and deductions
• payout or settlement amount
• return or cancellation status

This makes it easier to spot whether a difference is caused by a missing order, a timing issue, or a real value mismatch.

How Cointab handles the workflow

Cointab provides a repeatable reconciliation process that can be reused for each reporting period.

1. Upload the OMS file on Side A and the Nykaa Fashion report on Side B.
2. Map the required fields such as date, amount, and reference columns.
3. Optionally upload supporting data for lookups, enrichment, or calculations.
4. Create derived columns when business logic needs cleanup or normalization.
5. Run reconciliation manually or schedule it to run automatically.
6. Review the reconciliation report once processing is complete.
7. Download the Excel output for internal review, audit, or partner follow-up.

If the reconciliation needs recurring data flow, Cointab can also support automated input and output delivery through email, SFTP, or API.

Where AI helps

Cointab includes AI-assisted support for reconciliation work that usually takes extra manual effort.

AI formula builder

Finance users can describe a calculation in plain language, and Cointab can help generate an Excel-style formula for a derived column. This is useful when a field needs to be cleaned, combined, normalized, or conditionally calculated before matching.

AI-assisted open-item analysis

After structured matching is complete, AI can help analyze open items that do not match cleanly through rules alone. This is useful when references are inconsistent, descriptions vary, or the case needs additional business context.

AI reason and action analysis

For unresolved items, AI can help surface likely reasons for the mismatch, such as a missing file, a refund, a return, a fee difference, or an internal data issue. The output remains reviewable, so finance teams can keep control over the final decision.

Reconciliation outcomes you can review

Cointab separates records into clear reconciliation buckets so teams can focus on exceptions instead of checking every row manually.

Fully matched

These are records where the identifier and amount align according to the configured logic. For example, an OMS order matches a Nykaa Fashion marketplace record at the expected value.

Partially matched

These are records where the identifiers match, but the values differ. This is often the most useful exception category for marketplace finance teams because it highlights related transactions that still need review.

Unmatched

These are records found on one side but not the other. For example, an order may exist in the OMS but not appear in the marketplace report, or the marketplace report may show an item that is missing from the internal records.

Skipped

These are records that were not included in reconciliation because of missing data, invalid values, duplicate rows, or file issues. Skipped records are visible, which helps teams understand what was excluded and why.

Common discrepancy patterns in Nykaa Fashion reconciliation

Marketplace reconciliation often surfaces a predictable set of exceptions. Typical examples include:

• order present in OMS but missing from the marketplace report
• marketplace order present but not found in OMS
• order value difference due to discounts or charges
• settlement amount difference after deductions or adjustments
• return or cancellation reflected on only one side
• SKU-level mismatches caused by file mapping or data timing issues

By separating these cases clearly, Cointab makes it easier to assign follow-up work to the right finance or operations team.

Reusable setup for recurring periods

Once the Nykaa Fashion reconciliation is configured, the same workflow can be reused for future periods. Teams do not need to rebuild their mapping and matching logic each month.

This is helpful for:

• monthly close
• quarterly review
• year-end reporting
• running period-over-period comparisons
• maintaining a consistent reconciliation process across team members

If a file was missed earlier, the team can upload the missing file under the same reconciliation and refresh the report.

Audit-ready reporting and team visibility

Cointab generates downloadable reconciliation reports that show the matched, partially matched, unmatched, and skipped records in a reviewable format. This helps with internal checks, audit preparation, and partner follow-up.

The reconciliation history also stays available on the dashboard, so teams can revisit previous runs, check who executed a reconciliation, and track progress over time. Shared workspaces and role-based access help finance teams work from one place instead of passing Excel files around.

When a custom Nykaa Fashion workflow is useful

Some sellers use a standard marketplace report structure, while others need a custom workflow that reflects their internal setup. Cointab supports both.

A custom reconciliation is useful when the business needs to compare:

• OMS data with multiple Nykaa Fashion files
• order reports with payout and settlement reports
• sales data with returns or deduction files
• item-level records with supporting reference data

This flexibility makes it easier to handle marketplace reconciliation without rebuilding the process every period.