Swiggy Orders vs UrbanPiper Orders Reconciliation: A Complete Guide for Finance Teams

Swiggy orders vs UrbanPiper orders reconciliation is the process of comparing order records from Swiggy with order records captured or routed through UrbanPiper.

For restaurants, QSR chains, cloud kitchens, and food service businesses, Swiggy acts as the food delivery marketplace where customers place orders. UrbanPiper acts as an integration or order management layer that receives, routes, and syncs orders between aggregators and restaurant systems.

This reconciliation helps finance and operations teams answer:

• Are all Swiggy orders available in UrbanPiper?
• Are all UrbanPiper Swiggy orders present in Swiggy reports?
• Do order values, discounts, taxes, packaging charges, and net values match?
• Are cancelled, rejected, failed, or refunded orders handled correctly?
• Are outlet codes, order IDs, and order statuses mapped properly?
• Which orders are missing, mismatched, duplicated, or pending review?

For finance teams, this reconciliation supports sales validation, outlet-level reporting, cancellation tracking, tax review, settlement preparation, and audit readiness.

What Is Swiggy vs UrbanPiper Order Reconciliation?

Swiggy vs UrbanPiper order reconciliation compares two order-side reports for the same food delivery transactions.

Side A: Swiggy Order Report
This represents the marketplace-side order view. It may include Swiggy order ID, outlet, order date, customer order value, discount, tax, packaging charges, cancellation status, refund status, and final order status.

Side B: UrbanPiper Order Report
This represents the integration or order management view. It may include UrbanPiper order ID, aggregator order ID, outlet code, order status, item value, discount, tax, charges, cancellation status, and synced order details.

The goal is to confirm whether every Swiggy order is correctly captured in UrbanPiper and whether UrbanPiper has recorded the same order details, value, status, and outlet mapping.

Matching is usually based on:

• Swiggy order ID
• UrbanPiper order ID
• Aggregator order ID
• Outlet code
• Store name
• Order date
• Order time
• Gross order value
• Discount amount
• Tax amount
• Packaging charge
• Net order value
• Order status
• Cancellation status

If the order reference and amount match across both reports, the transaction can usually be treated as matched. If the order reference matches but the amount differs, it becomes an amount mismatch. If an order appears only on one side, it becomes an exception.

Why This Reconciliation Matters

Food delivery orders pass through multiple systems before they become final sales or settlement records.

A customer places an order on Swiggy. The order is routed through UrbanPiper to the restaurant outlet or POS. The order may be accepted, rejected, cancelled, modified, refunded, or fulfilled. If Swiggy and UrbanPiper do not match, finance and operations teams may not know whether order reporting is complete and accurate.

Without reconciliation, teams may face issues such as:

• Swiggy orders missing in UrbanPiper
• UrbanPiper orders missing in Swiggy
• Order value mismatches
• Discount mismatches
• Tax differences
• Packaging charge differences
• Cancelled orders treated as completed
• Rejected orders included in sales
• Outlet mapping issues
• Duplicate order records
• Month-end sales reporting gaps

A structured reconciliation process helps teams validate order completeness before relying on the data for sales, settlement, tax, and operational reporting.

Reports Involved

Side A: Swiggy Order Report

The Swiggy order report represents the marketplace-side view of orders.

Common fields may include:

• Swiggy order ID
• Restaurant or outlet name
• Outlet code
• Order date and time
• Order status
• Item value
• Discount amount
• Tax amount
• Packaging charge
• Delivery charge
• Gross order value
• Net order value
• Cancellation status
• Refund status

This report shows what Swiggy has recorded as customer order activity.

Side B: UrbanPiper Order Report

The UrbanPiper report represents the order integration view.

Common fields may include:

• UrbanPiper order ID
• Aggregator order ID
• Swiggy order reference
• Outlet name or outlet code
• Order received time
• Order accepted time
• Order status
• Item value
• Discount amount
• Tax amount
• Packaging charge
• Net order value
• Cancellation or rejection status
• Sync status

This report shows what UrbanPiper has captured, routed, accepted, rejected, or synced.

How Matching Typically Works

Swiggy vs UrbanPiper reconciliation usually works by comparing order references, outlet details, order status, and value fields.

