Refund and cancellation reconciler

What does the refund and cancellation reconciler produce?

Reconcile approved refund and cancellation requests against actual billing and fulfillment events.

Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.

What do you need before you start?

• Define the authorized source population and your review rules.
• Keep the unchanged original files and record the snapshot and exclusions.
• Review missing and invalid inputs before preparing the finalized pack.

What information do you enter?

Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.

• Approved requests. Exact headings request_id, order_id, action, amount, currency, approved_on, target_on, approved_by.
• Actual billing and fulfillment events. Exact headings event_id, request_id, order_id, event_type, amount, currency, event_on, status, reverses_event_id.
• Review reference. Customer-controlled review reference.
• Review owner. Responsible customer reviewer.
• Observation date. Real YYYY-MM-DD date. Effective date intervals include both endpoints.
• Selected source scope. Name actual populations, versions, period and known omissions.
• Population declaration. Choose the explicit working rule before preparing a result.
• Absolute reconciliation tolerance. Nonnegative plain decimal, at most six decimal places. The exact boundary is included.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the refund and cancellation reconciler work?

1. 1
   Select the actual sources

   Approved requests. Exact headings request_id, order_id, action, amount, currency, approved_on, target_on, approved_by.

2. 2
   Freeze the review rules

   Match exact request_id and order_id. Sum completed Refund events minus valid completed Reversal events in the approved currency. Confirm actual completed Cancellation events for requests requiring cancellation. Preserve pending and failed events. Detect duplicate event IDs, unsupported reversals, over-refunds, overdue requests and later charges or fulfillment after cancellation. The tool never sends money, cancels an order or changes billing.

3. 3
   Inspect complete findings

   Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.

4. 4
   Keep recoverable work

   Inputs and exact source bytes save locally and survive reload. Strict restores verify tool identity, input schema, original hashes and parsed bytes before atomic replacement. Earlier generic work, prior checkpoint files and purchases remain preserved separately.

5. 5
   Prepare the finalized pack

   Prepare seven core files and the exact selected attachments, then download them free. Review the fictional sample below.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• Common Format and MIME Type for Comma-Separated Values FilesCSV mechanics only. This source supplies no customer schema, legal requirement, matching identity, population completeness, threshold or reconciliation rule. Section 2 describes CSV records, field counts, double-quote escaping and embedded commas or line endings.RFC Editor. Reviewed 2026-10-09.

Common questions

What still needs review?

Mechanical working results use exact supplied source populations and your rules. Originals remain unchanged in this browser. No identity, legal obligation, source completeness, currency conversion, suppression consent, refund, cancellation, shipment or external operation is authenticated or performed.

Action is Refund, Cancel or Refund and cancel. Event type is Refund, Cancellation, Charge, Fulfillment or Reversal. Status is Completed, Pending or Failed. Dates are YYYY-MM-DD. Same-day ordering remains unknown.

At most 5000 rows, 50 fields, 100000 cells and 5000000 parsed characters per source, 10 MB per file. Exact decimal arithmetic supports 12 whole digits and 6 fractional places.

Complete reviews are bounded to 20000 findings and 15000000 result characters. Split larger populations into explicit source batches.

Formal reports show at most 100 findings and 400 characters per displayed field. Complete sources, findings and working output values remain in Excel and JSON.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all marketing and consumer protection tools.

• Advertising claim registerLink each claim to evidence, scope and approval. Try a free example, then review your inputs and the result. No account or payment required.
• Claim substantiation checkerAssess the evidence against a review framework. Try a free example, then review your inputs and the result. No account or payment required.
• Testimonial permission registerRecord permissions, restrictions and expiry. Try a free example, then review your inputs and the result. No account or payment required.
• Endorsement disclosure checkerReview content against the selected requirements. Try a free example, then review your inputs and the result. No account or payment required.
• Review incentive registerTrack benefits, disclosures and practices. Try a free example, then review your inputs and the result. No account or payment required.