What is Cancellations vs Refunds reconciliation?

Cancellations vs Refunds reconciliation is the process of comparing cancellation records with refund transactions to identify matched refunds, unrefunded cancellations, refunds without cancellations, amount differences, failed refunds, duplicate refunds, reversals, deductions, customer ledger differences, and open items.

What files are required?

The main files are usually the cancellation report and refund report. Depending on the workflow, payment gateway refund reports, bank statements, order reports, booking reports, customer ledgers, supplier statements, chargeback reports, ERP exports, or supporting data may also be used.

Can Cointab identify cancellations that were not refunded?

Yes. Cointab can show cancellation records that do not clearly match refund transactions.

Can Cointab identify refunds without cancellation records?

Yes. Refund transactions that do not clearly match cancellation records can be shown separately for review.

Can Cointab handle full and partial refunds?

Yes. Full refunds, partial refunds, excess refunds, short refunds, split refunds, and grouped refunds can be compared where the data is available.

Can Cointab identify failed refunds?

Yes. Failed, pending, rejected, reversed, cancelled, retried, and manually processed refunds can be included where the required data is available.

Can Cointab identify duplicate refunds?

Yes. Duplicate refund records can be flagged where the same order ID, booking ID, refund ID, payment ID, gateway reference, customer, or amount appears more than once.

Can Cointab reconcile cancellation charges and deductions?

Yes. Cancellation charges, penalties, supplier deductions, convenience fees, gateway fees, taxes, and non-refundable amounts can be compared where the data is available.

Can Cointab compare refunds with payment gateway records?

Yes. Payment gateway refund reports can be added to compare internal refund records with gateway refund statuses, refund IDs, failure reasons, and settlement updates.

Can Cointab compare refunds with bank statements?

Yes. Bank statements can be added to trace successful refunds to actual bank debits or payment processor settlement adjustments.

Can Cointab reconcile customer ledger impact?

Yes. Customer credits, wallet credits, refund payables, receivable adjustments, advances, credit notes, and customer ledger postings can be compared where the data is available.

Can Cointab handle manual refunds?

Yes. Manual refunds, offline payouts, wallet credits, credit notes, and adjustment entries can be included where the data is available.

Can I reuse this reconciliation every day or month?

Yes. Once this template is selected and the workflow is used, the same setup can be reused for daily, weekly, monthly, cancellation-cycle, refund-cycle, settlement-cycle, or custom reconciliation periods.

Can this run automatically?

Yes. Once configured, Cointab can receive or pull required reports through email, SFTP, or APIs where available, run reconciliation automatically, and push output back to downstream systems.

What if my cancellation or refund report format is different?

Cointab validates uploaded files against the expected format. If the file format is different, users can correct the file, update the workflow, or create a custom reconciliation.

Can AI help with cancellation and refund reconciliation?

Yes. AI can help match difficult open records, review messy references, analyze exceptions, create derived columns, and suggest possible reasons and next actions.

Can I manually match cancellation and refund records?

Yes. Users can manually match records that the system and AI could not confidently match, and undo manual matches if needed.

Can I download the cancellation and refund reconciliation report?

Yes. Users can download Excel reports with fully matched, partially matched, failed, reversed, unmatched, skipped, customer-level, order-level, booking-level, refund-level, and transaction-level details.

Popular reconciliation template

Cancellations vs Refunds Reconciliation

Reconcile cancellation records with refund transactions to match cancelled orders, cancelled bookings, refund eligibility, full refunds, partial refunds, failed refunds, reversals, deductions, cancellation charges, and open items in one structured workflow.

Upload the required cancellation and refund reports, select the period, run reconciliation, and review fully matched, partially matched, unmatched, failed, reversed, and skipped records.

Start this reconciliation Schedule guided setup

View demo report

Ready-made workflow · Reusable every period · Manual upload or automated data flow

Cancellation Report

Refund Report

Payment Gateway / Bank Data

Customer Ledger / ERP Data

Cointab Cancellations-Refunds Reconciliation

MatchedPartially MatchedFailedReversedUnmatchedSkipped

Reconcile cancellations with refund transactions

Cancellation systems and refund reports often show the same customer event with different references, timestamps, refund statuses, payment modes, deduction values, cancellation charges, and settlement records. Cointab helps bring these records into one clear reconciliation report.

The Cancellations vs Refunds Reconciliation template helps finance, operations, customer support, and accounting teams compare cancellation records with refund transactions.

