FTX.007.259

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

TMSIS Dataguide

Medicaid.gov

Version:

PAYMENT-PERIOD-START-DATE

Data Element

DE Number

FTX259

System DE Number

FTX.007.259

File Name

FTX - FINANCIAL TRANSACTION

File Segment Number

File Segment Name

STATE-DIRECTED-PAYMENT-SEPARATE-PAYMENT-TERM

Last updated

Overview Valid Values Related Rules Related DQ Measures Other Instances

Definition	The date representing the start of the time period that the payment is expected to be used by the provider.
Size	9(8)
FLF Start Position	765
FLF Stop Position	772
Segment Key Field Identifier	Not Applicable
Coding Requirements	1. The date must be a valid calendar date in the form "CCYYMMDD" 2. Mandatory 3. Value of the CC component must be equal to "20"

Valid Value Code Set	Valid Value Code	Valid Value Name	Valid Value Description	Effective Start Date	Effective End Date

RULE ID	RULE Definition
RULE-8252	If a financial transaction is from an FTX file, then the payment period start date value reported must be a valid date of the form CCYYMMDD.
RULE-8652	If the State Directed Payment Separate Payment Term segment is populated from a FTX file, then the PAYMENT-PERIOD-START-DATE must be populated
RULE-8724	If a financial transaction is a non-void, and the PAYEE ID is populated on State Directed Payment Separate Payment Term segment from the FTX file and the PAYEE ID type is either Sub-capitated network provider ID or State contracted FFS provider ID assigned by state, then the PAYEE ID value reported must be equal to a submitting state provider ID on a provider main attributes segment from a PRV file where the effective and end dates of the provider main attributes segment overlap with the payment period start date on the financial transaction.
RULE-8733	If a financial transaction is a non-void, and the PAYEE ID is populated on State Directed Payment Separate Payment Term segment from the FTX file and the PAYEE ID Type is State contracted FFS provider NPI, then the PAYEE ID value reported must be equal to a provider NPI on a provider identifier segment from a PRV file where the effective and end dates of the provider identifier segment overlap with the payment period start date on the financial transaction.
RULE-8742	If a financial transaction is a non-void, and the payer ID is populated on State Directed Payment Separate Payment Term segment from the FTX file and the payer id type is Sub-capitated network provider ID, then the payer ID value reported must be equal to a submitting state provider ID on a provider main attributes segment from a PRV file where the effective and end dates of the provider main attributes segment overlap with the payment period start date on the financial transaction.
RULE-8757	If a financial transaction is a non-void, and the PAYEE ID is populated on State Directed Payment Separate Payment Term segment from the FTX file and the PAYEE ID Type is Capitated plan ID, then the PAYEE ID value reported must be equal to a State Plan Identification Number on a managed care main segment from a MCR file where the managed care contract effective and end dates of the managed care main segment overlap with the payment period start date on the financial transaction.
RULE-8763	If a financial transaction is a non-void, and the PAYER ID is populated on State Directed Payment Separate Payment Term segment from the FTX file and the PAYER ID Type is Capitated plan ID, then the PAYER ID value reported must be equal to a State Plan Identification Number on a managed care main segment from a MCR file where the managed care contract effective and end dates of the managed care main segment overlap with the payment period start date on the financial transaction.
RULE-8772	If a financial transaction is a non-void, and the PAYEE ID is populated on State Directed Payment Separate Payment Term segment from the FTX file and the PAYEE ID Type is Beneficiary, then the PAYEE ID value reported must be equal to a MSIS Identification Number on a primary demographics eligibility segment from a ELG file where the primary demographic element effective and end dates of the primary demographics eligibility segment overlap with the payment period start date on the financial transaction.
RULE-8781	If a financial transaction is a non-void, and the PAYEE ID is populated on State Directed Payment Separate Payment Term segment from the FTX file and the PAYEE ID Type is Insurance carrier, then the PAYEE ID value reported must be equal to a Insurance Carrier ID Number on a TPL entity contact information segment from a TPL file where the TPL Entity Contact Information effective and end dates of the TPL entity contact information segment overlap with the payment period start date on the financial transaction.

Measure ID	Measure Name
RULE-8751	% of records with an MSIS ID not enrolled on PAYMENT-PERIOD-START-DATE
RULE-8757	% of records with a valid value for Payee ID (FTX00007) that do not have a corresponding MCR Managed Care Main segment for the same time period
RULE-8763	% of records with a valid value for Payer ID (FTX00007) that do not have a corresponding MCR Managed Care Main segment for the same time period
RULE-8652	% missing: PAYMENT-PERIOD-BEGIN-DATE (FTX00007)

DE Number	System DE Number	DE Name	File Segment Number	File Segment Name
FTX384	FTX.095.384	PAYMENT-PERIOD-START-DATE	FTX00095	MISCELLANEOUS-PAYMENT

Published Date	Data Guide Version	Data Element	Action	Field	Before	After
09/16/2024	4.0.0	FTX.007.259	UPDATE	File segment	None	73
09/16/2024	4.0.0	FTX.007.259	ADD	N/A		Created