Walmart's $100 Million Spark Driver Settlement: How Any Business Using Gig Delivery Should Document Driver Pay

Pull up the last delivery payout you sent — to a courier, a driver, anyone who carried something for your business last month. Now answer three questions from your own records: what was that worker shown when they accepted the job, what changed between acceptance and payday, and where is the paper trail tying the two together? If you cannot answer all three in under five minutes, you have the same gap that just cost the country's largest retailer $100 million.

On February 26, 2026, the Federal Trade Commission and eleven states announced a $100 million judgment against Walmart over its Spark Driver delivery program, which has run since 2018 and moved roughly 272 million deliveries through nearly a million drivers. Up to $79 million goes directly to drivers — about $63 million the company had already paid plus a roughly $16.2 million fund for the rest — with $11 million to the states and $10 million to the FTC. The allegations were all documentation failures at heart: drivers shown one number and paid another, with no record the driver could check. And the court order reads like a compliance checklist your business can adopt for free.

This post covers what the order requires, why tips keep tripping up delivery businesses, and the six-record system that keeps your driver pay defensible.

What the order actually requires​

Strip away the headline and the settlement imposes three duties that translate directly to any business paying gig drivers:

1. No modifying an offer after acceptance. Once a driver accepts, the pay terms are locked. The only permitted change is an increase — more tip, more earnings — with narrow exceptions for a failed delivery or an outright cancellation.
2. No misrepresenting the offer card. Distance, estimated time, number of stops, expected earnings: every fact the worker sees before accepting must be accurate.
3. An earnings verification program. The company must check that drivers are paid exactly what the initial offer showed, document the results, put a named employee in charge of the program, and report to the FTC every year for ten years.

Note what the enforcers did not accept as a defense: scale, software complexity, or "the algorithm did it." The order treats every accepted offer as a promise and every payment as something to reconcile against that promise. Your business is smaller, which makes that reconciliation easier, not optional.

The five alleged breakdowns — and the pattern behind them​

The complaint alleged five ways drivers ended up with less than the offer showed:

• Split tips nobody disclosed. A single customer order divided across several drivers had its tip divided too, while each driver was shown the whole tip.
• Batched orders edited mid-trip. When orders were removed from a multi-stop batch, base pay and tips shrank, but the offer card was never updated.
• Incentive terms kept back. Drivers chasing bonuses were not told every condition — the qualifying zone, store, or delivery count — and learned about the missing requirement only when the money did not arrive.
• Tips displayed but never collected. The checkout pre-authorized the order total but not the tip, so some "guaranteed" tips never existed as money. Drivers were not told when collection failed; the completed-delivery screen simply showed $0.
• "100% to the driver" that was not. Customers were told the full tip reached the driver while some tips were kept entirely — and when tips vanished, drivers saw a message implying the customer had adjusted the tip after delivery, even though genuine post-delivery tip reductions happened in only 0.04 to 0.09 percent of orders, by the company's own internal figures.

Walmart denied wrongdoing, as settling companies do. But do not read this as a one-company story. A year earlier, New York's attorney general secured $16.75 million from DoorDash for roughly 63,000 New York drivers over a pay model that used customer tips to cover guaranteed base pay instead of adding tips on top, covering May 2017 through September 2019. Tips are the recurring tripwire: money that passes through your hands but belongs to someone else, handled by software nobody reconciles. Every delivery business touches that wire. The fix is records.

1. Freeze the offer at the moment of acceptance​

The order's core idea is that the accepted offer is the contract. So keep it like one. For every job a driver accepts, snapshot these fields the moment they tap accept:

• Timestamp, driver ID, and the job or order identifiers
• Stops, distance, and estimated time as displayed
• Base pay shown, incentive shown, and the incentive's full conditions
• Tip shown, plus whether that tip was actually collected or only estimated
• The total the driver saw

If your delivery platform exports this, archive the export. If it does not, log it yourself — an API pull, an automated screenshot, a shared spreadsheet row per job. The medium does not matter; immutability does. A snapshot you can edit after the fact is a diary, not evidence. When a driver asks "why did I get less than the offer," this record is your first and best answer, and without it you are reconstructing history from memory.

2. Treat tips as pass-through money, never as revenue​

Customer tips are the single highest-risk line in delivery pay, and the settlement shows why: the business collected them, displayed them, moved them, and in some cases kept them. Run yours under three rules:

• Tips never touch your profit. They sit in a liability account from collection to payout — money you hold for someone else, like a security deposit. They are not revenue when collected and not your expense when paid out.
• Every tip ends in exactly one of two places. Paid in full to the driver, or refunded to the customer. There is no third destination. "Kept because the payout math got complicated" is how redress funds get started.
• Never use tips to top up base pay. If you guarantee a driver $20 and the customer tips $8, the driver gets $28, not $20 with the tip covering part of your promise. The DoorDash model that cost $16.75 million in New York was exactly this offset.

