Audience
- Agency administrators
- Accounting / back-office staff
- Implementation and support teams
This article explains the required Trams and Travelport+ configuration for service fees and how those settings affect agent workflows.
What This Setup Controls
Correct setup determines:
- Whether service fees interface correctly to Trams
- How commissions are calculated
- Whether tickets and service fees appear on the same invoice
- Why certain MIR warnings appear (and when they are normal)
Agents generally do not need to see or change these settings.
Trams Vendor Setup
ARC Service Fee Vendor
Create a vendor profile with the following values:
- Interface ID: XD
- Airline Number: 890
- Commission (recommended): 96.5%
Why 96.5%? ARC assesses a 3.5% processing fee on most service fees. Setting the commission to 96.5% results in the net amount posting correctly in Trams.
BSP Service Fee Vendor
Create a separate vendor profile with:
- Interface ID: XB
- Airline Number: 954
- Commission (recommended): 96.5%
Supplier (Non-ARC/BSP) Service Fee Vendor
Create a vendor profile for non-ARC/BSP fees:
- Interface ID: Any unused value (commonly SVCFEE)
- Airline Number: Not required
- Commission (recommended): 100%
Why 100%? Supplier service fees are retained entirely by the agency.
Travel Types (TT)
Service fees must use a valid Trams travel type.
- The default travel type for service fees is typically 11
- Confirm your agency’s value in:
- Utilities → Setup → Travel Types
Agents must use the same TT number consistently in DI.FT accounting.
Travelport+ MIR Configuration
Verify MIR Options
Enter:
MMOD
Confirm:
- MISC DOCS = Y
MPD Setting (Critical)
Enter:
MMTD
Locate the MPD field.
MPD = S vs MPD = N
MPD = S (Recommended for Most Agencies)
What it enables
- Automatic interfacing when agents use TKPSFP
- Ticket(s) and service fee interface to the same Trams invoice
What to expect
- Standalone service fees (SFP) generate two MIR records:
- When the fee is issued (no segments)
- When the invoice is generated
You may see the warning:
Error: Invoice Contains No Segments, Record Ignored
✅ This is expected behavior ✅ The service fee interfaces correctly on the second MIR
MPD = N
What it means
- TKPSFP cannot be used
- All service fees must be issued using SFP + DI.FT
- Agents must always use the service fee SmartButton or manual steps
When this may be preferred
- Agencies that never issue service fees with ticketing
- Agencies that want to avoid MIR warnings entirely
MPD Decision Summary
| Your Agency’s Workflow | Recommended MPD |
|---|---|
| Fees usually issued at ticketing | MPD = S |
| Mix of ticketed and standalone fees | MPD = S |
| Fees always issued separately | MPD = N |
Most agencies choose MPD = S to reduce agent steps and align with modern Travelport+ workflows.
What Agents Might Report (And Why It’s Normal)
“I saw an error saying no segments were found”
- Occurs when MPD = S and a standalone SFP fee is issued
- The first MIR is ignored
- The second MIR interfaces correctly
No action is required.
“My service fee didn’t interface”
Most common causes:
- DI.FT accounting entered after invoicing
- Incorrect vendor profile (wrong Interface ID)
- MPD setting does not match workflow used
What This Article Does NOT Cover
- Step-by-step agent commands
- Exchange procedures
- DI.FT field-level reference
Those topics are covered in linked articles below.