Refunds and Disputes

This standard governs refunds and payment disputes in the accounting system of All About Pawz, LLC: how a refund is issued, how the refund the Platform did not issue is caught, and how a dispute or chargeback is worked to its deadline. Money flowing backward needs more documentation than money flowing forward, because unwinding a sale touches the payment, the inventory, the revenue, the Seller's balance where a Seller is involved, and sometimes the processor: and every touch must be traceable. Whether a refund is due, and to whom, is governed by the Returns and Refunds Policy; chargebacks are governed by the Chargeback Policy. This standard states the accounting procedure under those policies and does not restate them. The Accounting Operator issues refunds and assembles dispute evidence; the Accounting Manager approves refunds above the operator's authority and owns the dispute calendar.

Issuing a refund

The issue-refund action protects against the most expensive refund mistake, the double refund: before doing anything, it checks the refund records for the order. A repeat request for the same order returns the existing refund instead of creating a second one. The operator shall nevertheless confirm no refund already exists for the order before issuing, including any refund made outside the Platform.

1. Confirm the refund is due under the Returns and Refunds Policy, and confirm the amount and the lines it covers.
2. Issue the refund through the administrative action. The sequence is: the order moves to refunded; the refund record is created (completed state, original-payment method, the reason supplied); the books entry posts: revenue debited, cash credited; and the action is recorded for audit.
3. Complete the refund lines: what was refunded per sale line: quantity, amount, and restock disposition. Line detail is what makes a partial refund auditable; refunding two of five items shall say which two, or inventory and revenue diverge.
4. Refund to the original payment method whenever possible. It is what the customer expects, what the processor's rules favour, and what keeps the payment and refund records matching.

Two cautions belong to every refund

• The books entry credits cash, while the shop sale debited checking. For a card sale refunded to the original method, the money leaves the checking account, not the cash drawer. Where the bank reconciliation under Banking shows a checking difference equal to a recent refund, this account mismatch is the first suspect, and the entry may need to be moved to checking by a correcting entry under Books.
• The books posting is best-effort: an error is recorded and the refund still completes. A refunded order with no journal entry is revenue that was never reversed. The operator searches the journal by the refund or order identifier and posts the entry by hand where it is missing, under Troubleshooting (Accounting Troubleshooting).

The refund the Platform did not issue

A refund made in the processor's own console, instead of through the administrative action, produces a negative row in the payment records: and stops there. No refund record is created, no journal entry posts, and the order's state does not change. This is the most common source of a refund that is in the processor and not in the books.

1. Weekly, the Accounting Operator takes the processor's refund list and matches each refund against the Platform's refund records.
2. For every refund with no matching record, the operator creates the refund record and posts the revenue-reversal entry manually.
3. Staff shall be trained to check the Platform's refund records for an order before touching the processor's console. The administrative action cannot double-refund an order; the console can, and an administrative refund plus a console refund for the same order is the classic double payment.

A refund the books never see overstates revenue by exactly the refund amount, and the month-end close in Troubleshooting (Accounting Troubleshooting) includes this match as a standing step.

Disputes and chargebacks

A dispute is a buyer contesting a payment, through the Platform's process or through the buyer's bank. The dispute record carries the dispute number, the linked payment, sale, and refund records, the amount, the reason, the processor's dispute identifier, and the opened, responded, and resolved times. A dispute is not a refund; it is a contest over whether the payment was valid, with its own course.

1. When a dispute opens, calendar the processor's deadline first. A missed deadline loses by default.
2. Gather the evidence: the order record, delivery confirmation, customer communications, and any refund record. Evidence submitted late might as well not exist.
3. Submit the evidence before the deadline and record the outcome either way. The win rate by reason shows which disputes are worth contesting and which recurring cause to fix at the source.

Chargebacks carry fees regardless of outcome, and the chargeback rate: chargebacks per hundred transactions: is a business-health measure. A rate approaching the card networks' limits is an emergency, and the fix is operational, not financial. Two rules protect the rate and the money

• Never issue a courtesy refund on a chargeback already decided against the Company; the money has already moved.
• Never ignore a chargeback notice because a refund was already given. Submit the refund as evidence: an unanswered chargeback counts against the rate even where the customer had already been made whole.

Disputes and chargebacks are handled under the Chargeback Policy, which governs deadlines, evidence, and who bears each cost.

Marketplace clawbacks

When destination charges begin under Payments (Accounting Payments), a dispute decided against the Seller triggers a transfer reversal: the disputed amount is pulled out of the Seller's connected account balance and appears as a transaction against the Seller. Where the Company returns its own fee to make the buyer whole, that return is booked as a reduction of fee revenue, not an expense: a debit against the fee revenue account: because the fee was never truly earned on a reversed sale. Fraud or ignored disputes trigger capability gating: payouts freeze during investigation, appearing in the records as a balance that grows with no payouts. That is an enforcement hold, not a defect, and it is released only by the trust and safety decision.

Reading the refund measures

The refund rate: refunds as a share of sales: broken down by reason is the diagnostic: defective, not as described, late, changed mind. A steady climb indicates a product, service, or Seller problem. A sudden spike in one reason is an incident: the operator investigates the underlying sales before processing the refunds. A staff member with an unusually high refund rate may simply be working the complaints desk; the Accounting Manager establishes the context before the figures alarm anyone.

Controls

• Separation of duties: the person who issues a refund does not reconcile the account it posts to, and no operator approves a refund the operator issued.
• No refund is issued outside the administrative action where the action can issue it; console refunds are the exception path and are caught by the weekly match above.
• A completed refund means the instruction went to the processor, not that the money arrived; card refunds take days to appear on a customer's statement. Before treating a refund as failed, the operator checks the refund's state and the processor's timeline.
• Where a dispute is won but funds remain held, the release is the processor's act on the processor's timeline. The operator records the win, calendars the expected release, and does not adjust the Seller's balance by hand: a manual adjustment double-counts when the processor's release lands.

Records created and where they are kept

Refund records and refund lines, dispute and chargeback records with their evidence and outcomes, Seller dispute records, and the related journal entries are kept in the accounting and commerce records and retained under the Regulatory Record Retention Policy.

Escalation

A chargeback approaching a network limit, a dispute involving alleged fraud, or any legal process: a subpoena, a regulator's inquiry, a court notice: goes to legal@aapawz.com on the day it is received. Refund system failures and unmatched console refunds go to the Accounting Manager and, where the cause is a system failure, to support@aapawz.com.

Review cadence

The Accounting Operator runs the processor-to-Platform refund match weekly. The Accounting Manager reviews the refund rate by reason and the dispute win rate monthly, and reviews this standard whenever the Returns and Refunds Policy or the Chargeback Policy changes.