JioMart Marketplace Reconciliation Using OMS

Cointab helps finance and marketplace operations teams reconcile JioMart marketplace data against their internal OMS records in a structured, repeatable way. Instead of comparing files manually in Excel, teams can upload reports, map the required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in an audit-ready report.

Why JioMart reconciliation needs a structured workflow

JioMart reconciliation usually involves more than one report and more than one kind of difference. Teams may need to compare order-level records, invoice values, service charges, disbursements, and returns while also checking whether the OMS reflects the same business activity.

That makes the process difficult to manage manually, especially when:

• order identifiers appear in different formats across files
• settlement values do not exactly match the OMS
• returns or deductions affect the final amount
• some records appear in one report but not the other
• the same reconciliation must be repeated for every period

Cointab brings these records into a structured Side A and Side B workflow so finance teams can see what matched, what did not match, and what needs review.

How Cointab handles JioMart reconciliation with OMS data

In this use case, Side A is typically your internal OMS or order records, and Side B is the JioMart marketplace reports.

Side A: your OMS records

Side A contains the records your business expects to be correct. These may include:

• order reports from your OMS
• internal sales data
• invoice or order working files
• order identifiers, amounts, and status fields

Side B: JioMart marketplace records

Side B contains the external records received from JioMart. Depending on the workflow, this may include:

• invoice report
• service invoice report
• disbursement report
• return report

Cointab lets users configure the required fields for each report, such as:

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

If a file does not match the configured format, the system can reject it with a clear error so finance teams can correct the issue before running reconciliation.

Reconciliation steps for JioMart and OMS

A typical JioMart OMS reconciliation follows a simple setup-and-run flow:

1. Upload the OMS report on Side A.
2. Upload the relevant JioMart reports on Side B.
3. Map the required fields once for each report.
4. Optionally upload supporting data such as mapping or reference files.
5. Create derived columns if a value needs to be cleaned, combined, or calculated.
6. Run reconciliation manually or on a recurring schedule.
7. Review the report dashboard and exception details.
8. Download the Excel output for internal review or follow-up.

This approach makes it easier to manage recurring reconciliation periods without rebuilding the workflow every time.

What the reconciliation report shows

Once reconciliation is complete, the report dashboard separates records into clear groups.

Fully matched

These are records where the identifier and amount align according to the configured logic. For example, an OMS order matches a JioMart record by order reference and value.

Partially matched

These are records where a relationship exists, but the amounts do not fully match. This is useful when the order appears on both sides, but the settlement, invoice, or return value needs review.

Unmatched

These are records that appear on one side but not on the other. For JioMart reconciliation, this may show:

• an OMS order not found in the JioMart report
• a JioMart record not reflected in the OMS
• a settlement or return entry that does not map to an internal record

Skipped

Skipped records are rows that were not included in reconciliation because of missing data, invalid values, duplicates, or another file issue. Keeping skipped items visible helps finance teams understand what was excluded and why.

Common exception patterns in JioMart reconciliation

Marketplace reconciliation is often about identifying the reason behind differences, not just finding a match.

Common exception patterns include:

• an order exists in OMS but is missing from the JioMart report
• the JioMart amount is lower or higher than the OMS amount
• a return or deduction changes the final settlement value
• the identifier is present but formatted differently across files
• one transaction is split across multiple entries on one side
• multiple transactions need to be compared as a net amount

Cointab applies structured matching logic first and then uses AI to analyze remaining open items where a deterministic match is not enough. This helps finance teams focus on the records that actually need attention.

Supporting data and derived columns

JioMart reconciliation often becomes easier when teams can enrich or normalize their data before matching.

Cointab supports optional supporting data such as lookup files, master files, or mapping sheets that help prepare the primary reports.

Teams can also create derived columns using AI-generated Excel-style formulas. This is useful when they need to:

• clean order references
• normalize identifiers
• calculate net values
• combine fields for matching
• convert status-based logic into a usable amount or reference column

Derived columns are recalculated whenever reconciliation runs, which keeps the setup reusable for future periods.

Manual match and missed file handling

Some JioMart exceptions require human review.

Cointab provides a manual match option for transactions the system cannot confidently match. This is useful when the finance team has business context that is not obvious from the data alone.

If a report was missed, the file can be uploaded under the same reconciliation and the report can be refreshed. That matters in real finance operations, where partner files or settlement files may arrive late.

Reuse for recurring periods

A major advantage of this workflow is reuse.

Once the JioMart OMS reconciliation is configured, the same setup can be used again for future periods. Finance teams can reconcile monthly, quarterly, or custom periods without rebuilding the process from scratch.

This helps teams maintain consistency across periods and reduces the spreadsheet work that usually comes with marketplace reconciliation.

Why finance teams use Cointab for marketplace reconciliation

Cointab is designed to make marketplace reconciliation transparent and reviewable for finance teams.

It helps teams:

• compare internal OMS records with external marketplace data
• identify discrepancies faster
• separate matched, partially matched, unmatched, and skipped items clearly
• reuse the same reconciliation setup for recurring runs
• produce audit-ready Excel reports for review and follow-up

For teams handling JioMart marketplace operations, that means less manual file comparison and a clearer view of what needs action in each period.

FAQs

What JioMart reports can be reconciled with OMS data?

Common report types include invoice reports, service invoice reports, disbursement reports, and return reports. These can be compared against OMS data depending on how your internal workflow is structured.

Can the same reconciliation be reused every month?

Yes. Once the field mapping and matching logic are set up, the same reconciliation can be reused for future periods, which reduces repeat configuration work.

What happens if an order is present in OMS but missing in JioMart?

It appears as an unmatched record, so the team can review whether the file is missing, the order was delayed, or the records need follow-up.

Does Cointab support manual matching?

Yes. If the system and AI do not confidently match a transaction, users can manually match records when the totals and business context support it.

Can skipped records be reviewed?

Yes. Skipped records remain visible in the reconciliation report so finance teams can understand which rows were excluded and why.