A typical process looks like this:

1. The Swiggy order report is uploaded.
2. The UrbanPiper order report is uploaded.
3. Swiggy order IDs and aggregator order IDs are matched with UrbanPiper references.
4. Outlet names or outlet codes are validated.
5. Gross order value, discounts, taxes, packaging charges, and net order values are compared.
6. Cancelled, rejected, failed, and refunded orders are reviewed separately.
7. Records are categorized as matched, partially matched, unmatched, or skipped.
8. Exceptions are reviewed by finance or operations teams.

For example:

• Swiggy shows an order of ₹750.
• UrbanPiper shows the same Swiggy order ID with order value of ₹750.
• The order is treated as matched.

Another example:

• Swiggy shows an order of ₹750.
• UrbanPiper shows the same order with value of ₹720.
• The ₹30 difference may be due to discount, packaging charge, tax treatment, item modification, rounding, or wrong amount field selection.
• This becomes an amount mismatch.

If a Swiggy order exists but no UrbanPiper record is found, it becomes a Swiggy-only exception.

If an UrbanPiper order exists but no Swiggy record is found, it becomes an UrbanPiper-only exception.

Common Exceptions in Swiggy vs UrbanPiper Reconciliation

1. Swiggy Order Missing in UrbanPiper

This happens when Swiggy shows an order, but no matching UrbanPiper order is found.

Possible reasons include:

• UrbanPiper sync failed
• Order was not routed correctly
• Aggregator order ID was not captured
• UrbanPiper report period is incomplete
• Outlet mapping is incorrect
• Order was cancelled before sync

This exception should be reviewed because every valid Swiggy order should usually have a corresponding UrbanPiper order record.

2. UrbanPiper Order Missing in Swiggy

This happens when UrbanPiper shows a Swiggy order, but no matching Swiggy record is found.

Possible reasons include:

• Swiggy report is incomplete
• Order reference was stored differently
• Order belongs to another period
• UrbanPiper record is duplicated
• Manual mapping is required
• Wrong Swiggy report was uploaded

This exception should be reviewed so every UrbanPiper order has marketplace-side support.

3. Amount Mismatch

Amount mismatches occur when the order reference matches, but Swiggy and UrbanPiper values do not match.

Possible causes include:

• Item value difference
• Discount difference
• Tax calculation difference
• Packaging charge difference
• Delivery charge treatment difference
• Item modification after order placement
• Rounding difference
• Wrong amount field selected

Amount mismatches affect sales validation, outlet reporting, and downstream settlement reconciliation.

4. Discount Difference

Discounts may be represented differently in Swiggy and UrbanPiper.

Common issues include:

• Platform discount shown in Swiggy but not in UrbanPiper
• Restaurant discount captured differently
• Coupon amount treated differently
• Discount included in gross value on one side but netted off on the other
• Outlet-level promotion not mapped correctly

Discount differences should be reviewed separately because they affect net sales and margin reporting.

5. Tax Difference

Tax differences occur when tax values do not match between Swiggy and UrbanPiper.

Possible reasons include:

• Different tax calculation logic
• Tax calculated before or after discount
• Item-level tax mapping issue
• Rounding difference
• Incorrect GST rate mapping
• Wrong tax field selected

Tax mismatches are important because they can affect GST reporting and audit support.

6. Cancelled or Rejected Order Difference

Orders may be cancelled, rejected, failed, or voided after being created.

Common issues include:

• Order cancelled in Swiggy but shown as accepted in UrbanPiper
• Order rejected by outlet but still present as active in one report
• Cancelled order included in sales value
• Refund status not updated consistently
• Cancellation timestamp differs between systems

These exceptions should be separated from completed sales.

7. Outlet Mapping Difference

Outlet-level reconciliation can fail if outlet names or codes differ across systems.

Possible issues include:

• Swiggy outlet name differs from UrbanPiper outlet name
• Outlet code missing in one report
• Same outlet has multiple aliases
• Order mapped to the wrong outlet
• Reports contain combined data for multiple outlets

Outlet mapping differences can distort store-wise sales and operational reporting.

8. Duplicate Orders

Duplicates may appear in either Swiggy or UrbanPiper reports.

Examples include:

