HL7 FT1 Segment: Financial Transaction
The HL7 FT1 segment (Financial Transaction) carries charge line-item details — procedure codes, amounts, performing provider, and diagnosis linkage. It repeats within DFT messages for each charge, forming the core of healthcare charge posting interfaces between clinical systems and revenue cycle management platforms.
FT1 Field Reference
Section titled “FT1 Field Reference”| Seq | Name | Type | Opt | Description |
|---|---|---|---|---|
FT1-1 | Set ID | SI | O | Sequence number (1, 2, 3...) |
★ FT1-2 | Transaction ID | ST | O | Unique charge identifier |
| Used for duplicate charge detection and charge-credit pairing. Credit reversals reference the original transaction ID. | ||||
FT1-3 | Transaction Batch ID | ST | O | Groups transactions for batch posting |
★ FT1-4 | Transaction Date | DR | R | Date/time range of service |
FT1-5 | Transaction Posting Date | TS | O | When the charge was posted |
★ FT1-6 | Transaction Type | IS | R | CG (Charge), CR (Credit), PA (Payment) |
| CG=Standard charge, CR=Charge reversal/credit (negative amount), PA=Payment, AJ=Adjustment, CO=Co-payment. | ||||
★ FT1-7 | Transaction Code | CE | R | CPT/HCPCS procedure code |
| Original procedure code field (v2.1+). Many interfaces also populate FT1-25. When both present, FT1-25 takes precedence. | ||||
FT1-8 | Transaction Description | ST | O | Human-readable charge description |
FT1-9 | Transaction Description (Alt) | ST | O | Alternate description |
★ FT1-10 | Transaction Quantity | NM | O | Number of units |
★ FT1-11 | Transaction Amount (Extended) | CP | O | Total charge amount |
FT1-12 | Transaction Amount (Unit) | CP | O | Per-unit charge amount |
★ FT1-13 | Department Code | CE | O | Originating department (ED, LAB, RAD) |
| Used to route charges: professional component (-26 modifier) to physician billing, technical component (-TC) to facility billing. | ||||
FT1-14 | Insurance Plan ID | CE | O | Associated insurance plan |
FT1-15 | Insurance Amount | CP | O | Amount covered by insurance |
FT1-16 | Assigned Patient Location | PL | O | Patient location at time of service |
FT1-17 | Fee Schedule | IS | O | Fee schedule used for pricing |
FT1-18 | Patient Type | IS | O | Inpatient, outpatient, etc. |
★ FT1-19 | Diagnosis Code (FT1) | CE | O | ICD-10 diagnosis for this charge |
| Directly impacts claim adjudication. Diagnosis must support medical necessity for the procedure code. Mismatches are a leading cause of claim denials. | ||||
★ FT1-20 | Performed By Code | XCN | O | Provider who performed the service |
★ FT1-21 | Ordered By Code | XCN | O | Provider who ordered the service |
FT1-22 | Unit Cost | CP | O | Per-unit cost |
FT1-23 | Filler Order Number | EI | O | Order number from fulfilling system |
FT1-24 | Entered By Code | XCN | O | Person who entered the charge |
★ FT1-25 | Procedure Code | CE | O | CPT code (v2.3+ preferred over FT1-7) |
| Preferred procedure code field in v2.3+. Takes precedence over FT1-7 when both are populated. | ||||
★ FT1-26 | Procedure Code Modifier | CE | O | CPT modifiers (repeating) |
| Modifiers affect claim adjudication: -26 (professional component), -TC (technical), -59 (distinct service). Sequenced by billing importance. Incorrect modifiers are a leading cause of denials. | ||||
FT1-27 | Advanced Beneficiary Notice | CE | O | ABN indicator |
FT1-28 | Medically Necessary Dup Proc | CWE | O | Medical necessity documentation |
FT1-29 | NDC Code | CWE | O | National Drug Code (pharmacy) |
FT1-30 | Payment Reference ID | CX | O | Payment/remittance reference |
FT1-31 | Transaction Reference Key | SI | O | Key for linking related transactions |
★ FT1-2 O Unique charge identifier
Used for duplicate charge detection and charge-credit pairing. Credit reversals reference the original transaction ID.
★ FT1-6 R CG (Charge), CR (Credit), PA (Payment)
CG=Standard charge, CR=Charge reversal/credit (negative amount), PA=Payment, AJ=Adjustment, CO=Co-payment.
★ FT1-7 R CPT/HCPCS procedure code
Original procedure code field (v2.1+). Many interfaces also populate FT1-25. When both present, FT1-25 takes precedence.
★ FT1-13 O Originating department (ED, LAB, RAD)
Used to route charges: professional component (-26 modifier) to physician billing, technical component (-TC) to facility billing.
★ FT1-19 O ICD-10 diagnosis for this charge
Directly impacts claim adjudication. Diagnosis must support medical necessity for the procedure code. Mismatches are a leading cause of claim denials.
★ FT1-25 O CPT code (v2.3+ preferred over FT1-7)
Preferred procedure code field in v2.3+. Takes precedence over FT1-7 when both are populated.
★ FT1-26 O CPT modifiers (repeating)
Modifiers affect claim adjudication: -26 (professional component), -TC (technical), -59 (distinct service). Sequenced by billing importance. Incorrect modifiers are a leading cause of denials.
R = Required, O = Optional, C = Conditional, W = Withdrawn (backward compatibility only)
FT1-6: Transaction Type Codes
Section titled “FT1-6: Transaction Type Codes”| Code | Meaning | Description |
|---|---|---|
| CG | Charge | Standard charge posting for a service rendered |
| CR | Credit | Charge reversal or credit adjustment |
| PA | Payment | Payment received (patient or payer) |
| AJ | Adjustment | Billing adjustment (contractual, write-off) |
| CO | Co-payment | Patient co-pay collected at point of service |
| DE | Deposit | Advance deposit or prepayment |
Charge-Credit Pairing
Section titled “Charge-Credit Pairing”When reversing a charge, a CR transaction must reference the original CG transaction:
FT1|1|CHG001||202603011415||CG|99284^ED Visit Level 4^CPT||||350.00FT1|2|CHG001-R||202603021000||CR|99284^ED Visit Level 4^CPT||||-350.00The credit amount is negative, and FT1-2 typically references the original transaction ID with a suffix (e.g., -R for reversal). This pairing ensures the billing system can net the transactions correctly.
FT1-7 / FT1-25: Procedure Coding
Section titled “FT1-7 / FT1-25: Procedure Coding”HL7 v2 has two fields for procedure codes due to version evolution:
| Field | Version | Data Type | Usage |
|---|---|---|---|
| FT1-7 | v2.1+ | CE | Original procedure code field — widely populated |
| FT1-25 | v2.3+ | CE | Preferred procedure code field — supports CPT components |
Most modern interfaces populate FT1-25 as the primary code and FT1-7 for backward compatibility. When both are present, FT1-25 takes precedence.
FT1|1||...|CG|99284^ED Visit Level 4^CPT|...|||||||||||||||99284^ED Visit Level 4^CPT|26^Professional Component^CPTMLCommon CPT Code Patterns
Section titled “Common CPT Code Patterns”| Category | CPT Range | Examples |
|---|---|---|
| E/M (Evaluation & Management) | 99201-99499 | 99213 (office visit), 99284 (ED level 4) |
| Surgery | 10000-69999 | 47562 (lap cholecystectomy) |
| Radiology | 70000-79999 | 71046 (chest x-ray 2 views) |
| Pathology/Lab | 80000-89999 | 85025 (CBC with diff) |
| Medicine | 90000-99199 | 93000 (ECG), 96372 (injection) |
FT1-26: Modifier Handling
Section titled “FT1-26: Modifier Handling”CPT modifiers in FT1-26 affect how payers adjudicate claims. FT1-26 repeats for multiple modifiers:
| Modifier | Meaning | Impact |
|---|---|---|
| -26 | Professional component only | Splits technical/professional billing |
| -TC | Technical component only | Facility charges only |
| -59 | Distinct procedural service | Overrides bundling edits |
| -25 | Significant, separately identifiable E/M | Allows E/M + procedure same day |
| -LT | Left side | Anatomic modifier |
| -RT | Right side | Anatomic modifier |
| -76 | Repeat procedure, same physician | Same procedure repeated |
| -77 | Repeat procedure, different physician | Same procedure, different provider |
| -XE | Separate encounter | Distinct encounter modifier |
Modifiers are sequenced by importance — the first modifier has the most significant billing impact. Incorrect modifier assignment is one of the leading causes of claim denials.
Key Implementation Considerations
Section titled “Key Implementation Considerations”Duplicate Charge Detection
Section titled “Duplicate Charge Detection”DFT interfaces must prevent duplicate charges from reaching the billing system:
- Match on FT1-2 (Transaction ID) + FT1-4 (Date of Service) + FT1-7/25 (Procedure Code) + PID-3 (MRN)
- Some systems generate the same DFT message during retransmission — use MSH-10 deduplication at the interface level
- Late-posted charges may appear days after the encounter — timestamp-based windows must account for this lag
Late Charge Processing
Section titled “Late Charge Processing”Charges posted after the initial billing cycle require special handling:
- Late charge flag: Some implementations add a custom Z-field or OBX note indicating a late charge
- Billing hold: Late charges may trigger a billing hold until reviewed by revenue cycle staff
- Account status check: If the account is already billed or closed, late charges may need to open a new claim or trigger a rebill
Institutional vs Professional Billing
Section titled “Institutional vs Professional Billing”Healthcare facilities submit two types of claims for the same patient encounter:
| Claim Type | Form | Content | FT1 Source |
|---|---|---|---|
| Institutional | UB-04 | Facility charges (room, equipment, supplies, technical component) | Charge capture systems, pharmacy, lab |
| Professional | CMS-1500 | Provider services (professional component, E/M) | CPOE, physician billing systems |
DFT interfaces often route charges to different billing systems based on FT1-13 (Department Code) and FT1-26 (Modifier). Professional component charges (-26 modifier) route to physician billing; technical component (-TC) routes to facility billing.