JioMart Marketplace Reconciliation Automation

Cointab helps JioMart sellers automate marketplace reconciliation across sales, settlement, returns, fees, and bank entries. Finance teams can upload their reports, map the required fields once, run reconciliation, and review a clear audit-ready report that shows what matched, what differed, and what still needs attention.

What JioMart marketplace reconciliation covers

For most sellers, JioMart reconciliation is not just one report comparison. It is usually a structured match between internal records and the reports received from the marketplace and the bank.

In Cointab, the workflow follows a simple Side A and Side B model:

• Side A: your internal records, such as sales data, ERP exports, order reports, or books
• Side B: external records, such as JioMart settlement files, service invoices, return reports, payout files, or bank statements

This makes it easier to compare the records your business expects with the records received from the marketplace or bank.

Common JioMart reconciliation workflows

JioMart sellers usually need more than one type of reconciliation. Cointab supports flexible setups for recurring marketplace operations, including:

• Sales vs settlement reconciliation to check whether order values are reflected correctly in the settlement report
• Settlement vs bank reconciliation to verify whether the deposited amount matches the expected payout
• Sales vs returns reconciliation to review returns, cancellations, and reversals
• Fee and deduction reconciliation to identify undercharges, overcharges, commissions, or other deductions
• Bank vs books reconciliation to compare receipts in the bank statement with internal accounting records

The same reconciliation setup can be reused for future periods, which helps finance teams avoid rebuilding the workflow every month.

How the reconciliation process works

1. Upload the required files

Users upload CSV, XLS, or XLSX files for the reports they want to compare. For each primary report, Cointab asks for the important fields such as:

• header row
• date column
• amount column
• reference or identifier column

For JioMart reconciliation, this often includes order IDs, transaction references, settlement IDs, invoice numbers, or bank reference numbers.

2. Map fields once

After upload, users map the required columns so the reconciliation engine knows which values to compare. This mapping step helps keep the process consistent across runs and periods.

If a file does not match the configured format, Cointab can reject it with a clear validation message so finance teams can fix the issue before reconciliation starts.

3. Add supporting data if needed

Some marketplace workflows need extra data before matching can begin. Cointab lets teams upload supporting datasets for lookups, merges, enrichment, or calculations.

Examples include:

• product master data
• SKU mapping files
• return reports
• fee rate files
• customer or vendor master data
• order metadata
• GST or tax mapping files

Supporting data is useful when a seller needs to enrich marketplace files before comparing them to settlements or books.

4. Create derived columns when required

If the raw file needs cleanup or calculation, users can create derived columns on either side. Cointab supports AI-assisted formula generation for finance teams that know the business rule but do not want to build formulas manually.

Examples of derived columns include:

• clean order ID
• normalized transaction reference
• net amount
• amount after fee
• refund amount as a negative value
• combined reference key

Derived columns help teams prepare JioMart data for matching without relying on manual Excel work.

5. Run reconciliation

Once the files and mappings are ready, users run reconciliation manually or schedule it to run automatically. Cointab applies structured matching logic to compare records across both sides.

The engine supports common matching scenarios such as:

• one-to-one matching
• one-to-many matching
• many-to-one matching
• many-to-many matching
• partial matching
• net-to-net matching
• contra matching

This is useful in marketplace workflows where one order, one settlement line, or one payout may relate to multiple records.

6. Review the report

When the run completes, users can review the reconciliation report in the dashboard. The report typically includes:

• total summary
• fully matched transactions
• partially matched transactions
• unmatched transactions
• skipped transactions
• filters for deeper analysis
• transaction-level details
• download option for the Excel report

What the reconciliation report shows

Cointab separates records into clear categories so finance teams know what happened to each transaction.

Fully matched

These are records where the identifiers and amounts match according to the configured logic. For example, a JioMart order may match the settlement report by order ID and amount.

Partially matched

These are records where the identifiers match but the amount differs. Partial matches are important because they often point to deductions, fees, rounding differences, returns, or other adjustments that need review.

Unmatched

These are records present on one side but not found on the other side. In a JioMart workflow, this may mean a sale is present in the internal file but missing from the settlement report, or a bank receipt is present but not reflected in the expected settlement file.

Skipped

Skipped records are rows that were not included in reconciliation because of missing data, invalid values, duplicate rows, or another file issue. Cointab keeps skipped records visible so finance teams can understand what was excluded and why.

Handling open items and exceptions

After structured matching is complete, Cointab can help analyze remaining open transactions. This is useful when a marketplace reference is incomplete, the description is inconsistent, or the reason for the difference is not obvious.

Finance teams can also use manual match for one-off exceptions when the business context is clear and the totals tally. Manual matches remain clearly marked so the audit trail stays transparent.

This makes the workflow practical for real marketplace operations, where late files, missing references, refunds, and deductions are common.

Why finance teams use Cointab for marketplace reconciliation

Cointab is built to reduce repetitive spreadsheet work and make reconciliation more repeatable across periods. For JioMart sellers and marketplace finance teams, that means:

• faster reconciliation runs
• less manual comparison in Excel
• consistent matching logic across periods
• clearer exception handling
• reusable setup for recurring monthly or daily runs
• audit-ready Excel export for review and follow-up

Teams can also configure automated data input through email, SFTP, or API, and Cointab can optionally push reconciliation output back to internal finance, accounting, analytics, or BI systems.

Reconciliation periods and reuse

Marketplace reconciliation often needs to run for monthly, quarterly, or custom periods. Cointab supports reusable workflows so teams can keep the same setup and only update the period and files.

This is especially useful when JioMart sellers need to compare:

• a single month of activity
• a custom settlement period
• a running reconciliation for open items
• historical reports for review or audit preparation

If a file is missed, users can upload it under the same reconciliation and refresh the report.

A structured workflow for JioMart sellers

For finance teams, the value of JioMart reconciliation is not just matching numbers. It is having a clear process that shows:

• what files were used
• what fields were mapped
• what matched automatically
• what remains open
• what was skipped
• what needs review
• what can be reused next period

That structure helps marketplace teams move from ad hoc spreadsheet checking to a repeatable reconciliation workflow with better visibility and control.