MensXP Reconciliation Using OMS

MensXP OMS reconciliation helps eCommerce finance teams compare internal OMS records with MensXP marketplace reports so they can verify sales, settlements, returns, losses, and open items in one controlled workflow.

Cointab is designed for this kind of reconciliation. Teams upload the required files, map the right fields once, run reconciliation, and review which transactions are fully matched, partially matched, unmatched, or skipped. The result is a clearer view of order accuracy and settlement differences without rebuilding Excel logic every period.

What MensXP OMS reconciliation covers

MensXP reconciliation is not limited to one report type. In practice, finance and marketplace teams often need to compare multiple records across the same period:

• Internal OMS order data against MensXP order and advice reports
• OMS settlement expectations against MensXP settlement or payout records
• Returns and cancellations against the original order ledger
• Lost, missing, or reversed transactions against internal records
• Fees, deductions, and adjustments that affect the final net amount

This makes the workflow useful for both finance close and day-to-day marketplace operations.

How Cointab structures the reconciliation

Cointab uses a Side A and Side B model so teams can keep the reconciliation process transparent.

Side A: Your OMS records

Side A contains the records your business expects to be correct. For MensXP reconciliation, this is usually the OMS export or another internal source of truth.

Typical Side A fields include:

• Order ID
• Transaction or payment reference
• Order date
• Amount
• SKU or item reference
• Customer or invoice identifier

Side B: MensXP marketplace records

Side B contains the external records received from MensXP.

Typical Side B fields include:

• Marketplace order or settlement reference
• Transaction date
• Gross or net amount
• Return or cancellation details
• UTR or payment reference, where available
• Adjustment or deduction information

Users can upload CSV, XLS, or XLSX files, then map the required columns such as date, amount, and identifiers. If a file does not match the configured format, Cointab can reject it with a clear message so the issue is visible before reconciliation runs.

Common MensXP reconciliation scenarios

1. OMS sales vs MensXP sales reports

This workflow checks whether the orders recorded in the OMS appear correctly in MensXP reports and whether the amounts match.

It helps identify:

• Orders present in both systems with matching amounts
• Orders present in both systems but with amount differences
• Orders recorded in the OMS but missing in MensXP
• Orders present in MensXP but missing in the OMS

2. OMS settlement vs MensXP settlement records

Marketplace settlements often include deductions, returns, fees, and adjustments. Reconciliation helps finance teams verify whether the final net settlement aligns with internal expectations.

This is useful for spotting:

• Under-settled orders
• Over-settled orders
• Missing settlement entries
• Unexpected deductions or reversals

3. Returns, losses, and reversals

Marketplace operations often involve cancellations, returns, or lost orders. These should be traced back to the original order so finance teams can understand why a transaction no longer appears as a clean sale.

Cointab helps teams review these cases as part of the same reconciliation instead of handling them in separate spreadsheets.

4. Missing or late files

If a MensXP report arrives late or a file was missed during the first run, users can upload the missing file under the same reconciliation and refresh the report. This is especially useful when teams work across multiple reports and close periods.

What the reconciliation engine shows

Once the reconciliation runs, Cointab organizes the results into clear status buckets.

Fully matched

These are transactions where the chosen identifiers and amounts match according to the reconciliation logic.

Partially matched

These are transactions where the records are related, but the amounts do not fully align. Partial matches matter because they often point to deductions, adjustments, or short settlement amounts that need review.

Unmatched

These are records present on one side but not found on the other. In MensXP reconciliation, unmatched items may indicate missing orders, missing settlements, unreported returns, or internal posting issues.

Skipped

Skipped records are rows that were not included in reconciliation because they were incomplete, invalid, duplicated, excluded by rule, or missing required data.

Showing skipped records is important because finance teams need to know what was ignored and why.

Supporting data and derived columns

MensXP reconciliation is often easier when teams enrich the main reports with supporting data.

Supporting data can include:

• Product master files
• Mapping tables
• Return or cancellation reports
• Tax or fee reference data
• Customer or vendor master files
• Internal lookup files used for enrichment

Cointab also supports derived columns. These are calculated fields that help normalize data before matching. For example, a team may create a cleaned order ID, a net amount, or a field that converts a business rule into a usable reconciliation column.

AI can help generate Excel-style formulas for these derived columns, which is useful when finance teams know the logic but do not want to write the formula manually.

Why finance teams use this workflow

MensXP reconciliation matters because marketplace data rarely stays in one clean table. Finance teams often need to compare sales, settlements, returns, fees, and adjustments across different reports and periods.

With Cointab, teams can:

• Reduce manual Excel matching and repeated file comparisons
• Reuse the same reconciliation setup for future periods
• Focus on exceptions instead of checking every row manually
• Review matched, partially matched, unmatched, and skipped transactions clearly
• Download audit-ready Excel reports for internal review and follow-up
• Keep the reconciliation visible in a shared team workspace

Reusable and automated reconciliation

Once a MensXP reconciliation is configured, it can be reused for the next period instead of being rebuilt from scratch.

Teams can also automate recurring workflows through email, SFTP, or API-based data input. That means files can be received, validated, loaded, and reconciled on a schedule when the required data is available.

This is useful for monthly close, recurring marketplace review, and finance operations that need consistent reporting without repeated manual uploads.

Manual review when needed

Not every exception can be matched automatically. When structured logic and AI do not have enough evidence, users can review the open items manually and apply a manual match if the totals and business context support it.

That keeps the process practical for real-world marketplace reconciliation, where some items need human review before they are closed.

MensXP reconciliation for audit-ready finance operations

A strong reconciliation process should make it clear what was matched, what was not matched, what was skipped, and what needs follow-up. That is the core of MensXP OMS reconciliation in Cointab.

Instead of relying on ad hoc spreadsheets, finance teams can work from a reusable reconciliation setup that supports consistent reporting, exception handling, and period-by-period review.