If your company supplies products to Swiggy through Scootsy Logistics Private Limited, your finance team may need to periodically reconcile the customer balance shown in Tally with the transaction statement or ledger shared by Swiggy.

Your Tally account tells you what your company has:

• Invoiced
• Received
• Credited
• Adjusted
• Left outstanding

Swiggy's records provide another view of the same commercial relationship.

Their file may show much more than simply debit and credit entries. It can contain:

• Invoice numbers
• PO numbers
• GRN numbers
• Payment references
• Payment status
• Paid amount
• Outstanding amount
• Due date
• Withholding tax
• Vendor credit numbers
• Internal document numbers

The reconciliation requirement is therefore:

Your Tally Customer Ledger ↔ Swiggy / Scootsy Invoice and Payment Records

Cointab can compare both datasets and help you understand:

• Which invoices agree
• Which invoice amounts differ
• Which invoices appear only in your books
• Which transactions appear only in Swiggy's records
• Which invoices Swiggy shows as paid
• Which invoices remain outstanding
• Whether deductions or withholding amounts explain payment differences
• Which transactions require manual review

The reconciliation can then be downloaded in Excel and repeated whenever updated records are available.

---

Why reconcile your Swiggy customer account?

If you supply Swiggy, your Tally may show a receivable balance against Scootsy Logistics Private Limited.

That balance can contain many individual transactions.

For example:

• New invoices
• Older unpaid invoices
• Partially paid invoices
• Customer payments
• Credit notes
• Withholding deductions
• Commercial adjustments
• Timing differences

The total outstanding in your books may not exactly agree with the amount Swiggy shows as payable.

The important question is not simply:

"Why are the closing balances different?"

The more useful questions are:

• Which invoice is missing?
• Which invoice has been paid?
• Which invoice is only partially paid?
• Is there a withholding deduction?
• Has Swiggy recorded a vendor credit?
• Is an invoice associated with a PO and GRN?
• Has a payment been made but not allocated in Tally?
• Is the invoice still outstanding according to Swiggy?

A transaction-level reconciliation answers these questions.

---

Your Tally customer ledger

A Tally customer ledger used for this reconciliation may contain:

The file is relatively simple.

Useful information may be contained in:

• Vch No.
• Particulars
• Vch Type

Depending on your accounting process, invoice references or payment information may appear inside the transaction description rather than in a dedicated field.

---

What does the Swiggy / Scootsy file contain?

The Swiggy-side file can be significantly richer.

A typical structure may include:

This means the reconciliation can go beyond simply matching invoices.

It can also help explain what happened after the invoice entered Swiggy's system.

---

Swiggy reconciliation is an invoice-to-payment reconciliation

A useful way to think about this workflow is:

Invoice → PO / GRN → Customer accounting → Payment → Outstanding balance

Your Tally may mainly show:

• Invoice
• Receipt
• Customer balance

The Swiggy file may provide the intermediate steps.

For example, an invoice could show:

• Invoice Number
• PO Number
• GRN Number
• Payment Status
• Paid Amount
• Outstanding Amount

This makes the customer reconciliation particularly useful for understanding why an invoice remains open.

---

How to reconcile your Tally ledger with Swiggy in Cointab

Start a new reconciliation in Cointab and choose:

Customer Reconciliation

For this workflow:

• Side 1 = Your Tally ledger for Scootsy Logistics Private Limited
• Side 2 = Swiggy / Scootsy transaction file

The process is:

Upload Your Tally → Upload Swiggy File → Configure Fields → Run Reconciliation → Review Exceptions

---

Step 1: Upload your Tally ledger

Upload the relevant Scootsy Logistics customer ledger exported from Tally.

Select the date

Choose:

Date

Select useful identifiers

Depending on your ledger, useful fields can include:

• Vch No.
• Particulars
• Vch Type

These can help identify invoices, receipts, or other accounting transactions.

Configure the amount columns

Map:

• Debit
• Credit

Cointab can now interpret your customer account.

---

Step 2: Upload the Swiggy / Scootsy file

Upload the transaction statement received from Swiggy.

Select the date

A relevant date may be:

Posting Date

Select identifiers

Useful transaction identifiers can include:

• Invoice Number
• Reference Number
• Document Identifier
• Document Number
• Payment reference number
• Vendor Credit Number
• PO Number
• GRN Number
• Payment Number
• Description

The advantage of this file is that several identifiers may help explain the same transaction.