This helps teams answer questions such as:

Which cancellations were refunded correctly?
Which cancelled orders, bookings, invoices, or transactions are still awaiting refund?
Which refunds were issued without a matching cancellation record?
Which cancellations were eligible for full refund, partial refund, or no refund?
Which refund amounts differ from expected cancellation refund values?
Which refunds failed, remained pending, were reversed, duplicated, delayed, or retried?
Which cancellation charges, deductions, penalties, convenience fees, supplier charges, gateway fees, or taxes explain the difference?
Which items need refund operations review, customer support follow-up, payment gateway follow-up, supplier follow-up, finance review, or accounting correction?

This template is useful for travel companies, booking platforms, eCommerce businesses, marketplaces, D2C brands, ticketing platforms, fintech companies, subscription businesses, finance teams, controllers, CFOs, and accounting firms that need a repeatable cancellation-to-refund reconciliation process.

Required files for this template

Cointab's ready-made workflow is designed around common cancellation reports, refund reports, payment gateway refund files, bank statements, customer ledgers, order reports, booking reports, ERP exports, and supporting finance or operations files.

Data source	Example records
Cancellation Report	Used as the cancellation-side source containing order IDs, booking IDs, invoice numbers, customer IDs, cancellation dates, cancellation status, cancellation reason, original transaction value, cancellation charge, refund eligibility, and expected refund amount.
Refund Report	Used as the refund-side source containing refund IDs, refund dates, refund status, refund amounts, payment references, original payment IDs, refund mode, customer details, and processor references.
Payment Gateway Refund Report	Optional, but useful where refunds are processed through payment gateways, PSPs, cards, UPI, wallets, net banking, or online payment methods.
Bank Statement	Optional, but useful where refund debits, failed refunds, reversal credits, chargebacks, or settlement adjustments need to be compared with actual bank movements.
Order / Booking Report	Optional, but useful where cancellations need to be connected back to original order, booking, ticket, reservation, invoice, subscription, or service records.
Customer Ledger Report	Optional, but useful where customer refunds, credit balances, advances, receivables, wallet credits, customer credits, and adjustment entries need to be reconciled.
Supplier / Partner Statement	Optional, but useful where supplier cancellation charges, supplier refunds, partner credits, marketplace deductions, or vendor-side cancellation adjustments affect the final refund amount.
Refund Failure / Reversal Report	Optional, but useful where refunds fail, are reversed, retried, cancelled, rejected, delayed, or moved to manual payout.
Chargeback / Dispute Report	Optional, but useful where cancellations lead to disputes, chargebacks, reversals, customer claims, or payment gateway deductions.
ERP / Accounting Export	Optional, but useful if refund payables, customer ledgers, revenue reversals, cancellation charges, refund liabilities, bank entries, and accounting postings are maintained in SAP, Oracle, NetSuite, Microsoft Dynamics, Tally, Zoho Books, QuickBooks, or another accounting system.
Supporting Data	Optional supporting files can be used for customer mapping, order mapping, booking mapping, payment mapping, refund mapping, supplier mapping, cancellation reason mapping, GL mapping, entity mapping, tax mapping, or other enrichment.

What Cointab matches in cancellation and refund reconciliation

Cointab compares cancellation records with refund reports across order IDs, booking IDs, customer references, original payments, refund values, charges, deductions, statuses, and optional bank or accounting data.

Cancellations and refunds

Match cancelled orders, bookings, invoices, tickets, services, or subscriptions with corresponding refund transactions.

Original transaction references

Compare order IDs, booking IDs, invoice numbers, payment IDs, transaction IDs, customer IDs, receipt numbers, gateway references, bank references, and refund references.

Customer details

Compare customer names, user IDs, email IDs, phone numbers, account numbers, wallet IDs, and customer ledger references where available.

Refund eligibility

Compare cancellation policy, cancellation date, refund window, cancellation reason, refund eligibility, non-refundable amount, and expected refund amount.

Refund amounts

Compare original amount, eligible refund amount, actual refund amount, partial refund amount, cancellation charge, convenience fee, supplier charge, tax amount, deduction amount, and net refund amount.

Refund status

Compare initiated, successful, pending, failed, reversed, rejected, retried, cancelled, partially refunded, fully refunded, and manually processed refund statuses.

Refunds and reversals

