Section 36: International Fuel Tax Association Transactions (IFTA)

From Nlets Wiki
Jump to: navigation, search

International Fuel Tax Association (IFTA) (FQC/FRC)

The purpose of the International Fuel Tax Association (IFTA) transaction is to identify companies severely delinquent in paying their fuel taxes. The inquiry will search the IFTA database and return exact matches based upon the Federal Identification Number (FEI).

This resource enables access to real-time data to Nlets members responsible for roadside enforcement of fuel tax laws. All information obtained via the Nlets system may be used only for criminal justice purposes. Improper use could result in suspension or complete termination of Nlets access.

This section describes how agencies may query a record in the IFTA database through Nlets. The inquiry (FQC) will search for revoked carriers and return exact matches (FRC) on the Federal Identification Number (FEIN).

This application allows Nlets users who are responsible for roadside enforcement of fuel tax laws to identify those companies that are severely negligent in paying their fuel taxes.

The IFTA index is created under the authority of IFTA and they will be responsible for its accuracy and keeping it up to date.

An agency may inquire upon the IFTA File by the Federal Identification Number (FEI). IFTA will search its index. There may be multiple responses if more than one state or province has entered a company onto the file. When a hit is made the system will access the contact information for the state or province that entered the record and insert the contact information into the response (FRC) as listed in the box below.

Section36-FRC.jpg

XML and Legacy Field Requirements

The following is required to inquire upon the IFTA file. The message type will be "FQC." The resultant response will be "FRC."

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<j:Organization>
  <j:OrganizationOtherID>
FEI/ 13 Alphanumeric Federal ID #
  • The Federal Identification Number is made up of a 2-letter jurisdiction abbreviation and the U.S. FEIN (9 characters). There is also a 2-character suffix but it will be ignored.
  • A file may be transferred to a state upon request through a dial up arrangement.
  • If a hit is realized, the user will contact the state of record to determine if the record is still valid.
  • Only two types of agencies can access the IFTA file.
  • Agencies charged with enforcement of vehicle or fuel tax laws within a state or province.
  • Law enforcement or criminal justice agencies for investigative purposes.
  • It is the responsibility of the IFTA Commissioner (IC) and the Nlets representatives to ensure that there is no unauthorized access.

Assuring the Integrity of the File

There is an IFTA Commissioner (IC) in each state that will be responsible for his/her states data on the file.

The IC will decide who can enter records within the state or province and will sign agreements and determine who will be in the Contact File.

The IC will also be responsible for validation of the file.

Assignment of ORIs

Only law enforcement, criminal justice or "S" ORIs with an "IFT" in the 3rd, 4th and 5th character can access the file.

Nlets will assign "S" ORIs to all IFTA users.

Non-criminal justice users that have been assigned an NCIC ORI may NOT access the IFTA file. They must use an Nlets assigned "S" ORI.

The format for IFTA ORIs will be: aaIFTbbbbS
aa state or province code
IFT fixed field
bbbb free field for user
S fixed field

These ORIs must be in ORION.

Validation of the File

States or provinces will be responsible for validating their portion of the file on a schedule to be determined by IFTA.

Help File

Information on IFTA along with a test record can be obtained by sending an administrative message to FTADMHELP.

Additional information on the International Fuel Tax Association (IFTA) can be found at http://www.iftach.org/.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

International Fuel Tax Association (IFTA) NIEM Specifications

This section describes the format and provides examples for IFTA queries and responses. IFTA queries should be sent to destination FT.

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: IFTA Query by Organization ID (FQC), IFTA Positive Response (FRC) and IFTA Negative (no hit) Response (FRC)

Query Formats

IFTA Query by Organization's IFTA ID (FQC)

Inquiry Data (n2:NLETSInquiryData)
This element will contain all elements specific to this transaction.

  Organization (nc:Organization)
  GJXDM: Details about a unit which conducts some sort of business or operations.
  This element encapsulates the information about the organization.

    nc:OrganizationOtherID
    This element will contain the Organization IFTA ID.

      Organization's IFTA ID (nc:IdentificationID)
    GJXDM: A generic identifier assigned to an organization.
    This element contains the IFTA ID (typically the same as FEIN) of the organization being queried. The value should be
    in the subelement j:ID.

Response Formats

IFTA Positive (hit) Response (FRC)

