Pepperfry Fee Reconciliation Software
Pepperfry fee reconciliation helps finance teams compare internal sales, expected commission, and settlement amounts against the reports received from the marketplace. For sellers with recurring order volume, the work usually spans order details, shipping charges, cancellations, refunds, deductions, and payout records.
Cointab replaces manual spreadsheet checks with a structured reconciliation workflow. You upload the relevant files, map the required columns once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in a clear report.
What Pepperfry fee reconciliation helps you check
Marketplace fee checks are not limited to commission alone. Finance teams often need to validate several moving parts across the transaction lifecycle.
Typical items to reconcile include:
- Commission charged on each order
- Shipping or logistics charges
- Cancellation-related adjustments
- Refunds and reversals
- Settlement deductions and credits
- Payout references such as UTR or settlement IDs
- Differences between expected and actual fees
This makes Pepperfry fee reconciliation useful not just for accounts teams, but also for marketplace operations teams and finance leaders who need clear visibility into deductions and settlement accuracy.
Side A and Side B in a Pepperfry fee workflow
Cointab uses a Side A and Side B model so teams can keep the reconciliation logic simple and transparent.
Side A: your records
Side A usually contains the records your business expects to be correct. For Pepperfry fee reconciliation, that may include:
- Internal sales or order report
- ERP or accounting export
- Expected commission or fee working
- Product master or SKU master
- Internal cancellation or returns data
Side B: Pepperfry records
Side B contains the external records received from Pepperfry. These may include:
- Order detail report
- Shipping details report
- Cancelled order report
- UTR or payout detail report
- Settlement or fee report
Cointab lets you map the columns you need on both sides, such as date, amount, order reference, transaction ID, SKU, settlement ID, or other business identifiers.
How Cointab handles the reconciliation process
Cointab is designed for teams that want a reusable workflow rather than a one-time spreadsheet exercise.
- Start a new reconciliation in your team workspace.
- Choose a popular reconciliation or create a custom one for Pepperfry fee matching.
- Upload the required files on Side A and Side B.
- Map the fields that matter, such as date, amount, and identifier columns.
- Add supporting data if needed, such as SKU mapping, fee rate files, or return data.
- Create derived columns when you need cleaned or calculated values.
- Run reconciliation manually or on a schedule.
- Review the output with matched, partially matched, unmatched, and skipped records.
- Download the Excel report for internal review, audit work, or partner follow-up.
Where supporting data helps
Pepperfry fee checks often need more than just two reports. Supporting data can help complete or prepare the primary records before matching begins.
Examples of supporting data include:
- SKU master
- Fee rate file
- Product master
- Return report
- Mapping file
- Tax or GST reference file
- Customer or vendor master
Supporting data is useful when you need to enrich a sales line, calculate expected commission, normalize identifiers, or merge multiple reports before reconciliation.
Derived columns for cleaner fee checks
Finance teams often need calculated fields before they can compare actual and expected values. Cointab supports derived columns so you can build those calculations without manually maintaining spreadsheet formulas.
Examples of derived columns for Pepperfry fee reconciliation include:
- Clean order ID
- Net amount
- Expected commission
- Amount after deductions
- Refund amount as negative
- Combined reference field
- Clean settlement ID
You can also use AI to create Excel-style formulas from simple instructions, which helps when your fee logic is clear but the formula is tedious to write by hand.
What the reconciliation report shows
Once the run is complete, Cointab presents the results in a report dashboard so finance teams can focus on exceptions instead of reviewing every row.
The report can show:
- Total summary
- Fully matched records
- Partially matched records
- Unmatched records
- Skipped records
- Transaction-level tables
- Filters for deeper review
- Detailed matched transaction view
- Downloadable Excel output
Fully matched
These are records where the relevant identifiers and amounts match according to the reconciliation logic. For a Pepperfry workflow, this may mean the internal order record aligns with the marketplace order or settlement record and the fee outcome is as expected.
Partially matched
Partially matched records are especially important in marketplace reconciliation. They show that the transaction is related, but the amount is different. This can happen when the charged fee does not match the expected fee, or when deductions, rounding, or settlement adjustments need review.
Unmatched
Unmatched records appear on one side but not the other. For example, an order may exist in your internal report but not in the Pepperfry payout file, or a settlement line may appear externally without a matching internal record.
Skipped
Skipped records are rows that were not included in reconciliation because of missing data, invalid values, duplicates, or rule-based exclusions. Keeping skipped rows visible helps finance teams understand what was left out and why.
Common Pepperfry fee exceptions
A structured reconciliation makes it easier to spot the reasons behind differences.
Common exception scenarios include:
- Commission charged higher than expected
- Commission charged lower than expected
- Shipping or logistics charges that do not align with the working file
- Settlement deductions that need explanation
- Cancelled orders still appearing in a fee report
- Missing payout references or settlement identifiers
- Amount differences caused by returns, refunds, or reversals
When open items remain after structured matching, Cointab can help analyze them further using AI-assisted exception review. If the evidence is not strong enough, the record stays unmatched so the workflow remains audit-friendly.
Manual match for reviewed exceptions
Some cases need human review. Cointab includes a manual match option for transactions that the system cannot confidently match.
Manual matching is useful when:
- An identifier is missing or incomplete
- The partner file uses a slightly different reference
- The finance team knows the business context
- A one-off exception needs to be resolved
- The system and AI do not have enough evidence to match automatically
Manual matches remain clearly marked, so the final report stays transparent.
Why finance teams use Cointab for marketplace fee reconciliation
Pepperfry fee reconciliation is often repeated every month or settlement period. Cointab is built to make that recurring work easier.
Benefits for finance teams include:
- Less manual spreadsheet work
- A reusable setup for future periods
- Clear matched, partially matched, unmatched, and skipped outputs
- Easier investigation of overcharges and undercharges
- Audit-ready Excel reports for internal review
- Team collaboration in one shared workspace
- Flexible handling of monthly, quarterly, yearly, or custom periods
If a file is missed, the reconciliation can be refreshed after the missing report is uploaded, which is useful when marketplace data arrives late.
Reusing the same setup for future periods
Once the Pepperfry workflow is configured, teams do not need to rebuild it every month. They can reuse the same reconciliation, select the new period, upload the files, and run the report again.
This reuse matters because marketplace finance work is repetitive by nature. A stable setup reduces configuration errors and makes period-end review more predictable.
Automation for recurring Pepperfry reconciliation
For teams that handle recurring marketplace data, Cointab can also automate the flow through email, SFTP, or API-based input. That means reconciliation can be triggered after the required files arrive, rather than waiting for manual uploads.
Automated reconciliation is helpful when Pepperfry reporting forms part of a broader finance process that also feeds accounting, reporting, or BI systems.
Audit-friendly reporting for finance review
The output is designed to help finance teams answer practical questions quickly:
- What matched exactly?
- What looks related but needs review?
- What is missing on one side?
- What was skipped and why?
- What amount difference needs investigation?
That clarity is what makes fee reconciliation useful for controllers, accounting teams, and marketplace finance teams that need controlled, reviewable records rather than loosely managed spreadsheet versions.
FAQ
What reports are usually used for Pepperfry fee reconciliation?
Teams typically use internal sales or order data on one side and Pepperfry reports such as order detail, shipping details, cancelled order, and payout or UTR data on the other side. Supporting files like SKU master or fee rate files can also help.
Can Cointab reconcile different fee types, not just commission?
Yes. The same reconciliation workflow can be used to review commission, shipping charges, settlement deductions, refunds, and other fee-related differences as long as the required data is available.
What happens if a file is missing?
If a required file is received later, it can be uploaded under the same reconciliation and the report can be refreshed. This is useful for late-arriving marketplace data.
Can this reconciliation be reused for future periods?
Yes. Once configured, the same Pepperfry fee reconciliation setup can be reused for future runs by selecting the period, uploading the new files, and running reconciliation again.
How does Cointab help with open items?
Cointab separates fully matched, partially matched, unmatched, and skipped records so finance teams can focus on exceptions. AI can assist with open-item analysis, and manual match is available when a human review is needed.
