How do you match a partial multi-item refund?

Last updated: 2026-07-31

Written and reviewed by Seller Profit Guard Editorial Team.

The invented order totals 89.00 EUR from 75.00 items, 8.00 shipping, and 6.00 tax. One refunded line carries 30.00 item value and 2.40 tax. A direct reference and valid timing support a partial match, leaving 56.60 EUR and two lines available for later evidence.

partial-refund ledger from protected order and refund evidence through relationship amount line and restoration controls — This original diagram explains a controlled partial-refund allocation using invented aggregate packets only.

Partial-refund grain

Use one invented multi-item order. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 1, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Opaque reference

Match ORDER-B-FIXTURE. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 2, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Three-line order

Preserve line eligibility. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 3, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

One-line refund

Allocate one affected line. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 4, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

partial-refund ledger: one-line refund — This original diagram makes a controlled partial-refund allocation reviewable without operational rows or settlement claims.

Original items

Reperform 75.00 EUR. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 5, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Original extras

Add shipping and tax. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 6, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Refunded item

Allocate 30.00 EUR. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 7, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Refunded tax

Allocate 2.40 EUR. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 8, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Cumulative value

Verify 32.40 EUR. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 9, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Remaining value

Preserve 56.60 EUR. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 10, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Coverage

Record one of three lines. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 11, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

partial-refund ledger: coverage — This original diagram makes a controlled partial-refund allocation reviewable without operational rows or settlement claims.

Future events

Prevent later double allocation. The partial-refund ledger records event grain, protected source fingerprints, invented opaque references, UTC order and refund events, currencies, original and refund components, prior matched refunds, cumulative amount, remainder, line coverage, tolerance, window, owner, reviewer, output hash, and prior accepted rule needed for a controlled partial-refund allocation.

At checkpoint 12, reperform the applicable relationship, timing, currency, component, cumulative, coverage, or evidence decision. State whether the packet supports Ready, Review, or Block and identify what still requires protected platform, payment, return, cancellation, settlement, accounting, tax, legal, or privacy evidence.

Partial Multi-Item Refund Matching: relationship integrity control

Tie every refund event to a direct reference or a documented protected review path. Control 1 defines the pass condition, source pointer, reviewer question, rejected shortcut, correction deadline, monitoring signal, stop rule, and restoration trigger for a controlled partial-refund allocation.

A nearby amount is not a relationship. Keep refund matching separate from duplicate detection, return receipt, cancellation, chargeback, fee credit, payout bridge, accounting recognition, tax treatment, customer communication, and production rewrite authority.

Partial Multi-Item Refund Matching: monetary integrity control

Tie every total to currency, components, signs, prior refunds, tolerance, and reporting cutoff. Control 2 defines the pass condition, source pointer, reviewer question, rejected shortcut, correction deadline, monitoring signal, stop rule, and restoration trigger for a controlled partial-refund allocation.

A balanced bare number is not evidence. Keep refund matching separate from duplicate detection, return receipt, cancellation, chargeback, fee credit, payout bridge, accounting recognition, tax treatment, customer communication, and production rewrite authority.

Partial Multi-Item Refund Matching: event integrity control

Preserve canonical order and refund events plus source status and extraction time. Control 3 defines the pass condition, source pointer, reviewer question, rejected shortcut, correction deadline, monitoring signal, stop rule, and restoration trigger for a controlled partial-refund allocation.

A valid timestamp cannot prove settlement. Keep refund matching separate from duplicate detection, return receipt, cancellation, chargeback, fee credit, payout bridge, accounting recognition, tax treatment, customer communication, and production rewrite authority.

Partial Multi-Item Refund Matching: privacy integrity control

Use invented aggregates publicly while operational references, rows, payments, and buyer data remain protected. Control 4 defines the pass condition, source pointer, reviewer question, rejected shortcut, correction deadline, monitoring signal, stop rule, and restoration trigger for a controlled partial-refund allocation.

The worksheet is not a file processor. Keep refund matching separate from duplicate detection, return receipt, cancellation, chargeback, fee credit, payout bridge, accounting recognition, tax treatment, customer communication, and production rewrite authority.

