App: [HOLD for payment 2023-10-23] 🟡 [$500] Add stylized receipts for distance requests

One thing I think we need to re-visit now that we shipped distance v1 is the receipt. For instance, this was recommended in the original design doc, though during the review process it was deemed unnecessary.

I think in hindsight that decision hasn’t turned out to be a great one. Reason being, you have to kind of deduce what the points on the map are, so what is point A and what is point B. For SBE, it was somewhat easy since the event looks like it was close to the Burbank airport? But yeah, I think a core part of mileage is knowing where someone went, whether it’s from A to B, or A to B to C.

As a result, I think we need to:

• Utilize the stylized receipt pattern that we’ve settled on for eReceipts
• Apply the same foundational styling for distance request
• Print the sum of a user’s Start, Stop, and Finish way points, each on their own row
• All while still showing the core information about the request, such as amount, date and distance merchant.

I’m going to assign the internal label, as this is dependent on related internal initiatives and Expensify employees have the most context. We can involve external as soon as the scope and todos are clear.

cc distance project team @neil-marcellini @hayata-suenaga @arosiclair @trjExpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b483120a2e8ed4dd
• Upwork Job ID: 1700221182911156224
• Last Price Increase: 2023-09-11