972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Travel and tourism

STLRPT Settlement transaction reporting

The UN/EDIFACT message exchanged between participants in a billing and settlement plan to report transaction data for processing and settlement.

Sent by
Billing and settlement plan participant, such as a reservation system or processing center
Received by
Other participants, such as airlines and agents
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT STLRPT message?

STLRPT is the UN/EDIFACT settlement transaction reporting message. The directory defines it as a message exchanged between participants in the Billing and Settlement Plan (BSP) to report transaction data for processing and account settlement. Participants include airlines, agents, computer reservation systems and the processing centers.

In a billing and settlement plan, travel agents sell tickets for many airlines and settle with all of them through one process. Sales and refund transactions are reported to a processing center, which bills agents and pays airlines.

How the EDIFACT STLRPT message worksDiagram of the UN/EDIFACT STLRPT Settlement transaction reporting message. Billing and settlement plan participant, such as a reservation system or processing center sends it to other participants, such as airlines and agents. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), DTM (Date/time/period) and NAD (Name and address) and body and segment groups: the required SG2 loop with DTM (Date/time/period) and the required SG4 loop with RFF (Reference), the required SG6 loop with BUS (Business function) and the required SG8 loop with LIN (Line item) and CNT (Control total). 7 conditional segment groups are listed by their trigger segment.How the EDIFACT STLRPT message worksSettlement transaction reporting: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSTLRPTSENDERBilling and settlementplan participant, suchas a reservationsystem or processingcenterRECEIVEROther participants,such as airlines andagentsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage STLRPTUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodNADName and addressBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 9DTMDate/time/periodMandatory group SG4 · repeats many timesRFFReferenceMandatory group SG6 · repeats up to 99BUSBusiness functionMandatory group SG8 · repeats many timesLINLine itemCNTControl total+ 7 conditional groups, starting with:CUXDOCPYTGIRBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for STLRPT. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT STLRPT message worksDiagram of the UN/EDIFACT STLRPT Settlement transaction reporting message. Billing and settlement plan participant, such as a reservation system or processing center sends it to other participants, such as airlines and agents. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), DTM (Date/time/period) and NAD (Name and address) and body and segment groups: the required SG2 loop with DTM (Date/time/period) and the required SG4 loop with RFF (Reference), the required SG6 loop with BUS (Business function) and the required SG8 loop with LIN (Line item) and CNT (Control total). 7 conditional segment groups are listed by their trigger segment.How the EDIFACT STLRPTmessage worksSettlement transaction reporting: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSTLRPTSENDERBilling andsettlement planparticipant,such as areservationsystem orprocessingcenterRECEIVEROtherparticipants,such as airlinesand agentsCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message STLRPT (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodNADName and addressBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 9DTMDate/time/periodMandatory group SG4 · repeatsmany timesRFFReferenceMandatory group SG6 ·repeats up to 99BUSBusiness functionMandatory group SG8 ·repeats many timesLINLine itemCNTControl total+ 7 conditional groups, starting with:CUXDOCPYTGIRBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for STLRPT.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends STLRPT, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around STLRPT and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Reporting ticket sales and refunds for settlement
  • Distributing billing data to airlines
  • Reconciling agents' sales with settlements

Where it fits in the message flow

This message STLRPT Settlement transaction reporting

No other message routinely comes directly before or after STLRPT; it is exchanged when the business event occurs. If the partners agree, the receiver confirms each interchange with a CONTRL syntax and service report.

Structure

Mandatory segments in STLRPT (directory D.21A)

In UN/EDIFACT directory D.21A, the STLRPT message has 65 segment positions arranged in 12 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • NAD
  • SG2 (DTM)
  • UNT

Practical example

STLRPT in practice

A reservation system reports the tickets issued by its travel agency users during a reporting period. The processing center aggregates the transactions, produces agents' billings and airlines' settlement data, and each airline reconciles the settlement with its own sales records.

Implementation

Implementation considerations for STLRPT

  • Follow the current settlement plan specifications, which may use formats other than EDIFACT.
  • Reconcile reported transactions with ticketing records.
  • Report refunds and exchanges as well as sales.
  • Meet the reporting calendar of the settlement plan.

How ECOM helps

Automate STLRPT with ECOM

Industry

Hospitality

Procurement, invoicing and supplier integration for hotels, restaurant groups and foodservice suppliers.

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related travel and tourism messages

All 16 travel and tourism messages

Need help with STLRPT?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us