Moways Expense Reimbursement

Problem it addresses

Expense reimbursement often breaks down when invoices, payments, itineraries, and personnel do not line up: a train ticket may not belong to the payer, a hotel invoice may lack a folio, ride-hail screenshots may not match invoices, or a meal cannot be tied to a person. Moways Expense Reimbursement treats these as hard gates: it will not pull mail until the date range, team members, and reimbursement owner are confirmed, and it blocks Excel export and packaging when the user or payer is missing, outside the project team, or insufficiently evidenced.

How it works

The skill runs a fixed pipeline:
- Confirm DATE_FROM, DATE_TO, TEAM_MEMBERS, and REIMBURSEMENT_OWNER before collection.
- Collect rail, airline, hotel, ride-hail, and meal invoices from mail and supplier platforms, then check for missed tickets.
- Parse passenger names, order IDs, check-in dates, and trip dates while keeping user and payer separate.
- Reconcile against payment records, ride-hail screenshots, and order reminders, with a default payment window from 45 days before to 7 days after the trip.
- Generate reconciliation_passed.json, then write the fixed-column Excel file and package files using YYYYMMDD_category_issuer_document_type.pdf.

Boundary: it does not issue invoices, modify invoices, or submit to finance systems. Ambiguous company ownership, missing hotel folios, multiple payment candidates, or unclear user/payer evidence will block completion. It fits teams with clear project ownership and a designated reimbursement lead that want auditable reimbursement evidence.