> ## Content Index
> Fetch the complete content index at: https://abundance.alloconomy.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Taskrabbit: Whose Money Is on the Invoice?
- URL: https://abundance.alloconomy.com/alloconomy/unit-economics-taskrabbit/
- Published: 2026-10-29T04:18:48.000Z
- Updated: 2026-11-01T22:14:34.000Z
- Description: Separate provider entitlements from platform revenue and connect support work to the task.
- Author: Sathya Narayanan
- Tags: Alloconomy, Foundations, Daily Unit Economics, #series-detail, #Import 2026-10-28 21:15

Foundations · Daily Unit Economics

The discipline of close at the unit level

1. Part 1[Why unit economics is hard](https://abundance.alloconomy.com/alloconomy/daily-unit-economics/)Five questions connect accounting discipline to daily decisions at scale.
2. Part 2[Uber · the completed ride](https://abundance.alloconomy.com/alloconomy/unit-economics-uber/)Follow a ride from fare and driver entitlement to insurance estimates and revised contribution.
3. Part 3[Airbnb · the reservation](https://abundance.alloconomy.com/alloconomy/unit-economics-airbnb/)Separate booking, cash, check-in, payout, and later service adjustments.
4. Part 4[Walmart · the retail order](https://abundance.alloconomy.com/alloconomy/unit-economics-walmart/)Follow item-level recognition, fulfillment costs, return estimates, and recovery of inventory.
5. Part 5**Taskrabbit · the completed task**Current essaySeparate provider entitlements from platform revenue and connect support work to the task.
6. Part 6[Netflix · the subscriber-day](https://abundance.alloconomy.com/alloconomy/unit-economics-netflix/)Connect service-day revenue to shared content costs without confusing allocation with causation.

**Who this is for.** You should already recognize the P&L (income statement), balance sheet, cash flow statement, accounting equation, and double-entry bookkeeping. You do not need to be an accounting specialist. For a refresher, start with James Hearle’s [Accounting Stuff accounting-equation refresher](https://accountingstuff.com/accounting-basics/accounting-equation?ref=abundance.alloconomy.com), then return to the worked example.

**Public sources and fictional examples.** Company-specific facts come only from cited public materials. Every scenario, workflow, cutoff, rate, volume, allocation, and profitability amount is invented for teaching and must not be read as a description of any company’s internal practice. The interpretations are my own and do not represent my employer or any other organization. No confidential, proprietary, or nonpublic information is used.

For the foundation, read [the series introduction](https://abundance.alloconomy.com/alloconomy/daily-unit-economics/) and [Monthly Close](https://abundance.alloconomy.com/alloconomy/month-end-close/).

## The customer pays $155 but the platform does not earn $155

In a fictional furniture-assembly task, the provider earns $100 for labor. The customer reimburses $20 of approved materials and adds a $10 tip. Combined platform fees are $25\. The customer’s total is $155.

Taskrabbit’s public guidance distinguishes provider charges, platform fees, expenses, and tips. It says providers receive all expenses and tips; fee presentation also varies in California and Massachusetts. We therefore use one invented combined platform-fee amount instead of claiming a universal invoice layout or fee rate. [Taskrabbit invoice-fee explanation](https://support.taskrabbit.com/hc/en-us/articles/46260407116955-I-d-Like-To-Understand-The-Fees-On-My-Task-s-Invoice?ref=abundance.alloconomy.com).

Our unit is the completed task. We assume a net platform-revenue model with a completed service and enforceable fee entitlement on October 28\. That recognition policy is a teaching assumption, not a verified description of Taskrabbit’s financial accounting. Taxes, subscriptions, and other business lines are excluded.

| Customer payment component | USD        | Economic owner in this case                          |
| -------------------------- | ---------- | ---------------------------------------------------- |
| Labor                      | 100.00     | Provider                                             |
| Materials reimbursement    | 20.00      | Provider                                             |
| Tip                        | 10.00      | Provider                                             |
| Platform fees              | 25.00      | Platform                                             |
| **Total customer charge**  | **155.00** | **$130 provider entitlement + $25 platform revenue** |

The $130 is an obligation to another party. It is not platform revenue available to cover operating costs.

## Determine which tasks can enter the daily result

The illustrative close selects tasks completed by local midnight and supported by evidence available at 06:00 the next morning. It checks completion, invoice revisions, disputed hours, approved reimbursements, and fee terms.

A scheduled task is not automatically completed. A completed task with a missing invoice is not automatically worth zero; it belongs in a defined estimation or exception process. A revised invoice must supersede its earlier version without creating a second task or a second fee.

The task identifier connects service evidence, invoice components, payment attempts, provider entitlement, refunds, and support. A provider identifier and customer identifier supply additional views, but neither replaces task-level reconciliation.

The operational team resolves completion exceptions. Finance owns the fee-recognition mapping and estimate policy. Engineering proves that the intended population and versions reached the report.

## Add the work needed to support the task

Assume payment processing costs $4.65, equivalent to an invented 3% of the full $155 collected. Processing cost can follow the gross collection even though revenue is only $25\. That is why revenue alone may be a poor payment-cost driver.

The task uses six minutes of support at an assumed $0.50 per minute, or $3\. Trust and safety resource use contributes $1.50 from a defined shared activity pool. Infrastructure adds $0.50\. An expected $2 platform-fee refund reduces fee revenue. It does not include the support and trust work already counted as costs.

| Daily task-close component                 | USD       |
| ------------------------------------------ | --------- |
| Gross company fee                          | 25.00     |
| Expected platform-fee refund               | −2.00     |
| **Net fee revenue**                        | **23.00** |
| Payment processing                         | −4.65     |
| Support activity                           | −3.00     |
| Trust and safety allocation                | −1.50     |
| Infrastructure allocation                  | −0.50     |
| **Contribution before other shared costs** | **13.35** |

The $13.35 is a contribution measure, not net profit. Provider labor is not subtracted a second time because it was never included in the $25 revenue.

The expected fee refund creates an estimated refund obligation in this model. Other protection costs may require insurance, reserve, or operating-expense treatment under their own facts. The invented categories here are not Taskrabbit’s disclosed expense classification.

## Reconcile the first settlement

If the processor settles net of $4.65, the bank receives $150.35\. Paying the provider $130 leaves $20.35 of cash from this transaction before other payments. That differs from $13.35 contribution because the $2 expected fee refund and $5 of other included costs can settle separately.

If provider payout is delayed, the retained cash balance is temporarily higher and the payable remains. Waiting to pay someone does not improve the task’s profitability.

The close must reconcile provider entitlements and settlements independently of platform margin. A perfect platform revenue total would not detect that $20 of materials reimbursement was sent to the wrong provider.

## Resolve a fee refund without charging it twice

A service issue is later resolved with a $4 refund of the platform fee. The provider keeps the agreed $130 entitlement. Net platform revenue becomes $25 − $4 = $21; the refund does not become an additional operating expense as well.

Total support rises from $3 to $5\. The processor fee is confirmed as $4.80\. Trust and safety and infrastructure remain unchanged.

Updated costs are **$4.80 + $5 + $1.50 + $0.50 = $11.80**. Updated contribution is **$21 − $11.80 = $9.20**.

| Change                                         | Contribution effect |
| ---------------------------------------------- | ------------------- |
| Processor fee increases by $0.15               | −$0.15              |
| Additional support                             | −$2.00              |
| Fee refund replaces $2 estimate with $4 actual | −$2.00              |
| **Total revision**                             | **−$4.15**          |

The $4 refund settles the $2 estimated refund obligation and reduces revenue by another $2\. Keeping the earlier $2 revenue reduction and subtracting another full $4 would understate contribution by $2.

The resolved service issue does not make unrelated pooled risks disappear. Any remaining exposure needs its own support and review.

## Review the pool as well as the task

Support minutes should reconcile to the workload pool used to calculate the rate. If the team has unused capacity, do not silently force it onto completed tasks just to make every cost allocated. Retain idle capacity or other unallocated expense as a visible bridge to the period accounts.

A daily cohort report also needs tasks with missing or disputed records. Excluding difficult tasks from the denominator while recognizing their fees would make the clean population look deceptively attractive.

The monthly reconciliation begins with period movements from task records, adds supported unallocated pools and other business activity, and explains differences in treatment. The cumulative $9.20 appears once in the lifetime task analysis; only its appropriate movements appear in each daily or monthly P&L.

## What the decision changes

A manager comparing service categories should ask whether similar fees create similar support and resolution work. An engineer should test invoice amendments and provider-payment matching. An investor should distinguish customer payment volume from platform revenue and then ask which costs remain outside the presented contribution measure.

For customers and providers, the same map explains why a large invoice is not a large platform profit and why a provider’s entitlement is not determined by the platform’s margin calculation.

**Remember the crux: one invoice contains money belonging to different parties.** Daily unit economics begins by respecting those boundaries, then follows the work required to complete and support the task.

---

[← Walmart · the retail order](https://abundance.alloconomy.com/alloconomy/unit-economics-walmart/) · [Netflix · the subscriber-day →](https://abundance.alloconomy.com/alloconomy/unit-economics-netflix/)