Partial Multi-Item Refund Matching: human authority control

Assign source, matching, privacy, exception, stop, and restoration owners. Control 5 defines the pass condition, source pointer, reviewer question, rejected shortcut, correction deadline, monitoring signal, stop rule, and restoration trigger for a controlled partial-refund allocation.

Ready cannot issue or reverse a refund. Keep refund matching separate from duplicate detection, return receipt, cancellation, chargeback, fee credit, payout bridge, accounting recognition, tax treatment, customer communication, and production rewrite authority.

Partial Multi-Item Refund Matching: rollback integrity control

Preserve sources, rules, prior matches, output hashes, exceptions, reconciliations, and tested restoration. Control 6 defines the pass condition, source pointer, reviewer question, rejected shortcut, correction deadline, monitoring signal, stop rule, and restoration trigger for a controlled partial-refund allocation.

Never overwrite the only event history. Keep refund matching separate from duplicate detection, return receipt, cancellation, chargeback, fee credit, payout bridge, accounting recognition, tax treatment, customer communication, and production rewrite authority.

partial-refund ledger: partial multi-item refund matching: rollback integrity control — This original diagram makes a controlled partial-refund allocation reviewable without operational rows or settlement claims.

Partial-refund grain: match lab 1

Reperform both invented packets. Use one invented multi-item order. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Test clean full, clean partial, malformed-reference, invalid-event, currency-mismatch, nonpositive-total, excess-line, refund-before-order, over-refund, reference-mismatch, stale-window, short-context, weak-scope, and open-conflict states. Record source version, authority, reconciliation, stop condition, and restoration action.

Opaque reference: match lab 2

Reperform both invented packets. Match ORDER-B-FIXTURE. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Three-line order: match lab 3

Reperform both invented packets. Preserve line eligibility. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

One-line refund: match lab 4

Reperform both invented packets. Allocate one affected line. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Original items: match lab 5

Reperform both invented packets. Reperform 75.00 EUR. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Original extras: match lab 6

Reperform both invented packets. Add shipping and tax. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Refunded item: match lab 7

Reperform both invented packets. Allocate 30.00 EUR. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Refunded tax: match lab 8

Reperform both invented packets. Allocate 2.40 EUR. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Cumulative value: match lab 9

Reperform both invented packets. Verify 32.40 EUR. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Remaining value: match lab 10

Reperform both invented packets. Preserve 56.60 EUR. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Coverage: match lab 11

Reperform both invented packets. Record one of three lines. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Future events: match lab 12

Reperform both invented packets. Prevent later double allocation. Change one reference, event, currency, component, prior refund, line count, tolerance, match window, context, or conflict only; preserve every other assumption and record original total, current refund, cumulative refund, remainder, gap, coverage, classification, and decision.

Allocate a partial refund without consuming the whole order

A partial event should reserve only the components and lines supported by the refund record. Keep the unrefunded balance and unaffected line eligibility available for later events. Closing the entire order after one partial match hides future refunds and produces false duplicate warnings.

Record whether shipping, tax, discounts, credits, and adjustments are allocated by line, proportion, explicit platform amount, or a separate event. Never invent an allocation merely to make line totals equal the aggregate refund.

Track repeated partial refunds as an ordered ledger

Sort accepted refund events by protected event time and stable transaction relationship, not by file row order. For each event, carry forward the previously matched cumulative amount and line allocation. The next event must reconcile against the remaining eligibility rather than the original order alone.

If two events share a timestamp or the platform's ordering semantics are unclear, quarantine the sequence for review. Preserve both source records and avoid choosing an arbitrary winner that changes the cumulative result.

Distinguish quantity coverage from line coverage

One order line may contain several units. A refunded-line count of one does not prove every unit on that line was refunded. Operational allocation should preserve line key, quantity ordered, quantity refunded, unit price, discount allocation, tax allocation, and remaining quantity.

The public fixture deliberately reports line coverage only. Treat it as a review indicator, not a complete inventory, return, or unit-level financial reconciliation.

