Swiggy, Urbanpiper and POS Reconciliation

Restaurants and food delivery businesses often need to reconcile three connected data sets: Swiggy order data, Urbanpiper routing data, and POS records. When these reports are reviewed manually in Excel, it becomes difficult to track missing orders, unmatched settlements, platform deductions, and amount differences across systems.

Cointab helps finance teams compare Side A and Side B records in a structured reconciliation workflow. Users can upload reports, map fields once, run reconciliation, review matched and unmatched transactions, and download audit-ready Excel reports for review and follow-up.

What this reconciliation helps you check

Swiggy, Urbanpiper, and POS reconciliation is useful when restaurants want to confirm that:

every Swiggy order appears in Urbanpiper and the POS system
every order captured in Urbanpiper originated from the expected Swiggy flow
amounts, discounts, GST, item details, and quantities are aligned across reports
settlement and payout entries match the underlying order data
deductions such as commission, TCS, TDS, coupons, packing charges, and cancellation charges are consistent with the expected business rules
open items are visible quickly instead of being buried in spreadsheets

This is especially important for finance teams that manage high-volume restaurant operations or multiple outlets and need a repeatable process for period-end review.

Typical reconciliation flow

Cointab supports both popular and custom reconciliation setups. For this use case, a team can create a workflow for:

Swiggy orders vs Urbanpiper records
Urbanpiper records vs POS data
POS data vs Swiggy order and settlement data
Bank settlement vs expected payout entries

The workflow follows the same structured process each time:

upload CSV, XLS, or XLSX files
map date, amount, and identifier fields such as order ID, transaction ID, settlement ID, or reference number
optionally add supporting data such as store mappings, product masters, or fee lookup files
create derived columns when a value needs to be cleaned, combined, or calculated
run reconciliation manually or on a schedule
review matched, partially matched, unmatched, and skipped records
export the report for internal review or partner follow-up

Swiggy with Urbanpiper

When Swiggy is connected to a restaurant through Urbanpiper, finance teams often need to verify whether the order flow is complete and consistent across both systems.

Cointab can help users compare:

whether Swiggy orders are present in Urbanpiper
whether Urbanpiper entries originated from Swiggy
whether amounts, discounts, GST, and reference details align
whether any order was missed, duplicated, or modified during routing

This makes it easier to identify mismatches before they flow into the POS or settlement process.

Urbanpiper with POS

Urbanpiper-to-POS reconciliation helps confirm that orders routed from the aggregator layer are recorded correctly in the billing or point-of-sale system.

Teams commonly use this reconciliation to check:

whether all Urbanpiper orders appear in the POS
whether the POS contains orders that were not routed through Urbanpiper
whether item counts, quantities, taxes, and discounts are consistent
whether the order reference can be traced across both systems

Where needed, supporting data can be uploaded to enrich the primary reports before reconciliation.

POS with Swiggy

Some teams prefer to reconcile the POS data directly with Swiggy reports and settlements. This is useful when the finance team wants to verify that the amount billed or received matches the order record stored in the restaurant system.

Cointab can help identify:

orders that appear in POS but are missing from Swiggy settlement data
settlement entries that do not match the original order amount
pending or open items that need review
differences that may be caused by coupons, deductions, refunds, or cancellation adjustments

Verifying Swiggy charges

Beyond order matching, restaurants often need to validate the charges applied to each order. Cointab can help users review charge-level differences and exceptions across reports.

Common charge checks include:

Commission charges

Verify whether commission has been applied as expected across stores and orders, and identify orders where the deduction looks inconsistent with the configured rate or agreement logic.

TCS and TDS

Review tax-related deductions to ensure they are reflected correctly in the reconciliation output and do not remain unexplained in open items.

Coupon and discount adjustments

Check how customer discounts, merchant-funded offers, and coupon deductions appear across Swiggy and internal reports.

Packing charges

Confirm whether packing charges collected from customers or adjusted in settlement data match the expected amount.

Cancellation charges

Track cancelled or adjusted orders and review whether the corresponding cancellation charge, payout impact, or settlement adjustment is reflected properly.

Bank settlement reconciliation

For many restaurant teams, the final control point is settlement visibility in the bank.

Cointab can also be used to reconcile settlement data against bank statements and payout records. This helps finance teams review whether:

settlement amounts were received correctly
all expected settlements have been received
reference numbers such as UTRs are traceable
the final bank credit matches the settlement report
open settlement items need follow-up

This closes the loop between order creation, platform reporting, and actual cash receipt.

Why finance teams use Cointab for this workflow

Cointab is designed for recurring finance operations, not one-time spreadsheet cleanup. For restaurant reconciliation, that means teams can:

reuse the same setup for future periods
run reconciliation on monthly, weekly, or custom settlement cycles
separate fully matched, partially matched, unmatched, and skipped records clearly
manually match only the exceptions that need human review
refresh the report if a file arrives late
keep the reconciliation history available on the dashboard for future reference

This reduces repeated configuration work and makes the process easier to audit.

How Cointab supports exception handling

When records do not match cleanly, Cointab keeps the exception visible rather than hiding it.

Users can review:

fully matched transactions
partially matched transactions where identifiers match but amounts differ
unmatched transactions present on only one side
skipped rows that were excluded because of missing or invalid data

For difficult open items, AI can help analyze why a transaction may be unmatched and suggest possible reasons or next actions. The system remains conservative, so weak matches are not forced into the report.

Reusable reconciliation for restaurant operations

Once a Swiggy, Urbanpiper, and POS workflow is configured, the same setup can be reused for future periods. Teams do not need to rebuild the logic every time they close a month or review a new settlement cycle.

This is useful for:

monthly store-wise reviews
outlet-level audit preparation
recurring settlement tracking
charge validation across multiple periods
finance control for multi-location restaurant businesses

Reporting and audit readiness

After the run is complete, users can download an Excel reconciliation report containing matched, partially matched, unmatched, and skipped records. The report gives finance teams a clean record of what was compared and what still needs attention.

The dashboard also preserves prior runs, so teams can return to a reconciliation later, review prior output, and track changes across periods without relying on scattered spreadsheets.

When this use case is most useful

This reconciliation is a strong fit when a restaurant or food business needs to compare multiple records that do not always share the same format or timing. It is especially useful when:

Swiggy order data is routed through Urbanpiper before reaching POS
settlement timing does not align with order timing
deductions and charges need separate validation
multiple stores or outlets must be reviewed together
finance teams want a repeatable and audit-friendly process instead of manual Excel checks