The pre-authorization failure carries its own lesson: only show a driver a tip you have actually secured. If your checkout authorizes the order total but not the tip, either fix the authorization flow or label the tip an estimate until the charge clears — before acceptance, not after.

In a plain-text ledger, the separation looks like this: fees you keep go to income, base pay and incentives go to expenses, and tips move through a liability account they never stick to. The docs cover account setup if you are starting from scratch.

2026-01-05 open Assets:Checking
2026-01-05 open Income:Delivery-Fees
2026-01-05 open Liabilities:Driver-Tips-Payable
2026-01-05 open Expenses:Delivery:Driver-Base-Pay
2026-01-05 open Expenses:Delivery:Driver-Incentives
 
2026-03-02 * "Deliveries completed" "week of Mar 2 — fees collected, tips held for drivers"
  Assets:Checking                  827.25 USD
  Income:Delivery-Fees            -612.50 USD
  Liabilities:Driver-Tips-Payable -214.75 USD
 
2026-03-06 * "Driver payouts" "base plus incentives paid, tips passed through in full"
  Liabilities:Driver-Tips-Payable    214.75 USD
  Expenses:Delivery:Driver-Base-Pay  612.50 USD
  Expenses:Delivery:Driver-Incentives 85.00 USD
  Assets:Checking                   -912.25 USD

Read the tips account at any moment and it tells you what you owe drivers right now. If it ever carries a balance you cannot explain driver by driver, stop and reconcile before the next payout run.

3. Put every incentive condition in writing before the work starts​

Undisclosed bonus conditions were a standalone allegation, and they are the easiest one for a small business to replicate by accident — a verbal "finish ten deliveries and there's a bonus," with the zone restriction mentioned only when someone asks. Write every incentive down before the first qualifying job, with all of it:

• The exact amount or rate
• The qualifying actions (deliveries, hours, referrals, zone, store)
• The time window and the payout date
• Any cap, and what happens at the boundary (the eleventh delivery, the job finished one minute late)

Send it to the drivers in the same channel where they accept jobs, and keep a copy with its effective dates. When terms change, the new version gets a new effective date; the old version stays on file. "We always required the downtown zone" wins no argument without a dated document that says so.

4. Keep an adjustment log with reason codes​

Things legitimately change after acceptance: customers cancel stops, deliveries fail, genuine mistakes need correcting. The order allows for failed deliveries and cancellations. What it does not allow is silent change. Give every post-acceptance adjustment its own row:

• The job ID and driver, the original amount and the new amount
• A reason code: customer tip change, cancelled stop, failed delivery, correction of an earlier error
• Who recorded it and when

Then reconcile weekly: every payout ties back to an offer snapshot plus logged adjustments, and every adjustment ties to a payout. Orphan rows in either direction get investigated the same week, while the delivery details are still fresh and the driver still remembers the trip. This is the same discipline as reconciling card payouts gross-to-net — the deposit must equal the components — applied to people instead of a processor.

5. File the tax paperwork like the payer you are​

Good pay records do double duty at tax time, because the totals you report come straight from the same log:

• Collect a Form W-9 before the first payment, not in January when you are assembling filings. Without a correct taxpayer ID on file, you generally must backup-withhold 24 percent of reportable payments and send it to the IRS — a mess that starts with one missing form.
• Know the Form 1099-NEC threshold for the year you paid. For payments made in 2025, you file for any contractor paid $600 or more. For payments made on or after January 1, 2026, the One Big Beautiful Bill Act raised the federal threshold to $2,000 per contractor (inflation-adjusted starting in 2027) — but several states still require reporting at $600, so check yours before skipping anyone.
• Keep employment-tax records at least four years. That is the IRS retention floor, and driver-pay disputes do not respect shorter horizons; the Spark settlement reached back to January 2021.

Your per-driver payout log — base, incentives, and tips passed through — is what ties to the totals on each information return. If a driver ever questions a 1099 total, the same offer snapshots and adjustment rows that answer "why did I get less" answer that too.

6. Run your own earnings-verification check​

The order makes Walmart verify earnings under a named overseer with documented results and annual reports. Shrink that to your size: once a month, pull five payouts at random and reconstruct each one from offer snapshot to bank transfer. Confirm the driver received exactly what the accepted offer showed, plus any logged increases, minus only logged adjustments with valid reason codes. Write down what you checked and what you found — one paragraph per payout, dated, in the same folder as the logs.

Give the job to one person by name, even if that person is you. The point is not bureaucracy; it is that verification happens on a schedule instead of after a complaint. A year of monthly spot-checks is the document you most want to have if a driver disputes pay, a platform audits you, or a state attorney general's office comes asking how you know your drivers got what they were promised.

Start with five payouts​

You do not need a verification department to get most of this. This week, export last month's driver payouts, pick five at random, and reconstruct each one from the offer the driver accepted to the money that landed. Every gap you cannot close — a missing snapshot, an unexplained adjustment, a tip you cannot trace — is a record to start keeping. Close those five gaps and you have the system; the rest is habit.