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 · Transport

TPFREP Terminal performance

The UN/EDIFACT message terminal operators use to report the operations they carried out for a vessel, such as moves, hatch cover handling and times.

Sent by
Terminal operator
Received by
Shipping line or vessel operator
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT TPFREP message?

TPFREP is the UN/EDIFACT terminal performance message. The directory defines it as a message for transmitting information about operations carried out by terminal operators, such as loading, discharging and rehandling of containers or roll-on/roll-off items, hatch cover handling and related activities and times.

Shipping lines use the report to measure terminal productivity, check invoices for terminal services and compare performance between ports. It summarizes a vessel call in terms of moves, times and resources used. It covers both container and roll-on/roll-off operations.

How the EDIFACT TPFREP message worksDiagram of the UN/EDIFACT TPFREP Terminal performance message. Terminal operator sends it to shipping line or vessel operator. It usually follows COPRAR. It is usually followed by INVOIC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG1 loop with TDT (Transport information) and LOC (Place/location identification). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT TPFREP message worksTerminal performance: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCOPRARContainerdischarge/loadingorderTPFREPSENDERTerminal operatorRECEIVERShipping line or vesseloperatorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage TPFREPUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 1TDTTransport informationLOCPlace/location identification+ 2 conditional groups, starting with:EQDNADBlue 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 TPFREP. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT TPFREP message worksDiagram of the UN/EDIFACT TPFREP Terminal performance message. Terminal operator sends it to shipping line or vessel operator. It usually follows COPRAR. It is usually followed by INVOIC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG1 loop with TDT (Transport information) and LOC (Place/location identification). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT TPFREPmessage worksTerminal performance: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCOPRARContainer discharge/loading orderTPFREPSENDERTerminaloperatorRECEIVERShipping line orvessel operatorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message TPFREP (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 1TDTTransport informationLOCPlace/location identification+ 2 conditional groups, starting with:EQDNADBlue 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 TPFREP.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends TPFREP, 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 TPFREP 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 operations performed during a vessel call
  • Supporting terminal invoices
  • Measuring terminal productivity

Where it fits in the message flow

Usually follows COPRAR Container discharge/loading order
This message TPFREP Terminal performance
Usually followed by INVOIC Invoice

Structure

Mandatory segments in TPFREP (directory D.21A)

In UN/EDIFACT directory D.21A, the TPFREP message has 18 segment positions arranged in 6 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
  • SG1 (TDT)
  • UNT

Practical example

TPFREP in practice

After a vessel call, the terminal sends the shipping line a TPFREP with the number of containers discharged, loaded and restowed, hatch covers handled, crane hours and the start and end of operations. The line checks the terminal's invoice against the report and adds the call to its productivity benchmarks.

Implementation

Implementation considerations for TPFREP

  • Agree definitions of moves and time measurements.
  • Reconcile performance data with COARRI reports and invoices.
  • Report by vessel call with consistent references.
  • Use the data for benchmarking only with comparable definitions.

How ECOM helps

Automate TPFREP with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

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 transport messages

All 36 transport messages

Need help with TPFREP?

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

Request a Demo Contact us