Match successful refunds, failed refunds, refund reversals, retry refunds, duplicate refunds, chargebacks, and manual correction entries.

Customer ledger impact

Compare customer credit, refund payable, customer wallet credit, receivable adjustment, advance adjustment, and accounting entries.

Bank and payment gateway movements

If bank or payment gateway files are included, compare refund debits, settlement adjustments, chargebacks, and processor statuses with internal refund records.

Accounting postings

If ERP or accounting data is included, compare refund liability, revenue reversal, cancellation income, deduction income, taxes, customer ledger entries, bank debits, and journal postings.

Common cancellation and refund reconciliation exceptions

Cointab helps finance teams focus on cancellation-refund differences instead of manually reviewing every cancelled transaction, refund, failed refund, deduction, reversal, and customer ledger entry.

Cancellation not refunded

A cancellation is recorded internally, but no matching refund transaction is found.

Refund without cancellation

A refund transaction appears without a matching cancellation record.

Expected refund amount mismatch

The cancellation record and refund record match, but the expected refund amount and actual refund amount differ.

Full refund expected but partial refund issued

A cancellation is eligible for a full refund, but only a partial refund was processed.

Partial refund expected but full refund issued

A cancellation is eligible for a partial refund, but the full transaction amount was refunded.

Cancellation charge mismatch

Cancellation charge, penalty, convenience fee, supplier deduction, or service fee does not match expected policy or internal records.

Refund failed but cancellation marked refunded

The internal system shows refunded, but the payment gateway, bank, or refund processor shows failed, rejected, pending, or reversed.

Refund successful but system not updated

A refund is successful in the payment gateway or bank, but the internal system still shows pending, failed, or not refunded.

Duplicate refund

The same order, booking, refund ID, payment ID, transaction ID, or customer reference appears more than once.

Refund reversal mismatch

A refund reversal appears in one report but is missing or recorded differently in another.

Delayed refund

A cancellation was eligible for refund, but the refund is processed in a later period than expected.

Manual refund mismatch

A refund moved to manual payout, offline transfer, wallet credit, credit note, or adjustment entry does not match the original cancellation.

Customer ledger mismatch

Customer credit, refund payable, wallet credit, advance balance, or receivable adjustment does not match cancellation and refund records.

Tax mismatch

Tax reversal, GST, VAT, TCS, TDS, service tax, or other tax treatment differs between cancellation and refund records.

Wrong customer allocation

A refund, reversal, credit, cancellation charge, or adjustment is mapped to the wrong customer, order, booking, wallet, branch, entity, or business unit.

Missing or unclear reference

Order ID, booking ID, invoice number, customer ID, payment ID, refund ID, gateway reference, bank reference, UTR, or narration is missing, incomplete, or inconsistent.

Skipped record

A row cannot be reconciled because required data is missing, invalid, duplicate, incomplete, or unusable.

How this ready-made reconciliation works

Cointab pre-configures the workflow so your team does not need to rebuild the cancellation and refund reconciliation setup every period.

Select the template

Choose Cancellations vs Refunds from popular reconciliations.

Select the period

Choose the day, week, month, quarter, cancellation cycle, refund cycle, settlement cycle, financial year, lifetime period, or custom period you want to reconcile.

Upload cancellation and refund reports

Upload the cancellation report, refund report, and any required payment gateway, bank, customer ledger, booking, order, supplier, chargeback, ERP, or supporting files.

Validate file format

Cointab checks whether the uploaded files match the expected structure and highlights missing or incorrect columns.

Run reconciliation

Cointab applies predefined data preparation and matching logic for cancellation and refund data.

Review output

View fully matched, partially matched, unmatched, failed, reversed, and skipped records.

Download or automate

Download the Excel report, or automate future data input and output through email, SFTP, or APIs.

Structured matching first, AI assistance for difficult cases

Cointab applies structured reconciliation logic first, then uses AI to help with difficult open records where fixed rules are not enough.

Structured matching

Structured matching can use:

Order IDBooking IDInvoice numberCancellation IDRefund IDPayment IDTransaction IDGateway referenceGateway refund IDBank referenceSettlement IDUTRReceipt numberCredit note numberCustomer IDUser IDCustomer nameCustomer emailCustomer phoneWallet IDSupplier IDPartner IDChannel codeProduct codeService codeCancellation statusRefund statusPayment statusGateway refund statusBank statusChargeback statusAccounting statusOriginal transaction amountEligible refund amountExpected refund amountActual refund amountPartial refund amountCancellation charge amountPenalty amountConvenience fee amountSupplier deduction amountGateway fee amountTax amountCredit note amountWallet credit amountManual payout amountReversal amountNet refund amountOrder dateBooking dateCancellation dateRefund initiation dateRefund success dateRefund failure dateReversal dateSettlement dateBank debit datePosting dateAccounting periodDerived or cleaned identifiers

