Magicpin Orders and Charges Reconciliation
Businesses that sell through Magicpin often need to reconcile internal order records with Magicpin annexure and settlement files. The goal is to confirm that each order was paid correctly and that commissions, discounts, and packing charges were applied as expected. Cointab provides a structured reconciliation workflow for comparing your Side A records with Magicpin's Side B reports, reviewing exceptions, and exporting audit-ready results.
Why Magicpin orders and charges reconciliation matters
Magicpin reconciliation is more than a payment check. Finance teams also need to verify charge components that affect margin and settlement accuracy.
A proper reconciliation process helps teams:
- confirm whether each order was paid in full, short-paid, overpaid, or still pending
- verify commission charges against the agreed rate or charge rule
- check discount deductions and promotional adjustments
- review packing charge calculations where applicable
- identify orders missing from one side of the reconciliation
- reduce manual spreadsheet work during period close
For restaurant, retail, and marketplace finance teams, these checks help keep sales, settlement, and charge reporting aligned.
How the Side A and Side B model applies
Cointab uses a Side A and Side B structure so finance teams can clearly define what is being compared.
Side A: your records
Side A contains the records your business expects to be correct. For a Magicpin workflow, this often includes:
- POS orders
- internal sales or order reports
- ERP exports
- store master data
- expected charge or rate card information
Side B: Magicpin records
Side B contains the records received from Magicpin. These usually include:
- Magicpin annexure
- settlement report
- payout details
- coupon or discount information
- charge and deduction details
Supporting data can be added on either side when it helps with mapping, enrichment, or calculation. For example, teams may use outlet mappings, rate files, or order metadata to prepare the data before reconciliation.
Typical reports used in Magicpin reconciliation
| Report | Purpose | Role in reconciliation |
|---|---|---|
| Magicpin Annexure | Shows order, payout, coupon, and related charge details | Side B |
| POS Orders | Contains the internal order-level transaction record | Side A |
| Store Master | Holds store mapping, outlet details, or commission rates | Supporting data |
| Settlement Report | Shows settled amounts and payout status | Side B |
These reports may be uploaded manually or automated later through email, SFTP, or API-based input, depending on the workflow setup.
Reconciliation workflow in Cointab
A Magicpin reconciliation in Cointab follows a repeatable workflow that finance teams can reuse for each period.
- Upload the required files for Side A and Side B.
- Map important fields such as order date, amount, reference ID, and outlet or store code.
- Add supporting data if the workflow needs enrichment or lookup logic.
- Create derived columns where needed, such as cleaned order IDs, normalized references, or calculated charge values.
- Run reconciliation manually or on a schedule.
- Review the report as Cointab processes the records.
- Explore fully matched, partially matched, unmatched, and skipped records.
- Download the Excel reconciliation report for review, follow-up, or audit support.
If needed, Cointab can also help after the structured rules are applied by analyzing difficult open transactions with AI-assisted review.
What the reconciliation report can show
Once the run is complete, the report helps finance teams separate clean matches from exceptions.
Payment and settlement outcomes
- Fully matched: order and settlement data match according to the configured logic
- Partially matched: the related order is found, but the amount differs
- Unmatched: the record appears on one side but not the other
- Skipped: the record was excluded because of missing data, invalid values, or another rule-based reason
Charge verification outcomes
The same workflow can also be used to review charge components such as:
- commission charges
- discount deductions
- packing charges
- other settlement differences supported by the file structure
This makes it easier to identify whether a charge was correctly applied, overcharged, undercharged, or not verified because of missing information.
Handling exceptions and open items
Not every record can be matched automatically. Magicpin reconciliation often includes exceptions that need review, such as missing references, partial matches, or differences in charge values.
Cointab helps teams by keeping exception handling transparent:
- open items remain visible instead of being hidden in formulas
- partially matched records are separated from fully matched records
- unmatched records are easy to filter and review
- skipped rows are shown so teams know what was excluded and why
When business context is known, users can also manually match transactions that the system and AI could not resolve confidently. This is useful for one-off exceptions or cases where supporting evidence is available outside the standard files.
Reuse, automation, and recurring runs
A major advantage of Cointab is reuse. Once a Magicpin reconciliation is configured, the same setup can be used again for future periods instead of rebuilding the workflow each month.
That is useful for recurring finance processes such as:
- monthly settlement reconciliation
- daily or weekly order-level checks
- month-end review of commissions and deductions
- outlet-level charge verification
Recurring workflows can also be automated with scheduled runs and data input through email, SFTP, or API. After reconciliation is completed, the output can be delivered back to internal systems as needed through email, SFTP, or API.
Why finance teams use this workflow
Magicpin reconciliation is often owned by finance, accounting, or marketplace operations teams because it affects revenue recognition, settlement review, and charge control.
Cointab supports that work by providing:
- a clear Side A / Side B structure
- reusable reconciliation setup for future periods
- structured matching logic for order and charge data
- exception analysis for unmatched and partially matched items
- downloadable Excel reports for review and audit support
- team workspaces with shared history and visibility
For teams that manage multiple outlets or high volumes of settlement data, this approach reduces repetitive spreadsheet work and makes reconciliation easier to standardize.
Working with Magicpin data in a finance process
A good Magicpin reconciliation process should make it easy to see:
- which orders were settled correctly
- which orders are pending payment
- whether commission was applied as expected
- whether discount deductions align with the source data
- whether packing charges were recorded correctly
- which records need follow-up or manual review
Cointab is designed to keep that process structured, reviewable, and reusable across periods.
