π Prerequisites
Features
What you get with this outcome
Bookings Under Control, Start to Finish
From the moment a booking is confirmed to the day the traveler returns home, Kaptio keeps everything organized. Amendments with automatic repricing, payment schedules that update dynamically, cancellation policies that calculate fees correctly, and a complete audit trail of every change. Whether Bunnik is processing room changes, DuVine is collecting final payments, or Belmond is handling a cancellationβthe booking lifecycle flows smoothly.
Visual coming soon
amendment-flow-diagram
Booking Amendments
Modify bookings through Package Modificationsβchange rooms, add passengers, swap optional components, or adjust pre/post stays. The system recalculates pricing automatically, preserving original prices for unchanged services while applying current rates to new additions. Review all changes before committing.
- βPackage Modifications for structured changes
- βAutomatic price recalculation
- βPrice preservation for existing services
- βReview changes before commit
Visual coming soon
payment-collection-diagram
Payment Collection
Configure payment schedules per channel or packageβdeposit, progress payments, final balance. Collect payments via integrated gateways (KT Pay, BPAY, EWay), payment links, or manual entry. Pay per passenger or per itinerary. Automatic status conversion from Option to Confirmed on deposit.
- βFlexible payment schedules (%, fixed amount)
- βMultiple payment methods per channel
- βPayment links via content documents
- βAuto-conversion on deposit payment
Visual coming soon
cancellation-flow-diagram
Cancellation Handling
Process full booking, passenger, or service cancellations with policy-based fee calculation. The system applies configured cancellation terms automaticallyβpercentage or fixed fees based on days before travel. Override capability for exceptions with proper permissions.
- βFull/Passenger/Service cancellation types
- βPolicy-based fee calculation
- βOverride with permission control
- βSupplier cancellation tracking
Visual coming soon
refund-transfer-diagram
Refunds & Transfers
Process refunds as negative payments with full audit trail. Transfer funds between bookings when customers rebook. Handle bulk payment imports for bank transfers and external payment gateways. Complete financial visibility from collection through reconciliation.
- βRefund processing with audit trail
- βInter-booking fund transfers
- βBulk payment import capability
- βFailed payment tracking
Visual coming soon
Booking Audit Trail
Booking Audit Trail
Complete history of all booking changes with user attribution and timestamps. Track who changed what, when, and why. Essential for dispute resolution, compliance, and operational accountability.
- βFull change history tracking
- βUser and timestamp attribution
- βReason capture for changes
- βSearchable audit log
Visual coming soon
Booking Lock & Unlock
Booking Lock & Unlock
Lock bookings to prevent further changes after finalization. Only users with specific permissions can unlock for modifications. Prevents accidental changes to confirmed, operational bookings.
- βLock booking to prevent changes
- βPermission-based unlock capability
- βOperational booking protection
- βManager override with audit
Visual coming soon
Mass Passenger Operations
Mass Passenger Operations
Move passengers between departures when tours are cancelled or consolidated. Mass update passenger information, assign to new departures, and communicate changesβall in batch rather than one-by-one.
- βMass passenger transfer between departures
- βBatch information updates
- βDeparture consolidation support
- βBulk communication triggers
User Journey
Step-by-step flow from start to finish
πΊοΈUser Journey Flow
Follow the steps from start to finish
Implementation Plan
How to implement this outcome
π Project Overview
Payment Configuration
Week 1- β’ Configure payment schedules per channel
- β’ Set up payment methods and gateways
- β’ Configure pay-per-passenger vs. pay-per-itinerary
- β’ Set up payment link in content templates
Amendment & Cancellation
Week 2- β’ Configure cancellation policies per service
- β’ Set up Package Modifications workflow
- β’ Configure price preservation rules
- β’ Set up cancellation override permissions
Training & Launch
Week 3-4- β’ Create agent training materials
- β’ Train finance team on bulk imports
- β’ UAT with real amendment scenarios
- β’ Go-live with monitoring
Resources
Configs, tools, and documentation to help you
βοΈ Golden Configs
Payment Schedule Configuration
Configure deposit/progress/balance schedules with percentage or fixed amounts per channel or package
Cancellation Policy Configuration
Set up tiered cancellation fees based on days before travel with channel and service variations
Amendment Workflow Rules
Configure Package Modifications behavior, price preservation rules, and approval requirements
Booking Amendments
When customers need to change their bookings, Package Modifications provides a structured workflow.
Types of Amendments
| Amendment Type | Handled Via | Notes |
|---|---|---|
| Room changes | Package Modifications | Swap room types, change occupancy |
| Add/remove passengers | Package Modifications | Affects pricing and allocation |
| Optional components | Package Modifications | Add/remove activities, excursions |
| Pre/post stays | Package Modifications | Add/remove accommodation extensions |
| Add standalone services | Builder Tab | Flights, insurance, transfers |
| Date changes | Complex - may require new booking | Depends on availability |
Package Modifications Workflow
- Open Modify: From Builder tab, select package and click βModifyβ
- Review in Wizard: Booking Wizard opens with current configuration
- Make Changes: Adjust passengers, rooms, options, pre/post
- Review Pricing: System shows updated pricing with changes highlighted
- Commit or Reset: Apply changes to itinerary or cancel
Price Preservation
Kaptio preserves original prices for unchanged services:
- Existing service lines keep their original price
- New additions get current live pricing
- Removed services may trigger cancellation fees
Example: Customer booked Japan Discovery at $4,400. Six months later, they add a pre-stay hotel. The tour stays at $4,400 (original price), but the hotel is priced at todayβs rate.
Amendment Limitations
- No record lock: Two users can edit simultaneouslyβestablish process controls
- Cancellation fees not in wizard: Passenger/room cancellations with fees require separate cancellation process
- Documents donβt auto-regenerate: Agent must regenerate and resend after changes
Payment Collection
Kaptio supports flexible payment collection through multiple channels and methods.
Payment Schedule Configuration
Payment schedules define when payments are due:
| Component | Configuration Options |
|---|---|
| Deposit | Percentage or fixed amount, due on booking |
| Progress Payment | Percentage or fixed, due X days before travel |
| Final Balance | Remaining amount, due X days before travel |
Schedules can be set at:
- Channel level (default)
- Package level (override)
- Service level (specific rules)
- Itinerary level (exceptions)
Pay Per Passenger vs. Pay Per Itinerary
| Mode | Description | Best For |
|---|---|---|
| Pay Per Passenger | Each passenger has own payment schedule | Direct customers, households |
| Pay Per Itinerary | One payment schedule for entire booking | Trade partners, group bookings |
Configuration is set at Channel level with Account-level overrides available.
Payment Methods
| Method | Description |
|---|---|
| KT Pay | Integrated gateway (BPAY, EWay, cards) |
| Payment Link | Sent in content documents, customer self-service |
| Manual | Agent enters payment received via other channels |
| Bulk Import | Finance imports bank transfers, external gateways |
Payment Collection Flow
Option Status β Deposit Payment β Confirmed Status
Confirmed β Progress Payment β Balance Payment β Fully Paid
The system automatically converts Option to Confirmed when deposit is received.
Cancellation Handling
Cancellations can be processed at different levels with policy-based fee calculation.
Cancellation Types
| Type | Scope | Process |
|---|---|---|
| Full Booking | Entire itinerary | Cancellation button on itinerary |
| Passenger | Single passenger | Cancellation button β select passenger |
| Service | Individual service | Delete from Builder tab |
Cancellation Policy Application
Policies are configured per service with tiered fees:
| Days Before Travel | Cancellation Fee |
|---|---|
| 60+ days | 10% of booking value |
| 30-59 days | 25% of booking value |
| 15-29 days | 50% of booking value |
| 0-14 days | 100% of booking value |
The system calculates fees automatically based on:
- Days until travel start date
- Configured cancellation terms
- Service-specific policies
Fee Override
Users with the βCan Override Cancellation Percentageβ permission can adjust calculated fees. All overrides should be documented for audit purposes.
Cancellation Statuses
After cancellation:
| Confirmation Status | Meaning |
|---|---|
| Cancelled Manually | Was unconfirmed, no supplier action needed |
| Unconfirmed Cancellation | Requires supplier cancellation confirmation |
For supplier-confirmed services, a separate process handles supplier cancellation requests.
Refunds & Transfers
Processing Refunds
Refunds are recorded as negative payments:
- Navigate to Payments tab
- Add Manual Payment
- Enter negative amount
- Add notes documenting reason
- Save
For gateway-integrated payments, refund capability depends on the payment gateway. Some require manual processing outside Kaptio.
Fund Transfers
When a customer rebooks to a different tour:
- Process refund on original booking (negative payment)
- Apply payment to new booking
- Document the transfer relationship in notes
Best Practice: Use consistent naming conventions for transfers (e.g., βTransfer from ITN-00001234β).
Bulk Payment Import
For bank transfers and external payment gateways:
- Finance team prepares import file
- Upload via Data Import Wizard or custom application
- Payments are matched to bookings
- Manual reconciliation for unmatched amounts
Kaptio is productizing a bulk import solution to simplify this process.
Payment Reminders
Configure automated reminders for upcoming payments.
Reminder Configuration
Using Salesforce Flows, you can:
- Send reminder X days before payment due date
- Escalate if payment is overdue
- Create tasks for agents to follow up
Content Integration
Payment information can be included in content documents:
- Payment schedule with due dates
- Outstanding balance
- Payment link for self-service collection
Reporting
Key reports for booking lifecycle management:
Payment Reports
| Report | Purpose |
|---|---|
| Outstanding Payments | Amounts due by date |
| Payment Aging | Overdue payments by age |
| Collection by Method | Breakdown by payment type |
| Pay Per Passenger | Individual passenger balances |
Amendment Reports
| Report | Purpose |
|---|---|
| Recent Amendments | All changes in period |
| Price Adjustments | Bookings with price changes |
| Service Additions | Added services after booking |
Cancellation Reports
| Report | Purpose |
|---|---|
| Cancellation Summary | All cancellations with fees |
| Cancellation by Reason | Grouped by cancellation reason |
| Supplier Cancellations | Pending supplier confirmations |
Best Practices
For Amendments
- β Always review pricing before committing changes
- β Document reason for amendment in notes
- β Regenerate and resend documents after changes
- β Notify suppliers of material changes
For Payments
- β Send payment reminders before due dates
- β Process bulk imports daily for bank transfers
- β Reconcile payment reports weekly
- β Follow up on failed payments immediately
For Cancellations
- β Review calculated fees before processing
- β Document any fee overrides with reason
- β Process supplier cancellations promptly
- β Issue refunds within company SLA
Common Pitfalls
Avoid these implementation mistakes
Always document amendment reasonsβthey're needed for supplier reconciliation and audit trails
Process refunds promptlyβdelayed refunds generate customer complaints and chargebacks
Don't skip cancellation fee reviewβoverride without documentation creates revenue leakage
Missing payment schedule configurationβleads to incorrect due dates and collection timing
No record lock during Package Modificationsβtwo users can edit simultaneously causing conflicts
Forgetting to regenerate documentsβcustomers receive outdated information after amendments