Nykaa Marketplace Fee Reconciliation

Cointab helps Nykaa sellers reconcile marketplace fees by comparing internal sales records with marketplace settlement and payout data. Instead of checking fee deductions manually in Excel, finance teams can upload reports, map key fields once, and review matched, partially matched, unmatched, and skipped transactions in a structured workflow.

What Nykaa marketplace fee reconciliation covers

Marketplace fee reconciliation helps finance teams verify whether the charges applied against each order or settlement line are consistent with the underlying transaction data.

For Nykaa sellers, this usually means comparing:

• internal sales or order data
• marketplace settlement or payout reports
• fee and deduction details
• returns, cancellations, or adjustment data
• supporting reference files used for lookup or enrichment

The goal is to understand whether the marketplace has charged the expected fee, whether there is a difference in settlement, and which records need follow-up.

Side A and Side B in the reconciliation flow

Cointab uses a Side A / Side B model so finance teams can keep the setup clear and auditable.

Side A: your records

Side A contains the records your business expects to be correct. For a Nykaa fee workflow, this may include:

• order and sales reports
• internal revenue or ERP exports
• invoice or ledger data
• order-level reference data
• supporting product or SKU mappings

Side B: external marketplace records

Side B contains the records received from the marketplace or related external source. For this use case, that may include:

• settlement reports
• payout reports
• deduction summaries
• fee and commission details
• return or adjustment information

If the reconciliation requires enrichment, teams can also upload supporting data such as product masters, fee mappings, or reference files before running the match.

How Cointab reconciles marketplace fees

Cointab turns fee reconciliation into a repeatable process instead of a monthly spreadsheet exercise.

1. Upload the files

Users upload the required CSV, XLS, or XLSX files for Side A and Side B. Multiple files can be used where needed, as long as they follow the same configured format.

2. Map the required fields

Teams map the key columns once, such as:

• order date
• amount
• settlement value
• transaction reference
• order ID or other identifier columns

If needed, users can also add supporting datasets for enrichment or lookup before reconciliation begins.

3. Create derived columns when needed

Cointab supports derived columns, which are calculated fields created from existing data. This is useful when fee logic needs a clean amount, a normalized reference, or a net value before matching.

Examples include:

• net order amount
• cleaned order reference
• amount after adjustment
• fee basis amount
• normalized settlement reference

AI can help generate Excel-style formulas for these calculated columns, which reduces manual formula work.

4. Run the reconciliation

When the user runs the workflow, Cointab applies structured matching logic to compare the two sides. The engine supports simple and complex matching scenarios, including one-to-one and grouped comparisons where records need to be netted or compared across multiple lines.

5. Review the results

Once the reconciliation is complete, users can review the report dashboard and inspect the records that matched, did not match, or need review.

What the reconciliation report shows

Cointab presents reconciliation results in a format that is useful for finance review and audit preparation.

Fully matched records

These are transactions where the records align according to the reconciliation logic. For a fee workflow, this means the order and deduction or settlement record match as expected.

Partially matched records

These are records that are related, but the amounts do not fully agree. In a fee context, that may indicate:

• a higher-than-expected deduction
• a lower-than-expected deduction
• a difference caused by returns or adjustments
• a settlement variance that needs review

Unmatched records

These are transactions found on one side but not the other. For example, a sale may exist in the internal report but not appear in the marketplace settlement file, or vice versa.

Skipped records

Skipped records are rows that were not included in reconciliation because of missing data, invalid values, duplicates, or a file issue. Visibility into skipped rows helps finance teams understand exactly what was excluded.

Common fee differences finance teams review

Nykaa marketplace fee reconciliation often involves reviewing more than just a simple commission line. Finance teams may also need to check:

• deductions tied to marketplace fees
• shipping or handling adjustments
• return-related differences
• cancellation-related changes
• rounding or settlement variances
• missing or delayed payout rows
• reference mismatches across reports

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

Why finance teams use Cointab for marketplace fee reconciliation

Faster recurring checks

Once a reconciliation is configured, the same setup can be reused for future periods. Teams do not need to rebuild formulas or matching logic every month.

Better control over exceptions

Cointab separates fully matched, partially matched, unmatched, and skipped records so the team can focus on issues that need attention.

Audit-ready reporting

Users can download Excel reconciliation reports for internal review, partner follow-up, and audit support. The output is structured and easy to trace back to source files.

Team collaboration

Finance teams can work in a shared workspace with roles and permissions instead of passing spreadsheets around by email.

Automation for recurring workflows

Where a workflow is repeated regularly, Cointab can support automated data input through email, SFTP, or API, and can also automate scheduled reconciliation runs.

When Nykaa fee reconciliation is especially useful

This use case is valuable when a business:

• sells through Nykaa on a recurring basis
• manages high transaction volumes
• needs to verify deductions and settlement values
• wants a cleaner month-end close process
• needs to compare sales, fees, and payouts across reports
• wants to reduce manual Excel-based checking

It is also useful for teams that need a transparent workflow where every match, mismatch, and skip is visible and reviewable.

FAQs

What data is needed for Nykaa marketplace fee reconciliation?

At minimum, finance teams usually need a sales or order report on one side and a settlement or payout report on the other. Supporting files can be added if fee calculation or enrichment requires extra reference data.

Can Cointab handle partially matched fee records?

Yes. Partially matched records are clearly separated so teams can review transactions where the reference matches but the amount differs.

Can the same reconciliation be reused for future periods?

Yes. Once configured, the workflow can be reused for later periods with the same structure, which reduces repeated setup work.

Does Cointab support manual review for exceptions?

Yes. Users can review open items and manually match records when the business context is clear and the totals tally.

Can the reconciliation be automated?

Yes. Cointab supports recurring workflows with automated data input and scheduled reconciliation runs where the setup has already been defined.