Select the amount

Use the relevant:

Amount

field for transaction comparison.

Additional fields such as:

• Paid Amount
• Outstanding Amount
• Withhold Tax Amount

can provide important context while reviewing the reconciliation.

---

Step 3: Run the Customer Reconciliation

Once both datasets are configured, start the reconciliation.

Cointab identifies transaction references from the selected fields and compares the corresponding financial records.

For invoice reconciliation, the basic logic is:

Fully Matched

The invoice can be identified on both sides and the values agree.

Partially Matched

The invoice is identifiable in both datasets, but the values differ.

Unmatched

A corresponding invoice or transaction cannot be found on the other side.

This immediately reduces a large customer account into a smaller exception population.

---

Fully Matched Swiggy invoices

Suppose your Tally contains:

Invoice: INV-7621

Amount: ₹1,75,000

Swiggy contains:

Invoice Number: INV-7621

Amount: ₹1,75,000

The invoice exists in both systems for the same amount.

Cointab classifies the invoice as:

Fully Matched

No invoice-level discrepancy needs to be investigated.

You can then use Swiggy's additional payment fields to understand whether the invoice is:

• Paid
• Partially paid
• Outstanding

---

Partially Matched invoices

Suppose:

Your Tally

Invoice:

INV-8152

Amount:

₹2,20,000

Swiggy

Invoice Number:

INV-8152

Amount:

₹2,15,000

The invoice number connects the two transactions, but the values differ.

Cointab reports:

Partially Matched

You can now investigate the ₹5,000 difference.

The cause could relate to:

• Different invoice value recorded
• Credit adjustment
• Withholding
• Commercial deduction
• Incorrect posting
• Other transaction difference

---

Invoice present in your Tally but missing from Swiggy

Suppose you have raised:

Invoice: INV-9045

Amount: ₹3,40,000

but no corresponding Invoice Number or reference can be found in the Swiggy file.

Cointab reports:

Present in Your Tally but not in Swiggy

You can investigate whether:

• Invoice has not reached Swiggy's accounting system
• Invoice is pending processing
• Invoice reference was entered differently
• PO or GRN process is incomplete
• Invoice belongs to another accounting period
• Invoice is under review
• Transaction is missing

This creates a specific customer-side action item.

---

Transaction present in Swiggy but missing from your Tally

The opposite situation can also occur.

Swiggy may show:

Vendor Credit Number: VCN-4821

Amount: ₹38,000

but your Tally ledger contains no identifiable corresponding transaction.

Cointab reports:

Present in Swiggy but not in Your Tally

Your finance team can investigate whether:

• A credit note needs to be recorded
• An adjustment is missing
• A receipt was not allocated
• The transaction exists under another reference
• Swiggy's entry needs clarification

This provides an internal reconciliation worklist.

---

Use Invoice Number as the primary commercial reference

The Swiggy file contains a dedicated:

Invoice Number

field.

This can be particularly useful because the internal Swiggy:

• Document Number
• Document Identifier

may not match your Tally voucher number.

For example:

Your Tally

Vch No.:

SI/24-25/1942

Swiggy

Document Number:

5100873491

Invoice Number:

INV-7621

Your own invoice reference may be INV-7621.

The Swiggy internal document number is simply their accounting-system identifier.

The reconciliation should therefore focus on the common commercial reference rather than assuming internal accounting numbers must match.

---

PO Number can help investigate invoice exceptions

The Swiggy file also contains:

PO Number

This can be useful when an invoice does not reconcile cleanly.

For example, suppose your Tally shows an invoice that Swiggy has not yet recognized.

The PO Number can help determine:

• Which purchase order the invoice belongs to
• Whether the commercial order exists
• Whether another invoice reference was used
• Whether the issue is invoice-specific rather than order-specific

For suppliers processing many Swiggy orders, this additional reference can be helpful when several invoices have similar values.

---

GRN Number can explain why an invoice is pending

The file also provides:

GRN Number

or Goods Receipt Note number.

For product suppliers, invoice processing may depend on the customer confirming receipt of goods.

This creates a commercial flow such as:

PO → Supply → GRN → Invoice → Payment

If your invoice exists but the corresponding GRN is missing or incomplete, the invoice may not have progressed normally through the customer's process.

The reconciliation therefore provides more context than simply saying:

Invoice unmatched

You can also review whether a related:

• PO Number
• GRN Number

exists.

---

