A corporate eSIM plan is a small product with a large admin surface. The traveler needs data. Finance needs one invoice. IT needs a clear device and support rule.
Use this checklist before you order for a team. It covers the buying model, the invoice, the phone rule, the data policy, and the pilot.
Start with the trip pattern
List the destinations, the trip length, the number of travelers, and how often the team travels. A team that flies to one region every month needs a different model from a team with rare long-haul trips.
Also list the phones. A team with a mix of eSIM phones and older phones needs both formats. A team with company phones needs the device owner and the unlock status.
Choose the buying model
- Bulk order: buy a set of plans before a trip or a quarter.
- Team eSIM vouchers: one code for each traveler, sent before departure.
- Labelled SIM packs: one pack for each phone without eSIM, handed over at the office.
- Team orders on one invoice: a list of travelers, one order, one invoice.
- API: connect the travel system or the expense tool.
Start with the model your team can run today. The corporate travel page shows a team invoice. The team orders use case shows the flow from the trip list to the invoice.
One invoice and cost centres
Finance needs a clear record. Put the cost centre, the trip, and the traveler on the order. Group the invoice by cost centre if the company uses them.
Ask:
- Who pays: the company, the department, or the traveler?
- Which cost centre gets the charge?
- Does the invoice need a purchase order number?
- Which currency is the invoice in?
- Who approves an extra eSIM order for a longer trip?
The invoice should show the plan, the format, the number of travelers, and the cost centre. It should not show card data.
Check the device rule
- Which phones support eSIM?
- Are the phones carrier locked?
- Who installs the eSIM: the traveler or IT?
- What is the fallback if the install fails?
- Does the company allow a second line on a company phone?
- Does the traveler keep the home line for calls?
A phone with eSIM gets a voucher. A phone with only a SIM slot gets a labelled SIM pack. A locked phone needs the carrier to unlock it before the trip.
Set the data policy
- Is the plan data-only?
- Do calls and messages stay on the company line?
- Which apps may use the travel data?
- Is personal use allowed?
- What happens when the plan runs out?
- Does a stay longer than 30 days get a new eSIM?
A data-only plan is simple for finance and IT. The traveler keeps the company line for calls. The plan is a separate data line, not a replacement for the company number.
Set the support path
- Who answers first: the travel manager, IT, or RoamWorks?
- How does the traveler report a failed install?
- Can support find the order by the traveler or the trip?
- Who approves a replacement?
- Who handles an unused pack or voucher?
- What is the response time during a trip?
Write the split into the agreement. A traveler who lands with no data should not wait for an office approval.
Run a pilot
Use one team, one route, and 10 to 30 travelers. Give the pilot a clear start and end date.
Check:
- The phone check and the format choice.
- The voucher or pack delivery.
- The install time.
- The first support case.
- The invoice and cost centre.
- The unused packs or codes.
Do not roll out to the whole company from one successful install. Use the pilot to find the support cases and the invoice errors.
Measure the result
Compare:
- Roaming cost before and after.
- Number of support tickets.
- Time to install.
- Data use per traveler.
- Admin time per trip.
- Unused packs or codes.
A lower data price is not a result if the support load doubles. A fast install and a clean invoice matter as much as the plan price.
Common mistakes
- No phone check before the order.
- One code for two travelers.
- No cost centre on the order.
- A data plan that replaces the company line by mistake.
- No support path after hours.
- No new eSIM for a stay longer than the plan.
- A pilot with no measures.
Sources and checked
- Apple Support, About eSIM on iPhone, checked 27 October 2026.
- European Commission, Roaming abroad, checked 27 October 2026.
- Information Commissioner's Office, UK GDPR guidance and resources, checked 27 October 2026.
- RoamWorks team order notes, checked 27 October 2026.
Talk to us about the team, the route, and the invoice. The contact page starts the fit call.