Quick Answer
Define base, distance, waiting, accepted surge, tips, and exception rules in a versioned courier-pay policy. Preserve the accepted rate and earned amount, calculate applicable minimum-pay top-ups separately, and reconcile uncertain disbursements before issuing a replacement.
Turn delivery records into explainable earnings#
A per-drop model is more auditable when each payable drop ties back to a clear delivery record and proof-of-delivery evidence such as photos or digital signatures. Those controls help reduce disputes and improve accountability.
The pay rule must also explain work that does not end in a completed drop: waiting, a customer cancellation, an attempted delivery, and a required return. Define those outcomes before launch, so a courier does not discover the payment rule after doing the work.
The rates and trigger thresholds below are invented design examples. They are not market rates, a recommendation to classify workers as contractors, or proof of compliance with local minimum-pay and payment-timing rules. Approve the applicable labor and contractual requirements separately for each market.
A versioned per-drop formula#
For the illustrative policy v3, completed-drop earnings equal base pay + eligible distance pay + payable waiting time + accepted surge bonus + tips + approved adjustments. Any mandatory minimum-pay top-up is calculated separately over the legally relevant worker and period population. Permitted deductions, if any, must have their own lawful basis and explanation.
| Component in v3 | Illustrative rule | Evidence |
|---|---|---|
| Base | $4.00 for a completed eligible drop. | Accepted offer and delivery outcome. |
| Distance | $0.75 per eligible mile. Use the disclosed route basis; approved diversions create an adjustment. | Route version, eligible distance, and diversion reason. |
| Waiting | $0.20 per minute after an illustrative first five minutes. | Arrival and release times, with a correction path for missing events. |
| Surge | Fixed $2.00 bonus on eligible offers accepted while the zone bonus is active. | Offer ID, acceptance time, zone, and bonus-policy version. |
| Tips | Show final earned tip separately and pass it through under the applicable rules. | Tip event and any permitted, explained correction. |
| Other outcomes | Cancellation, failed attempt, return, and top-up rules defined separately. | Outcome facts and the rule version that applies. |
Suppose a courier accepts an eligible offer at 17:58 while the $2 bonus is active. The completed job includes four eligible miles and 12 minutes of recorded waiting. A $3 tip is final. Earnings are $4 + (4 × $0.75) + (7 × $0.20) + $2 + $3 = $13.40, before any required period-level top-up. Platform processing fees are not silently taken from that amount.
In this example, surge switches off at 18:00 and the courier completes at 18:14. The accepted $2 still applies. Store the accepted offer and its calculation inputs; do not reprice it using the surge setting at completion. If your actual product promises a multiplier instead, state exactly which components it multiplies, the rounding rule, and how the accepted quote is protected.
Define surge activation and expiry#
An illustrative zone rule might activate the $2 bonus when more than 20 unassigned eligible jobs persist across three consecutive five-minute observations. It might stop offering the bonus when backlog falls below 10 across three such observations, subject to a stated maximum activation duration and a re-evaluation. These numbers are hypothetical and require validation against your own service and cost data.
Different activation and deactivation thresholds can reduce oscillation. Preserve the observation timestamps, backlog definition, available-courier measure if used, rule version, activation interval, and any authorised override. If the feed is stale, do not silently invent a live-demand value: follow a documented outage policy and honour offers already accepted.
Ending surge changes future offers. A budget cap or rollback should not erase a bonus already promised. Make zone boundaries and qualifying acceptance times visible so Support can explain why two nearby deliveries had different rates.
Pay exception work under an explicit rule#
| Outcome | Illustrative treatment to define in advance |
|---|---|
| Customer cancels before assignment | No courier work yet; no job earning under this example. |
| Customer cancels after pickup | Example cancellation policy pays $4 plus eligible distance and waiting already performed, plus the accepted $2 bonus when applicable. A return creates a separate work record. |
| Recipient unavailable after documented attempt | Apply the approved attempt policy and pay qualifying distance/waiting; missing completion does not prove that no compensable work occurred. |
| Address corrected or route diverted | Preserve the accepted route and add an approved, linked distance or time adjustment. |
| Photo upload delayed | Use other supported evidence or timely review; a failed upload alone does not establish fraud or justify an indefinite earned-pay hold. |
| Second courier performs a reattempt | Create a new assignment and work record; do not overwrite the first courier’s entitlement. |
For the example cancellation after pickup, assume two eligible miles, eight waiting minutes, and an accepted $2 bonus: $4 + $1.50 + $0.60 + $2 = $8.10. The three payable waiting minutes follow the same illustrative five-minute threshold. A return fee or new delivery must be specified separately; do not pay a completed-drop base and cancellation base twice for one outcome.
Check the market rule independently of the formula#
Per-order pay can coexist with a statutory minimum calculation. In New York City, the DCWP delivery-worker FAQ explains the applicable app and worker categories, standard and alternative payment methods, and treatment of trip and on-call time. As of October 3, 2026, it lists $22.13 per hour, excluding tips for pay periods beginning on or after April 1, 2026. A per-drop example alone does not satisfy those rules.
The restaurant delivery-worker notice also describes pay transparency, all earned tips, weekly earnings payment, and a no-fee payment option. Use the applicable local rules for your actual service and worker arrangement. Do not reuse a restaurant-app rule as a universal parcel-courier rule or treat tips as a substitute for a required platform-funded minimum.
Preserve the earning even when payout fails#
Create one earning record per assignment outcome and component, tied to its policy and accepted offer. Deduplicate delivery events before calculating, and use a controlled adjustment record for corrections. Do not delete the original earning when a destination account changes or a disbursement fails.
| Payment state | Meaning and next action |
|---|---|
| Earned/payable | Approved amount owed, not yet submitted for disbursement. |
| Submitted/processing | Attempt exists; await authoritative provider outcome. |
| Unknown | Response or events are incomplete; reconcile the existing attempt. |
| Paid | The selected rail’s documented successful outcome is confirmed and linked to the earning. |
| Failed/returned | Authoritative failure or return recorded; preserve the liability and assess a new permitted attempt. |
| Held for a lawful reason | Reason, owner, review deadline, and affected amount visible; undisputed earned amounts handled under applicable timing rules. |
Persist the attempt identity before calling the provider and ensure only one worker releases the same payable amount. Recover a lost response using the original provider’s supported lookup or replay rules. Stripe’s idempotency documentation, for example, describes parameter matching and finite key retention. A stable local identifier is not an unlimited provider guarantee.
Never send another rail because the first outcome is unknown. A cancellation request needs confirmation that execution was prevented. A new payout after confirmed failure needs a new attempt record linked to the same outstanding obligation, without recalculating the courier’s earned rate. Confirmed returns reopen the amount owed while preserving the original paid and return history.
Give couriers a line-item statement and dispute path#
Show assignment ID, accepted offer, outcome, base, distance basis, waiting minutes, surge, tips, adjustments, any lawful deductions, and final amount. For the worked completed drop, the courier should see the $13.40 calculation and the payment attempt’s status separately. “Processing” must not be described as bank receipt.
A dispute should reopen the component and evidence, not require the courier to repeat the entire story. Record the requested correction, investigator, deadline, decision, and linked adjustment. Missing telemetry needs a usable alternate-evidence path. Restrict location and delivery evidence to the people who need it and retain it under the applicable policy.
Measure contribution across completed and failed work#
Courier earnings are only part of platform cost. In a hypothetical period, assume $15,000 earned delivery revenue, $10,000 courier pay including exception work and surge, $500 processing costs, $1,000 support costs, and $500 other direct costs. Contribution is $3,000. If 1,000 drops complete, contribution per completed drop is $3, but the numerator includes the work and costs of failed attempts too.
Count payouts rather than drops for a per-payout fee: a weekly payout can contain many deliveries. Keep customer tips and pass-through amounts separate from platform revenue under your accounting policy. Model a disruption period with more waiting, cancellations, required returns, and minimum-pay top-ups, rather than assuming all extra jobs are clean completions.
In a bounded pilot, keep the rate version fixed and compare matched zones or periods with clear limitations. Track completion, timeliness, courier earnings and disputes, contribution, missing evidence, and unknown payout amounts together. Roll back future surge offers if the policy fails its agreed criteria while honouring accepted offers and outstanding earnings.
Sources#
Frequently Asked Questions
Which time determines the surge bonus?
The time and eligibility rule promised in the accepted offer. In the illustrative policy, an eligible acceptance while surge is active locks the bonus even if surge ends before completion.
Should failed delivery mean zero courier pay?
Not automatically. Apply the approved rules and applicable law to work already performed, including waiting, distance, attempts, and returns. Keep separate assignment outcomes and avoid duplicating mutually exclusive pay components.
Can a payout failure erase an earning?
No. Preserve the amount owed and the original earning calculation. Resolve the disbursement attempt separately; an unknown outcome blocks a replacement payout until authoritative evidence permits one.
Does the worked rate satisfy minimum-pay laws?
No compliance conclusion is implied. The invented component rates demonstrate calculation mechanics. Apply the actual worker, service, time, tip, and period rules for the relevant jurisdiction and calculate required top-ups separately.
Researched and edited by the Gruv editorial team. Gruv builds cross-border billing, payouts, and finance-operations software for global businesses.
Sources
Educational content only. Not legal, tax, or financial advice.
Related Posts
The Freelance Payment Penalty: A Modeled Audit of Platform Fees, FX Spreads, and Payout Delays
The money rarely disappears through a single, easy-to-spot fee. The real loss is stacked. A marketplace takes its commission, a processor adds a charge for international cards, a bank or payment company converts the currency at a spread, a platform holds the funds before release, and a wire sheds a little to intermediaries on the way in. Each layer looks defensible on its own, but the worker feels the combined result as a smaller deposit and a later payday.
How to Respond to a Subpoena for Business Records
Move fast, but do not produce records on instinct. If you need to **respond to a subpoena for business records**, your immediate job is to control deadlines, preserve records, and make any later production defensible.
A US Expat's Guide to Investing in UCITS ETFs to Avoid PFIC Issues
The real problem is a two-system conflict. U.S. tax treatment can punish the wrong fund choice, while local product-access constraints can block the funds you want to buy in the first place. For **us expat ucits etfs**, the practical question is not "Which product is best?" It is "What can I access, report, and keep doing every year without guessing?" Use this four-part filter before any trade: