What changed
Confirm organizational activation, match the transaction identity, amount and currency, then resolve duplicates and exceptions. The 43.00 USD reference total below is a reproducible teaching calculation, not a real Waymo or Ramp transaction, price quotation or performance test.
The change is in the handoff after a ride
In Waymo’s original announcement, the update connects ride receipts to the corresponding Ramp expense for organizations already using Ramp, reducing manual searching, uploading and attaching. The event date is October 28, not this article’s publication date.
The practical decision is which manual handoff the connection replaces and who will handle exceptions. The review method below is editorial guidance. It does not describe a matching algorithm published by either company.
Confirm activation and trip availability separately
Waymo’s integration page provides a contact route for organizations to sign up or activate Ramp. The announcement does not establish that your organization has already enabled it. Follow your existing internal process before entering employee information into a new workflow.
An expense connection also does not establish that the planned trip is available. Confirm the actual origin and destination in the service. The separate city-access and airport-trip checks explain why a city launch is insufficient evidence for a particular pickup or drop-off.
Who confirms each part?
Organization administrator
Confirm the business account, Ramp connection and required permissions, with a named owner for activation problems.
Travel arranger
Verify the real route and travel plan. Expense connectivity is not evidence that a specific trip can be booked.
Expense reviewer
Choose the transaction identity, currency and status used for review, and define which differences require a person to investigate.
Three export rows need not represent three expenses
The identifiers, amounts and errors below are fictional teaching material created for this article. They are not a Ramp export specification or an observed system failure. Assume an internal handoff sheet uses a transaction identifier for posted expenses in one currency, with receipt amounts and export provenance retained separately.
The first row agrees. The second has a 1.00 USD attachment difference requiring investigation. The third repeats the same transaction identifier: check for a repeated import before concluding that a second ride occurred.
| Transaction ID | Expense amount | Receipt amount | Initial action |
|---|---|---|---|
| trip-A101 | 24.60 | 24.60 | Amount agrees; continue business-purpose review |
| trip-A102 | 18.40 | 19.40 | Difference 1.00; keep as an exception |
| trip-A102 | 18.40 | 19.40 | Repeated identifier; inspect import provenance |
Reproduce 43.00 instead of 61.40
Under the case’s explicit assumptions—one currency, posted expenses and stable identifiers—the two unique expenses are 24.60 and 18.40, totaling 43.00. Adding all three rows produces 61.40 and counts 18.40 twice. This is a teaching example of duplicate rows, not evidence that the integration duplicates charges.
Keeping one receipt amount for each unique transaction gives 24.60 + 19.40 = 44.00, which exceeds the expense total by 1.00. Retain the 43.00 expense baseline, flag trip-A102 and leave approval unresolved. Editing both sides until the totals agree would erase the question that needs investigation.
Without a stable transaction identifier, do not delete rows merely because the date and amount match. Two genuine trips can cost the same. Check source records and use the composite-key and blank-field review to decide which evidence fields your own handoff needs.
Reference answer for the fictional case
24.60 + 18.40 + 18.40 = 61.40 USD
Unique expenses:24.60 + 18.40 = 43.00 USD. trip-A102 receipt difference:19.40 − 18.40 = 1.00 USD.
Pilot a complete section of the workflow
As an editorial recommendation, choose a bounded expense period whose source records can be traced, using your organization’s existing permissions. A screenshot showing an attached document is not a complete acceptance result. Follow the expense through to the record a reviewer can actually confirm.
Keep the pilot’s scope, dates and exception outcomes. One successful record does not establish success for every employee, route or expense status. When amounts differ, preserve the transaction and receipt rather than adjusting values to create an artificial match.
Four questions to close the pilot
- Has the administrator confirmed activation and a responsible owner?
- Can sampled expenses be traced to their receipts, with identity, amount and currency agreeing?
- Can a repeated import be distinguished from two genuine expenses of the same amount?
- Do unmatched or inconsistent records enter an exception queue rather than becoming implicitly approved?
Confirm the scope beyond the announcement
The announcement establishes an easier receipt handoff. This article does not infer coverage for every refund, adjustment, historical trip or third-party expense. Ask the provider about the actual configuration and processing rules. We did not sign in to an enterprise account, take a test ride or execute an approval process.
If your organization does not already use Ramp, assess the fit with its travel process before changing systems. Route availability and unclear spending rules remain separate adoption questions; automatic attachments do not settle them.
Common questions
Does an automatically attached receipt mean an expense is approved?
Attachment alone does not establish approval. Follow organizational rules for purpose, identity, amounts and exceptions, with the appropriate authorized reviewer. This article does not set a reimbursement policy for any organization.
Should one of two equal-value rows be deleted?
Check the transaction identity and original source first. Equal amounts do not establish a shared transaction. The example flags the third row because the scenario explicitly supplies the same identifier and a repeated-import context.
