The setting
is a transportation platform that connects riders with rideshare, bikes, scooters and other ways to get around. is software that lets companies provide ride benefits and manage rides for employees or customers.
Receipt retries protect delivery while duplicate records undermine expense reporting.
The integration must recover from slow provider responses without turning one completed ride into two expense records.
Who you’d be doing this for
“Finance asked why one airport ride showed up twice, and I had to pull the trip apart by hand.”
Larisa Szymanski · Corporate Travel Manager · a character in this brief
Administers a Business Travel program whose employees submit ride receipts through Concur.
What is at stake
Concur users receive duplicate receipts for a single business ride after delayed responses. You must choose between an idempotency guard in delivery and a narrower retry change that preserves existing behavior.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- duplicate prevention vs receipt timeliness
- narrow rollback vs durable delivery semantics
- provider uncertainty vs reliable expense records
Why Lyft
Business Travel depends on reliable Concur receipt delivery to keep company-sponsored rides visible in corporate expense workflows.
Written with these in mind
Not your kind of problem? 73 more at Lyft, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Lyft. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Staff Software Engineer, Lyft Business (opens in a new tab)
- From the foundational mechanics of a company funding and provisioning a ride to the tailored workflows that get an employee to a client meeting or home after a late shift, we sweat the small stuff to make Lyft the transportation solution businesses build their programs on.
- Engineering Manager, Lyft Business (opens in a new tab)
- Senior Software Engineer, Lyft Business (opens in a new tab)
- The Business Travel team enable organizations to provide customized ride benefits at scale - whether that's employees expensing business trips and earning rewards.
- As a backend engineer, you'll build systems that power complex benefit rules, location restrictions, and integrations with expense providers like Concur and Expensify.
Reporting read before this brief was written
The pieces closest to the situation in this brief.
A Business Travel Show America session page dated 2 September 2026 says that employees who book through personal app accounts and submit manual receipts make ground spend nearly invisible to finance teams, and names Lyft Business among the centralized platforms meant to prevent this.
Modernizing Ground Transportation Policy Oversight - Business Travel Show America 2026 (opens in a new tab) · businesstravelshowamerica.com · Sep 2, 2026
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about money moving incorrectly, late, or twice.
One card purchase can produce two expense records after a receipt correction.
You must protect fast matching without letting policy and accounting work split across duplicates.
Duplicate refunds reached 0.34% of canceled orders during a six-hour spike.
You have to weigh a quick workflow change against preserving every valid payment retry.
Shoppers receive duplicate order updates after WhatsApp delivery succeeds.
You must stop the extra SMS without delaying real fallbacks.
The same setting, from another role
Each is set around Lyft’s Lyft Business, written for a different role. They’re separate briefs, not the same scenario.
Enterprise sellers are rebuilding call context while buyers ask different questions about controls and spend visibility.
You have to decide what AI extracts, what sellers verify, and what never enters Salesforce unchecked.
Multinational travel managers are planning European ground programs while incumbent suppliers already hold much of that spend.
You must weigh an early partner commitment against promises the first package cannot reliably make.
A $2 million corporate travel program is at risk after executive-transfer costs spiked during a board meeting week.
You must weigh durable revenue against the pricing and service commitments that can survive scrutiny.
Other problems with a similar purpose
In each of these, as in this one, the aim is to trace a strange, repeatable failure back to its root cause and leave behind a fix that quietly holds.
Completed repeated assay tasks remain open in Worklists after their workflow record closes.
You must weigh a fast status correction against preserving the execution history reviewers rely on.
Amended container bookings can hold uploaded documents in the Document Platform while customers see none in the Client Application.
You have to weigh a quick recovery against preserving document access boundaries.
6.8% of completed audio jobs now wait more than ten minutes for a Flow status.
You must weigh a targeted retry correction against a rollback that restores speed but removes newer recovery behavior.
