1. Use Uber Eats Payment Details
Payment Details can contain multiple rows associated with the same payout. The important fields for this workflow are Total payout, Payout reference ID, and Payout Date. Payout Recon groups rows that share a payout reference before comparing anything with the bank.
2. Keep payout grouping separate from bank matching
Do not try to match every order-level line directly to the bank. The bank normally receives the settlement-level payout, not one deposit per order. First calculate the grouped payout total, then compare that payout with candidate deposits.
3. Use the bank posting date as a timing check
The payout initiation date and the bank posting date do not need to be identical. Use a date window that reflects normal settlement timing while still preventing old or unrelated deposits from becoming candidates.
4. Investigate Uber Eats-only payouts
An Uber Eats-only payout means the grouped payout exists but no bank candidate met the amount and date rules. Check whether the deposit posted later, the description filter excluded it, the bank export is incomplete, or the payment details fall outside the period you intended to reconcile.
5. Investigate bank-only deposits
A bank-only result means a candidate deposit was not assigned to any grouped payout. Confirm that it is actually an Uber Eats deposit and not another settlement source included by a broad bank filter.
6. Keep ambiguous matches unresolved
Duplicate amounts and overlapping date windows can create multiple valid candidates. A bank reconciliation should preserve that uncertainty until you can identify the correct counterpart instead of choosing whichever row happens to appear first.