Nykaa Marketplace Reconciliation Using ERP

Reconcile Nykaa marketplace data with ERP records in a structured workflow that helps finance teams identify settlement differences, missing orders, fee deductions, and unmatched transactions. Instead of comparing files manually in Excel, teams can map the required fields once, run reconciliation, and review results in an audit-friendly format.

Why Nykaa marketplace reconciliation matters

Nykaa marketplace reporting often needs to be compared with internal ERP records to confirm that orders, invoices, settlements, and bank receipts align. In practice, finance teams may need to validate:

• Marketplace sales against ERP sales invoices
• Settlement or payout reports against internal books
• Order-level details against ERP exports
• Returns, fees, deductions, and adjustments against expected amounts
• Bank entries against payout or settlement records

When these records do not line up, teams must find out whether the issue is a missing order, a timing difference, a deduction, a return, or a data entry problem in the ERP.

Side A and Side B in this reconciliation

Cointab uses a simple Side A / Side B model for marketplace reconciliation.

This structure makes it easier to see what is expected internally versus what was reported by the marketplace.

Typical reports used for Nykaa ERP reconciliation

A Nykaa marketplace reconciliation workflow may use one or more of the following files:

• Nykaa order report
• Nykaa sales report
• Nykaa payout or settlement report
• Bank statement
• ERP export from the finance system
• Supporting files such as SKU mapping, tax mapping, fee mapping, or order metadata

If the business reconciles at a detailed level, the workflow can also use identifiers such as order ID, invoice number, settlement ID, payment reference, or SKU.

How the reconciliation workflow works

A reusable reconciliation setup helps finance teams repeat the same process for every period.

1. Upload the Side A and Side B files, or configure automated data input.
2. Map the required columns such as date, amount, and identifiers.
3. Add supporting files if lookup or enrichment is needed.
4. Create derived columns where calculations are required.
5. Run reconciliation manually or on a schedule.
6. Review the report dashboard and drill into exceptions.
7. Download the Excel report for audit, internal review, or partner follow-up.

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

What Cointab helps classify

The reconciliation report separates records into clear outcome groups so finance teams can focus on exceptions.

Fully matched

These are transactions where the relevant identifier and amount match according to the reconciliation rules.

Partially matched

These are transactions that are related across both sides, but the amounts do not fully agree. This is useful when the order exists in both systems but deductions, returns, or fee differences still need review.

Unmatched

These are records present on one side but not found on the other. For Nykaa ERP reconciliation, this may include:

• Orders in ERP but not in Nykaa reports
• Orders in Nykaa reports but not in ERP
• Payout entries that do not tie to a bank line
• Settlement records that do not tie to an internal invoice or order

Skipped

Skipped rows are records that were excluded because they were incomplete, invalid, duplicated, or did not meet the configured rules. Keeping skipped items visible helps teams understand why they were not included.

Common exception patterns in marketplace reconciliation

Marketplace reconciliation usually uncovers a few recurring patterns.

• Settlement value is lower than expected because of marketplace fees or deductions
• Settlement value is higher or lower due to returns, reversals, or adjustments
• Orders exist in ERP but are missing from the marketplace report
• Marketplace records exist but have not been posted correctly in ERP
• Amounts match at the order level but differ after taxes, commissions, or rounding
• One internal record needs to be matched against multiple marketplace entries, or vice versa

Cointab’s reconciliation engine is designed for structured matching, including one-to-one, one-to-many, many-to-one, and grouped comparisons.

Using supporting data for better matching

Nykaa reconciliation often becomes easier when supporting data is added before matching. Supporting data is not reconciled directly. It is used to enrich or prepare the primary files.

Examples include:

• Product master
• SKU mapping file
• Fee rate file
• Tax mapping file
• Order metadata
• Return report
• Delivery or reference data

This is useful when the ERP file does not already contain every field needed for a clean comparison.

Derived columns for ERP and marketplace reports

Finance teams often need calculated columns before reconciliation begins. Cointab supports derived columns that are created from existing data.

Examples include:

• Clean order ID
• Net amount after deductions
• Amount excluding tax
• Refund amount as negative
• Combined reference field
• Normalized transaction ID

AI can help generate Excel-style formulas for these derived columns, which reduces manual formula work and keeps the setup reusable.

Why this workflow is useful for finance teams

Reconciliation of Nykaa marketplace data using ERP is not just about finding differences. It also helps teams keep the finance process consistent and reviewable.

Benefits include:

• Less manual Excel work
• Faster review of open items and exceptions
• Reusable setup for future periods
• Clear separation of matched, partially matched, unmatched, and skipped records
• Better visibility into settlement differences and missing entries
• Audit-ready reports for internal control and month-end close
• A shared workspace for finance and operations teams

Reusing the same setup for future periods

Once the Nykaa reconciliation has been configured, the same setup can be reused for the next month, quarter, or custom period. Teams usually only need to select the reconciliation, choose the period, upload the latest files, and run the report again.

This is especially useful for recurring marketplace close cycles where the same matching logic is needed every period.

Automated reconciliation and output delivery

For recurring workflows, data can be received or pulled through email, SFTP, or API integrations. After the reconciliation run completes, output can also be delivered back to other systems through email, SFTP, or API.

This makes the reconciliation process more suitable for daily or periodic finance operations, not just one-time file review.

FAQ

What does Nykaa marketplace reconciliation with ERP compare?

It compares internal ERP records with Nykaa marketplace reports to validate sales, settlements, payouts, returns, and related differences.

Can this workflow handle fees, deductions, and returns?

Yes. Supporting files and derived columns can be used to prepare amounts for reconciliation and to analyze differences caused by fees, deductions, or returns.

What if the file format changes?

If a file does not match the configured format, the system can reject it with a clear error so the issue is visible before reconciliation runs.

Can the same reconciliation be reused every month?

Yes. Once the workflow is configured, it can be reused for future periods without rebuilding the setup each time.

Can finance teams review unmatched records separately?

Yes. The report separates fully matched, partially matched, unmatched, and skipped records so teams can focus on exceptions first.