Reconcile customer refunds against aggregator payout reports when the refund/adjustment line item posts in a later settlement period than the original order

Steps

1. Record every customer-facing refund or comp with its originating order id and the date it was issued in your own system of record, independent of when the aggregator reports it
2. Pull each aggregator's financial/adjustment report (e.g., DoorDash financial reports, Uber Eats payment detail reports) on a recurring schedule and match adjustment line items to your internal refund log by order id
3. Expect adjustment postings to lag the original order's settlement period — a refund issued this week may not appear in the payout report until a subsequent cycle, so reconcile on a rolling window rather than a single settlement snapshot
4. Flag refunds you issued that haven't appeared in any aggregator report after a reasonable number of cycles as exceptions requiring manual follow-up with the platform
5. Separately track adjustment reason codes (customer refund vs platform error credit vs chargeback) since they net against revenue differently for accounting purposes