Matching scenarios

One-to-one
One cancellation record matches one refund transaction.
One-to-many
One cancellation maps to multiple refund attempts, partial refunds, gateway refunds, wallet credits, credit notes, reversal entries, or manual payouts.
Many-to-one
Multiple cancellations are grouped into one refund batch, bank debit, settlement adjustment, or accounting entry.
Many-to-many
Multiple cancellation records, refund transactions, gateway entries, bank entries, chargebacks, credit notes, and accounting postings are grouped and compared together.
Partial matching
Identifiers match, but expected refund amount, actual refund amount, deduction amount, tax amount, charge amount, or refund status differs.
Status-level matching
Cancellation status, refund status, gateway status, bank status, chargeback status, customer ledger status, and accounting status are compared together.
Policy-level matching
Refund eligibility, cancellation window, non-refundable amount, cancellation charge, partial refund rule, and deduction logic are checked where data is available.
Customer-level matching
All cancellations, refunds, credits, wallet movements, and customer ledger adjustments for a customer are grouped and compared.
Settlement-level matching
Refunds, gateway adjustments, chargebacks, settlement deductions, bank debits, and accounting entries are compared together where required.
Net and contra matching
Cancellations, refunds, failed refunds, reversed refunds, duplicate refunds, chargebacks, cancellation charges, deductions, credits, wallet credits, and manual adjustments are netted where required.

AI-assisted transaction matching

After structured rules run, AI helps match difficult open transactions where:

References are incomplete
Order IDs or booking IDs are missing
Refund IDs are formatted differently across systems
Customer names are written differently
Gateway references appear in different fields
One cancellation has multiple partial refunds
One refund batch contains multiple cancellations
A failed refund is retried under a new reference
A refund reversal is not clearly linked to the original refund
Cancellation policy deductions require contextual review
Supplier deductions or cancellation charges are described inconsistently
Bank narration is messy
Amounts require business context
Multiple possible matches exist

AI exception analysis

For transactions that remain open, AI can help identify possible reasons such as:

Cancellation not refundedRefund without cancellationExpected refund mismatchFull refund expected but partial refund issuedPartial refund expected but full refund issuedCancellation charge mismatchRefund failed but marked refundedRefund successful but system not updatedDuplicate refundRefund reversal mismatchDelayed refundManual refund mismatchCustomer ledger mismatchTax mismatchWrong customer allocationPosting period differenceInternal system issuePayment gateway issueUnclear reference

AI assists matching and exception review, but Cointab keeps reconciliation transparent, reviewable, and audit-friendly.

Audit-ready cancellation and refund reconciliation reports

Cointab gives your team a clear report showing which cancellation, refund, payment gateway, bank, customer ledger, credit note, reversal, and accounting records matched, partially matched, remained unmatched, failed, or were skipped.

Report categories

Fully matched
Cancellation and refund records where identifiers, statuses, and amounts match.
Partially matched
Records where identifiers match but expected refund amount, actual refund amount, deduction amount, cancellation charge, tax amount, or status differs.
Unmatched in cancellation records
Refund transactions that do not clearly match cancellation records.
Unmatched in refund records
Cancellation records that do not clearly match refund transactions.
Refund failure differences
Records where failed, pending, rejected, reversed, cancelled, or retried refund statuses require review.
Refund amount differences
Records where full refund, partial refund, excess refund, short refund, cancellation charge, deduction, or net refund amount requires review.
Cancellation charge differences
Records where cancellation charges, penalties, convenience fees, supplier deductions, or no-refund policy requires review.
Reversal and retry differences
Records where refund reversals, retry refunds, duplicate refunds, or manual correction entries require review.
Customer ledger differences
Records where customer credits, wallet credits, refund payables, receivable adjustments, advances, or credit notes require review.
Tax and accounting differences
Records where tax reversal, revenue reversal, refund liability, bank debit, customer ledger, or journal posting requires review.
Settlement and bank differences
Records where gateway refund status, bank debit, settlement deduction, chargeback, or payment processor update requires review.
Skipped
Records excluded due to missing, invalid, duplicate, incomplete, or unusable data.

