When to Use This Workflow
Use this workflow when any of the following apply:
- You are issuing a service fee without airline ticketing
- You prefer not to use the combined ticketing with service fee command (TKPSFP)
- You are issuing a service fee after tickets have already been issued
- You are processing any type of exchange
- You cannot use TKPSFP
If you are issuing a new airline ticket and service fee at the same time, see Issuing ARC/BSP Service Fees with Airline Tickets (TKPSFP) instead.
Important Rule (Do Not Skip)
When using this workflow:
DI.FT accounting must be entered before generating an invoice or MIR.
If DI.FT remarks do not exist before invoicing, the service fee will not interface correctly to Trams.
What This Workflow Does
This workflow creates an ARC or BSP service fee using the traditional SFP command and manually supplies the accounting information required for Trams.
Unlike TKPSFP:
- DI.FT accounting is required
- Invoicing depends on what exists in the PNR
Quick Steps
| IMPORTANT: Before issuing service fees, ensure the initial setup has been completed. |
| Action | Example | |
|---|---|---|
| 1 | Book air segments but do not issue ticket(s) | |
| 2 | Create service fee MCO using SFP format | SFPUSD50.00/LR |
| 3 | Retrieve the PNR and create service fee free-text (DI-FT) accounting remark. | DI.FT-MS90A*ALXD*TK0000000000*TCSERVICE FEE*TF50.00*CM96.5*PNSMITH/JOHN |
| 4 | Enter form of payment | DI.FT-MS90*FPVI4444333322221111 |
| 5 |
Generate invoice and MIR
|
TKP TKPDIDAD |
Step-by-Step Instructions
Step 1 — Issue the Service Fee
Create the service fee using the SFP command.
Format
SFP(currency)(amount)/LR
Example
SFPUSD50.00/LR
The /LR option creates the required paid and due segments in the PNR.
Step 2 — Add DI.FT Accounting Information
Retrieve the PNR and enter the free-text accounting remark.
Format
DI.FT-MS(ms#)A*AL(airline code)*TK(MCO number)*TT(travel type)*TF(amount)*CM(commission)
Example (ARC)
DI.FT-MS90A*ALXD*TK0000000000*TT11*TF50.00*CM96.5
Key Notes
- Each service fee must use a unique MS number
- First fee: MS90
- Second fee: MS91
- Airline code:
- ARC: ALXD
- BSP: ALXB
- If the commission is already defined in the Trams vendor profile, *CM may be omitted.
Step 3 — (Optional) Override Form of Payment
If the service fee was paid using a different method than the PNR form of payment, add a second DI.FT line. This information must be included when invoicing a service fee with an even exchange.
Format
DI.FT-MS(ms#)*FP(payment method)
Example
DI.FT-MS90*FPVI4444333322221111
Step 4 — Generate Invoice and MIR
Choose the correct command based on the PNR contents.
If issuing airline tickets:
TKP
If not issuing airline tickets:
TKPDIDAD
If adding a service fee after ticketing
TKPDIDAD/SNONE
- Requires at least one non-air (auxiliary) segment
Special Scenarios
Service Fee-Only PNR
When the PNR contains only a service fee:
- A placeholder tour segment is required
- Use:
TKPDIDAD
Multiple Service Fees
- Each fee must use a different MS number
- Accounting lines must remain sequential
Example:
First service fee using MS line number 90:
DI.FT-MS90A*ALXD*TK089000101*TT11*TF35.00*CM96.5
DI.FT-MS90*PNSMITH/JOHNSecond service fee using MS line number 91:
DI.FT-MS91A*ALXD*TK089000102*TT11*TF35.00*CM96.5
DI.FT-MS91*PNSMITH/JANEWhat You Will See in Trams
- Service fee appears as an ARC/BSP transaction
- Commission applied according to vendor setup
- Invoice behavior depends on whether tickets are present
Common Mistakes
- Entering DI.FT accounting after invoicing → Service fee will not interface
- Reusing the same MS number for multiple fees → Accounting conflicts in Trams
- Using TKPSFP during exchanges → Service fee will not interface