Handle shipping and tax as explicit components

A partial item refund may include no shipping, all shipping, proportional shipping, or a separately entered amount. Tax treatment may follow platform calculations and jurisdictional rules. Preserve the platform-provided refund components instead of calculating a replacement policy in this matcher.

When source exports expose only an aggregate refund, label component allocation unknown and keep the event out of component-level conclusions. Matching the total does not authorize a guessed tax or shipping split.

Prevent double allocation across item aliases

Catalog renames, SKU aliases, variation changes, and bundled components can cause one refunded line to appear unrelated to the original item. Use a versioned protected line-key and alias mapping before allocating value. Do not rely on product title similarity.

If an alias maps to several original lines, retain the refund as a review candidate until quantity, variant, price, and platform relationship evidence select one unique target.

Reconcile future eligibility after every event

After each accepted partial refund, recalculate remaining monetary eligibility, remaining quantities, open lines, unresolved components, and monitoring status. Store the output hash and reporting cutoff so the next run can detect changed history or a newly arrived refund.

A negative remainder, reopened closed line, changed prior event, or disappearing transaction is a stop condition. Restore the last accepted ledger and investigate source drift before continuing.

Keep store credit and original-method refunds separate

A platform may support multiple refund destinations. Even when the order relationship is the same, preserve refund method, status, and monetary unit as separate evidence. Do not merge store credit with a processor refund merely because both reduce remaining customer eligibility.

This matcher does not determine legal expiration, escheatment, revenue recognition, cash settlement, or customer communication duties. Those decisions require current platform and professional evidence.

Design a reversible partial-refund correction

Before correcting a match, preserve the prior event linkage, component allocation, cumulative balance, line state, reviewer decision, output hash, downstream uses, and restoration command. Apply the corrected rule to a protected copy and reconcile every later event in sequence.

Stop when correction changes currency totals, creates duplicate allocations, produces negative eligibility, alters unrelated orders, or cannot restore the previous ledger. A correction is complete only when the chain re-performs and rollback passes.

Partial Multi-Item Refund Matching: intent-specific implementation walkthrough

partial-refund ledger checkpoint 1 addresses partial-refund grain for a controlled partial-refund allocation. Use one invented multi-item order. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 2 addresses opaque reference for a controlled partial-refund allocation. Match ORDER-B-FIXTURE. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 3 addresses three-line order for a controlled partial-refund allocation. Preserve line eligibility. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 4 addresses one-line refund for a controlled partial-refund allocation. Allocate one affected line. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 5 addresses original items for a controlled partial-refund allocation. Reperform 75.00 EUR. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 6 addresses original extras for a controlled partial-refund allocation. Add shipping and tax. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 7 addresses refunded item for a controlled partial-refund allocation. Allocate 30.00 EUR. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 8 addresses refunded tax for a controlled partial-refund allocation. Allocate 2.40 EUR. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 9 addresses cumulative value for a controlled partial-refund allocation. Verify 32.40 EUR. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 10 addresses remaining value for a controlled partial-refund allocation. Preserve 56.60 EUR. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 11 addresses coverage for a controlled partial-refund allocation. Record one of three lines. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

partial-refund ledger checkpoint 12 addresses future events for a controlled partial-refund allocation. Prevent later double allocation. Record the accepted relationship, rejected alternative, source version, reviewer, follow-up date, monitoring trigger, and rollback reference.

For a controlled partial-refund allocation, require all nine release confirmations, real source-review and policy-effective dates, strict decimal and whole-number literals, a bounded component amount, a bounded order-line count, and a minimum closed evidence duration. The evidence month must contain every event, the policy must predate or equal the earliest event, the review must cover the latest event, and the inclusive event span must meet the stated minimum. When this partial-refund ledger Blocks, quarantine its classification, totals, remainder, event gap, and coverage as Unavailable until the governing packet is repaired and independently reviewed.

Evidence boundary for a controlled partial-refund allocation

