# Map the work behind one travel booking

This is an editable responsibility map for a buying discussion. It describes handoffs to investigate, not integrations claimed to exist in a named product. Confirm the actual system, person and exception process for every arrow.

```mermaid
flowchart TD
    W["Website booking"] -->|"Reservation details"| M["Operational record"]
    S["Adviser or supplier booking"] -->|"Import or manual entry"| M
    M -->|"Agreed customer information"| D["Customer documents"]
    M -->|"Transaction data"| A["Accounting"]
    A -->|"Reconciliation findings"| M
```

## Assign the responsibility

| Work | System used | Owner | What triggers an exception | How completion is checked |
|---|---|---|---|---|
| Record each supplier confirmation and reference | | | | |
| Keep traveller and lead-customer details accurate | | | | |
| Distinguish started, pending and confirmed components | | | | |
| Record supplier cost, customer price and charges | | | | |
| Send the correct customer document | | | | |
| Transfer required transaction data to accounting | | | | |
| Match customer receipts and supplier liabilities | | | | |
| Trace a refund through both operational and financial records | | | | |

Travelify's published product scope states that it works alongside accounting rather than replacing it. Ask for the sample export or the actual proposed connection before deciding that a handoff is covered.

Source checked 18 October 2026: https://www.travelgenix.io/what-we-do/travelify