Quick Submit: when the right feature is the one that removes work

At Expedia, hotel partners invoice us after a guest’s stay. The process required partners to generate a CSV or Excel file containing all bookings for a period, formatted to our specification, then upload it through a portal. For a partner with a thousand bookings in a month, this was hours of manual work or custom automation they had to build themselves.

I was on the team rebuilding the backend invoice reconciliation process when I noticed the support queue. Frequent queries from partners asking why a booking was underpaid or rejected. Almost always a minor data error in the uploaded file: a date format slightly off, a total that did not match our records, a booking ID transposed.

We kept patching the processing pipeline to handle these edge cases gracefully. But the fixes were treating symptoms.

The real problem

I talked to the partner representatives about how partners actually generated these files. The larger chains had automated systems that pulled from their own databases. But smaller partners, hundreds of them, were manually copying booking data from our portal into spreadsheets, formatting it to spec, and uploading it back.

They were copying our data, reformatting it, and sending it back to us. We already had everything we needed.

The solution nobody asked for

There were business constraints that prevented a true “one-click pay me” button. Invoices had to exist as submitted files for audit and categorization purposes. But within those constraints, there was a simpler path.

I built Quick Submit: partners could filter their bookings by date range and other attributes, download the data pre-formatted to our invoice specification, and immediately re-upload that same file as their invoice. The round-trip was download, review, submit. Minutes instead of hours, with zero data entry errors because the data originated from our systems.

The results

Partner support issues related to invoicing dropped by over 95%. Partners who already had automated file generation switched to Quick Submit because it was simpler than maintaining their own tooling. The feature was adopted broadly and quickly became the default workflow.

The lesson that stuck with me: the best feature is often one that removes work rather than adding capability. We did not make the upload smarter. We made it unnecessary.