Magicpin, Urbanpiper and POS Reconciliation

Cointab helps restaurant and QSR finance teams reconcile Magicpin, Urbanpiper, and POS data in one structured workflow. Compare order records, charges, and settlements across systems, then review matched, partially matched, unmatched, and skipped transactions in an audit-ready report.

Why this reconciliation matters

When Magicpin is connected through Urbanpiper and a POS system is also part of the workflow, the same order can appear in multiple reports with small but important differences. Finance teams often need to verify whether every order was captured correctly, whether the amounts tally, and whether charges such as commission, packing fees, and discounts were applied as expected.

Manual checks in Excel can work for a small volume of orders, but they become difficult when the same reconciliation must be repeated every day or every settlement cycle. Cointab gives teams a reusable reconciliation setup so the same checks can be run again with fresh files and the same mapping rules.

Common reconciliation scenarios

Magicpin vs Urbanpiper

Use this reconciliation when you want to compare Magicpin order data with the Urbanpiper report that feeds your restaurant operations.

Typical checks include:

• Orders present in Magicpin but missing in Urbanpiper
• Orders present in Urbanpiper but not found in Magicpin
• Differences in order amount, GST, discounts, or other charge fields
• Missing or duplicated references that need follow-up

Urbanpiper vs POS

Use this reconciliation to compare Urbanpiper orders against your POS records.

Typical checks include:

• Urbanpiper orders not captured by POS
• POS entries that do not map back to Urbanpiper orders
• Amount mismatches across order, tax, and discount fields
• Missing order references or inconsistent identifiers

POS vs Magicpin settlement checks

Use this reconciliation when the finance team needs to verify whether Magicpin payouts and settlements match the POS order base.

Typical checks include:

• Whether Magicpin has settled all eligible orders recorded in POS
• Which orders are still open or pending
• Whether the amount received matches the expected payment amount
• Which settlement entries need manual review

What Cointab checks in the workflow

Cointab lets you define Side A and Side B for each reconciliation.

• Side A can be your internal order or POS records
• Side B can be Magicpin, Urbanpiper, or settlement records received from the platform

The platform can then compare key fields such as:

• Order ID
• Settlement ID
• Transaction reference
• Amount
• GST or tax amount
• Discount amount
• Commission amount
• Packing charge
• UTR or settlement reference

The reconciliation engine supports structured matching for:

• One-to-one matches
• One-to-many or many-to-one cases
• Partial matches where the reference matches but the amount differs
• Netting scenarios where multiple entries need to be compared together
• Contra or offsetting entries when applicable

Charge verification for restaurant finance teams

Beyond order matching, this use case is often about understanding the charges that affect net settlement.

Commission charge verification

Cointab can help finance teams check whether commission has been applied correctly at a store or order level. This is useful when commission rates vary across locations or when charge treatment changes over time.

Packing charge verification

If packing charges are collected or passed through in the order flow, Cointab can help identify orders where the packing charge is missing, undercharged, or does not match the expected value.

Discount and coupon verification

Discounts and coupons are another common source of reconciliation differences. Cointab helps teams review whether:

• the discount amount matches the order record,
• a customer-facing coupon was applied correctly,
• a non-merchant-supported coupon was debited to the merchant,
• or an extra discount was applied unexpectedly.

Bank settlement and UTR matching

Restaurant and QSR finance teams often need to connect order-level data with settlement-level data in the bank. Cointab can support this by reconciling settlement PDFs or payout reports against internal order records.

This helps teams review:

• UTR-level settlement details
• Settlement amounts received in the bank
• Differences between order totals and net payout values
• Open items that still need to be settled or investigated

How the reconciliation workflow works

A typical setup follows a simple, repeatable process:

1. Upload the required files for Side A and Side B
2. Map the key fields such as date, amount, and reference columns
3. Add supporting files if extra lookup or enrichment is needed
4. Create derived columns when a formula is needed to clean or calculate values
5. Run the reconciliation manually or on a schedule
6. Review the matching results and exception buckets
7. Download the Excel report for review, audit, or partner follow-up

If a file is missed, it can be added later and the report can be refreshed under the same reconciliation.

Supporting data and derived columns

Restaurant reconciliation often requires more than a simple two-file comparison. Cointab supports optional supporting data to enrich or prepare the primary reports before matching.

Examples include:

• Store mapping files
• Product master files
• Fee or commission rate files
• Return or refund data
• Order metadata files
• GST or tax mapping data

Teams can also create derived columns for calculations such as:

• Clean order IDs
• Normalized references
• Net amounts after fee treatment
• Amounts excluding tax
• Delivered payment amounts

AI can help generate Excel-style formulas for these derived columns when the business logic is clear but the formula is time-consuming to write manually.

Review matched, partially matched, unmatched, and skipped records

The reconciliation report is designed for finance review, not just system output.

• Fully matched records show where identifiers and amounts align
• Partially matched records show where the reference matches but the amount differs
• Unmatched records show items present on one side but not found on the other
• Skipped records show rows that were not included because of missing data, invalid values, or file issues

This helps finance teams focus on exceptions instead of checking every row manually.

Manual review and exception handling

Not every issue can be resolved by rules alone. When needed, teams can manually match transactions that are clearly related but could not be matched automatically.

This is useful when:

• partner references are incomplete,
• records are split across multiple rows,
• data arrives late,
• or the business context is known by the finance team but not obvious from the file alone.

AI can also help analyze open items and suggest possible reasons for differences, such as missing files, refunds, fees, deductions, or settlement timing issues.

Built for recurring reconciliation

This use case is rarely a one-time task. Restaurant finance teams usually need the same checks every day, week, or month.

Cointab is built so the setup can be reused for future periods. Once the fields and matching logic are configured, teams can run the same reconciliation again for the next period without rebuilding the workflow.

That makes it easier to keep reconciliation consistent across stores, outlets, periods, and settlement cycles.

Audit-ready reporting for finance teams

Each run produces a report that is suitable for internal review and follow-up. Teams can use the output to:

• review open exceptions,
• track charge differences,
• verify settlement activity,
• and keep a clear record of what matched and what did not.

For finance operations, this creates a more controlled process than working from disconnected spreadsheets and ad hoc checks.