1. Define the payout month before matching
Scope the marketplace payouts to the calendar month you are closing. Do not simply reconcile every row in whatever files were downloaded. A month-specific scope makes it clear which payouts belong in the close.
2. Give the bank a short grace window
A payout dated at the end of the month may post to the bank in the first few days of the next month. Extend the bank search beyond month-end while keeping the platform payout scope fixed to the month being closed.
3. Reconcile each platform independently against the same bank export
DoorDash and Uber Eats use different export structures, so normalize each platform into payout-level entries first. Then match each platform against its eligible bank candidates. Platform-specific bank description filters help prevent unrelated deposits from becoming candidates.
4. Separate matching exceptions from setup problems
If a payout has no bank candidate, that is a reconciliation exception: show it as Payout not in bank. If the payout amount or date column cannot be identified, that is a file/setup problem and should be fixed before interpreting the reconciliation.
5. Do not close while ambiguity remains
A month can look balanced even when duplicate amounts were paired incorrectly. A conservative close should require unique payout-to-bank counterparts and leave duplicate candidate graphs unresolved until reviewed.
6. Export the evidence for review
The close report should preserve matched counts, platform-only payouts, bank-only deposits, ambiguities, the selected month, and the bank grace window. That creates a review artifact even when the free browser session itself does not store close history.
7. Investigate platform-specific issues in the standalone reconcilers
For unusual DoorDash exports, use the DoorDash bank reconciler with manual compatible-column mapping. For Uber Eats, use the Uber Eats payout reconciler to inspect the Payment Details grouping and bank match separately.