n2:NLETSResponseData
This element will contain all elements specific to this transaction.

  Organization (n2:RevokedCarrierOrganization)
  NIEM: Details about a unit which conducts some sort of business or operations.
  This element encapsulates the information about the organization.

    Organization Name (nc:OrganizationName)
    NIEM: A name of an organization.
    This element contains the name of the organization.

    Organization's IFTA ID (nc:OrganizationOtherIdentification)
    NIEM: An alternate identifier assigned to an organization.
    This element encapsulates the IFTA ID (typically the same as FEIN) of the organization. The subelement
    nc:IdentificationSourceText will be set to "IFTA". The value should be in the subelement nc:IdentificationID.

    Organization's DOT Number (nc:OrganizationOtherIdentification)
    NIEM: An alternate identifier assigned to an organization.
    This element encapsulates the IFTA ID (typically the same as FEIN) of the organization. The subelement
    nc:IdentificationSourceText will be set to "DOT". The value should be in the subelement nc:IdentificationID.

    Contact Information (nc:OrganizationPrimaryContactInformation)
    NIEM: A preferred means of contacting an organization.
    This element encapsulates contact information for the organization.

      Telephone Number (nc:ContactTelephoneNumber)
      NIEM: A telephone number for a telecommunication device by which a person or organization may be contacted.
      This element contains the telephone number. The actual value will be in the subelement nc:FullTelephoneNumber.

    Organization Doing Business As (nc:OrganizationDoingBusinessAsName)
    NIEM: A name an organization uses for conducting business.
    This element contains the organization's name for doing business.

    Organization Augmentation (j:OrganizationAugmentation)
    NIEM: Additional information about an organization.

      Organization Jurisdiction (j:OrganizationJurisdiction)
      NIEM: An area of service or jurisdiction an organization has over a region.
      This element encapsulates information regarding organization's jurisdiction.

        Jurisdiction Text (nc:JurisdictionText)
        NIEM: An area in which an organization or person has some kind of authoritative capacity or responsibility over.
        The organization's jurisdiction.

    Organization Status Date (nc:OrganizationStatus)
    NIEM: A date a status was set, effected, or reported.
    This element will indicate the date upon which the organization's status was changed to revoked. The actual value will be reported in the
    nc:StatusDate/nc:Date elements.

IFTA Negative (no hit) Response (FRC)

Response Data (n2:ResponseText)
This element will contain all elements specific to this transaction.

  Response Text (n2:NLETSResponseData)


  This element will contain the free text driver's license response. Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to


  ensure that the response does not contain any characters illegal in XML.

International Fuel Tax Association (IFTA) NIEM Examples

Example 1: IFTA query by organization.

Example 2: IFTA positive response.

Example 3: IFTA Negative (no hit) response.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>FRC</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>FT0000000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>01232</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>71236</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="FRC">
    <n2:ResponseText>
      <![CDATA[IFTA NUMBER: AZ22590687501 
        ORGANIZATION NAME: JOHN SMITH 
        DOING BUSINESS AS NAME: JOHN TRUCKING 
        JURISDICTION: AZ 
        CONTACT NUMBER: (602) 555-1234 
        STATUS: REVOKED AS OF 20100101]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Legacy (DEPRECATED)

International Fuel Tax Association (IFTA) Legacy Specifications

This section describes formats and provides examples for accessing records in the International Fuel Tax Association (IFTA) Index database.

Query Formats

There may be multiple responses if more than one state or province has entered a company onto the file. When a hit is made, the system will access the contact information for the state or province that entered the record and insert the contact information into the response.

The message type will be "FQC". The resultant response will be "FRC". The following entry will be required to query the IFTA file.

Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
FEI/ 13 Alphanumeric Federal ID #
International Fuel Tax Association (IFTA) Legacy Examples

Example 1: IFTA query by organization.

FQC.AZNLETS20.FT.TXT
FEI/AZ22590687501

Example 2: IFTA positive response.

FRC.FT0000000
09:00 01/01/2012 11236
09:00 01/01/2012 31238 AZNLETS20
TXT
IFTA Number: AZ22590687501
Organization Name: JOHN SMITH
Doing Business As Name: JOHN TRUCKING
Jurisdiction: AZ
Contact Number: (602) 555-1234
Status: Revoked as of 20100101

Example 3: IFTA Negative (no hit) response.

FRC.FT0000000
13:00 01/01/2010 01232
13:00 01/01/2010 71236 AZNLETS20
TXT
No record found. Please note that the IFTA, Inc database returns only revoked vehicles

Top

Downloads

Download FQC Schema

Download FRC Schema

Download FRC Stylesheet

Top