Report capabilities

Summary cards
Transaction-level details
Cancellation-level filters
Refund-level filters
Customer-level filters
Payment mode filters
Refund status filters
Failure reason filters
Difference amounts
Policy-level view
Matched transaction drill-down
Manual match
Undo manual match
Excel export
Audit-friendly output

Automate recurring cancellations and refunds reconciliation

Once this workflow is stable, Cointab can automate file input, reconciliation runs, and output delivery.

Bring data into Cointab

Data can be received or pulled through:

EmailSFTPAPI integrations, where available

Run automatically

Schedule reconciliation:

DailyWeeklyMonthlyCancellation cycle-wiseRefund cycle-wiseSettlement cycle-wiseAt month-end closeAfter cancellation report exportAfter refund report exportAfter payment gateway refund file receiptAfter bank statement receiptAfter customer ledger exportAfter all required files are availableAt a custom frequency

Push output back

Send reconciliation output to:

Order management systemBooking systemERPAccounting systemPayment operations dashboardRefund operations dashboardCustomer support dashboardFinance operations dashboardBI dashboardInternal finance systemAnalytics databaseData warehouseInternal exception trackerCustomer follow-up workflowPayment gateway follow-up workflowRefund approval workflowAccounting close workflowAudit or compliance system

Matched cancellations and refunds
Unrefunded cancellations
Refunds without cancellations
Failed refund records
Pending refund records
Duplicate refund records
Refund reversal differences
Partial refund differences
Short refund records
Excess refund records
Cancellation charge differences
Supplier deduction differences
Tax differences
Customer ledger differences
Payment gateway differences
Bank debit differences
Wrong customer allocation records
Timing differences
Open items
Suggested actions
Excel reconciliation report
Structured API output

View a cancellations and refunds demo report

See how Cointab presents Cancellations vs Refunds output with matched, partially matched, failed, reversed, unmatched, and skipped records.

Cancellations vs Refunds Demo

Explore a sample report showing cancelled orders or bookings, refund transactions, expected refund amounts, actual refund amounts, cancellation charges, failed refunds, duplicate refunds, reversals, customer ledger differences, and open items.

View demo report

Explore related refund, booking, and payment reconciliations

Cointab supports other cancellation, refund, booking, order, payment gateway, bank, customer ledger, books, ERP, and finance reconciliation workflows.

Bookings vs Payment Gateway

Reconcile booking records with payment gateway reports across paid bookings, failed payments, refunds, cancellations, gateway fees, and settlements.

View template

Bookings vs Supplier Statement

Reconcile booking records with supplier statements across supplier invoices, cancellations, refunds, credits, commissions, taxes, and payables.

View template

Refund and Reversal Reconciliation

Reconcile refunds, reversals, failed refunds, chargebacks, bank debits, customer ledgers, and accounting records.

View template

Sales vs Returns vs Refunds

Reconcile sales, returns, refunds, customer payments, credit notes, and accounting records.

View template

Payment Gateway Settlement vs Bank

Reconcile payment gateway settlements with actual bank statement credits.

View template

Bank Statement vs Books

Compare bank statement entries with accounting or books records.

View template

Built for teams reconciling cancellations with refunds

This template is useful for teams that regularly reconcile cancelled transactions, customer refunds, payment gateway refunds, failed refunds, reversals, deductions, cancellation charges, and open items.

Travel companies

For travel businesses reconciling cancelled bookings, customer refunds, supplier deductions, cancellation penalties, payment gateway refunds, and customer support cases.

Booking platforms

For platforms reconciling booking cancellations, refund eligibility, partial refunds, failed refunds, wallet credits, and customer ledger entries.

eCommerce businesses

For teams reconciling cancelled orders, refunds, payment gateway refund statuses, customer credits, COD refunds, and accounting records.

Marketplaces

For marketplaces reconciling cancellations across sellers, suppliers, platforms, payment gateways, customer refunds, partner deductions, and settlement adjustments.

D2C brands

For brands reconciling cancelled orders, refund transactions, wallet credits, bank refunds, payment gateway updates, and customer service tickets.

Ticketing platforms

For platforms reconciling ticket cancellations, refund charges, partial refunds, chargebacks, failed refunds, and settlement deductions.

