Two actions, both retry-safe, both requiring a Source Event ID: Add Mileage Entry and Add Income Entry.
Add Mileage Entry
Required: Distance, Business Purpose, and the Source Event ID.
- Distance is the one-way distance in your account's mileage unit. Enable Round Trip only when that value excludes the return leg — enabling it on a distance that already includes the return doubles the trip.
- Business Purpose must be specific: "Client meeting", "Deliver equipment to job site". A generic purpose is what makes a log fail scrutiny later.
- Date is optional; leave it blank only when the Zap intentionally uses the current-date default. Backdated trips need the date mapped.
- Destination, City, and Notes support the record. Do not repeat the Business Purpose in Notes.
- Expense Category is only for overriding the account mileage default.
The entry is converted at the account's configured mileage rate. Do not hardcode a rate in your Zap.
Add Income Entry
Required: Amount, Income Source, Payment Method, and the Source Event ID.
- Amount is gross, before processor fees or tax collected are subtracted. Map fees into Fees and tax into Tax Collected rather than netting them off the amount — otherwise the deductions become invisible.
- Tax Collected is sales tax, GST, HST, or VAT you collected. It is not income tax withheld.
- Reference is the invoice, payout, or transaction reference that traces the payment. Map it; it is what makes a payout reconcilable months later.
- Income Category can be left blank to categorize during review.
Returns a Review Income URL. A payout automation is exactly the case where a review step earns its place — marketplace payouts often bundle several underlying payments.
Both
Client or project group fields select from existing ExpenseBot groups; neither
action creates one. Dates go to the sheet as unambiguous YYYY-MM-DD.