• Same Swiggy order repeated
• Same UrbanPiper order repeated
• Same aggregator order ID repeated
• Duplicate export from one system
• Duplicate file upload
• One order mapped to multiple records

Duplicates can overstate order counts and sales values if not identified.

Why Manual Excel Reconciliation Is Difficult

Many teams reconcile Swiggy and UrbanPiper orders manually in Excel.

The usual process includes:

1. Exporting Swiggy order data.
2. Exporting UrbanPiper order data.
3. Cleaning order IDs, outlet names, outlet codes, and dates.
4. Matching records using lookup formulas.
5. Comparing gross value, discount, tax, packaging charge, and net amount.
6. Reviewing cancelled, rejected, refunded, and unmatched orders.
7. Preparing exception reports.

This becomes difficult as order volumes increase across multiple outlets.

Common Excel challenges include:

• Different order ID formats
• Missing aggregator order references
• Outlet naming differences
• Cancelled orders mixed with completed orders
• Tax and discount logic differences
• Duplicate entries missed
• Broken lookup formulas
• Manual copy-paste errors
• No clear audit trail

A structured reconciliation workflow reduces these risks.

What a Good Swiggy vs UrbanPiper Reconciliation Process Should Include

A reliable process should include:

• Complete Swiggy order report
• Complete UrbanPiper order report
• Order ID and aggregator reference matching
• Outlet-level mapping
• Gross value comparison
• Discount comparison
• Tax comparison
• Packaging charge comparison
• Net sales comparison
• Cancellation and rejection visibility
• Swiggy-only exception reporting
• UrbanPiper-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which orders matched, which orders are missing, and which value differences require review.

How Cointab Helps

Cointab can help finance teams automate Swiggy vs UrbanPiper order reconciliation by comparing Swiggy order data with UrbanPiper order data in a structured workflow.

Finance teams can map order references, aggregator order IDs, outlet codes, amount fields, discount fields, tax fields, charges, and date fields once and reuse the setup for future periods.

Cointab helps teams:

• Upload Swiggy and UrbanPiper reports
• Match Swiggy orders with UrbanPiper orders
• Compare gross order value, discounts, taxes, packaging charges, and net values
• Identify fully matched orders
• Highlight amount mismatches
• Show Swiggy-only and UrbanPiper-only exceptions
• Review cancelled, rejected, refunded, or skipped records
• Detect duplicate orders
• Download audit-ready Excel reports

This reduces manual Excel work and gives finance and operations teams better visibility into order-level differences.

Business Value

Swiggy vs UrbanPiper order reconciliation helps finance teams:

• Validate online food order completeness
• Ensure UrbanPiper order capture accuracy
• Identify missing or duplicate orders
• Track cancelled and rejected order differences
• Improve outlet-level sales accuracy
• Support GST and tax review
• Prepare cleaner data for settlement reconciliation
• Reduce manual reconciliation work
• Speed up month-end close
• Strengthen audit documentation

It also helps operations teams identify sync issues between Swiggy and UrbanPiper faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile Swiggy and UrbanPiper reports regularly
• Use Swiggy order ID, UrbanPiper order ID, aggregator order ID, and outlet code wherever available
• Separate completed, cancelled, rejected, failed, and refunded orders before review
• Compare gross sales, discounts, taxes, packaging charges, and net values separately
• Maintain a clean outlet mapping master
• Track timing differences separately from true mismatches
• Check duplicate order IDs and aggregator references
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

Swiggy orders vs UrbanPiper orders reconciliation helps finance teams confirm whether marketplace orders, integration records, outlet mapping, order values, discounts, taxes, cancellations, refunds, and statuses are properly aligned.

Because this reconciliation depends on order IDs, aggregator references, outlet codes, value fields, discount logic, tax values, cancellation status, and timing differences, manual Excel reconciliation can become slow and error-prone as order volumes grow.

With Cointab, finance teams can automate Swiggy vs UrbanPiper order reconciliation, reduce manual Excel work, identify missing or mismatched orders faster, and generate audit-ready reports for review.

Start your 14-day free trial with Cointab and automate Swiggy vs UrbanPiper order reconciliation without relying on manual Excel work. No credit card required.

Visit: https://www.cointab.net/