Authenticate using Uber's OAuth 2.0 client credentials flow with the eats.pos_provisioning and eats.report scopes appropriate for financial data access
Query the financial reports endpoint specifying a date range and store UUID to retrieve itemized payout records
Use the next_page_token returned in the response to paginate through large result sets, storing each page before fetching the next
For each order record, extract marketplace_fee, delivery_fee, tip, and tax amounts to build a per-order reconciliation ledger
Cross-reference the payout_id against your internal order records using the external_reference_id field to match platform orders to POS records
Aggregate totals and compare against the ACH deposit amount received in the corresponding payout period
Known gotchas
Financial report data is typically available with a 24-48 hour lag; do not treat same-day queries as complete for reconciliation
Tax amounts on Uber Eats reports reflect marketplace facilitator tax where applicable; double-counting with your own tax system is a common reconciliation error
The external_reference_id field is only populated if you set it at order injection time via the POS integration; ad hoc orders placed natively on the platform will have null values
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp