Skip to content

How do I automate rideshare income?

The Rideshare (Uber / DiDi) workflow turns your Uber or DiDi payment or tax summary emails into transactions. Forward a summary and myaccountant splits out fares, tips, service fees, booking fees and tolls with the correct GST, ready for your review.

Set up the workflow

Step 1. Go to Workflows and open the Rideshare (Uber / DiDi) card.

Step 2. Click Add rideshare workflow, choose Uber or DiDi, and pick the business it belongs to. Each business can have one rideshare workflow — a business that's already set up shows a Configured badge. If you drive for both platforms, you can switch the platform later in the workflow's settings.

Step 3. On the workflow's settings page, copy the Forwarding address with Copy. This address is unique to this workflow — anything sent to it lands here, no matter who sent it.

Step 4. Review the settings and click Save settings:

  • Platform — which platform this workflow is set up for. You can switch it here if you change platforms.
  • Auto-post clean runs — when a summary passes the confidence and net-deposit checks, post it to your books automatically and skip the review step.
  • Sender allowlist — only accept statements forwarded from these addresses (for example noreply@uber.com). Type an address and click Add. Leave it empty to accept any sender.

Step 5. Set up an auto-forward filter in Gmail or Outlook so your weekly summaries forward themselves — see What are Workflows?

When the workflow is created, myaccountant also adds a small set of rideshare accounts to that business's chart of accounts (Rideshare Clearing, Rideshare fares, Rideshare tips, Rideshare incentives, Rideshare service fees, Rideshare booking fees and Rideshare tolls), so extracted lines map somewhere sensible from day one.

Review a run

Step 1. Open the workflow's run history (click View run history from settings, or open the workflow from the list). Each forwarded summary appears as a run — "Week ending" with the date, the platform, when it was received, and the gross income, expenses and net amounts.

Step 2. Check the status badge:

  • Ready to post — everything checked out; it's waiting for you (or was queued to auto-post).
  • Needs review — something didn't add up, for example the stated net deposit doesn't match the sum of the lines, or a line couldn't be read confidently.
  • Posted — already on your books.
  • Duplicate — a summary for the same platform and period was already received.
  • Failed — the email couldn't be processed; the reason is shown in red on the run.

Step 3. Click a run to open it. You'll see four summary cards — Gross income, Total expenses, Stated net deposit and Computed net — and the extracted Lines, each with its label, kind (Gross fares, Service fee, Tolls and so on), account, amount and GST.

Step 4. Adjust anything that's wrong: change a line's account from the dropdown, edit its amount or GST, or add a note in Memo. Click Save edits to keep your changes.

Post to your books

Click Post to ledger. Income and expense transactions are created in the business, with everything settling through the Rideshare Clearing account — when the platform's actual deposit arrives in your bank feed, you match it against that clearing account.

Already posted but spotted a mistake? Edit the lines and click Re-post with edits — the original posting is reversed and replaced with your corrected figures.

If a run fails

  • "Sender … is not on the allowlist" — the email came from an address that isn't on your Sender allowlist. Add the sender on the settings page, then forward the summary again.
  • Extraction failed — the failure reason is shown in red on the run. Forward the original platform email (not a screenshot or a reply) and try again.
  • A run that needs attention never posts by itself — auto-post only applies to runs that pass every check.

Note: you can't delete a rideshare workflow while it still has in-flight runs — post, reject or resolve them first. Posted statements stay on your books even after the workflow is deleted.

Share X LinkedIn Email

Did this answer your question?