Reconcile invoices with the purchase and receipt lifecycle

For a supplier to a large customer, an invoice may need to connect with several upstream records.

For example:

Your records

Invoice:

INV-5832

Swiggy records

PO:

PO-784521

GRN:

GRN-346821

Invoice:

INV-5832

Payment Status:

Pending

This tells you that the invoice has made it into the customer's records and is connected with a procurement and receipt process.

The remaining issue may now be payment rather than invoice recognition.

---

Payment Status makes the reconciliation more actionable

One of the most useful fields in the Swiggy file is:

Payment Status

Instead of only determining whether an invoice exists, you can also see its payment state.

For example:

This creates a much more useful accounts receivable view.

A fully matched invoice is not necessarily a closed invoice.

It may simply mean both parties agree that the invoice exists for the same value.

The next question is:

Has it actually been paid?

---

Paid Amount and Outstanding Amount help explain customer receivables

The Swiggy file contains:

• Paid Amount
• Outstanding Amount

These fields provide valuable information when reviewing open customer invoices.

Suppose:

Invoice Amount

₹2,00,000

Paid Amount

₹1,50,000

Outstanding Amount

₹50,000

Instead of treating the transaction simply as "unpaid," the reconciliation shows that the invoice is partially settled.

Your Tally should ultimately reflect the same economic position.

If your books still show:

₹2,00,000

outstanding, you may need to investigate whether the ₹1,50,000 customer receipt has been posted or allocated correctly.

---

Identify payments that may be missing from your Tally

Suppose Swiggy reports:

Payment Number: PAY-782145

Paid Amount: ₹4,75,000

Payment Status: Paid

but your Tally ledger does not contain the corresponding customer receipt.

This is a strong internal exception.

Possible causes include:

• Payment has been received but not recorded
• Receipt has been posted to another customer
• Payment is sitting as an unidentified bank receipt
• Payment was entered using a different reference
• Allocation is pending

The Swiggy payment information gives your finance team a much better starting point for investigation.

---

Payment reference number can help locate receipts

Swiggy provides:

Payment reference number

This can be useful when matching a customer payment against:

• Tally receipt
• Bank transaction
• Collection record

Your Tally narration may contain the same payment reference even if the voucher numbers differ.

For example:

Swiggy

Payment reference:

UTR987654321

Your Tally

Particulars:

Receipt Swiggy UTR987654321

The common payment identifier helps establish the relationship.

---

One payment can settle multiple Swiggy invoices

Large customers commonly make consolidated payments.

Suppose Swiggy has four invoices:

• INV-101 – ₹1,00,000
• INV-102 – ₹1,50,000
• INV-103 – ₹2,00,000
• INV-104 – ₹50,000

Swiggy may make one payment of:

₹5,00,000

Your Tally may therefore contain one receipt while Swiggy's records show several invoices as cleared or paid.

A simple one-invoice-to-one-payment lookup cannot fully explain this relationship.

Customer reconciliation needs to distinguish between:

Invoice matching

and:

Payment settlement

Cointab can support more complex matching relationships where required.

---

Due Date helps separate reconciliation from collections

The Swiggy file also includes:

Due Date

This is useful because not every outstanding invoice represents a reconciliation problem.

Consider two fully matched invoices.

Invoice A

Outstanding:

₹2,00,000

Due Date:

Next month

Invoice B

Outstanding:

₹2,00,000

Due Date:

45 days ago

Both invoices reconcile correctly.

But Invoice B may require immediate collection follow-up.

This distinction is important.

Reconciliation asks:

Do both parties agree on the transaction?

Collections asks:

Has the customer paid it when due?

The Swiggy file provides information relevant to both questions.

---

Outstanding Amount can help prioritize collection follow-up

Once invoices have been reconciled, you can use:

Outstanding Amount

to understand which items still require payment.

For example:

• Fully Matched + Zero Outstanding → financially agreed and settled
• Fully Matched + Outstanding Balance → agreed but unpaid
• Partially Matched + Outstanding Balance → reconciliation and collection issue
• Missing from Swiggy → invoice-recognition issue

This is much more actionable than looking only at the total customer balance in Tally.

---

Withholding tax can explain why payment does not equal invoice value

The Swiggy file includes:

Withhold Tax Amount

This can be important when the amount received is lower than the original invoice amount.

For example:

Invoice

₹1,00,000

Withhold Tax Amount

₹2,000

Cash paid

₹98,000

If the reconciliation compares only:

Invoice ₹1,00,000 ↔ Cash ₹98,000

the transaction appears to have a ₹2,000 difference.

But the Swiggy records may explain the difference through withholding.

This allows your finance team to distinguish between:

• Genuine short payment
• Expected withholding
• Other unexplained deduction

---

Do not treat every lower payment as a mismatch

Customer receipts can differ from invoice values for legitimate reasons.

Possible components include:

• Withholding tax
• Credit adjustment
• Vendor credit
• Other agreed deductions

The reconciliation should therefore provide enough transaction detail for finance users to explain the difference rather than automatically treating every lower receipt as an accounting error.

---

Vendor Credit Number can identify customer-side adjustments

The Swiggy file includes:

Vendor Credit Number

This can help identify credits or adjustments that affect your receivable balance.

Suppose Swiggy records:

Vendor Credit Number: VCN-7845

Amount: ₹25,000

but the corresponding credit note does not appear in your Tally.

Your receivable balance may therefore be ₹25,000 higher than the amount Swiggy considers payable.

Cointab can surface the transaction as an exception for your finance team to investigate.

---

Credit adjustments can be as important as invoices

When reconciling a large customer, focusing only on invoices can produce an incomplete result.

Your account may also contain:

• Credit notes
• Debit notes
• Returns
• Commercial claims
• Price adjustments
• Other deductions

These transactions directly affect the amount receivable.

The Swiggy file's Vendor Credit Number provides an additional reference that can help explain such differences.

---

Document Type can tell you what kind of transaction you are reviewing

The Swiggy dataset also contains:

Document Type

This can be useful while investigating unmatched records.

A transaction that appears in Swiggy but not in your Tally may not necessarily be another invoice.

It could represent a different accounting document.

Knowing the document type can help determine whether you should search for:

• Invoice
• Payment
• Credit
• Adjustment
• Other transaction

This reduces unnecessary investigation.

---

Different accounting document numbers are normal

Your Tally voucher number and Swiggy's internal Document Number will often be different.

For example:

Your Tally

Vch No.:

SI/2094

Swiggy

Document Number:

5100948752

Document Identifier:

DI-78241

Invoice Number:

INV-9021

The useful common business reference is likely:

INV-9021

not either company's internal accounting document number.

Cointab can use several configured identifiers rather than requiring one common document-number field.

---

AI-assisted identifier extraction can help with Tally Particulars

Your Tally may contain important transaction information inside:

Particulars

For example:

Swiggy Invoice INV-9021 PO 78452

The Swiggy file may separately contain:

Invoice Number: INV-9021

PO Number: 78452

AI-assisted identifier extraction can help identify these useful references from Tally descriptions and use them during reconciliation.

This reduces the need to manually split or clean Tally narration before matching.

---

Manual Match for transactions you recognize

Some transactions may still use completely different references.

For example:

Your Tally

Vch No.:

CN/482

Amount:

₹32,500

Swiggy

Vendor Credit Number:

VCN-81742

Amount:

₹32,500

Your finance team knows that both transactions represent the same credit adjustment.

If the automatic reconciliation cannot establish the relationship confidently, use:

Manual Match

You can:

1. Select the transaction from your Tally.
2. Select the corresponding Swiggy record.
3. Compare the details.
4. Confirm the match.

Cointab then records the transaction as manually reconciled.

---

Manual Match is useful for old or differently referenced transactions

Large customer accounts often accumulate historical transactions where reference quality is inconsistent.

Examples include:

• Old credit notes
• Manually posted receipts
• Rebooked invoices
• Incorrect narrations
• Legacy voucher numbers
• Adjustments

Your finance team may know the correct relationship from supporting documents.

Manual Match allows these genuine relationships to be completed without altering either source file.

---

A fully matched invoice can still be outstanding

This is an important distinction in this reconciliation.

Suppose:

Your Tally

Invoice:

INV-4421

Amount:

₹3,00,000

Swiggy

Invoice:

INV-4421

Amount:

₹3,00,000

Payment Status:

Pending

Outstanding Amount:

₹3,00,000

The invoice is:

Fully Matched

because both parties agree that the invoice exists for ₹3,00,000.

But it is still:

Outstanding

because Swiggy has not yet paid it.

This means reconciliation status and payment status answer two different questions.

---

Reconciliation status vs payment status

For finance teams, it can be useful to think of every invoice across two dimensions.

Reconciliation status