The full fixture rebuilds 94.00 USD from 82.00 items, 7.00 shipping, and 5.00 tax, then matches the same components and two-of-two lines 5.1 days later. The partial fixture rebuilds 89.00 EUR, matches a 32.40 EUR current refund to one of three lines, and preserves 56.60 EUR remaining eligibility.

These invented aggregates demonstrate deterministic contracts only. They cannot prove platform issuance, buyer receipt, processor settlement, cancellation, return, restock, fee credit, chargeback outcome, accounting recognition, tax treatment, lawful processing, file correctness, or permission to alter a source.

Release, monitor, and restore the partial-refund ledger

Block invalid references, events, currencies, amounts, cumulative totals, lines, context, scope, tolerance, or conflicts. Review reference mismatch or an event gap above the declared window. Ready clears only the entered aggregate fixtures.

Before indexing or operational reuse, preserve backups and pass type, unit, integration, build, content, similarity, SEO, image, link, privacy, mobile, deployment, and live checks. Monitor schema, reference, event, currency, refund, line, duplicate, and platform-status changes without claiming same-day traffic or financial causality.

Sources and further reading

Etsy Help: issue a full or partial refund: Official seller workflow for full and partial refunds, Payment account effects, fee credits, timing, and separate cancellation.
Etsy Help: refunds, returns, and exchanges: Official seller-policy, agreement, return, and Purchase Protection context.
Etsy Help: download sold transactions: Official order-item, order, Etsy Payments sale, and deposit CSV export types.
Etsy Help: Payment account: Official statement, fee, credit, shipping, reserve, and deposit context.
Etsy Help: chargebacks: Official distinction between a chargeback-related debit and an order refund.
Shopify Help: exporting orders: Official transaction-history CSV fields for order, kind, time, status, amount, currency, and gateway.
Shopify Help: refunding orders: Official full, partial, multi-transaction, store-credit, shipping, fee, return, and restock considerations.
Seller Profit Guard methodology: Deterministic fixtures, evidence precedence, release, correction, monitoring, and rollback.

Related Seller Profit Guard tools

Refund to Order Matcher: Classify invented full and partial refund packets.
CSV Date and Currency Normalizer: Normalize invented event times and monetary values first.
Seller CSV Column Mapper: Map approved refund and order fields to stable canonical names.
Duplicate Order Checker: Detect repeated source events separately from refund matching.
Marketplace Payout Anomaly Checker: Bridge aggregate refund effects to payout evidence separately.
Methodology: Apply calculation, release, correction, and rollback controls.
Data Privacy: Keep operational orders, refunds, and buyer data protected.
Refund to Order Matcher Formula Contract: Define direct references, UTC events, currency, original and refund components, prior refunds, line coverage, tolerance, match window, and evidence.
Refund to Order Matcher Full-Refund Example: Reperform a 94.00 USD original order and full refund using direct reference, UTC events, components, zero prior refunds, and complete line coverage.
Refund Matching Mistakes That Create False Links: Diagnose nearest-amount guesses, omitted prior refunds, mixed grain or currency, reversed signs, duplicate events, and chargeback confusion.
Reliable Refund and Order Matching Sources: Map each field to first-party order, refund, transaction, statement, line, status, currency, and schema evidence without exposing private records.
Safe Refund Matching Thresholds: Set structural blocks, amount tolerance, match-window review, cumulative-refund limits, line coverage, exceptions, monitoring, and rollback.
Full vs Partial Refund Matching: Compare closure, component allocation, line coverage, remaining eligibility, later-event risk, match class, monitoring, and restoration.
Refund Matching Operating Routine: Build a repeatable workflow for source intake, normalization, direct matching, component reconciliation, exception review, monitoring, and rollback.
Interpret Refund Matcher Results: Explain what full, partial, review-candidate, unresolved, remaining amount, event gap, line coverage, Ready, Review, and Block prove and cannot prove.
Refund to Order Match Audit Template: Provide a standalone order, refund, reference, time, currency, component, cumulative, line, source, exception, monitoring, and restoration record.

Next step: Open Seller Profit Guard.

This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.