Refund operations teams

For teams reviewing refund status, pending refunds, failed refunds, duplicate refunds, payment gateway issues, and manual payouts.

Customer support teams

For teams reviewing customer complaints around cancelled but not refunded transactions, failed refunds, delayed refunds, duplicate refunds, and refund status mismatches.

Finance teams

For teams preparing recurring cancellation and refund reconciliation reports for daily review, month-end close, reporting, and audit.

Accounting teams

For teams reconciling revenue reversals, refund liabilities, customer ledger entries, tax reversals, bank debits, credit notes, and journal postings.

Controllers

For controllers who need visibility into unrefunded cancellations, duplicate refunds, incorrect deductions, refund failures, and customer ledger differences.

CFOs

For finance leaders who want stronger control over refund exposure, cancellation deductions, customer liabilities, cash outflows, accounting accuracy, and audit readiness.

Accounting firms

For CA, CPA, or outsourced accounting teams handling travel, eCommerce, marketplaces, bookings, refunds, and cancellation reconciliation for multiple clients.

Trusted by teams handling cancellation and refund reconciliation

Cointab is used by finance and operations teams that reconcile high-volume, multi-source transaction data across cancellations, refunds, payment gateways, banks, customer ledgers, booking systems, order systems, books, ERP systems, partner reports, and internal systems.

“We have worked on many softwares but we love the ease of using cointab. The staff and support is very instant. They are approachable, proficient and patient. Team is very cooperative with the customisations. The experience of using cointab was nice.”
— Urbanic

Cancellations vs Refunds FAQs

Start Cancellations vs Refunds Reconciliation

Use Cointab's ready-made cancellations and refunds reconciliation workflow to match cancelled transactions, expected refunds, actual refunds, failed refunds, reversals, deductions, customer ledger entries, review exceptions, and export audit-ready reports.

Start this reconciliation Schedule guided setup

View demo report

Ready-made workflow · Reusable every period · Manual upload and automation supported

Cancellations vs Refunds Reconciliation

Upload the required cancellation and refund reports, select the period, run reconciliation, and review fully matched, partially matched, unmatched, failed, reversed, and skipped records.

View demo report

Ready-made workflow · Reusable every period · Manual upload or automated data flow

Data source

Example records

Cancellation Report

Used as the cancellation-side source containing order IDs, booking IDs, invoice numbers, customer IDs, cancellation dates, cancellation status, cancellation reason, original transaction value, cancellation charge, refund eligibility, and expected refund amount.

Refund Report

Used as the refund-side source containing refund IDs, refund dates, refund status, refund amounts, payment references, original payment IDs, refund mode, customer details, and processor references.

Payment Gateway Refund Report

Optional, but useful where refunds are processed through payment gateways, PSPs, cards, UPI, wallets, net banking, or online payment methods.

Bank Statement

Optional, but useful where refund debits, failed refunds, reversal credits, chargebacks, or settlement adjustments need to be compared with actual bank movements.

Order / Booking Report

Optional, but useful where cancellations need to be connected back to original order, booking, ticket, reservation, invoice, subscription, or service records.

Customer Ledger Report

Optional, but useful where customer refunds, credit balances, advances, receivables, wallet credits, customer credits, and adjustment entries need to be reconciled.

Supplier / Partner Statement

Optional, but useful where supplier cancellation charges, supplier refunds, partner credits, marketplace deductions, or vendor-side cancellation adjustments affect the final refund amount.

Refund Failure / Reversal Report

Optional, but useful where refunds fail, are reversed, retried, cancelled, rejected, delayed, or moved to manual payout.

Chargeback / Dispute Report

Optional, but useful where cancellations lead to disputes, chargebacks, reversals, customer claims, or payment gateway deductions.

ERP / Accounting Export

Optional, but useful if refund payables, customer ledgers, revenue reversals, cancellation charges, refund liabilities, bank entries, and accounting postings are maintained in SAP, Oracle, NetSuite, Microsoft Dynamics, Tally, Zoho Books, QuickBooks, or another accounting system.

Supporting Data

Optional supporting files can be used for customer mapping, order mapping, booking mapping, payment mapping, refund mapping, supplier mapping, cancellation reason mapping, GL mapping, entity mapping, tax mapping, or other enrichment.

Start Cancellations vs Refunds Reconciliation

View demo report

Ready-made workflow · Reusable every period · Manual upload and automation supported