Skip to main content
Top

Introduction to Trips

SoldoPlans_Enterprise_202407_R_EN.svg

WC_Trips_IntroScreen_202508_EN.webp

Trips makes business travel easier to plan, approve, and manage. Instead of requesting a lump sum, employees create an itemised request with all expected expenses, giving reviewers and finance teams clearer control and visibility. Once approved, funds are transferred directly to the traveller’s card. They can be sent in full straight away, or split so that pre-trip expenses (like flights and hotels) are funded immediately, while on-trip expenses (like meals or taxis) are sent at the start of the trip.

Why use Trips?

  • Plan ahead — capture flights, hotels, taxis, and other costs before travel begins.
  • Control spending — approve only what’s needed and split transfers between pre-trip and on-trip expenses.
  • Stay compliant — ensure requested spend is within policy, remove unused funds automatically, and block cards at the end of the trip.
  • Track with ease — transactions are linked to the Trip, making reporting simple.

Who can use Trips?

  • Employees — request funds for your own travel, or on behalf of someone else if you are a manager.
  • Managers — create Trip requests on behalf of your team.
  • Reviewers — approve or decline requests, adjust expense allocation, and set end-of-trip rules.
  • Admins and Super admins — configure workflows, create Trips manually, and manage funds and rules.

About the Trips feature

What is a Trip?

A Trip is a request created specifically for business travel in the Soldo web app. It allows employees, reviewers, and admins to manage travel budgets with greater clarity and control.

When creating a Trip request, the requester enters:

  • Title and destination
  • Start and end dates for the trip
  • Traveller and the card that will be used for the trip
  • An itemised list of expenses, each with:
    • Expense category or description of expense
    • Amount
    • Spend period: Before the trip (e.g. flights) or During the trip (e.g. meals)

What you can do with Trips

  • Request funds for a trip with an itemised list of expenses such as flights, hotels, and taxis.
  • Specify when expenses happen - before or during the trip. So funds can be sent at the right time.
  • Approve or decline requests with full visibility and the ability to adjust or add expenses.
  • Split transfers - send some money upfront for bookings, and the rest at the start of the trip.
  • Apply end-of-trip rules - automatically remove unused funds or block the card when the trip ends.
  • Create Trips on behalf of others as an Admin or Super admin.
  • Track and report on travel spend by linking transactions to Trips and filtering reports.

Approvals

Trip requests follow your company’s configured request workflow (single or multi-step). Reviewers can:

  • Approve or decline, with optional notes for the requester
  • Select the funding source for the trip (e.g. Main wallet or Company wallet)
  • Adjust or add expenses
  • Choose how to transfer money:
    • Approve in full — send all funds immediately
    • Split transfer — send pre-trip funds now and on-trip funds at the trip start date
  • Apply end-of-trip rules:
    • Unused funds: leave in the wallet or remove automatically
    • Card: keep active or block automatically

Note: End-of-trip rules trigger automatically 12 hours after the trip ends.

Assigning transactions

  • Transactions with an authorisation date between the Trip’s start and end dates are automatically assigned to that Trip.
  • From transaction details, users can reassign or unassign the Trip at any time.

Note: A transaction can only be linked to a Trip if its authorisation date falls between the Trip’s creation date and end date.

Manual Trip creation

Admins and Super admins can create a Trip directly without a user request:

  1. Go to the Trips section.
  2. Select Create trip.
  3. Enter the same details as a standard request, including traveller, traveller card, expenses and end-of-trip rules.

Getting started with trips

Read our step-by-step guides for using Trips:

SoldoPlans_Enterprise_202407_R_EN.svg

WC_Trips_IntroScreen_202508_EN.webp

Trips makes business travel easier to plan, approve, and manage. Instead of requesting a lump sum, employees create an itemised request with all expected expenses, giving reviewers and finance teams clearer control and visibility. Once approved, funds are transferred directly to the traveller’s card. They can be sent in full straight away, or split so that pre-trip expenses (like flights and hotels) are funded immediately, while on-trip expenses (like meals or taxis) are sent at the start of the trip.

Why use Trips?

  • Plan ahead — capture flights, hotels, taxis, and other costs before travel begins.
  • Control spending — approve only what’s needed and split transfers between pre-trip and on-trip expenses.
  • Stay compliant — ensure requested spend is within policy, remove unused funds automatically, and block cards at the end of the trip.
  • Track with ease — transactions are linked to the Trip, making reporting simple.

Who can use Trips?

  • Employees — request funds for your own travel, or on behalf of someone else if you are a manager.
  • Managers — create Trip requests on behalf of your team.
  • Reviewers — approve or decline requests, adjust expense allocation, and set end-of-trip rules.
  • Admins and Super admins — configure workflows, create Trips manually, and manage funds and rules.

About the Trips feature

What is a Trip?

A Trip is a request created specifically for business travel in the Soldo web app. It allows employees, reviewers, and admins to manage travel budgets with greater clarity and control.

When creating a Trip request, the requester enters:

  • Title and destination
  • Start and end dates for the trip
  • Traveller and the card that will be used for the trip
  • An itemised list of expenses, each with:
    • Expense category or description of expense
    • Amount
    • Spend period: Before the trip (e.g. flights) or During the trip (e.g. meals)

What you can do with Trips

  • Request funds for a trip with an itemised list of expenses such as flights, hotels, and taxis.
  • Specify when expenses happen - before or during the trip. So funds can be sent at the right time.
  • Approve or decline requests with full visibility and the ability to adjust or add expenses.
  • Split transfers - send some money upfront for bookings, and the rest at the start of the trip.
  • Apply end-of-trip rules - automatically remove unused funds or block the card when the trip ends.
  • Create Trips on behalf of others as an Admin or Super admin.
  • Track and report on travel spend by linking transactions to Trips and filtering reports.

Approvals

Trip requests follow your company’s configured request workflow (single or multi-step). Reviewers can:

  • Approve or decline, with optional notes for the requester
  • Select the funding source for the trip (e.g. Main wallet or Company wallet)
  • Adjust or add expenses
  • Choose how to transfer money:
    • Approve in full — send all funds immediately
    • Split transfer — send pre-trip funds now and on-trip funds at the trip start date
  • Apply end-of-trip rules:
    • Unused funds: leave in the wallet or remove automatically
    • Card: keep active or block automatically

Note: End-of-trip rules trigger automatically 12 hours after the trip ends.

Assigning transactions

  • Transactions with an authorisation date between the Trip’s start and end dates are automatically assigned to that Trip.
  • From transaction details, users can reassign or unassign the Trip at any time.

Note: A transaction can only be linked to a Trip if its authorisation date falls between the Trip’s creation date and end date.

Manual Trip creation

Admins and Super admins can create a Trip directly without a user request:

  1. Go to the Trips section.
  2. Select Create trip.
  3. Enter the same details as a standard request, including traveller, traveller card, expenses and end-of-trip rules.

Getting started with trips

Read our step-by-step guides for using Trips:

0 people voted. Sum of votes: 0