Nykaa Marketplace Reconciliation Using ERP

For brands selling on Nykaa, reconciliation often involves more than comparing a sales report to an ERP export. Finance teams may need to match orders, settlements, refunds, returns, deductions, fees, and payment entries across multiple files. Cointab provides a structured way to reconcile Nykaa marketplace data with ERP records so teams can review matched, partially matched, unmatched, and skipped transactions in one place.

Why Nykaa marketplace reconciliation matters

Nykaa marketplace reporting can differ from internal ERP records for many reasons. Orders may be cancelled, refunded, partially fulfilled, or settled in later periods. Fees, commissions, taxes, and other deductions may also appear in settlement reports but not in the same format inside the ERP.

Without a structured workflow, teams often rely on Excel formulas, manual checks, and repeated file comparisons. That slows down month-end close and makes it harder to explain open items during review or audit.

A dedicated Nykaa marketplace reconciliation workflow helps finance teams:

• compare marketplace data with ERP entries in a repeatable process
• identify missing orders, duplicate rows, and amount differences
• separate settlement differences from genuine data issues
• keep a clear audit trail of what matched and what still needs review
• reuse the same setup for future periods instead of rebuilding it each month

Typical reports used in the reconciliation

Cointab supports a Side A and Side B workflow. For Nykaa reconciliation, Side A is usually the business's internal records and Side B is the external marketplace data.

Depending on the workflow, teams may also add supporting files such as product master data, SKU mapping, tax mapping, or fee rate files. Supporting data is not reconciled directly, but it can help enrich, merge, or calculate fields before the main comparison.

How Cointab handles Nykaa ERP reconciliation

Cointab is built for structured reconciliation rather than one-off spreadsheet matching. A typical workflow looks like this:

1. Upload the Nykaa reports and ERP exports.
2. Map required fields such as date, amount, and identifier columns.
3. Optionally add supporting files for lookups, enrichment, or calculations.
4. Create derived columns where needed, such as clean order IDs, net amounts, or normalized references.
5. Run the reconciliation manually or on a schedule.
6. Review the report dashboard with matched and open items.
7. Download the Excel report for internal review, follow-up, or audit support.

If a file does not match the configured format, Cointab can flag the issue clearly so the team knows what needs correction before the run continues.

What gets matched in the report

Cointab's reconciliation engine can compare records using structured matching logic across order IDs, transaction IDs, invoice numbers, settlement IDs, SKUs, and other business identifiers.

The system can handle common finance scenarios such as:

• one-to-one matching
• one-to-many matching
• many-to-one matching
• many-to-many matching
• partial matching
• net-to-net comparison
• contra-style matching where relevant to the workflow

For Nykaa marketplace reconciliation, that means teams can compare sales, settlements, refunds, and deductions even when the data is not in exactly the same format on both sides.

How to read the reconciliation results

Once the reconciliation run is complete, Cointab groups the data into clear outcome categories.

Fully matched

These are records where the key identifiers and amounts align according to the configured logic. For example, an ERP order line may match a Nykaa sales record with the same reference and amount.

Partially matched

These are records where the identifiers suggest a link, but the amounts do not fully agree. This often happens when deductions, refunds, rounding, or partial settlements are involved.

Unmatched

These records exist on one side but were not found on the other. Common examples include:

• an order present in Nykaa but missing from ERP
• an ERP entry that has not yet appeared in the marketplace report
• a settlement row with no matching internal reference
• a refund or return that has not been booked correctly

Skipped

These records were not included in the comparison because they were incomplete, invalid, duplicate, or excluded by rule. Skipped rows remain visible so the team can understand why they were ignored.

Common mismatch reasons in marketplace reconciliation

Nykaa marketplace reconciliation usually reveals a small set of recurring exception types. These may include:

• missing order imports into ERP
• settlement timing differences between marketplace and books
• cancellations, returns, or refunds not booked correctly
• commissions, shipping charges, or platform fees
• tax or GST mapping differences
• duplicate rows in one of the source files
• partial shipments or partial settlements
• reference fields that differ across systems

Cointab helps teams isolate these cases so they can focus on the exceptions instead of manually reviewing every row.

Reusable setup for recurring periods

A major benefit of using Cointab for Nykaa marketplace reconciliation is reuse. Once the workflow is configured, the same setup can be used again for the next month, quarter, or custom period.

That reduces repeat work because teams only need to:

• select the reconciliation
• choose the period
• upload the latest files, or use automated data input where configured
• run reconciliation
• review the report

If a file is received late, the missed report can be uploaded under the same reconciliation and the output can be refreshed.

Automation for recurring finance operations

For teams that reconcile Nykaa data regularly, Cointab can also support automated data input and scheduled runs through email, SFTP, or API-based workflows where configured.

This is useful when the team wants reconciliation to become part of daily or period-end finance operations instead of a manual monthly upload process. The output can also be delivered back to internal systems through email, SFTP, or API, depending on the workflow design.

Audit-friendly reporting for finance teams

Cointab provides a reconciliation report that is designed for finance review. The output shows transaction-level details along with summary views so teams can explain what matched, what did not, and what requires follow-up.

Finance teams can use the report to support:

• month-end close
• internal review
• vendor or marketplace follow-up
• audit preparation
• reporting to leadership

The result is a clearer view of Nykaa marketplace data without rebuilding the reconciliation in Excel every period.