Does the invoice agree between your books and Swiggy?

Possible outcomes:

• Fully Matched
• Partially Matched
• Unmatched

Payment status

Has the agreed invoice been settled?

Possible outcomes may include:

• Paid
• Partially Paid
• Outstanding
• Other customer-defined status

This helps separate accounting differences from normal accounts receivable.

---

Example: invoice exists in both systems and is fully paid

Your Tally:

INV-6214
₹1,50,000

Swiggy:

Invoice Number: INV-6214
Amount: ₹1,50,000
Paid Amount: ₹1,50,000
Outstanding Amount: ₹0
Payment Status: Paid

The invoice agrees and is settled.

The finance team should be able to identify the corresponding receipt in its own books.

If the invoice still appears outstanding in Tally, the payment allocation requires investigation.

---

Example: invoice agrees but is only partially paid

Your Tally:

Invoice: INV-7362
Amount: ₹2,40,000

Swiggy:

Invoice Number: INV-7362
Amount: ₹2,40,000
Paid Amount: ₹1,80,000
Outstanding Amount: ₹60,000

The invoice itself reconciles completely.

But ₹60,000 remains receivable.

This is primarily a collections item rather than an invoice-recognition difference.

---

Example: withholding explains a payment difference

Suppose:

Invoice amount

₹5,00,000

Swiggy Withhold Tax Amount

₹10,000

Paid Amount

₹4,90,000

If your finance team sees only the ₹4,90,000 bank receipt, it may initially appear that Swiggy has short-paid ₹10,000.

The withholding field provides an explanation for the difference.

Your team can then verify whether the corresponding withholding treatment has been recorded correctly in your books.

---

Example: invoice is in Tally but Swiggy has no record

Your Tally contains:

Invoice: INV-9845

Amount: ₹1,95,000

No corresponding Swiggy Invoice Number or reference can be identified.

Cointab reports:

Present in Your Tally but not in Swiggy

You can use supporting information such as:

• PO Number
• Delivery information
• Invoice copy
• GRN status

when following up with the customer.

---

Example: Swiggy records a vendor credit missing from your books

Swiggy contains:

Vendor Credit Number: VCN-6524

Amount: ₹45,000

Your Tally contains no corresponding transaction.

Cointab reports the item as an exception.

Your finance team can investigate whether:

• You issued a credit note
• Customer has taken an unauthorized deduction
• Credit was booked under another reference
• Entry is still pending internally

This prevents the credit from remaining hidden inside the overall customer balance difference.

---

Example: payment exists in Swiggy but is not allocated in Tally

Swiggy reports:

Payment Number: PAY-452187

Payment reference number: UTR123456789

Paid Amount: ₹7,50,000

Your Tally customer ledger does not show a clear corresponding receipt.

You can search:

• Bank records
• Unallocated receipts
• Other customer ledgers
• Tally narration

using the Swiggy payment reference.

Once the receipt is correctly allocated, the updated Tally ledger can be uploaded and reconciled again.

---

Use the reconciliation to create two worklists

The final output can naturally be split into two categories of action.

Customer-side follow-up

Transactions in your Tally but not found in Swiggy may require you to ask:

• Has the invoice been booked?
• Is the PO correct?
• Has the GRN been completed?
• Is the invoice under review?
• Was another reference used?

Internal finance follow-up

Transactions in Swiggy but missing from your Tally may require you to ask:

• Have we recorded the receipt?
• Is withholding accounted for?
• Is the vendor credit valid?
• Did we miss a credit note?
• Is the receipt allocated to the correct customer?

This makes the reconciliation directly actionable.

---

Download the complete Swiggy reconciliation in Excel

Once you have reviewed the results, download the complete reconciliation working from Cointab.

The Excel output can contain:

• Fully Matched transactions
• Partially Matched transactions
• Unmatched transactions
• Manual Matches
• Source transaction details

You can retain fields from Swiggy such as:

• Invoice Number
• PO Number
• GRN Number
• Payment Status
• Paid Amount
• Outstanding Amount
• Due Date
• Withhold Tax Amount
• Payment reference number

These provide valuable context during accounts receivable review.

---

Use the Excel working for customer follow-up

Instead of sending a generic message saying:

"Please confirm our outstanding balance."

you can work from specific exceptions.

For example:

• Invoice INV-8421 is not present in your statement.
• Invoice INV-7642 shows a different amount.
• Invoice INV-9421 shows Paid but the receipt is not reflected in our ledger.
• Vendor Credit VCN-4521 does not exist in our books.

