Uber Eats → bankbrowser-only CSV matching

Turn order-level payment details
into bank-level payouts.

Upload an Uber Eats Payment Details CSV and your bank transactions CSV. PayoutLab groups Total payout by Payout reference ID, then matches those grouped payouts to bank deposits one-to-one.

Sample data

Test the grouped-payout flow first.

Download both sample CSVs and upload them below. The Payment Details sample deliberately uses Uber's two-row header pattern. With the default settings, expect 2 matched payouts for $495.50, 1 Uber Eats-only payout for $150.00, and 1 bank-only deposit for $180.00.

Uber Eats sample CSV Bank sample CSV

1Uber Eats Payment Details CSVPayoutLab groups Total payout by Payout reference ID before matching the bank.Choose Uber Eats CSV2Bank transactions CSVExport the account that receives Uber Eats deposits.Choose bank CSV

Local processing: the selected files are parsed and grouped in your browser. PayoutLab does not upload the CSV contents.

Why Payment Details can reconcile to the bank

Uber documents Total payout as the payout associated with an order, Payout Date as the date Uber initiated that payout, and Payout reference ID as the identifier connecting Payment Details to the Payout Summary report.

Uber: Payment Details report ↗

Payout Summary remains the accounting cross-check

Uber says the Payout Summary contains aggregate payouts that reflect the amount deposited to the merchant's bank account, and recommends using Payout Reference ID to reconcile it with Payment Details.

Uber: Payout Summary reporting ↗

Matching rules

Payment Details rows with the same Payout reference ID are summed first. Each grouped Uber Eats payout can then match at most one bank row. Amounts must be within the selected tolerance and, when both dates are available, within the selected date window.

Both CSVs remain in the browser. Refreshing or closing the page discards the imported data.