This makes customer reconciliation discussions much more precise.

---

Upload corrected records and reconcile again

Once differences have been investigated:

• Your Tally may be corrected
• Receipts may be allocated
• Credit notes may be booked
• Swiggy may update an invoice
• Customer-side records may be corrected

Upload the revised files again.

Cointab reruns the reconciliation using the latest data.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as the underlying accounting differences are resolved.

---

Repeat the Swiggy reconciliation every month

If you supply Swiggy regularly, the account continuously changes.

Each month can contain:

• New invoices
• New GRNs
• New payments
• Withholding entries
• Vendor credits
• Previously outstanding invoices
• Previously unresolved reconciliation differences

The same reconciliation can therefore be reused each month.

A typical workflow becomes:

1. Export your latest Scootsy Logistics ledger from Tally.
2. Obtain the latest Swiggy / Scootsy transaction file.
3. Upload your Tally ledger to Cointab.
4. Configure date, identifiers, debit and credit.
5. Upload the Swiggy file.
6. Configure Invoice Number and other reference fields.
7. Run Customer Reconciliation.
8. Review Fully Matched invoices.
9. Investigate Partially Matched invoices.
10. Review invoices missing from Swiggy.
11. Review Swiggy transactions missing from Tally.
12. Check Payment Status and Outstanding Amount.
13. Investigate withholding and vendor credits.
14. Complete Manual Matches where required.
15. Download the reconciliation working.
16. Correct internal entries.
17. Follow up with Swiggy on customer-side exceptions.
18. Upload revised files and rerun where required.

---

Older outstanding invoices can reconcile later

Timing differences are normal.

For example:

July

You raise an invoice.

The invoice exists in Tally but Swiggy has not yet completed its internal posting.

The transaction remains unmatched.

August

The invoice appears in Swiggy's latest file together with:

• PO Number
• GRN Number
• Payment Status

Cointab can now reconcile the previously open invoice with the new customer-side record.

This allows unresolved transactions to continue across periods until the customer account is fully aligned.

---

Why this reconciliation is useful for brands selling through quick commerce and modern trade

Brands selling through their own website often reconcile:

Orders → Payment Gateway → Bank

Brands selling through marketplaces may reconcile:

Orders → Marketplace Settlement → Bank

But when selling directly to a large institutional customer such as Swiggy, the finance process is different.

The relationship is closer to:

PO → Supply → GRN → Invoice → Customer Accounting → Payment

The resulting reconciliation is therefore not simply a payment-gateway settlement exercise.

It is a full customer accounts receivable reconciliation.

---

How Cointab helps with Tally vs Swiggy reconciliation

Cointab's Customer Reconciliation workflow can help you:

• Upload your Tally customer ledger
• Upload the Swiggy / Scootsy file
• Configure different data formats
• Select Invoice Number and other identifiers
• Use PO Number and GRN Number as supporting references
• Use payment references while investigating collections
• Automatically identify corresponding invoices
• Separate Fully Matched invoices
• Identify invoices with amount differences
• Identify transactions present only in your Tally
• Identify transactions present only in Swiggy
• Review Payment Status
• Review Paid Amount and Outstanding Amount
• Investigate withholding-related differences
• Review Vendor Credit Numbers
• Manually match transactions where references differ
• Download the reconciliation working in Excel
• Upload corrected records and reconcile again
• Repeat the process for future periods

---

Automate your Tally vs Swiggy customer reconciliation

If you supply Swiggy through Scootsy Logistics Private Limited and currently reconcile their transaction file against your Tally customer account manually, Cointab can automate much of the repetitive comparison work.

The process becomes:

Your Tally Ledger → Swiggy / Scootsy File → Automated Matching → Invoice and Payment Review → Exception Resolution → Updated Reconciliation

You can identify:

• Invoices that agree
• Invoices with value differences
• Invoices missing from either side
• Payments that may not be allocated
• Outstanding invoices
• Withholding differences
• Vendor credits and adjustments

The complete reconciliation can then be downloaded in Excel and reused as the working for customer follow-up and month-end review.

If you currently reconcile your Swiggy / Scootsy Logistics customer account manually using Tally and Excel, you can use Cointab to automate the process.

Try Cointab

For larger customer ledgers, custom Swiggy files, or more complex accounts receivable reconciliation requirements:

Book a Demo