Visa - Commercial - Format - 4 - 0 - Revision - 3 1

Interface Specifications Guide
VISA COMMERCIAL
FORMAT 4.0
R EVISION 3
T h is Interface Specifications Guide contains updated Visa Commercial Format 4.0 File Formats and
is intended for use by Visa Issuers and Processors of Visa commercial card transactions. This
document contains the confidential and proprietary information of Visa Inc. It may be used only for
the operation of Visa card programs and may not be duplicated, published, transmitted, or disclosed
without Visa’s prior written permission.
Visa Commercial Format 4.0 Interface Specifications Guide • VCF 4.0 Revision 3 1
Revision History
Version Date Modified By Description
4.0 - Original
2003 Initial specification for VCF 4.0
Release
4.1 Minor clarifications and corrections
4.2 September Global Product Added supplemental processing

2007 Office information, file structure details and
additional details on how to build a
substantial VCF file.
4.3 April 2009 Commercial Updated Fuel Types to be inline with

Information the October 2006 PCATS industry
Management standard.
© 2009 Visa Inc. All rights reserved.
Contents
Chapter 1 Overview........................................................................6
Visa Commercial Format............................................................................... 6
Terminology............................................................................................. 6
Understanding the Visa Commercial Format 4.0..................................... 7
Key Concepts ................................................................................................ 7
Chapter 2 Preparing Data Files ...................................................14
Fundamentals of the VCF 4.0 File Structure ............................................... 14
Record Groups ...................................................................................... 14
Architecture at the Record Group Level ................................................ 14
Logical Sequence of the Groups ........................................................... 15
File Types and File Organization................................................................. 17
VCF File Types - US and International.................................................. 17
File Organization ................................................................................... 18
Structure of a Transaction Set............................................................... 19
Header / Trailer Sequence Number....................................................... 19
Records and Data Requirements ................................................................ 20
Record formats...................................................................................... 20
General data requirements.................................................................... 20
Creating a Visa Commercial Format 4.0 Transaction File........................... 21
Important Points to Remember:............................................................. 22
Additional References: ................................................................................ 23
System Processing Routines:...................................................................... 24
Chapter 3 Visa Commercial Format 4.0 Data Formats..............26
Introduction.................................................................................................. 26
VCF File Formats and Delimiters ................................................................ 27
Formatting examples................................................................................... 27
Examples of valid records for US Members .......................................... 28
Examples of invalid records for US Members ....................................... 29
Specification Layout .................................................................................... 29
Basic Record Types .................................................................................... 30
ACCOUNT BALANCE– Type 1............................................................. 31
Account Balance (T1) Summary Notes: ................................................ 37
CARD ACCOUNT – Type 3................................................................... 39
Card Account (T3) Summary Notes: ..................................................... 51
CARDHOLDER – Type 4 ...................................................................... 53
Cardholder (T4) Summary Notes: ......................................................... 57
CARD TRANSACTION – Type 5........................................................... 58
Card Transaction (T5) Summary Notes:................................................ 78
COMPANY – Type 6 ............................................................................. 80
Company (T6) Summary Notes:............................................................ 84
ORGANIZATION – Type 10 .................................................................. 85
Organization (T10) Summary Notes:..................................................... 90
PERIOD – Type 11................................................................................ 92
Period (T11) Summary Notes:............................................................... 95
HEADER/TRAILER ............................................................................... 97
Header/Trailer Summary Notes:.......................................................... 100
Enhanced Data Record Types .................................................................. 101
Key Concept for Enhanced Data Records:................................................ 101
CAR RENTAL SUMMARY – Type 2 ................................................... 102
Car Rental Summary (T2) Summary Notes......................................... 107
LINE ITEM DETAIL – Type 7 .............................................................. 108
Line Item Detail (T7) Summary Notes: ................................................ 113
LINE ITEM SUMMARY – Type 8......................................................... 114
Line Item Summary (T8) Summary Notes:.......................................... 119
LODGING SUMMARY – Type 9.......................................................... 120
Lodging Summary (T9) Summary Notes:............................................ 126
PASSENGER ITINERARY – Type 14................................................. 127
Passenger Itinerary (T14) Summary Notes:........................................ 133
LEG-SPECIFIC INFORMATION – Type 15 ........................................ 134
Leg Specific Information (T15) Summary Notes:................................. 140
SUPPLIER – Type 16.......................................................................... 141
Supplier (T16) Summary Notes:.......................................................... 151
FLEET SERVICE – Type 17................................................................ 152
Fleet Service (T17) Summary Notes: .................................................. 165
FLEET PRODUCT – Type 18.............................................................. 166
Fleet Product (T18) Summary Notes:.................................................. 170
Temporary Services – Type 20 ........................................................... 171
Temporary Services (T20) Summary Notes:....................................... 175
Shipping Services – Type 21............................................................... 176
Shipping Services (T21) Summary Notes: .......................................... 180
HEADQUARTER RELATIONSHIP – Type 25..................................... 181
Headquarters Relationship (T25) Summary Notes:............................. 183
LODGING DETAIL – Type 26 ............................................................. 184
Lodging Detail (T26) Summary Notes: ................................................ 189
CAR RENTAL DETAIL – Type 27 ....................................................... 190
Car Rental Detail (T27) Summary Notes:............................................ 192
ALLOCATION – Type 28..................................................................... 193
Allocation (T28) Summary Notes:........................................................ 196
ALLOCATION DESCRIPTION – Type 29 ........................................... 197
Allocation Description (T29) Summary Notes:..................................... 198
RELATIONSHIP – Type 30 ................................................................. 199
Relationship (T30) Summary Notes: ................................................... 200
PHONE– Type 31................................................................................ 201
Phone (T31) Summary Notes:............................................................. 204
REFERENCE DATA– Type 99............................................................ 205
Reference Data (T99) Summary Notes:.............................................. 207
Appendix A: Changes from VCF 3.0 to VCF 4.0.........................208
Appendix B: VCF Data Fields / VCF Records..............................213
Appendix C: Record Types and Relationships ...........................228
Appendix D: Visa Europe Data Requirements ............................230
Appendix E: VCF 4.0 Multi-Byte Capabilities .............................231
Index ...............................................................................................247
Chapter 1 Overview
Visa Commercial Format

This Interface Specifications Guide provides reference information for preparing data files in Visa Commercial
Format 4.0. The guide is intended for use by data processing analysts and other individuals who are
responsible for sending or receiving Visa commercial information. Visa Commercial Format supports Level
1, 2, and 3 transaction data. It can be used for Point of Sale transaction data as well as data that has been
enriched by matching to other sources.
This specification has been divided into three chapters for easier reading. The first chapter is an overview
of the terminology and key concepts associated with a VCF 4.0 file. The second chapter provides details on
preparation for constructing a valid VCF 4.0 file, the sequence of records which must be delivered to VIS
for processing, and supplemental information to enhance understanding of the file’s structural details. In the
third chapter, format details are provided along with the layout of each of the VCF 4.0 valid record types.
The section of the specification detailing information about record types has been divided into “Basic
Record Types” and “Enhanced Data Record Types”. Following the third chapter, there are five appendices:
A. Changes to VCF in Version 4.0 – lists the differences between VCF 3.0 and VCF 4.0, and the
differences between VCF 4.0 Revisions 1 , 2 and VCF 4.0 Revision 3.
B. VCF Data Fields/VCF Records – details the data field names contained within each record type.
C. Record Types and Relationships – shows the construction of a VCF file (referential integrity) and the
relationships between each of the record types.
D. Visa Europe Data Requirements – contains information about VCF 4.0 pertinent to Visa Europe.
E. VCF 4.0 Multi-Byte Capabilities – Details Visa’s support for multi-byte capabilities
Members currently sending in files with the VCF 4.0 format are strongly encouraged to refer to the changes
documented below.
Terminology
Enhanced Data: Additional detailed information typically related to a corporate or purchasing transaction.
This is also referred to as Addendum Data. Enhanced data is appended or matched to the financial
transaction. This extra data is used in facilitating compliance, program management and reporting for an
Acquirer, Issuer or Company. The source of enhanced data may be from data providers or from
information available at the Point of Sale.
Level I Data: Also referred to as Financial Data. This is the minimum amount of data required to clear
and settle the financial transaction (T5). The data includes merchant name, city, state and zip code, amount
of sale and date of sale. The data is transferred in a TC05 record from the Acquirer to Visa.
Level II Data: Often also called Enhanced Data. This term is not to be confused with Summary VAT in
Europe. Additional clarification about Summary VAT data can be obtained at mailto:[email protected].
This email address is monitored and will provide answers for specific questions. Level II Data is the
additional non-financial transaction data that accompanies Level I data from the merchant through Visa’s
clearing and settlement. This data varies by transaction type, e.g., airline, hotel, car rental, fleet, etc. For
airline transactions, this data contains detail on the first 4 legs of an airline itinerary. The data is transferred
in a TC05 record from the Acquirer to Visa.
Level III Data: All additional transaction data elements not attached to Level I financial records. For
airline transactions this includes all of the information on an airline ticket. The data is transferred in a TC50
or TCN/VXML format from either the Acquirer or 3rd party Data Provider. Level III data can be summary
level, e.g. applicable to the entire airline transaction, or line item detail level, e.g. trip leg specific.
MIER: Visa’s Issuer Merchant Exchange Record format. Used as a data source for specific information
found in the VCF 4.0 files.
TCN: The TCN passenger name refers to information received from the Airline Tariff Publishing
Company’s Ticket Exchange System.
VIS: Visa Information Source, a component of Visa Information Management systems. Helps clients
manage expenditures and enhance business decisions by leveraging key data from their Visa Commercial
card program.
VXML: Visa Extensible Markup Language (VXML). This is an enhanced data message format to provide a
standard means of capturing and delivering enhanced data.
Understanding the Visa Commercial Format 4.0

Once a member has the ability to create a VCF file containing substantial data and passes certification with
Visa, they can produce Visa Information Source (VIS) reports to track, analyze, and manage commercial
card programs. Additional information about the required certification process can be found in the Visa
Commercial Format (VCF) Member Development Guide for Certification, which describes the VCF file construction
and the process and requirements for passing VCF certification. The VCF 4.0 file and its data can also be
processed within the larger VIM (Visa Information Management) system (of which VIS is a component) for
additional reporting such as 1099 and socio-economic reports (within the US). Contact your Visa Account
Representative for further information on VIM services available.
For members converting from earlier VCF formats to VCF 4.0, the InfoSpan 2.4 Interface Specifications Guide
may be particularly helpful. Visa Commercial Format (VCF) was previously called the InfoSpan Format.
This guide is an update to that earlier guide, which provided specifications for the InfoSpan 2.0 (VCF 2.0)
and InfoSpan 3.0 (VCF 3.0) file formats. Additional valuable information may be found in Appendix A:
Changes to Visa Commercial Format in Version 4.0.
Other documents such as BASE II Clearing and Settlement Codes or MIER documentation can be
requested from a Visa Account Representative, if desired.
To create a useful and substantial VCF 4.0 file requires an understanding of the file’s structure, the file load
process, and a few key concepts. This will ensure a smoother certification process as well as improved
ongoing management of the commercial card program.
Key Concepts
Record Type
The basic building block of a Visa Commercial Format file is a Record Type. As of this publishing date,
there are twenty-seven record types supported. The name of the record type describes the content of its
records. For example, record type 4 is ‘Cardholder’, and the contents are information about the company’s
cardholder.
Eight of these record types are basic building blocks for a VCF 4.0 file. The other nineteen record types are
used for processing different types of enhanced data records. Format and processing information for the
nineteen enhanced records is found in a later section of this manual called Enhanced Record Types.
Information about the basic set of eight record types is found in the section titled Basic Record Types.
Members should discuss which record types are relevant to their processing needs prior to building files for
certification and upload.
Field
Each VCF 4.0 record is made up of several fields. The content and format of each field is dependent on the
record type. For example, a Cardholder record type (T4) would contain information about the cardholder,
including Company Identification (the company providing the commercial card to that cardholder),
Cardholder Identification (how the cardholder is uniquely identified within a company), and many other
identifying characteristics. A portion of the cardholder record type (T4) fields is shown below:
Primary Key
A specific number of fields within a record, when combined, provide a unique key into that record. In the
example shown, the combination of Company Identification and Cardholder Identification, together known
as a primary key, must point to a single, unique cardholder. Each record type in a VCF 4.0 file has a primary
key associated with it.
Block
In order to construct a valid VCF 4.0 file, it is necessary to build and submit several groups of valid record
types. Each group may be thought of as a table of data or information. For example, a set or group of
cardholder records would be loaded to specify valid cardholders for a participating company. A group of
records of the same record type are downloaded in a single block.’
Block Header / Block Trailer

In order to construct a valid block of data, two additional records must be added:
The first record shown above is a block header (as indicated by an “8” in the first field). A block header
must be the first record in a block of records. The last record shown above (as indicated by a “9” in the
first field) is a block trailer, which must be the last record of each block of records submitted. Also note that
every record in a block must be of the same record type.
Hierarchy
Most organizations are structured as hierarchies. There are employees, who report to supervisors, who
report to managers, etc. until the top layer of the company is reached. A hierarchy is a graphical
representation of that multi-tiered organization.
The Organization Record (T10) supports the viewing of financial information throughout a hierarchical
structure. There is a single top parent node per company in the Visa processing system. In the example
shown, this would be the “Executive” box. Each of the other boxes in the above diagram would have its
own T10 (Organization) record which would describe the other child hierarchies reporting to it. Note that
the Top Parent Node must be set up first, or at the same time, as the other hierarchy nodes in the Visa
processing system. Child hierarchies are built down from the parent.
A hierarchy has a field called Effective Date associated with it. This Effective Date, found in the
Organization (T10) record (field #5), is the date at which the hierarchical relationship being described is
effective. For the Top Parent Node, the effective date must be equal to or earlier than the Effective Date of
the other child hierarchies reporting to it. At the present time, there is only one hierarchical structure
permitted per company. The Effective Date of the Top Parent Node for a company is the date that the
Company establishes its relationship with Visa’s information systems, and cannot be changed. The
Effective Date for other (non-Top Parent) nodes will change if the node’s position in the hierarchy moves.
Billing Period
A company’s Billing Period is specified in the Period (T11) record type. A Billing Period is the period of
time during which charges are accumulated prior to being reported on a statement. Each Billing Period has
a defined Start Date (field #5) on which charges begin to accumulate, and a defined End Date (Field #6)
which closes the Billing Period. Each Billing Period is identified by a number simply labeled ‘Period’ (Field
#3), which must be unique to the company, but not necessarily sequentially incremented as long as it’s
unique to the company.
Billing Periods must represent contiguous periods of time, not overlapping. The Start Date and End Date
fields must be unique across a company. Only one billing period may be open at a given point in time.
Start Date 3
End Date 1 = Start Date 2 – 1 day
End Date 3 = Start Date 4 – 1 day

Start Date 1
Billing Period #1
Billing Period #2 Billing Period #3
Start Date 2 End Date 2 = Start Date 3 – 1 day
For more information on Billing Period Rules and processing topics, please see the Visa Commercial Format
(VCF) Member Development Guide for Certification.
Account Number
In the Visa processing systems, an account number may represent various types of accounts: An individual
account is a single account in the VIM system. This account may be individually billed, i.e. all charges made
against Account A appear in Account A’s billing statement. Or, an individual account may roll up to a
corporate or billing account. In this case, all charges made against one or more accounts are all aggregated
under a billing or corporate account number. In this case, the charges for each individual account billed
under a corporate account number are called individual memo accounts.
In the figure shown above, for example, the Payable Department and the Receivable Department may both
be structured such that their billing rolls up to the Accounting Department. However, the Sales
Department may be classified as an individual account. In that case, it would not roll up to the Marketing
Department, but instead would be responsible for paying its own bills.
Billing Accounts
As described above, Visa processing supports member banks that use a billing account structure in which
transactions in individual accounts are rolled-up for payment to Billing Account(s) also known as
consolidated billing, centrally-billed, or roll-up accounts.
In summary, there are three different account types supported in VCF 4.0:
• Individual Paying Account (individuals paying their own bills): these accounts are not part of a larger
billing structure
• Individual Paid-for Accounts: These accounts are paid for by a billing account.
• Billing Accounts (paying their own transactions as well as those for other card accounts): These are
master accounts which pay the bills for one or more individual paid-for accounts, as well as paying for
their own transactions.
Structurally, the Card Account (T3) is the same for individual accounts or for billing accounts. However,
there are ramifications to the contents of the record depending on who is paying for the charges.
For the T3 record:
And for the corresponding T1 record:
All account numbers must be a maximum of 19 digits, and must be all digits.
Billing Cycles
When one billing period ends and there are no additional transactions to be posted for that billing period,
the member’s cycle processing routine should produce Account Balance records (T1) and generate Period
(T11) records to start a new billing cycle. A cycle routine should begin as soon as the processing date (load
date in the file header and trailer) is higher than the billing period end date. The cycle process must generate
two T11 records, one to close the last billing period, and one to open the new billing period. There must be
no date gaps between billing periods.
An Account Balance (T1) record should be generated for all T3 accounts by creating the Previous Balance
(Field #5) from the last cycle’s Current Balance (Field # 6), and totaling all T5s for this billing period to
create the period’s Current Balance. When executing VIS reports, only the accounts with both T5 and T1
records for that closed billing period will have cardholder statements. For open billing periods the system
calculates the starting balance and ending balance from the transaction data that has been sent in for the
cycle, and ‘NA’ is displayed in ‘Necessary Adjustments’. For completeness of reporting, there should be a
T1 record for the Billing Account and each Individual Account in the cycle file, whether or not there are any
transactions during the cycle and whether the accounts are open or closed.
In the Account Balance (T1) record for Individual Accounts for which the individual pays:
• The Previous Balance (Field #5) must be the current balance amount carried over from the last billing
cycle.
• The Current Balance (Field #6) must equal the sum of all transactions, both debits and credits, for
this Individual Account for this billing period.
In the Account Balance (T1) record for Individual Accounts which are paid for at the end of the cycle by a
Billing (Paying) Account:
• The Previous Balance (Field #5) is expected to be zeros (since it was paid for). Under unusual
circumstances, there may be an outstanding balance, if the Billing Account failed to pay.
• The Current Balance (Field #6) is expected to be the sum of all debit and credit transactions for this
account during this cycle.
Dual Currency in the Latin America and Caribbean Region
The Visa processing systems provides support for both domestic and international transactions. Domestic
transactions are billed in the local currency, and international transactions are billed in US Dollars. Only
two different billing currencies are supported in the VIS system today. However, multiple source currency
codes are supported.
To support the dual currency requirement, Visa systems take VCF data and separate the transactions into
two “companies” based on the Billing Currency Code. One company will contain the domestic
transactions, and the other will contain the transactions billed in US Dollars. All Account Balance (T1) and
Card Transaction (T5) records will be sorted by billing currency code. Other record types such as Card
Account (T3) and Cardholder (T4) record types will be duplicated in each company. These two
“companies” will both be available in VIS for reporting.
A Dual Currency Company is identified by having more than one currency code in the Card Transaction
(T5) Billing Currency Code field. There is no other flag or indicator field.
Changing Information in VIS
When a record is loaded into VIS and its first byte (Load Transaction Code) is a 3 (Change matching
transaction) or 4 (Add if transaction doesn’t exist or change existing transaction), the VIS system will try to
match the primary key for the new record to a primary key for an existing record. If such a match is found,
and the field is updateable, the data in the fields of the new (incoming) record will replace the data that was
in the fields of the existing record. For fields that are not populated in the new record, i.e. two consecutive
TAB characters, the data in the existing record will not change.
Chapter 2 Preparing Data Files
Fundamentals of the VCF 4.0 File Structure

Visa Commercial Format data consists of individual Visa commercial transactions, or records, gathered into
a tab-delimited, variable-length file called a transaction file. Files are accepted in EBCDIC, TC50 and some
proprietary formats and then converted to ASCII in Visa systems. The terms record and transaction are
used interchangeably throughout this document. The following are the important record groups found in
VCF files:
Record Groups
Starter Data These are the required records to set up a new company. Starter records are required in an
initial file when a new company number is introduced. Starter records contain the accounts, cardholders
and company data which form a data foundation to which transactions and billing cycles can be linked.
Starter records include the following:
o T6 Company Record
o T10 Organization Record
o T4 Cardholder Record
o T3 Card Account Record
o T11 Period Record
Financial transaction data. Financial records are conveyed in the (T5) Card Transaction records.
These records include all debits and credits, fees and other transactions that debit or credit the account.
Card transactions are directly linked to Card Accounts, Cardholders and Billing Cycles. When new accounts
are added, Visa Systems must receive T3 and T4 records for new accounts before the new account T5
financial transactions can be processed.
Billing cycle data. Monthly billing cycle information is conveyed using the Account Balance (T1) record
and the Period (T11) records. The Account Balance record conveys end of cycle balances while the Period
records close the current cycle and open a new billing cycle. The Starter, Financials and Cycle data form the
VCF basic record set and are the basis for certification.
Enhanced data. These optional records, often called Addendum records, add detail to purchases such
as Hotel, Airlines, Car Rentals and other transactions commonly used for business expense reporting and
corporate program maintenance. They provide data over and above the basic VCF Record Set.
Architecture at the Record Group Level

The VCF record groups have special inter-relationships and dependencies which are shown in the Figure
below.
Starter Data are records that form a meta-data layer of interlocking information that is complete unto itself.
Therefore, a Starter file may contain only the Starter records: T6, T10, T4, T3 and T11. This Starter data
links the financials as shown in the diagram below. The fields which link the different records are shown on
the connecting lines.
The “Financials” group of data may accompany the Starter data set, but cannot stand on its own. For
example, in the figure above, a T5 Card Transaction cannot be processed before a T3 record for that
account has been declared. This declaration of the Account record may happen in the same file, or in a
previous file. Likewise the T1 Account Balances cannot be processed before the Accounts and Billing Cycle
that is closing have been declared.
Logical Sequence of the Groups

Starter Data creates a foundation.
A base of cardholders (T4) and accounts (T3) is grouped by company (T6). It is organized and reported on
as broken out by hierarchy (T10). The reporting cycle is established by the billing period (T11).
Financial Transactions build on the Starter foundation.
Financials are the heart of a reporting system. They can be reported by Functional Organization, Billing
Organization or any other hierarchy customized for that company.
Enhanced Data Records build on the Financials and expand their value.
The enhanced data platform based on the VCF record set and addendum records currently provides a range
of data and reporting services to Issuers, their Customers, Merchants, Data Providers and Third Party
reporting services.
File Types and File Organization
VCF File Types - US and International

o Inbound Files: These are files received into Visa systems from Issuers, customers and other
business partners. These files go through a Visa certification process prior to acceptance into
production.
o Outbound Files: These files are created by Visa systems and provide data feeds to various data
end points. For further information, please contact your Visa account representative.
o 4.0 US Member/Processor Files, Inbound: These are files created in a format that strictly
adheres to this 4.0 specification. US files are processed by the Visa Edit Package and systems which
are specialized to the needs of US accounts. From a format perspective, fields are expected to be
correct in format, length and number of fields to a record.
o Field Padding for US files:
Numeric fields should be right-justified, zero filled and padded to the left. Rules
follow strictly to this specification unless exception instructions are given in the field
description.
Alphanumeric fields should be left-justified, space filled and padded to the right.
Rules follow strictly to this specification unless exception instructions are given in
the field description.
US files are generally fully padded for either ‘X’ or ‘9’ formats.
o 4.0 International Member/Processor Files Inbound: These files are received in a format that
meets the special needs of the international community. The files have an international edit and
enrichment package. From a format perspective, fields are accepted as follows:
o Field Padding for International files:
Numeric fields may be fully zero filled, padded with spaces or empty (meaning the
field is designated by a TAB only). An example of a numeric field often empty or
space-filled would be a non-required date field. International files may be
compressed, which removes all spaces not surrounded with data. Numeric fields
which must be numeric are especially annotated in the field description.
Alphanumeric fields may be padded with spaces or empty. Fields not in use should
always be initialized to prevent nulls and other non-standard data errors.
For international files, padding and field values are usually optional for non-required
fields, and for fields that don’t specifically say “must be numeric” such as the T1
fields.
File Organization
VCF files contain records for one or more companies depending on the requirements of the member /
processor, as pictured below.
Company data is sent to Visa on each company’s scheduled frequency, daily,

weekly, or monthly.
The Bank or Processor controls the correct loading of data into Visa Systems
by maintaining a data sequence number for each company. This sequence
number typically starts with ‘1’ when a company is first introduced, and then
is incremented by ‘1’ for every subsequent file of data for that company.
Within a file, company data typically differs. It may include Starter data for
new companies and/or Financials and/or Cycle and/or Enhanced Data as
shown.
This data specification refers to Transaction Sets1 and Transaction Blocks in the section on Headers and
Trailers. These are the records which provide file control for the data records as pictured here.
Õ Each company in a file represents a Transaction Set.

Õ Each Transaction Set contains one or more Transaction Blocks.
Õ All Blocks in a transaction set must belong to a single company

and Blocks of the same record type cannot be repeated within the
Transaction Set.
Õ Each Transaction Block contains a specific type of VCF record.
Õ Different Transaction Blocks may have different numbers of
records.
Õ The number of records in Blocks and Sets is controlled by
Headers and Trailers.
1
In VCF 2.0 and 3.0, transaction sets were called downloads.
Structure of a Transaction Set
A Transaction Set consists of one or more blocks of transaction records. All records in a Transaction Set
must belong to a single company. The following diagram illustrates the structure of a single Transaction Set
in the transaction file:
A Transaction Set is delimited by a header

transaction at the beginning and a trailer
transaction at the end. To ensure the integrity of
each Transaction Set, the trailer transaction
includes information that allows for validation of
the contents. Thus the trailer, in addition to
repeating the fields in the header, contains fields
for the number of included transactions (Record
Count) and the sum of all included billing amounts
(Total Amount; only used in the case of Type 5
Card Transaction records). For more information
about preparing header and trailer transactions, see
the Header/Trailer record.
Header / Trailer Sequence Number

Each Transaction Set (Company) has its own sequence number to help track the data in production, and to
ensure that Visa loads VCF company data in the correct sequence. The sequence number is not a “file”
sequence number, it’s a company sequence number within that file. Each company may have a
different sequence number within the file, depending on many factors, including when the company is first
introduced into Visa systems and the frequency in which the company is sending data. In an initial starter
file, when the account is first loading companies into Visa production, all companies in the file may start
with the same sequence number. However, if a company has no data on a certain day, it may be excluded
from the file. When it next appears in a VCF file, it must increment its sequence number by “1” or cause a
Visa system error.
As an Example:
There are several basic rules which pertain to the Sequence Number:
• A sequence number counter must be maintained for each company.
• A sequence number may start with ‘1’, but that is not required.
• Whatever a sequence number begins with, it must be incremented by “1” in the next file in which that
company appears.
• A company that has no data to report may be absent from the daily file.
• Sometimes companies send null or empty Transaction Blocks when there is no daily data to report.
• A Transaction Set with empty Transaction Financials Block will increment the sequence counter.
• A company may report data on a basis other than daily.
• There cannot be any gaps in the sequence number due to holidays or weekends.
• The sequence must be contiguous.
Records and Data Requirements

Record formats
As discussed earlier, a Visa Commercial Format record consists of a series of data fields containing values.
The fields are delimited by {TAB} characters (ASCII character 9):
[Field 1] {TAB} [Field 2] {TAB} [Field 3]
Each record is uniquely identified by a primary key. Primary key fields are noted in the record type
descriptions in Chapter 3, “Visa Commercial Format 4.0 Data Formats.” The primary key field cannot be
empty, or all spaces or zeros. For some record types, the primary key consists of more than one field. In
such cases, all the primary key fields must have values.
Each record type may have fields that are required other than the primary or key fields. Required fields are
noted in the record type descriptions. A required field must contain a value. Non-required fields can be
empty (contain no value).
Field 1 of each transaction record is used for the Load Transaction Code. This code specifies the action to
be taken by Visa processing when the record is encountered (add the record, or replace the record, i.e.
replace the values in the old record with the values in the new or incoming record.).
Applications that incorporate Visa Commercial Format 4.0 data must be set up to use the Load
Transaction Codes described here.
General data requirements

Following are general requirements for providing valid data in Visa Commercial Format records.
Requirements that are specific to each record type are included in the record type descriptions in Chapter 3.
• Numeric fields can only contain the ten digits (0 to 9).

• Numeric fields cannot contain negative values, except for specific fields in the following record
types: Account Balance, Lodging Detail, and Car Rental Detail.
• When allowed, negative numbers must be represented by the “-” character in the first position of
the field.
• All date fields must have the format MMDDCCYY. The only record types which allow future
dates, i.e. dates greater than the processing date, are T6 (Fiscal Year Date), and T11 (Billing Period
End Date (for the current billing period)).
• No date in a load transaction record can be earlier than the Company’s effective date, which is
specified in Field 15 in the Company record type.
• Every transaction must include a load transaction code in Field 1.
• The primary key data field(s) in each record must have a value.
• All other required fields must have values.
• To set a field to ‘empty’ (containing no data), enter a back-slash (“\”) in the first position of the
field. (Not valid for primary key or other required fields).
• To leave an existing data value as is without making any change to the field, enter two consecutive
{TAB} delimiters in the field’s position.
• Account Numbers should always be left justified, space filled and padded to the right.
• Each record type contains four (4) optional fields labeled ‘Optional Field 1’, ‘Optional Field 2’,
‘Optional Field 3’ and ‘Optional Field 4’. These fields may be empty, or may contain valid values.
If a member does not wish to provide data in those fields, a TAB character representing that fact
should be provided for each empty field.
Creating a Visa Commercial Format 4.0 Transaction File

Take the following steps to create a Visa Commercial Format 4.0 transaction file:
1. Review this Interface Specifications Guide to become familiar with the basics of providing data using Visa
Commercial Format. Make sure you understand the VCF transaction file data structure. Refer to
Chapter 3, “Visa Commercial Format 4.0 Data Formats,” for detailed descriptions of the record
types and the data fields within each record type. Review the Visa Commercial Format (VCF) Member
Development Guide for Certification for additional certification information.
2. Prepare this list of files to be sent for a certification review. The following rules are also important to
note:
a. Starter data needs to be presented before T5s and T1.
b. Starter Transactions (T6, T10, T4, T3, and T11s) are not repeated in later files unless there is
a specific need to do so.
c. T11s set the billing period number used by T5s and T1s.
d. Whenever a billing period changes, two T11s should be sent:
i. One to close the current period
ii. One to open the new period
e. T1s calculate the account balance for the period that is closing
f. T1 Account Balance fields must be accurate to produce balanced statements in VIS.
3. Ensure that all records and data meet the requirements described in Chapter 3 and in the previous
“Record Formats” section.
4. Group the data according to record type, creating a block of transactions for each record type.
5. Create valid header and trailer records to delimit each block.
6. Group one or more blocks of records for a single company into a transaction set, placing blocks of
information in the order discussed above. Note: Transaction Sets for multiple companies may be
sent in a single load file.
7. Generate header and trailer records for the entire load, utilizing the sequence number logic discussed
above.
8. Deliver the transaction file for loading into the VIS system.
Important Points to Remember:

• Starter Data is introduced before or in the same file as T5s and T1s.
• Once Starter Data (T6, T10, T4, T3, T11) is sent, there is no reason to resend that data unless there
are new or changed T3 or T4 or T10 records. T6 and T11 records may be sent in every file.
Although the processor may not reject the duplicate records, it is not best practice to resend
unnecessary data.
• T11s define the billing period start and billing period end date used by T5s and T1s. A company can
have only one open billing period at any given time (both in the file and in the system).
• When cycle processing changes the billing period, two T11s must be sent; one is to close the current
period, and the next is to open the new period.
• Headers and trailers are required.
Additional References:
For additional information on ISO Country Codes, see
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39719&ICS1=1&ICS2=1
40&ICS3=30&showrevision=y&scopelist=CATALOGUE
For information about ISO 4217 Currency Codes, click on
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=34749&ICS1=3&ICS2=6
0&ICS3=
System Processing Routines:
As the VCF basic file is organized into Starter Data, Financials data and Cycle data, it is necessary for the
member or their processor to build system routines which can be easily triggered to produce this data.
Starter Process: This is triggered under the following situations:

Circumstance Description Records Generated
A new company is introduced New companies must be subscribed in VIM, and Required: T6, T10, T4, T3, T11
must send complete starter data prior to or
concurrent with financials and balances. Optional: T5, T1, Enhanced Data
Records matching T5s, as desired
New hierarchies are introduced New T10 records are added and any T4s and T3s Required: T10s
which are affected are either added or changed.
Optional: T3s and T4s as impacted
Hierarchies are changed. Existing T10 records are changed and any T4s and Required: T10s
T3s which are affected are either added or changed.
Optional: T3s and T4s as impacted
New accounts are added New T3s and any associated new T4s are added. T3s Required: T3s any associated new T4s
may not be added without an associated T4 either in
the database or in the file.
New cardholders are added or New T4s are either added or changed. There is no Required: New T4s. If T4s are changed,
changed requirement that corresponding T3s must also be change T3s may be required.
added. If changes impact existing T3s, they must be
changed. Optional: Associated new or change T3s
Changes to Company record Occasionally company data changes such as name, Required: Change T6
address, etc.
Resend Starter Data There may be rare instances in which Starter Data Required: T6, T10, T4, T3, T11
which was already sent for a company needs to be
resent to Visa. Optional: T5, T1 (if providing historical
data), Enhanced Data Records matching
T5s, as desired. Note that if a T1 is sent,
at least 2 T11s would be required along
with it.
Starter data may not be resent in daily transaction files with the following exceptions:
• T6 Company record may be sent in any file.

• T11 may be sent in any file
• Maintenance records (Adds / Changes) for T10s, T4s and T3s may be sent in any file.
See Member Development Guide for VCF Certification for more information on Starter routines.
Financials Process: This is triggered under the following situations:
The Financial Transaction is linked to the Account record and the Period Record, and therefore must not
precede those records in the Visa systems.
Post new Transactions Financial transactions of all kinds are posted and sent Required: T5s or empty file
to Visa according to the cycle and file frequency
Optional: Associated Enhanced Data
schedule.
Records
Note: Some companies generate an
empty Transaction Block when there are
no transactions to report. This must be
stated in the Enrolment Document.
Post late Transactions Monthly statements include financials which are Required: T5s
posted on a date that falls between the start and end
dates of a billing period. Late financials may be posted
Records
to an earlier closed period as long as the correct period
is properly referenced.
Changes to a posted The T5 record has a key consisting of the following Required: Change T5s
Transaction fields: Account Number, Posting Date, Transaction
Reference ID, Sequence Number. When changes to a
Records
transaction are sent, these fields must match the
original transaction exactly. Otherwise duplicate
transactions will result.
Financial transactions may be sent in any file, as long as starter data for those transactions is included or
already sent.
See Member Development Guide for VCF Certification for more information on Financials routines.
Cycle Process: This is triggered under the following situations:

The End Date of the open billing period, or the End Date + 1 is reached in the processor system.
A cycle has been triggered by Check the processing (system) date against the End Required:
the cycle end date and system Date of the current billing period. If system date is
• T11 to close the current billing period
date equal or higher, initiate cycle processing to close the
current period and open a new period. • T11 to open the new billing period
• T1s for all accounts for the closing
billing period
The Cycle process is critical to generating correct VCF data. There are many important rules concerning the
creation of billing periods which are found in the Member Development Guide for VCF Certification.
VCF files do not allow overlapping billing periods for a company. The solution to multiple billing period
cycles for a company is to break out multiple companies that have unique and distinct billing cycle patterns.
Chapter 3 Visa Commercial Format 4.0 Data
Formats
Introduction
The tables in the following sections describe the specifications for formatting Visa commercial transaction
data in Visa Commercial Format 4.0. These tables detail the fields contained in every record type in which
data can be provided. The following information is included for each field:
No. (Number)
A unique number assigned to each data field in a record type. This number defines the position of the
field in the record.
Field Name
This column indicates the name of each field.
Field Format
Field Format designates the type and maximum length of the data in each field. The first position
specifies the data type:
X = Character (all character fields are left justified)
9 = Numeric (all numeric fields are right justified)
The number in parentheses after the ‘X’ or ‘9’specifies the maximum length of the field:
(99) = Maximum length of the field
Each field can contain data that is between 0 and the maximum field length. Character field lengths must
be divisible by two to support Chinese, Korean, and Japanese double-byte characters.
Data Source
The Data Source field shows the source of the field and any formatting offset. Data sources include the
VisaNet BASE II Clearing and Settlement Interchange Formats and Visa’s Merchant Profile Service Reference
Manual, section on Issuer Merchant Information Exchange Record (MIER) Formats.
Note: BASE II and MIER source files are both fixed-length. The Visa BASE II TC 05 Financial Transaction is
not the same as the T5 record type.
Description
The Description field contains a brief summary of the information represented in each field.
Edit Criteria
The Edit Criteria column lists the rules that must be followed in order to provide valid data for each
field. This column describes specific conditions or restrictions for each field, such as lists of allowed
values or whether the field is required (must have a value).
Other Criteria
Primary Key: Defined as data to uniquely identify each row in a table. A unique key or primary key
comprises a single column or set of columns. No two distinct rows in a table can have the same value (or
combination of values) in those columns. Many primary key fields must be unique, such as Account
Number. Others may be subordinate keys such as the transaction reference number.
VCF File Formats and Delimiters

VCF data files which are inbound to Visa Systems are expected in the following Standard file and data
formats:
o Variable Length, Tab delimited, or
o VCF wrapped within a TC50
No other formats can be certified without prior agreement between Visa and the member. Any
special formats or record/field exceptions granted must be identified to the certifier prior to the
beginning of certification.
Variable length, Tab delimited files:

o Inbound data to Visa Production Systems may be in EBCDIC or ASCII format. Visa systems will
convert EBCDIC files to ASCII at the inception of file processing.
o Certification files must be sent in ASCII (.txt) format.
o Files must not contain Nulls which are ‘00’ in ASCII and 0000 0000 in EBCDIC.
o Fields are delimited by TABS, and Records are delimited by Carriage Return and Line Feed at the
end of the record, as per the chart below.
o TXT files should be viewed in the PC TXT format rather than other TXT formats such as UNIX
TC50:
o These are files containing data in VCF 4.0 format that are transmitted enclosed in a TC50 message.
o Please refer to the BASE II Clearing Interchange Format TC50 to TC 92 for detail rules on this
format.
o Exceptions to standard, documented TC50 format for VCF 4.0 files require an exception review
with Visa.
Formatting examples
Following are some examples of valid and invalid record formats. The examples illustrate a record type that
is defined with the following three fields:
Field 1 9(01)
Field 2 X(10) (required field)
Field 3 9(08)
Please note that for 4.0 International Members, no padding of any field is accepted. The following
examples are for US Members only.
Examples of valid records for US Members

Example 1:
Example 2:
Example 3:
Examples of invalid records for US Members
Example 1:
Example 2:
The first invalid example illustrates data that is longer than an allowed field length. The last example is
missing a value for Field 2, a required field.
Specification Layout
The following portion of the manual is divided into two sections. The first section focuses on basic record
types essential to building up a valid, substantial, VCF 4.0 file. The second portion, “Enhanced Record
Types” describes those records used to carry line item detail as well as other enhanced transactional or
organizational information. Visa’s commercial card enhanced data services enable delivery and processing of
enhanced data designed to meet the needs of larger corporations and government entities in collecting
important non-financial information from commercial card usage. This information can assist commercial
clients with accounting automation, tax compliance, purchasing control, and supplier and commodity
management.
Basic Record Types
The following record types are considered to be part of the basic VCF 4.0 record set:
• Account Balance (T1)
• Card Account (T3)
• Cardholder (T4)
• Card Transaction (T5)
• Company (T6)
• Organization (T10)
• Period (T11)
In addition, the file and block header and trailer records are basic to the construction of a VCF 4.0 file, and
will be described in this section.
ACCOUNT BALANCE– Type 1
The Account Balance record provides account balances per billing period for each Account Number. An
Account Number can represent an individual cardholder, a consolidated billing account, or an individual
memo account. [See Account Number in the Key Concepts section for further information.]
The Account Balance records are used to summarize billing information for a specific time period. The
particular account “owner” for the balance amounts shown in this record is determined by the Primary Key
for the record: The Account Number (Field #2) and the Closing Date (Field #3). These two fields cannot
be empty or contain only spaces and must uniquely represent the account responsible for the charges
incurred. In this specification, these primary key fields are indicated by a “**” following the field name. All
amounts and counts contained in this record type belong to the account indicated by the primary key.
The following requirements exist for the primary key values:

For Add:
• The Account Balance record corresponding to the account uniquely indicated by the Account Number
and Closing Date must not already exist in the application.
For Change:
• The corresponding Account Balance must exist in the application.
Account Balance (1)
NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

FORMAT SOURCE
1 Load Transaction 9(01) Code which determines Values:

Code the action to be taken by
1 = Add the transaction
Visa Systems on this
record: either Add, or 3 = Change the matching
Change. transaction
4 = Add if transaction does not
exist, or change existing
transaction.
For Add/Change:
• Required and must be either a
1, 3 or 4
2 Account X(19) Cardholder Account For Add/Change:
Number** Number appearing on the
• Required.
front of the card; in most
cases, transmitted by • Must be a valid Account
BASE II. Number; must be all digits,
and cannot be empty.
Note: International may
reference accounts which • Must exist in the application,
begin with a “4” but are i.e. must be declared in a Card
not Visa Accounts. Account (T3) record in a
Length must be in a range previous file or concurrently
between 1 and 19. in this file to identify the
account.
Account Balance (1)

FORMAT SOURCE
3 Closing Date** 9(08) Closing Date of the Billing For Add/Change

Period for this Balance
• Required.
Record. End Date of the
T11 Billing Period • Must be a valid date in
referenced in Field #4 MMDDCCYY format and
(Period). equal to the Billing Period
End Date.
4 Period 9(05) Billing Period number For Add:
previously assigned by the
• Required.
Issuer/ Processor in a T11
record. • Must exist in the application.
Note: If this is end of For Change:
cycle data, must be the • Required
period that is closing.
• Must exist in the application.
5 Previous Balance 9(16) Account Balance at the Two decimal places are implied
end of the previous Billing (1234 = 12.34).
Period.
For Add/Change:
Note: If this is an
• Not required, and can be
account paid for by a
spaces or empty.
Billing Account, special
rules apply. See end of • If a value is provided, it must
this section. be numeric.
• Can be negative.
6 Current Balance 9(16) Should equal the sum of Two decimal places are implied
all T5 transactions for the (1234 = 12.34).
period plus the Previous
For Add:
Balance.
• Required.
Note: If Billing Accounts
are used, see Previous and • Must be numeric.
Current Balance rules at • Can be negative
the end of this section.
• If this is end of cycle data,
must be the balance of the
period that is closing.
For Change:
• Cannot start with ‘\.’
• If provided, must be numeric.
7 Credit Limit 9(16) Maximum Balance Two decimal places are implied
permitted for the Account (1234 = 12.34).
in currency units
For Add/Change:
applicable to the company
to which this balance • Not required.
applies. • If provided, must be numeric.
Account Balance (1)

FORMAT SOURCE
8 Current Amount 9(16) Current Amount Due Two decimal places are implied
Due expressed in specific (1234 = 12.34).
International Standards
For Add/Change:
Organization (ISO)
Currency units. • Not required.
When the Account has • If provided, must be numeric.
provisions for less than • Can be negative
the complete payment, the
Current Amount Due may
be less than the Current
Balance.
When consolidating a
Billing Account, the
Current Amount Due
contains the total of all the
individual Accounts that
have been consolidated
together.
When consolidating an
individual Cardholder
Account into a Billing
Account, the Current
Amount Due is set to
zero.
9 Past Due Count 9(05) Number of periods (in 30- Values:
day receivable units) the
0 = None
Cardholder’s Account has
been Past Due. 1 = 1 Billing cycle
If the Account is a Billing 2 = 2 Billing cycles
Account, this field
3 = 3 Billing cycles
contains the units of time
that the Billing Account 4 = 4 Billing cycles
has been Past Due.
If this is an individual
Cardholder Account
consolidated into a Billing For Add/Change:
Account, this field is set to
• Not required.
zero.
• If provided, must be valid
value.
• If not provided (spaces or
empty) and field 19 (Past Due
Plus Cycles Amount) is
provided, default will be 6.
Account Balance (1)

FORMAT SOURCE
10 Past Due Amount 9(16) Previously billed Amounts Two decimal places are implied
that have not been paid. (1234 = 12.34).
Past Due Amount is set to For Add/Change:
zero for an individual
• Not required.
account that has been
consolidated. • If provided, must be numeric.
For a non-consolidated • Cannot be negative.
individual Cardholder
Account, Past Due
Amount contains the Past
Due Amount of the
Cardholder Account.
11 Disputed Amount 9(16) Amount in dispute by the Two decimal places are implied
Cardholder for this (1234 = 12.34).
Account with the issuing
For Add/Change:
bank.
• Not required.
• Can be negative.
12 Billing Currency 9(05) BASE II International Organization For Add:
Code for Standardization (ISO)
Clearing and • Required.
Currency Codes as used in
Settlement • Must be a valid ISO Currency
BASE II.
Codes Code.
For Change:
• Must be a valid ISO Currency
Code.
13 Amount Past Due 9(16) Previously billed amounts Two decimal places are implied
One Billing Cycle that have not been paid (1234 = 12.34).
within the first billing
For Add/Change:
period.
• Not required.
Two Billing Cycles that have not been paid (1234 = 12.34).
within the second billing
For Add/Change:
cycle.
• Not required.
Three Billing that have not been paid (1234 = 12.34).
Cycles within the third billing
For Add/Change:
cycle.
• Not required.
Account Balance (1)

FORMAT SOURCE
Four Billing that have not been paid (1234 = 12.34).
Cycles within the fourth cycle.
For Add/Change:
• Not required.
Five Billing Cycles that have not been paid (1234 = 12.34).
within the fifth cycle.
For Add/Change:
• Not required.
Six Billing Cycles that have not been paid (1234 = 12.34).
within the sixth cycle.
For Add/Change:
• Not required.
Plus Billing Cycles that have not been paid (1234 = 12.34).
over more than X cycles.
For Add/Change:
X is identified by Field 9
(Past Due Count) • Not required.
20 Past Due One 9(05) Number of times payment For Add/Change:
Billing Cycle is past due in the first
• Not required.
Count cycle, since account open.
• If provided, must be numeric
21 Past Due Two 9(05) Number of times payment For Add/Change:
Billing Cycles is past due in the second
• Not required.
22 Past Due Three 9(05) Number of times payment For Add/Change:
Billing Cycles is past due in the third
• Not required.
23 Past Due Four 9(05) Number of times payment For Add/Change:
Billing Cycles is past due in the fourth
• Not required.
24 Past Due Five 9(05) Number of times payment For Add/Change:
Billing Cycles is past due in the fifth
• Not required.
Account Balance (1)

FORMAT SOURCE
25 Past Due Six 9(05) Number of times payment For Add/Change:

Billing Cycles is past due in the sixth
• Not required.
26 Past Due Plus 9(05) Number of times payment For Add/Change:
Billing Cycles is past due in the X cycle,
• Not required.
Count since account open. X is
identified by field 27 (Past • If provided, must be numeric
Due Cycles Count).
27 Past Due Cycles 9(05) Identifies number of Values:
Count cycles the Past Due Plus
0 = None
Billing Cycles Count field
is based on. 1 = 1 Billing cycle
For Add/Change:
• Not required.
value.
• If not provided and Field 26
(Past Due Plus Billing Cycles
Count) is provided, default
will be 6.
28 Last Payment 9(16) Amount of last payment Two decimal places are implied
Amount transaction. (1234 = 12.34).
For Add/Change:
• Not required.
29 Last Payment 9(08) Date last payment For Add/Change:
Date transaction was made.
• Not required, defaults to zeros.
• If provided, must be a valid
date in MMDDCCYY format.
30 Payment Due 9(08) Date payment is due. For Add/Change:
Date • Not required, defaults to zeros.
date in MMDDCCYY format.
Account Balance (1)

FORMAT SOURCE
31 High Balance 9(16) High balance amount for Two decimal places are implied
life of account. (1234 = 12.34).
For Add/Change:
• Not required.
32 Optional Field 1 X(26) Free format. May not For Add/Change:
contain nulls. If not in
• Not required.
use, should be initialized
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Account Balance (T1) Summary Notes:
The T3 Account Record corresponding to this Account Balance record must exist in this file, a previous
file, or a starter file (See the “Creating a Visa Commercial Format 4.0 Transaction File” Section).
The following elements found in this record type are critical to developing an understanding of the Account
Balance record:
• Account Number (Field #2): If the file contains dual currency information, the Account Number
field in this record as well as in the Card Account (T3) record cannot be longer than 16 characters.
In addition, in Dual Currency situations, there must be an Account Balance (T1) record for each
billing currency for which there is a matching Card Transaction (T5) record. Note: Dual Currency
is only available in the Latin America and Caribbean Region.
• Closing Date (Field #3): The Closing Date must match the Closing Date in the Period Record
(Record Type 11), and must be greater than the Account Open Date found in the Type 3 records.
• Period (Field #4): The Period must match the Period (Field #3) value in the Period Record (T11).
If the company is in a cycle, the period must be the one that is closing.
• Previous Balance (Field #5): This balance should be the same as the Current Balance in the previous
billing cycle’s T1 record. If the field is blank, and a previous T1 has been received for this account,
the field will be enriched to match the ending balance of the previous T1 after validation that the
previous T1 was the previous cycle. Otherwise, the field will be set to “0”.
• Current Balance (Field #6): If the Current Balance is not valid, the field will be set to the Current
Due Amount. If both fields are empty, the field will be set to “0”.
For a review of the correct settings for Previous and Current Balance field, see the earlier section
Billing Accounts .
• Current Due Amount (Field #8): When the Account has provisions for less than complete payment,
the Current Due Amount may be less than the Current Balance. For Consolidated Billing Accounts,
the Current Amount Due contains the total of all the individual Accounts that have been
consolidated. When consolidating an individual Cardholder Account into a Billing Account, the
Current Amount Due for that individual cardholder is set to zero. If the field is blank, it will be set
to “0”.
• Billing Currency Code (Field #12): This field must match the billing code in associated T5 records.
CARD ACCOUNT – Type 3
A Card Account record identifies and describes an account. The account is identified by the Account
Number and linked to a cardholder by the value in the Cardholder Identification field. The information in
this record describes attributes of a card account. An Account Number can represent an individual
cardholder, a consolidated billing account, or an individual memo account (individual account paid by
another entity). [See Account Number in the Definitions section for further information.]
The particular account “owner” in this record is determined by the Primary Key for the record: the
Cardholder Identification (Field #2), and the Account Number (Field #3). These fields are required and
cannot be empty or contain all spaces or zeros. They must uniquely represent a valid card account. As is the
convention in this specification, these fields are indicated by a “**” following the field name. All account
attributes contained in this record type belong to the account indicated by the primary key.
An account number in this record does not have to be a Visa account. For example, if a Company is doing
consolidated billing and the account paying the bill is a savings account, that account number would be used
in this record. At the present time, for loading into VIS, an Account Number has to start with ‘4’. This may
be changed in the future.

For Add:
• The Account Number should not already exist in the application, i.e. have been previously loaded.
• The Cardholder Identification must either be introduced in the file with the Account, or be already
declared in the Visa Commercial Card database. Therefore, in order to process this record, the user
must have previously created the Cardholder (T4) records. See Section “Creating a Visa Commercial
Format 4.0 Transaction File”.
For Change:
• If the Cardholder ID is not the same as the value as the Cardholder Identification value previously
loaded, it will be considered a change of the Cardholder Identification.
• The Account Number must exist and be open in the application without any dependencies.
Card Account (3)

FORMAT SOURCE

Change. transaction
. 4 = Add if transaction does not
transaction.
For Add/Change:
• Required and must be a 1, 3,
or 4.
Card Account (3)

FORMAT SOURCE
2 Cardholder X(20) Identification number For Add:

Identification** used to uniquely identify a
• Required.
cardholder or an employee
within the company. • Must be previously sent in an
associated T4 or in this file.
For Change:
• If this Cardholder ID does not
match the one that was
previously sent, it will be
considered as a Change of
Cardholder ID.
• Cannot contain ‘\’ in the first
position, which causes the
field to be empty.
3 Account X(19) Cardholder Account For Add/Change:
• Required.
front of the card;
transmitted by BASE II. For Add:
In exceptional cases, may • Must not be previously loaded
be a different kind of • Must contain numbers
account.
• For loading into VIS, must
begin with a “4”.
For Change:
• Must be previously sent
4 Hierarchy Node X(40) Identifies a Node in a For Add:
Hierarchy (organizational
• Required.
chart). It represents the
active Hierarchy Node to For Change:
which the Card Account • Cannot contain ‘\’ in the first
belongs. This Hierarchy position, which causes the
Node must be in this file field to be empty.
or previously sent.
• The Card Account must be
A Card Account can be open. Closed accounts
associated with only one cannot be added.
Hierarchy Node.
For Add/Change:
• Must have been previously
sent.
• Must be active in the
application.
Card Account (3)

FORMAT SOURCE
5 Effective Date 9(08) Represents the date when For Add:

relationship with the
• Not required; default is
Hierarchy Node begins.
Header/Trailer Processing
For Change transaction Date.
code (change the • May not be a future date
Hierarchy Node), the date (higher than Processing Date).
when the relationship with
a new Node became • Should not be lower than
effective. Account Open Date.
• Must be MMDDCCYY
See T3 Summary Notes
format.
for further explanation of
this field. For Change:
• If no value is provided and
there is a change of Hierarchy
Node, the Header/Trailer
Processing Date is used.
For Add/Change:
• Not required.
• The greater of the Hierarchy
Node Start Date, Card
Account Open Date, or the
provided Effective Date will
be used.
date.
6 Account Open 9(08) Date the Card Account For Add:
Date was opened.
• Required; or default to
Must be earlier than the Header Processing Date.
Header Processing Date. • Must be MMDDCCYY or
zeros.
For Change:
• Not updateable.
• If change value is provided, it
will be ignored.
Card Account (3)

FORMAT SOURCE
7 Account Close 9(08) Date the Card Account For Add:

Date was closed.
• Not required.
Is associated with the For Change:
Status Code and the
Reason Status Code fields • Cannot be provided if the
in this record. account is already closed.
For Add/Change:
• If provided, must be in
MMDDCCYY format.
• Must be later than or equal to
the Open Date.
• Must be earlier than or equal
to the Header Processing
Date.
8 Card Expire Date 9(08) Contains the year and For Add:
month after which the
• Not required.
card expires.
For Add/Change:
MMDDCCYY format or
zeros.
9 Card Type 9(01) Code identifying the type Values:
of Visa Commercial card.
1 = Corporate
Note that Fleet Service is
2 = Purchasing
covered in Purchasing
Card. 3 = Business Credit
Multiple card types for a 4 = Commercial
single company are not
5 = Fleet
allowed.
6 = Distribution
7 = Business Debit
For Add:
• Required.
• Must be valid value as listed
above.
For Change:
• Not updateable. If provided,
the value will be ignored.
10 Spending Limit 9(16) Spending Limit permitted Two decimal places are implied
per Billing Period (1234 = 12.34).
For Add/Change:
• Not required.
Card Account (3)

FORMAT SOURCE
11 Statement Type 9(01) Code which indicates the Values:

Billing cycle Frequency.
1 = Weekly
Note: Currently multiple
2 = Biweekly
Billing Cycle Frequencies
are not supported within 3 = Monthly
the same Company ID.
4 = Automatic transfer
All accounts within the
Company ID process on For Add:
the same billing cycle.
• Required or default to 3.
For Change:
• Not required.
value as shown above.
12 Last Revision 9(08) Date of the last review of For Add/Change:
Date this Account by the Issuer.
• Not required.
MMDDCCYY format or
zeros.
13 Transaction 9(16) Maximum Amount Two decimal places are implied
Spending Limit allowed per transaction for (1234 = 12.34).
this Account.
For Add/Change:
• Not required.
14 Corporation 9(01) Used to specify whether Values:
Payment Billing Accounts are used.
0 = This account pays its own
Indicator This field works in bills. Next field is expected to be
association with the next spaces. This setting is used both
field, Billing Account. for Billing Accounts, and for
Individual accounts that pay their
own bills.
1 = This account is paid for by a
Billing Account, which is found in
the next field. The Billing
Account number is expected to be
a different number than the
Account Number in this record.
For Add:
• Defaults to 0 if field is empty
or spaces.
For Add/Change:
• Not required.
• If provided, must be 0 or 1.
Card Account (3)

FORMAT SOURCE
15 Billing Account X(19) Card Account to which For Add/Change:

Number the transactions are billed.
• If the Corporation Payment
Indicator is set to 1, this field
should contain a Billing
Account number. Billing
Account Number must exist a
T3 record in the file or be
previously sent.
• If the Corporation Payment
Indicator is set to “0”, this
field should be spaces or
empty.
• If provided, must contain only
numbers.
16 Cost Center X(50) Default Cost Center for an For Add/Change:
account.
• Not required.
• Cannot contain the character
‘\’ (except in first position).
• If it starts with ‘\’, any
relationships with Cost
Centers are removed.
• If the value provided does not
exist in the application, the
Cost Center is created using
“Load Transaction - Card
Account” as description.
• Must be active.
17 G/L Sub-account X(76) Default G/L Sub-account For Add/Change:
for an account.
• Not required.
• If the value provided doesn’t
G/L Sub-account is created
using “Load Transaction -
Card Account” as description.
relationships with G/L Sub-
accounts are removed.
• Must be active.
18 Transaction Daily 9(08) Represents the maximum For Add/Change:
Limit number of transactions
• Not required.
that can be charged to a
card account on a daily • If provided, must be numeric.
basis.
Card Account (3)

FORMAT SOURCE
19 Transaction Cycle 9(08) Represents the maximum For Add/Change:

Limit number of transactions
• Not required.
that can be charged to a
card account on a billing • If provided, must be numeric.
cycle basis.
20 Cash Limit 9(16) Represents the maximum Two decimal places are implied
Amount amount of Cash Advance (1234 = 12.34).
transactions that can be
For Add/Change:
charged to the Account on
a billing cycle basis. • Not required.
21 Status Code 9(02) Status of a Card Account. Values:
1 = New
2 = Opened
3 = Closed
4 = Suspended
5 = Reinstated
For Add:
Required or defaults as stated
below:
• 3 (Closed) if there is an
Account Close Date;
• 1 (New) if the Account Open
Date is within the last 30 days
• 2 (Opened) for all other cases.
For Change:
• Not required.
• If provided, must be a value
above.
Card Account (3)

FORMAT SOURCE
22 Reason Status 9(02) Reason for card account Values:

Code status change
1 = Canceled
New accounts default to 0.
2 = Transferred from another
account
3 = Transferred to another
account
4 = Suspended two times during a
12 month period
5 = Past due for undisputed
amounts
6 = In dispute
7 = In collection
8 = Stolen or Lost
9 = Left employment
10 = Voluntarily
11 = Fraud
12 = Write-off
13 = Write-off - Attorney
14 = Write-off - Delinquency
15 = Write-off - Bankruptcy
16 = Write-off - Deceased
17 = Write-off - Fraud
18 = Write-off - Miscellaneous
For Add/Change:
• Not required.
value from the above list.
23 Status Date 9(08) Date on which card For Add/Change:
account status was
• Not required.
changed.
• If the status has changed in
this record and no date is
provided, the Header
Processing Date is used.
MMDDCCYY format.
Card Account (3)

FORMAT SOURCE
24 Pre-funded 9(01) Flag indicating if the card Values:

Indicator account is pre-funded.
0 = No
1 = Yes
For Add:
• Default = Zero if no value is
provided.
For Add/Change:
• Not required
25 City Pair Program 9(01) Flag indicating that the Values:
Indicator card account is subject to a
0 = No
City Pair Program.
1 = Yes
For Add/Change:
• Not required.
value.
26 Task Order X(26) A document that specifies For Add/Change:
Number and authorizes products
• Not required.
and services required and
the negotiated price at
which they will be
provided.
27 Fleet Service 9(01) Flag indicating that the Values:
Indicator card account is subject to
0 = No
receive Fleet Service Data.
1 = Yes
Valid only for Purchasing
Cards. For Add:
provided.
For Add/Change:
• Not required.
28 Credit Rating X(02) Processor provided code For Add/Change:
for credit rating.
• Not required.
29 Credit Rating 9(08) Date on which the card For Add/Change:
Date account credit rating was
• Not required.
changed.
• If provided, must be a
MMDDCCYY format or
zeros.
Card Account (3)

FORMAT SOURCE
30 Annual Fee Flag 9(01) Annual Fee Associated Values:

with account.
0 = No Annual Fee
1 = Annual Fee
For Add:
provided.
For Add/Change:
• Not required.
31 Annual Fee Month 9(02) Works in association with Values:
previous field, Annual Fee
01 = January
Flag.
02 = February
Month in which annual fee
assessed to account. 03 = March
04 = April
05 = May
06 = June
07 = July
08 = August
09 = September
10 = October
11 = November
12 = December
For Add/Change:
• Required if Annual Fee Flag
is 1.
• Any value in this field will be
ignored if the Annual Fee
Flag is different from 1
value.
Card Account (3)

FORMAT SOURCE
32 Card Receipt 9(01) Denotes cardholder Values:

Verification Flag activation status of card.
0 = Not Activated
1 = Activated
For Add:
provided.
For Add/Change:
• Not required.
33 Check Indicator 9(01) Indicates the account has Values:
checks.
0 = No
1 = Yes
For Add:
provided.
For Add/Change:
• Not required.
34 Account Type Flag 9(01) Account processing type Values:
code. Does not imply
1 = Corporate
how the account is billed.
2 = Individual
3 = Diversion
For Add/Change:
• Not required.
value.
35 Lost/Stolen Date 9(08) Date when the card was For Add/Change:
stolen or lost.
• Not required.
MMDDCCYY format or
zeros.
36 Charge-Off Date 9(08) Date account has been For Add/Change:
sent to collections.
• Not required.
MMDDCCYY format or
zeros.
Card Account (3)

FORMAT SOURCE
37 Charge-Off 9(16) Amount of Charge-Off. Two decimal places are implied

Amount (1234 = 12.34).
For Add/Change:
• Not required.
38 Transfer Account X(19) Account number to or For Add/Change:
Number from which balances are
• Not required.
transferred.
• If provided, T3 for this
account must be in this file or
previously sent.
39 Calling X(02) Type of calling card For Add/Change:
Card/Phone Type associated with account.
• Not required.
40 Emboss Line 1 X(50) Embossed Text, plastic For Add/Change:
line 1.
• Not required.
41 Emboss Line 2 X(50) Embossed Text, plastic For Add/Change:
line 2.
• Not required.
42 Last Credit Limit 9(08) Date of latest credit limit For Add/Change:
Change Date change.
• Not required.
MMDDCCYY format or
zeros.
43 Last Maintenance 9(08) Maintenance date of a For Add/Change:
Date NAR change to Name or
• Not required.
Address fields
MMDDCCYY format or
zeros.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Card Account (3)

FORMAT SOURCE

• Not required.
to spaces.
Card Account (T3) Summary Notes:
The following elements found in this record type are critical to an understanding of the Card Account
record:
• Cardholder Identification (Field #2): The Cardholder ID must match the Cardholder ID in the
corresponding Cardholder (T4) record. If the Cardholder ID in this field does not match the Id
that was sent previously in this field, and the Load Transaction Code (Field #1) is “3” (Change) or
“4” (Add or change, and the record already exists in the file), it will be considered a change of
cardholder ID in the T3. However, changes are valid only if there is an associated T4 either in the
database or in the file. The Cardholder Identification must either be introduced in the file with the
Account, or be already declared in the Visa Commercial Card database. Therefore, in order to
process this record, the user must have previously created the Cardholder (T4) records.
field cannot be longer than 16 characters.
• Hierarchy Node (Field #4): This must be an existing hierarchy node in an Organization Record
(T10).
• Effective Date (Field #5): The Effective Date must be earlier than or equal to the Header Processing
Date. The greater of the fields Hierarchy Node Start Date (T10), Card Account Open Date (T3),
and the provided Effective Date (T3) will be used as the effective date for this account.
The Effective Date will determine when an account is associated with a Hierarchy Node, either for
a new account, or for one transferring to a new hierarchy node. The old relationship with a
previous node is ended the day before the effective date.
Note that a change to a hierarchy’s Effective Date does not result in a change to the Account’s
Effective Date.
• Account Open Date (Field #6): This field cannot be updated in the VIM system. It also must be
greater than or equal to the Hierarchy Node Start Date. It can, however, be earlier than the
Company Effective Date (T6). If the data in this field is invalid or missing, the Company’s
Effective Date in the Company Record (T6) will be used.
• Account Close Date (Field #7): Field must be later than or equal to the Account Open Date (Field
#6), and earlier than or equal to the file Header Processing Date.
• Card Type (Field #8): The Card Type must match the Card Type found in the Company Record
(T6) and the Period Record (T11) unless the Company Card Code = ‘9’. If no value is found, “1”
(Corporate) is used. This field cannot be updated in the VIM system.
• Corporation Payment Indicator (Field #14): This field indicates who is responsible for paying the
bills associated with this card account. “1” (Yes) indicates that this account does not pay its end of
cycle bills. If this field contains “1” (Yes), the account number of the client company who pays the
bills should be shown in the next field (Billing Account Number – Field #15). The Card Account
(T3) record matching this billing account number must be previously loaded into the application or
be in this file.
• Annual Fee Month (Field #31): Field is required if the Annual Fee Flag (Field #30) is “1” (Annual
Fee)
CARDHOLDER – Type 4
The Cardholder record type contains information about the person using the Visa commercial card. This
record type contains identifying information about the cardholder including demographics, and identifiers
placing the cardholder in a company and a hierarchical node.
The Cardholder records are used to provide detailed information about a particular cardholder, who is
identified by the Primary Key for the record: The Company Identification (Field #2), and the Cardholder
Identification (Field #3). These fields are required and cannot be empty, spaces, or zeros. They must
uniquely represent a valid cardholder belonging to this client company. These fields are indicated by a “**”
following the field name. All attributes contained in this record type belong to the cardholder identified by
the primary key.

For Add:
• The cardholder identification must not already exist in the application.
• The Company Identification must exist in the application. In order to process this record, the user
must have previously created the Hierarchy Node (T10 records), as well as the Company (T6) record.
See Section titled “Creating a Visa Commercial Format 4.0 Transaction File”.
For Change:
• Cardholder ID and Hierarchy Node must both exist in the application, and the Hierarchy Node must
be active.
Cardholder (4)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
• Required and must be a 1, 3
or 4
2 Company 9(10) Issuer-assigned Company For Add:
Identification** Identification. It identifies
• Required.
a unique entity out of
multiple companies in an • Must be in the same load file
issuer’s portfolio. or previously loaded.
Cardholder (4)

FORMAT SOURCE
3 Cardholder X(20) Identification Number For Add:

Identification** used by a client company
• Required.
to uniquely identify an
employee or Cardholder. • Unique field. May not be
duplicated.
field to be empty.
For Change:
• Must be previously sent.
4 Hierarchy Node X(40) Hierarchy Node of the For Add:
Cardholder.
• Required.
• Must be a Hierarchy Node
previously sent or in this file.
For Change:
field to be empty.
For Add/Change:
• Must be previously sent and be
active.
5 First Name X(20) Cardholder’s first name. For Add:
• Required if Last Name is not
provided.
For Change:
field to be empty if Last
Name field has no values.
6 Last Name X(20) Cardholder’s last name. For Add:
• Required if First Name is not
provided.
For Change:
field to be empty if First
Name field has no values.
7 Address Line 1 X(40) First line of Cardholder For Add/Change:
address.
• Not required.
8 Address Line 2 X(40) Second line of Cardholder For Add/Change:
address.
• Not required.
Cardholder (4)

FORMAT SOURCE
9 City X(20) City where the Cardholder For Add/Change:

works.
• Not required.
10 State/Province X(04) Code of the state or For Add:
Code province where the
• Required for US and
Cardholder works.
Canada.
Codes are validated only • If no value is provided, blank
for US and Canada is used.
For Change:
• If value ‘\’ is found in the
first position, which causes
the field to be empty, blank is
used.
For Add/Change:
state/province code for the
Cardholder’s country.
11 ISO Country Code 9(05) BASE II International Organization For Add:
Clearing and for Standardization (ISO)-
• Required or default to
Settlement assigned code for the
cardholder’s company
Codes. country where the
country code.
Cardholder works.
For Add/Change:
• Cannot be empty or spaces or
zeros.
• Must be a valid country code.
12 Postal Code X(14) Postal code for the For Add/Change:
Cardholder’s business
• Not required.
address.
For Cardholders in the
United States, it contains
the zip code of the
business address.
For Cardholders in other
countries, it contains the
country postal code.
13 Address Line 3 X(40) Third line of Cardholder For Add/Change:
address.
• Not required.
14 Mail Stop X(14) Cardholder’s physical For Add/Change:
location number at his or
• Not required.
her place of employment.
15 Phone Number X(14) Cardholder’s work For Add/Change:
telephone number.
• Not required.
Cardholder (4)

FORMAT SOURCE
16 Fax Number X(14) Cardholder’s work Fax For Add/Change:

number.
• Not required.
17 SSN Other ID X(20) Cardholder’s Social For Add/Change:
Security Number or other
• Not required.
identifying number (other
than the Cardholder
Identification field).
18 Training Date 9(08) VISA Cards Training Date For Add/Change:
for the Cardholder.
• Not required.
MMDDCCYY format or
zeros.
19 E-mail Address X(128) Cardholder’s electronic For Add/Change:
mail address.
• Not required.
20 Authorized User 1 X(26) Authorized User #1 for For Add/Change:
this account.
• Not required.
this account.
• Not required.
this account.
• Not required.
23 Employee ID X(10) Cardholder’s employee ID For Add/Change:
• Not required.
24 Home Phone X(14) Cardholder’s home phone For Add/Change:
Number number
• Not required.
25 Middle Name X(30) Cardholder’s middle name. For Add/Change:
• Not required.
26 Visa Commerce X(19) Cardholder’s Visa For Add/Change:
Buyer ID Commerce Buyer ID.
• Not required.
27 Vehicle ID X(20) Vehicle ID for Fleet For Add/Change:
program assigned to the
• Not required.
card account.
28 Miscellaneous X(16) Defines what For Add/Change:
Field 1 Miscellaneous Field 1
• Not required.
description contains.
29 Miscellaneous X(26) Account base information For Add/Change:
Field 1 for extract.
• Not required.
Description
30 Miscellaneous X(16) Defines what For Add/Change:
Field 2 Miscellaneous Field 2
• Not required.
description contains.
Cardholder (4)

FORMAT SOURCE
31 Miscellaneous X(26) Account base information For Add/Change:

Field 2 for extract.
• Not required.
Description
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Cardholder (T4) Summary Notes:
The following elements found in this record type are critical to understanding the Cardholder record:
• Company ID (Field #2): Must match the Company ID (Field #2) found in the headers for the block
and the entire set of records, i.e. the transaction set.
• Cardholder Identification (Field #3): The Cardholder ID found in the T4 must be the same as the
Cardholder ID found in all of the Card Account records (T3s) associated with this cardholder. That
is, Field #3 in this cardholder record (T4) must match Field #2 in Card Account records (T3s) for
this cardholder’s accounts.
• Hierarchy Node (Field #4): This hierarchy node must be an existing node as specified in the
Organization Record (T10). The Hierarchy must be created before cardholder records can be
added. Cross check with Card Account (T3) and Company (T10) records.
CARD TRANSACTION – Type 5
The Card Transaction record type contains information on a specific Visa commercial card transaction such
as a purchase, or return. This information includes details such as identifiers, supplier/vendor information,
transaction amounts, tax amounts, and other supplemental information.
The Card Transaction records are used to provide detailed information about particular transactions. For an
individual Card Transaction record, the particular transaction is determined by the Primary Key: the
Account Number (Field #2), Posting Date (Field #3), Transaction Reference Number (Field #4), and the
Sequence Number (Field #5). These four fields are required and cannot be empty, zeros or spaces.
Together they must uniquely represent a valid transaction. These fields are indicated by a “**” following the
field name. All attributes contained in this record type belong to the transaction indicated by the primary
key.

For Add:
• The corresponding Card Transaction (based on the Account Number, Posting Date, Transaction
Reference Number, and Sequence Number) must not already exist in the transaction.
• The Account Number related to the Card Transaction must exist, and the Hierarchy Node related to
the card account (or, for consolidated accounts, the Hierarchy Node related to the billing account)
must be active on the transaction’s Posting Date. This implies that Card Account (T3), Company
(T6), and Organization (T10) records corresponding to this card transaction must be previously loaded
into the system.
For Change:
• The corresponding Card Transaction must exist in the application, and not have any dependencies.
For Visa Europe originated Visa Purchasing transactions, please refer to Appendix D for further
considerations.
Card Transaction (5)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
or 4.

FORMAT SOURCE
2 Account X(19) TCR0 (5-23) Cardholder Account For Add:

• Required.
front of the card.
• Must be numeric.
• For loading into VIS, must
begin with a 4.
• The Account Number related
to the Card Transaction must
exist, i.e. the Card Account
(T3) record must exist in the
file being loaded, or in a
previously loaded file.
• The Hierarchy Node related to
the card account must be
active on transaction Posting
Date, i.e. the corresponding
T10 record must be
previously loaded.
• If Account Number is
consolidated, the Hierarchy
Node related to the billing
account must be active on
transaction Posting Date.
3 Posting Date** 9(08) Date the amount of this For Add:
transaction is applied to
• Required.
the account. This date
works directly with Period • Must be a valid date in
in field 6. MMDDCCYY format.
• Date must be contained in the
range of the Period in field 6.
4 Transaction X(24) BASE II Reference Number of a For Add:
Reference TCR0 (27- transaction.
• Required. Must be different
Number** 49)
from zero if the transaction
type code is 10 (Purchase), 11
(Credit Voucher), 20 (Manual
Cash Disbursement), 22
(ATM Cash Disbursement) or
80 (Convenience Checks).
• Optional for all other
transaction types.
field to be empty.

FORMAT SOURCE
5 Sequence 9(10) This is not Transaction Sequence For Add:

Number** the BASE II Number assigned by the
• Required.
sequence Processor during the
number. posting process to • Must be numeric.
uniquely identify a • Must be unique within this
transaction within a posting run.
posting run.
6 Period 9(05) Billing Period number For Add:
assigned in this file or
• Required.
previously sent.
For Change:
The Posting Date in field
3 must fall within the date • Cannot contain ‘\’ in the first
range of this Period. position, which causes the
field to be empty.
For Add/Change:
• Must have been previously
sent.
7 Acquiring BIN 9(06) BASE II Acquiring Bank For Add::
TCR0 (28- Identification Number
• Required if the transaction
33) (BIN) of a supplier related
to the transaction.
(ATM Cash Disbursement),
or 80 (Convenience Checks).
transaction types.
For Change:
8 Card Acceptor ID X(26) BASE II Reserved for future use. For Add:
TCR1 (81-
103)
position.
For Change:

FORMAT SOURCE
9 Supplier Name X(26) BASE II Supplier name included in For Add:

TCR0 (92- a transaction.
116)
type code is 11 (Credit
Voucher), 20 (Manual Cash
Disbursement), 22 (ATM
Cash Disbursement), or 80
(Convenience Checks), and
Merchant Category Code is
not 6012 (Financial
Inst./Merchandise).
transaction types.
field to be empty.
For Change:
10 Supplier City X(14) BASE II City of a supplier included For Add:
TCR0 (117- in a transaction.
129)
or 80 (Convenience Checks)
and Merchant Category Code
is not 6012 (Financial
Inst./Merchandise).
transaction types.
field to be empty.
For Change:

FORMAT SOURCE
11 Supplier X(04) BASE II Code of a supplier state or For Add:

State/Province TCR0 (142- province included in a
• Not required.
Code 144) transaction.
• If no value is provided, blank
Validated only in US is used.
and Canada.
• If provided for US and
Canada, must be a valid
supplier’s country.
For Change:
12 Supplier ISO 9(05) BASE II International Organization For Add:
Country Code TCR0 (130- for Standardization (ISO)-
132) assigned code of a country
where the supplier is
located.
transaction types.
• If required, must be a valid
country code.
For Change:
13 Supplier Postal X(14) BASE II Postal code of a supplier For Add:
Code TCR0 (137- location included in a
• Not required.
141). transaction.
Alternate • Cannot contain ‘\’ in the first
source of position, which causes the
data is field to be empty.
TCR6 (144- For Change:
154) for
Visa Europe • Not updateable. If provided,
originated the value will be ignored.
Visa If data is provided in the TCR6
Purchasing record, that data overwrites any
transactions data from the TCR1.

FORMAT SOURCE
14 Source Amount 9(16) BASE II Supplier Source Amount Two decimal places are implied
TCR0 (77- of a transaction. (1234 = 12.34).
88)
For Add:
• Required.
• May not be all zeros.
For Change:
field to be empty.
For Add/Change:
15 Billing Amount 9(16) BASE II Amount to be billed or Two decimal places are implied
TCR0 (62- credited to the Cardholder. (1234 = 12.34).
73)
For Add:
• Required.
For Change:
field to be empty.
For Add/Change:
16 Source Currency 9(05) BASE II Currency of the Source For Add:
Code TCR0 (89- Amount in which the
• Required.
91) transaction was made.
For Change:
field to be empty.
For Add/Change:
Currency Code.

FORMAT SOURCE
17 Merchant 9(04) BASE II Four (4)-digit numeric For Add:

Category Code TCR0 (133- classification identifier,
136) modeled after the
Standard Industrial
Classification (SIC) code,
and designed to group
suppliers in similar lines of
business.
• Must be equal to 6010 or 6011,
6012, 6050 or 6051 if the
transaction type code is 20
(Manual Cash Disbursement),
22 (ATM Cash
Disbursement), or 80
(Convenience Checks).
transaction types.
• If required, must be a valid
Merchant Category Code.
For Change:

FORMAT SOURCE
18 Transaction Type X(02) Code identifying the type Values:

Code of Account posting
10 = Purchase
resulting from a
transaction. 11 = Credit Voucher
20 = Manual Cash Disbursement
CREDITS: 22 = ATM Cash Disbursement
Payments = 30, 31 30 = Payment Reversal - NSF
Check
Other Credits = 11, 61,
63,65, 71, 73 31 = Payment
DEBITS: 40 = Finance Charge
Purchases, Debits = 10, 50 = Annual Fee
20, 22, 62, 64 66, 80,
52 = Miscellaneous Fees
Fees = 40, 50, 52, 54, 56,
54 = NSF Check Fee
82, 84, 86, 88
56 = Report Fee
61 = Credit Adjustment
62 = Debit Adjustment
63 = Finance Charge Credit
Adjustment
64 = Finance Charge Debit
Adjustment
65 = Other Credits
66 = Other Debits
71 = Fuel Discount
73 = Non-Fuel Discount
80 = Convenience Checks
82 = Convenience Checks Fees
84 = Travelers Checks Fees
86 = ATM Fees
88 = Late Fees
For Add:
• Required.
• Must be a valid value.
For Change:

FORMAT SOURCE
19 Transaction Date 9(08) BASE II Date on which transaction For Add:

TCR0 (58- was made at the merchant
• Required.
61) site, merchant website, or
point of sale. For Change:
Date must be equal to or • Cannot contain ‘\’ in the first
higher than the Account position, which causes the
Open Date and the field to be empty.
Posting Date.
20 Billing Currency 9(05) BASE II Currency in which For Add:
Code TCR0 (74- transaction amount is
• Required.
76) billed.
For Change:
field to be empty.
For Add/Change:
• If changed, must be a valid
Currency Code.
21 Tax Amount 9(16) BASE II For U.S.: Sales Tax Two decimal places are implied
TCR6 (5-16) Amount included by Point (1234 = 12.34).
of Sale (POS)-capable
For Add/Change:
suppliers.
• Not required.
For Canada: Provincial
Sales Tax (PST) Amount • Cannot be provided if VAT
or QST (only for Quebec) Amount is provided.
included by Point of Sale • If provided, must be numeric.
(POS) capable suppliers.
For Change:
The cardholder’s
• Cannot be provided if Tax2
state/province code and
Amount has already been
the presence of a tax rate
processed as being an HST.
for QST determine if the
amount is used to calculate • For Visa Europe originated
QST or not. QST is only Visa Purchasing transactions,
valid for Quebec. field must NOT contain
Transaction VAT Total
Not applicable for Visa
Europe originated Visa
Purchasing transactions.
22 Dispute Amount 9(16) Amount in dispute for a Two decimal places are implied
transaction. (1234 = 12.34).
For Add/Change:
• Not required.

FORMAT SOURCE
23 Dispute Reason 9(01) Code indicating the reason Values:

Code for dispute of a
1 = Presented item is not the
transaction.
requested item
2 = Item is illegible
3 = Data image is incomplete
4 = No image was transmitted
For Add/Change:
• Not required.
value.
24 Dispute Date 9(08) Date of dispute for a For Add/Change:
transaction.
• Not required.
• If provided, must be later than
or equal to the company’s
effective date.
• Must be in a MMDDCCYY
format or zeros.
25 Commodity Code X(04) BASE II Code identifying a For Add/Change:
TCR6 (76- Commodity for Value
• Not required.
79) Added Tax (VAT)
purposes.
Visa
Europe: All For VAT purpose, the
- TCR6 (76- commodity code means
79) “line item detail” (LID) or
“summary tax data”
(SUMM).
For Visa Europe
originated Visa Purchasing
Transactions: not required
by corporate. However, if
provided must also include
option of XML or XMLL.
Note: this is not to be
confused with the Item
Commodity Code field in
Record Type 7.

FORMAT SOURCE
26 Supplier VAT X(20) BASE II Supplier Value Added Tax For Add:
Number TCR6 (31- (VAT) Identification
• Not required.
50) Number.
For Change:
Visa For Visa Europe
Europe: originated Visa Purchasing • Not updateable. If provided,
SVAT / Transactions: Must include the value will be ignored.
LID – two-character alpha
TCR6 (31- Country prefix
50)
VGIS –
Party”SU”\
Ref”VA”
27 Supplier Order X(25) BASE II Supplier Purchase Order For Add/Change:
Number TCR1 (133- Number of a Card
• Not required.
157) transaction.
When For Visa Europe
TCR1 (129) originated Visa Purchasing
=1 transactions: Must contain
Supplier Invoice Number
Visa
Europe:
SVAT /
LID –
TCR1 (133-
157)
VGIS –
InvoiceHea
der\Invoice
Number
28 Customer VAT X(14) BASE II Customer Value Added For Add/Change:
Number TCR6 (51- Tax (VAT) Registration
• Not required.
63) Number.
Visa For Visa Europe

Europe: transactions, must include
SVAT /
two character alpha
LID –
Country prefix
TCR6 (51-
63)
VGIS –
Party”BY”\
Ref”VA”

FORMAT SOURCE
29 VAT Amount 9(16) BASE II Value Added Tax (VAT) Two decimal places are implied
TCR6 (18- Amount of a Card (1234 = 12.34).
29) transaction.
For Add/Change:
Note: this field is no
• Not required.
longer used in the VIS
application. Calculation is • Cannot be provided if Tax
now based on an internal Amount (Field #21 – Sales
cost allocation translation Tax Amount, PST Amount)
table. or Tax2 Amount (Field #30 –
GST Amount) is provided.
For Visa Europe
originated Visa Purchasing • The supplier’s country code
Card transactions, must must be different from U.S.
contain the transaction (840).
level VAT amount. • Must be numeric.
30 Tax2 Amount 9(16) BASE II Goods and Services Tax Two decimal places are implied
TCR6 (18- (GST) or Harmonized (1234 = 12.34).
29) Sales Tax (HST) Amount
For Add/Change:
of a transaction.
• Not required.
Note: Distinction is made
between GST and HST • Cannot be provided if VAT
based on the cardholder’s Amount (Field #29)is
state/province code, provided.
country code, and the • The supplier’s country code
availability of a tax rate. must be different from U.S.
See notes following the (840) or the Cardholder’s
transaction for additional country code must be Canada
detail. (124).
For Visa Europe
transactions, must NOT
contain Transaction VAT
Total

FORMAT SOURCE
31 Purchase X(02) BASE II Identifies the content of Values:

Identification TC05-TCR1 the Purchase Identifier
0 = Purchase Identification
Format (129) Field (Field #33) for a
contains a free text item
transaction.
description
contains other numbers
contains Customer defined
data (CRI)
contains a Rental Agreement
Number
contains a Hotel Folio
Number
For Add/Change:
• Not required.
value.
32 Customer X(50) BASE II A code provided by the For Add/Change:
Code/CRI TC05-TCR6 cardholder at the time of
• Not required.
(111-127) the transaction.
In some Used by the commercial
cases, this clients for accounting and
field reconciliation purposes.
contains a
This is field 33 in the Base
G/L Sub-
II Edit Package Spec.
account.
33 Purchase X(76) BASE II Purchase Identification of For Add/Change:
Identification TC05-TCR1 a transaction. It is used for
• Not required.
(133-157) Point of Sale (POS)
Purchase Identification, • This is field 32 in the Base II
and may contain additional Edit Package Spec.
descriptive information to
further describe the
transaction.
34 Transaction Time 9(04) BASE II The time of day at which Format HHMM
TC05-TCR6 the transaction took place.
For Add/Change:
(107-110)
• Not required.
• If provided, must be a valid 24
hours time in HHMM format.

FORMAT SOURCE
35 Tax Amount 9(01) BASE II Code indicating if the tax Values:

Included Code TC05-TCR6 amount (which can be
0 = Tax not included
(17-17) Sales, VAT, or PST) is
included in the Source 1 = State or Provincial Tax
amount of the transaction. included
2 = Transaction not subject to tax.
For Add/Change:
• Not required.
value.
36 Tax 2 Amount 9(01) BASE II Code indicating if the Values:
Included Code TC05-TCR6 Tax2 amount (which can
0 = Transaction not subject to tax.
(30-30) be GST or HST) is
included in the Source 1 = Subject to tax
amount of the transaction.
For Add/Change:
• Not required.
value.

FORMAT SOURCE
37 Order Type Code 9(02) BASE II Code indicating how the Values:
TC05-TCR1 transaction order was
Space = Field not applicable or
(116-116) placed. It can be by
acquirer did not specify.
mail/telephone, recurring
order, installment, or other 0 = Field not applicable or
mail order. acquirer did not specify.
1 = Single transaction for a
mail/telephone order.
2 = Recurring transaction.
3 = Installment payment.
4 = Unknown classification/other
mail order.
5 = JET Secure Electronic
Commerce Transaction™
with cardholder certificate.
6 = Non-Authenticated Security
Transaction with SET™
merchant certificate.
Transaction without SET
merchant certificate, such as a
channel-encrypted
transaction.
8 = Non-secure transaction.
Transaction that does not
comply with SET, and the
merchant is SET-capable.
For Add/Change:
• Not required.
value.
38 Message X(16) BASE II The Message Identifier is For Add/Change:
Identifier TC05-TCR6 used to link the TC50
• Not required.
(92-106) acquirer-provided
enhanced data records
with the draft data
transaction.

FORMAT SOURCE
39 Processor X(52) A value used by the For Add/Change:

Addendum Key Processor to identify/link
• Not required.
this financial record to its
appropriate addendum or
enhanced data record.
If value present it will be
used for matching.
40 Merchant Profile 9(12) MIER (2- A Visa value assigned to For Add/Change:
Service Identifier 13) each unique merchant
• Not required.
(MPS-ID) location.
For Change:
• If provided, must exist in the
application.
41 Usage Code 9(01) BASEII A value representing either Values:
TC05-TCR0 the purchase or
For Purchases:
(147) chargeback re-
presentment. 1 = First Presentment
2 = Second Presentment
For Chargeback:
1 = First Chargeback
2 = Second Chargeback
For Add/Change:
• Not required.
• If provided, must be a 1 or 2.
42 Enriched X(02) Transaction retransmitted Values:
Transaction Flag with enriched data.
0 = Not Retransmitted
1 = Retransmitted
For Add/Change:
• Not required.
value.
43 Billing Account X(19) Account responsible for For Add/Change:
Number billing for One Card
• Not required.
product.
44 DDA Number 9(15) Account number to be For Add/Change:
debited for AutoPay ACH.
• Not required.
For Change:
application.

FORMAT SOURCE
45 DDA Savings 9(15) Savings account number For Add/Change:

Number from which payment is
• Not required.
made.
For Change:
application.
46 Dispute Status X(02) Status describing the For Add/Change:
Code current stage of dispute
• Not required.
processing.
47 Matched 9(01) Indicates whether a Values:
Indicator transaction has been 0 = Not Matched
matched to an order.
1 = Matched
Issuer specific definition.
For Add/Change:
• Not required, defaults to 0.
value.
48 Routing Number 9(10) Bank routing number of For Add/Change:
payment account.
• Not required.
For Change:
application.
49 Authorization X(06) Identifying value that For Add/Change:
Number comes with the
• Not required.
transaction.
For Change:
application.
50 Cardholder X(02) Online transaction For Add/Change:
Transaction approved by cardholder.
• Not required.
Approval Issuer specific.
51 Extract ID 9(15) Number identifying in For Add/Change:
which extract the
• Not required.
transaction was processed.
For Change:
application.

FORMAT SOURCE
52 Memo Post Flag 9(01) Indicates transaction is Values:

memo posted to
0 = Not Posted
cardholder. Issuer specific.
1 = Posted
For Add/Change:
• Not required.
value.
53 Statement Date 9(08) Date when transaction will For Add/Change:
appear on the statement.
• Not required.
MMDDCCYY format or
zeros.
54 User Data 1 X(20) For Visa User defined transaction For Add/Change:
Europe, data.
• Not required.
SVAT / For Visa Europe
LID – n/a originated Visa Purchasing
transactions, contains Ref
VGIS –
ACD – customer specified
InvoiceHea
reference
der\Ref”AC
D”
55 User Data 1 X(20) Issuer specific. For Add/Change:
description For Visa Europe • Not required.
transactions, contains
VGIS-ACD
Europe: data.
• Not required.
VGIS –
AWE – customer
InvoiceHea
specified cost centre
der\Ref”A
WE”
description For Visa, Europe • Not required.
VGIS-AWE

FORMAT SOURCE
Europe, data.
• Not required.
contains For Visa Europe
SVAT / originated Visa Purchasing
LID – n/a transactions, contains Ref
IV – original invoice
VGIS –
number (used on credit
InvoiceHea
notes only)
der\Ref”IV
”
VGIS-IV
Europe, data.
• Not required.
VGIS –
PONum – customer
InvoiceHea
specified Purchase Order
der\PONu
Number
m
VGIS-PONUM
data.
Europe, • Not required.
transactions, contains Net
VGIS - Transaction Value
InvoiceSum
mary\Invoi
ceTotals\N
etValue
NET TXN VALUE

FORMAT SOURCE
64 Visa Commerce X(20) Traces individual payment For Add/Change:

Batch ID to batch in which it
• Not required.
originated.
65 Visa Commerce 9(08) Date that payment For Add/Change:
Payment transaction was submitted
• Not required.
Instruction Date to Visa Commerce.
Denotes when buyer • If provided, must be a
scheduled payment. MMDDCCYY format or
zeros.
66 Line Item 9(01) Line Item has been Values:
Matched matched. Issuer Specific.
0 = Not Matched
Indicator
1 = Matched
For Add/Change:
• Not required.
value.
67 Issuer-Defined X(02) Issuer specific. For Add/Change:
Usage Code • Not required.
68 Source X(10) Source of enhanced For Add/Change:
transaction information.
• Not required.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
73 Reserved Field X(30) Reserved for Future Use. For Add/Change:
• Not required.
• Not required.

FORMAT SOURCE

• Not required.
• Not required.
Card Transaction (T5) Summary Notes:
The following elements found in this record type are critical to understanding the Card Transaction record:
field cannot be longer than 16 characters. The Card Account (T3) record for the account number
to which this transaction belongs must exist in a previous file or the starter file.
• Posting Date ((Field #3): The Posting Date must be equal to or greater than the Transaction Date,
and cannot be earlier than the Company Effective Date (T6). The date must also be greater than or
equal to the Account Open Date of the associated Card Account (T3). Note: the Posting Date
must fall within the Billing Period Date Range.
• Acquiring BIN (Field #7): This field is required if the Transaction Code (Field #18) is 10, 11, 20, 22,
or 80. The Acquiring BIN is a non-changeable field. Visa’s enriched data processing will try to
enrich this field, if possible.
• Card Acceptor ID (Field #8): Although this field is reserved for future use, it is also non-changeable.
• Supplier Name (Field #9): This field is required if the Transaction Code (Field #18) if 11, 20, 22, or
80 and the MCC (Merchant Category Code – Field #17) is not 6012. This field is non-changeable.
• Supplier City (Field #10): Supplier City is required if the Transaction Code (Field #18) is 11, 20, 22,
or 80, and the Merchant Category Code is not 6012. If not supplied “Unknown” will be used.
• Supplier State/Province Code (Field #11): Field is non-changeable.
• Supplier ISO Country Code (Field #12): Supplier ISO Country Code is required if the Transaction
Code (Field #18) is 11, 20, 22, or 80, and the Merchant Category Code is not 6012. This field is
non-changeable.
• Supplier Postal Code (Field #13): Field is non-changeable.
• Merchant Category Code (Field #17): Merchant Category Code is required if the Transaction Code
(Field #18) is 10, 11, 20, 22, or 80. It must be 6010 or 6011, 6012, 6050 or 6051 if the code is 20,
22, or 80. This field is non-changeable.
• Transaction Type Code (Field #18): This field is non-changeable.
• Transaction Date (Field #19): The date provided must be less than or equal to the Posting Date. It
must be greater than or equal to the Account Open Date, and less than or equal to the load date. It
cannot be a future date.
• Billing Currency Code (Field #20): There cannot be more than two (2) Currency Codes per
company.
• Tax Amount (Field #21): This field is used in Cost Allocation to calculate/display the Net Amount
to the user. The calculation is Net Amount = Billing Amount – Tax Amount, and is only calculated
if the cardholder did not provide the tax.
• Supplier VAT Number (Field #27): This field is non-changeable.
• Tax2 Amount (Field #30): If the HST Rate is available in the VIS database for the cardholder’s
state/province, then HST is calculated. If the GST Rate is available, then the GST is calculated.
VIS relies on an international tax rates table to be correctly set up, if GST/HSST/PST/QST value
is to be calculated. The HST is only valid for Canada. This field is also used in Cost Allocation to
calculate/display the Net Amount to the user. The calculation is Net Amount = Billing Amount –
Tax Amount and is only calculated if the cardholder did not provide the tax. The calculation is only
done for Canadian suppliers, or if the cardholder is from Canada.
For tax-related fields, the following relationships apply:
COMPANY – Type 6
The Company record type contains information describing a single company. This record type is part of the
starter data (See section on creating a VCF 4.0 file.) The Company record must be loaded prior any
account, cardholder, or transactional information.
Company records are used to provide detailed information about a Client Company. The particular
Company identified in this record is determined by the Primary Key for the record: the Company
Identification (Field #2), and the Company Name (Field #3). These two fields are required and cannot be
empty, spaces or zeros. They must uniquely represent a Client Company. These fields are indicated by a
“**” following the field name. All account attributes contained in this record type belong to the Company
indicated by the primary key.

For Add:
• The Company Identification must not already exist in the application.
For Change:
• The Company ID must exist in the application without any dependencies.
Company (6)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
or 4.
• Required.
a unique company among
multiple companies in an • Must be numeric.
issuer’s portfolio. • Must not already exist in the
application.
For Change:
Company (6)

FORMAT SOURCE
3 Company Name** X(80) Client company name. For Add:

• Required.
For Change:
field to be empty.
4 Address Line 1 X(80) First line of the client For Add/Change:
company address.
• Not required.
5 Address Line 2 X(80) Second line of the client For Add/Change:
company address.
• Not required.
6 City X(20) Name of the city where For Add/Change:
the client company is
• Not required.
located.
7 State/Province X(04) Client company’s For Add:
Code state/province code.
• If no value is provided, blank
Validated for US and is used.
Canada only. For Change:
• If value provided is ‘\’, blank
is used.
For Add/Change:
• In US and Canada, must be a
valid state/province code for
the company’s country.
8 ISO Country Code 9(05) BASE II International Organization For Add:
Clearing and for Standardization (ISO)-
• Required.
Settlement assigned Country Code of
Codes the client company • Must be a valid country code.
location. For Change:
9 Postal Code X(14) Postal code of the client For Add/Change:
company location.
• Not required.
For American companies,
it contains the zip code.
For companies outside of
the United States, it
contains the country
postal code.
Company (6)

FORMAT SOURCE
10 Fiscal Year Date 9(08) Fiscal Year End Date of For Add:
the client company.
• Required.
When adding a new • Expected to be future date.
company, this year’s fiscal
date is given. For Change:
field to be empty.
For Add/Change:
MMDDCCYY format.
11 Spending Limit 9(16) Total Spending Limit for Two decimal places are implied
the associated with this (1234 = 12.34).
client company.
For Add/Change:
• Not required.
12 Card Type 9(01) Code identifying the type Values:
1 = Corporate
The Processor can specify
2 = Purchasing
All Products in the Load
function. 3 = Business Credit
Note that Fleet Service is 4 = Commercial
covered in Purchasing
5 = Fleet
Card.
6 = Distribution
7 = Business Debit
9 = Multiple Card Types
For Add:
• Required or the default is 2.
For Change:
field to be empty.
For Add/Change:
value.
Company (6)

FORMAT SOURCE
13 Issuer Name X(40) Name of the Issuing Bank For Add:

that provides the
• Required.
Corporate or Purchasing
Cards to the client For Change:
company. • Cannot contain ‘\’ in the first
field to be empty.
14 Organization 9(01) Indicator of who manages Values:
Hierarchy the organization hierarchy
0 = Member Financial
Management of the company.
Institution/Data Processor
Indicator
1 = Client
For Add:
• Required.
For Change:
• Cannot start with ‘\’.
For Add/Change:
value.
15 Effective Date 9(08) Date on which a Company For Add:
is effective, i.e. is known
• Required or default to
to the Visa processing
Header Processing Date.
system.
• Must be in MMDDCCYY
The Effective Date must format.
be prior to or equal to the
Header Processing Date in • If supplied, must be earlier
order to create the than or equal to the Header
Company record and the Processing Date.
Organization records. For Change:
No data can be created • Not updateable. If provided,
before the Effective Date. the value will be ignored.
Account Open date may
be earlier than Company
Effective Date.
16 Address Line 3 X(80) Third line of client For Add/Change:
company address.
• Not required.
Company (6)

FORMAT SOURCE
17 Federal 9(01) Indicates whether the Values:

Organization company is a Federal
0 = No
Indicator Organization.
1 = Yes
For Add:
• Zero (0) will be used if no
value is provided.
For Add/Change:
• Not required.
• If provided, must be a 0 or 1.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Company (T6) Summary Notes:
The following elements found in this record type are critical to understanding the Company record:
• ISO Country Code (Field #8): This must be a valid code value in the current country code table. If
data is missing, the ISO Country Code in the Cardholder (T4) records will be used. This field is
non-changeable.
• Card Type (Field #12): Card Type is matched against the Card Type in the Period (T11) and Card
Account (T3) records. The Card Type in this T6 record will take precedence over any other card
types in other record types.
• Effective Date (Field #15): Although this field has the same name as fields in other record types, the
Effective Date field in T6 records indicates when the Client Company became effective in the
application. This date must be prior to the Processing Date (Field #4) found in the header of a load
and transactions cannot be dated earlier than the Effective Date in this record. The Card Account
(T3) Account Open Date, may, however, be earlier than the Company Effective Date.
ORGANIZATION – Type 10
The Organization record type contains information describing a node in the organizational hierarchy of a
company. The organization’s hierarchical structure needs to be established in the reporting system prior to
the addition (loading) of cardholder, account, or transactional data.
The organization is uniquely identified by the following Primary Key fields: Company Identification (Field
2), and Hierarchy Node (Field 3). These fields are required and cannot be empty or contain all zeros or
spaces. They must uniquely represent an organization. These fields are indicated by a “**” following the
field name. All attributes contained in this record type belong to the organization indicated by the primary
key.

For Add:
• The Company Identification must exist in the application.
• The Hierarchy Node must not already exist in the application.
For Change:
• The Hierarchy Node must exist in the application, and must be active.
Organization (10)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
• Required and must be a 1,3 or
4.
• Required.
a unique entity among
multiple companies in an • Must exist in the application.
issuer’s portfolio.
Organization (10)

FORMAT SOURCE
3 Hierarchy Node** X(40) String identifying the For Add:

Hierarchy Node which
• Required
represents the organization
an account and cardholder • Must not already exist in the
are associated with. application.
Organization may be For Change:
functional or billing related • Must be previously sent.
or whatever structure suits
• Must be active.
the company.
A Cardholder or
Account may not be
added before the
Hierarchy is sent or
established in the Visa
system.
4 Parent Hierarchy X(40) Parent Hierarchy Node on This field must be blank if this
Node an Organization chart to record is the Top Node.
which this Node reports
For Add:
or is associated.
• Must not be blank if a top-
There can be many Parent
level node already exists.
Nodes within the
structure, but there can be For Change:
only one Top Node. • Cannot contain ‘\’ in the first
field to be empty.
• The Top Node cannot be
moved to another Node
Level. Parent of Top Node
must be blank.
• Cannot be a child of node
moved.
For Add/Change:
• Must be active.
• Must be a different value from
Hierarchy Node.
Organization (10)

FORMAT SOURCE
5 Effective Date 9(08) Future dates cannot be For Add/Change:

used. Must be equal to
• If the Effective Date is earlier
or lower than the
than the Start Date of the new
Header Processing
Parent Node, then the Start
Date.
Date of the new Parent Node
For Add transaction code will be used instead of the
(adding a new node), this Effective Date.
is the date when the new • If no value is provided, the
node became effective; Header Processing Date is
therefore, this is the date used.
the relation with Parent
Hierarchy Node started. • Must be a valid date.
• Must be earlier than or equal
For Change transaction
to the Header Processing
code (changing a Parent
Date.
Hierarchy Node), date the
relation with the new For Change:
Parent Node became • If the Effective Date is earlier
effective. than the Start Date of the
The relation with the old Node itself, then the Start
Parent Hierarchy Node is Date of the Node will be used
ended the day before the instead of the Effective Date.
Effective Date.
A Parent Hierarchy Node
change cannot be effective
before the new Parent
Hierarchy Node is started.
The Effective Date is
ignored if the Parent
Hierarchy Node specified
is the same as in the
application.
6 Description X(40) Name or label associated For Add:
with a Hierarchy Node.
• Required.
7 Manager Last X(20) Node Manager’s last For Add/Change:
Name name.
• Not required.
8 Manager First X(20) Node Manager’s first For Add/Change:
Name name.
• Not required.
9 Manager Title X(40) Title of the Hierarchy For Add/Change:
Node Manager.
• Not required.
10 Manager Training 9(08) Date a Manager was For Add/Change:
Date trained to process the
• Not required.
Cards under his/her
authority. • If provided, must be a valid
date.
Organization (10)

FORMAT SOURCE
11 Manager Phone X(14) Node Manager’s telephone For Add/Change:

Number number.
• Not required.
12 Task Order X(26) A document that specifies For Add/Change:

Number and authorizes products
• Not required.
and services required, and
the negotiated price at
which they will be
provided.
13 Contact First X(20) First name of the Contact For Add/Change:
Name (Program Coordinator).
• Not required.
14 Contact Last X(20) Last name of the Contact For Add/Change:
Name (Program Coordinator).
• Not required.
15 Contact Address X(40) First Line of address of For Add/Change:
Line 1 the Contact (Program
• Not required.
Coordinator).
16 Contact Address X(40) Second Line of address of For Add/Change:
• Not required.
Coordinator).
17 Contact Address X(40) Third Line of address of For Add/Change:

• Not required.
Coordinator).
18 Contact City X(20) City where the Contact For Add/Change:
(Program Coordinator)
• Not required.
works.
19 Contact X(04) State or province code For Add/Change:
State/Province where the Contact
• Not required.
Code (Program Coordinator)
works. • If provided, must be a valid
country.
20 Contact Country 9(05) ISO Country Code where For Add/Change:
Code the Contact (Program
• Not required.
Coordinator) works.
country code.
Organization (10)

FORMAT SOURCE
21 Contact Postal X(14) Postal code for the For Add/Change:

Code Contact’s (Program
• Not required.
Coordinator’s) business
address.
For the United States, the
zip code of the business
address.
For other countries, this is
the country postal code.
22 Contact Phone X(16) Contact’s (Program For Add/Change:
Number Coordinator’s) phone
• Not required.
number.
23 Contact Fax X(16) Contact’s (Program For Add/Change:
Number Coordinator’s) fax
• Not required.
number.
24 Contact E-mail X(140) Contact’s (Program For Add/Change:
Address Coordinator’s) electronic
• Not required.
mail address.
25 Second Hierarchy X(56) Processor-specific second For Add/Change:
Node representation of the
• Not required.
Representation Hierarchy Node.
26 Third Hierarchy X(56) Processor-specific third For Add/Change:
Node representation of the
• Not required.
Representation Hierarchy Node.
27 Tree ID X(02) Identifies the hierarchy For Add/Change:
tree this node is related to.
• Currently not validated, as
Tree is used in the sense Visa processing only
of the organization supports a single tree.
pattern.
28 Cost Center X(50) Default Cost Center for a For Add/Change:
node.
• Not required.
• If the value provided does not
“Load Transaction - Card
Account” as description.
• Must be active.
Organization (10)

FORMAT SOURCE
29 G/L Sub-account X(76) Default G/L Sub-account For Add/Change:

for a node.
• Not required.
G/L Sub-account is created
using “Load Transaction -
Card Account” as description.
relationships with G/L Sub-
accounts are removed.
• Must be active.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Organization (T10) Summary Notes:
The following elements found in this record type are critical to understanding the Organization record:
• Hierarchy Node (Field #3): The Hierarchy Node is matched against the Hierarchy Nodes in the T3
(Card Account) and T4 (Cardholder). The Hierarchy Node cannot be equal to the Parent Hierarchy
Node.
• Effective Date (Field #5): The Effective Date, i.e. the date at which this new node relationship
begins, will be matched against the Card Account (T3) and Cardholder (T4) Account Open Date,
and must be earlier than or equal to that date. For adding or changing records, if the Effective Date
is prior to the Start Date of the Parent Node, then the Start Date of the New Parent Node will be
used instead of the Effective Date. That is, the new relationship cannot begin prior to the start date
of the New Parent Node. For deleting, if the Effective Date is earlier than the Start Date of the
current Parent Node, then the Start Date of the new current node will be used. Again, the
relationship cannot be removed prior to the start date of the new current node.
• Tree ID (Field #27): In situations where the corporation has multiple hierarchies it wishes to track,
for example, one for reporting, and another for billing, the use of a Tree ID allows the user to set
up and report against multiple hierarchies. Use of this structure can be quite complex, and
additional research should be performed to validate its use. At present, Visa processing only
supports the use of one tree.
• Cost Center (Field #28) and G/L Sub-account (Field #29): Use of these accounting identifiers
allows the user to automatically allocate charges against a pre-defined cost center or accounting
code.
PERIOD – Type 11
The Period record type defines information about the billing period, as assigned by the Processor. These
periods are used to tie individual transactions to the proper account balances. A billing period is also
referred to as a billing cycle. A period, or cycle, is a defined amount of time during which card-related
activities occur and are recorded for reporting and/or billing on a defined time interval.
A Period record is used to provide detailed information about a Client Company’s Billing Period and how
that billing period is defined. The particular Billing Period identified in this record is determined by the
Primary Key for the record: the Company Identification (Field #2), the Period (Field #3), and the Card
Type (Field #4). These three fields are required and cannot be empty, all zeros or spaces. They must
uniquely identify a Client Company’s Billing Period. These fields are indicated by a “**” following the field
name. All period-related attributes contained in this record type belong to the Period indicated by the
primary key.

For Add:
• The Company Identification must already exist in the application.
• The Period must not already exist in the application, and
• The Card Type must be a valid card type defined previously for the company.
For Change:
• The Company ID must exist in the application without any dependencies.
• The Period must exist in the application without any dependencies, and
• The Card Type must be a valid card type defined previously for the company.
Period (11)

FORMAT SOURCE

Change transaction
transaction.
For Add/Change:
or 4.
• Required.
a unique entity among
multiple companies in an • Must exist in the application.
issuer’s portfolio.
Period (11)

FORMAT SOURCE
3 Period** 9(05) Billing Period number For Add/Change:

assigned by the Issuer/
• Required.
Processor.
The Billing Period number
must be unique for a For Add:
particular client company, • Must not duplicate a
i.e. a Company cannot previous billing period
have multiple billing number.
periods identified by the
same number. For Change:
• Must be previously sent.
4 Card Type** 9(01) Code identifying the type Values:
1 = Corporate
Should agree with the
2 = Purchasing
Company record Card
type unless multiple card 3 = Business Credit
types are used. For
4 = Commercial
multiple card types, there
is no cross-check between 5 = Fleet
the T6 and T11 fields.
6 = Distribution
The T11 Card Type field
is not used in VIS 7 = Business Debit
reporting.
For Add/Change:
• Required.
• Must be a valid value as listed
above.
Period (11)

FORMAT SOURCE
5 Start Date 9(08) Start Date of the Billing For Add:

Period.
• Required.
Please see Billing Period • Must be unique.
rules at the end of this
section. • If not the first billing period,
must equal the previous End
Date + 1.
For Change:
field to be empty.
For Add/Change:
• Must be a MMDDCCYY
format.
the company effective date.
• Must not already exist for the
Company and Card Type.
• Must be earlier than the Period
End Date.
6 End Date 9(08) End Date of the Billing For Add:
Period.
• Required.
Please see Billing Period • Must be unique.
rules at the end of this
section. • If not the first billing period,
must equal the next cycle’s
Start Date - 1.
For Change:
field to be empty.
For Add/Change:
• Must be a MMDDCCYY
format.
the Start Date.
• Must not already exist for the
Company and Card Type.
Period (11)

FORMAT SOURCE
7 Period Complete 9(01) Indicates if this billing Values:

Indicator period is Open or Closed.
0 = OPEN
1 = CLOSED
For Add:
• Required.
For Change:
field to be empty.
For Add/Change:
• Must be a 0 or 1.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Period (T11) Summary Notes:
The following elements found in this record type are critical to understanding the Period record:
• Company Identification (Field #2): The Company Record (T6) for the company utilizing this Period
record must be previously loaded into the system.
• Period (Field #3): The Period value is matched against the Period field in the Account Balance (T1)
record, and the Card Transaction (T5) record.
• Card Type (Field #4): The card type must match a valid Card Type in the Company (T6) record. The
Card Type must also match the Account Record’s Card Type (T3). Note: there is no
complementary “Multiple Card Types” value in the T11 at this time, and there is no cross-check
between the T11 Card Type field, and the T6 Card Type field.
• Start Date (Field #5): The Start Date of a period must be the same as the End Date of the Previous
Period, plus one day. It must also be later than the Effective Date of the Company. The Start Date
must also not exist for the Company and Card Type.
• End Date (Field #6): The End Date of the period must equal the Start Date of the Next Period
minus one day. It must also be later than the Start Date of the period, and must not already exist
for the Company and Card Type. Transaction Posting Dates (T5) records are compared to the
period Start Date and End Date to see which billing period they belong to.
• Period Complete Indicator (Field #7): This field is cross checked within the application to see if the
previous Period is closed.
For clarification, please review the earlier sections in the specification on the topics of billing accounts,
billing periods, and billing cycles.
HEADER/TRAILER
The purpose of header and trailer records is to segregate information related to a specific company.
Headers and trailers pass data required to process the file correctly in Visa systems and ensure through
record types and ‘totals’ counts that the file is complete and accurate. Set headers and trailers delimit the
beginning and end of data for a company. Block headers and trailers uniquely identify the type of
transactions (records) in each record block. The Transaction Set Header, Block Header, Transaction Set
Trailer, and Block Trailer are all constructed with fundamentally the same fields. Various fields may be
validated in some instances and not validated in others. Headers and trailers are further described in
Chapter 2, Preparing Data Files. In the following chart, the primary key fields are referenced by a “**”
following the field name.
Header/Trailer
NO. FIELD NAME FIELD DESCRIPTION EDIT CRITERIA

FORMAT
1 Transaction 9(01) Primary Key. Values:

Code** Codes indicate either Header or 6 = Header for a transaction set
Trailer, and either Set or Block.
7 = Trailer for a transaction set
8 = Header for a block of
transactions/records
9 = Trailer for a block of
transactions/records
Required and must be one of valid values
above.
2 Company 9(10) Primary Key. Required for headers and trailers.
Identification** Issuer-assigned ID identifying the
company whose data is in this
transaction set or block.
3 Sequence 9(05) Primary Key. Required for headers and trailers.
Number** Each transaction set is identified May be populated in transaction block
with a Sequence Number header/trailer, but not validated for block
maintained for each company. header/trailer.
This sequence number ensures
Must be numeric.
that transaction sets for a
company are processed in the Must be in strict numeric sequence with
correct sequential order. the last file sequence number loaded, by
an increment of 1.
Must not be already loaded for this
company.
4 Processing Date 9(08) This field must contain the system May be used as a default date for many
date from the processor creating fields such as T3 Effective Date, etc.
the VCF file. The Processing
Required for headers and trailers.
Date is useful information for
client and for file identification Must be a valid MMDDCCYY format.
purposes.
Must not be all zeros.
Header/Trailer

FORMAT
5 Record Type Code 9(02) For transaction block Values:

headers/trailers.
1 = Account Balance
Code indicates the type of VCF 2 = Car Rental Summary
record contained in the
transaction block. 3 = Card Account
4 = Cardholder
5 = Card Transaction
6 = Company
7 = Line Item Detail
8 = Line Item Summary
9 = Lodging Summary
10 = Organization
11 = Period
14 = Passenger Itinerary
15 = Leg-Specific Information
16 = Supplier
17 = Fleet Service
18 = Fleet Product
20 = Temporary Services
21 = Shipping Services
25 = Headquarter Relationship
26 = Lodging Detail
27 = Car Rental Detail
28 = Allocation
29 = Allocation Description
30 = Relationship
31 = Phone
99 = Reference Data
Required and must be a valid code for
block header/trailer. Should be zeros for
transaction set header/trailer.
Header/Trailer

FORMAT
6 Record Count 9(10) Total record count within a block Required for trailers.
or a transaction set.
Should be numeric.
For transaction set: Count
Must match the number of records in the
includes all records and Block
block or transaction set trailer. This
headers and trailers. Header and
applies only to trailers.
trailer for the Set are excluded.
For transaction block: Count
includes number of records within
the Block. Block header and
trailer are excluded.
7 Total Amount 9(16) For transaction set trailer: Sum Two decimal places are implied (1234 =
of the Billing Amounts in the T5 12.34).
Card Transaction record.
Must match the sum of the Billing
For transaction block trailer: Amounts in the T5 Card Transaction
Sum of the Billing Amounts in the records for this company. This is
T5 Card Transaction record. For required only for transaction set trailers
all other block trailers, should be and for the T5 block trailer. For other
zeros. trailers should be zeros.
8 Load File Format X(10) Identifies the VCF format of a Value: 4.0
file. All sets and blocks in the
Required for headers and trailers.
transaction set are expected to be
the same format.
9 Issuer X(10) Visa established with the member Required for headers and trailers.
Identification the correct value to be used in this
Must agree with Business Identification
Number field.
(BID) in the Visa system for this account.
10 Processor 9(10) Number of the Visa Processor Required for headers and trailers.
Identification which is assigned to process this Must be numeric.
Number VCF file. Visa established with
the member the correct value to
be used in this field, and that value
must be sent by the
member/processor on the file
inbound to Visa systems.
Header/Trailer

FORMAT
11 Visa Region 9(1) Identifies which Visa region the Values:

Identification file belongs to.
1 = United States
2 = Canada
3 = European Union
4 = Asia Pacific
5 = Latin America and Caribbean
6 = Central & Eastern Europe, Middle
East & Africa
Required for headers and trailers and
must be a valid code. See your Visa
Account Manager for assigned value.
12 Processor X(10) Identifies the platform or Required for headers and trailers.
Platform operating system on which the file
Reference was generated. Examples: UNIX,
MVS COBOL, AS400, etc. This
free format text field is used by
the Certifier in certifying member
VCF 4.0 files.
13 Optional Field 1 X(26) Free format. May not contain Not required.
nulls. If not in use, should be
initialized to spaces.
Header/Trailer Summary Notes:
Valid headers and trailers are required for blocks of Visa records, as well as for an entire VCF Transaction
Set (File). For additional information on their usage and requirements, see the section on How to construct
a valid VCF 4.0 File in this manual. Contact a Visa Representative to obtain information about Processor
Identification and Visa Region Identification values.
Enhanced Data Record Types
The following record types are considered to be the enhanced data portion of the VCF 4.0 record set:
• Car Rental Summary (T2)
• Line Item Detail (T7)
• Line Item Summary (T8)
• Lodging Summary (T9)
• Passenger Itinerary (T14)
• Leg-Specific Information (T15)
• Supplier (T16)
• Fleet Service (T17)
• Fleet Product (T18)
• Temporary Services (T20)
• Shipping Services (T21)
• Headquarters Relationship (T25)
• Lodging Detail (T26)
• Car Rental Detail (T27)
• Allocation (T28)
• Allocation Description (T29)
• Relationship (T30)
• Phone (T31)
• Reference Data (T99)
This section provides additional detail about the various record types designed for supporting Visa’s
enhanced data services. For further information, please contact your Visa representative.
Note: All amount fields in these enhanced data records are in the currency where the transaction took
place, i.e. the source currency.
Key Concept for Enhanced Data Records:

Item Sequence Number
An Item Sequence Number is a required field in many enhanced data records. This field should begin with
“1” and be incremented by “1” for each subsequent record of that record type based on the number of
detail records which refer to the T5 transaction.
For example, if a Car Rental Summary record (T2)says that the rental was for four days, then, if there are
any T27 records associated with the transaction (which is not required), then there should be 4 T27 records
referencing the same T5 transaction for the car rental. Each T27 would then contain data for one day of the
rental. The first T27 detail record would have an item sequence number of 00001, and the following
records would contain 00002, 00003, and 00004 in the Item Sequence Number field. The data for the detail
records is generated by the member if the member is sending the enhanced data detail records, or by Visa, if
Visa is generating this information through matching.
CAR RENTAL SUMMARY – Type 2
The Car Rental Summary record type contains summary information for Visa commercial card transactions
conducted at car rental merchants. This record provides additional details for those card transactions with
respect to rental rates, specific car rental-related charges, and rental event logistics such as pick-up and
return locations, etc.
The primary key to this record consists of four fields: Account Number (Field #2), Posting Date (Field
#3), Transaction Reference Number (Field #4), and Sequence Number (Field #5). These records are
indicated below with a “**” following the field name. The combination of these four fields must uniquely
identify a transaction record (T5) for the underlying transaction with the car rental merchant.
The following rules apply to the primary key fields in the Car Rental Summary record:
For Add:
Reference Number, and Sequence Number) must exist in the application.
• The Car Rental Information must not already exist in the application.
For Change:
• The Car Rental Information must exist in the application.
Car Rental Summary (2)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
or 4.
2 Account X(19) BASE II Cardholder Account For Add/Change:
Number** TCR0 (5-23) Number appearing on the
• Required.
front of the card.
3 Posting Date** 9(08) Posting Date of a For Add/Change:
transaction.
• Required.
• Must be a valid date.
4 Transaction X(24) Reference Number of a For Add/Change:
Reference T5 transaction.
• Required.
Number**

FORMAT SOURCE
5 Sequence 9(10) Transaction Sequence For Add/Change:

Number** Number assigned by the
• Required.
Processor during the
associated T5 posting • Must be numeric.
process to uniquely
identify a transaction
within a posting run.
6 No-Show 9(01) BASE II Indicator of a transaction Values:
Indicator TCR3 Car due to no-show charges.
0 = No
Rental (27)
1 = Yes
For Add/Change:
• Not required.
value.
7 Daily Rental Rate 9(16) BASE II Daily Car Rental Rate of a Two decimal places are implied
TCR3 Car Card transaction. (1234 = 12.34).
Rental (44-
For Add/Change:
55)
• Not required.
8 Other charges 9(16) BASE II Other charges identified Two decimal places are implied
TC50-TCR0 by the Car Rental Extra (1234 = 12.34).
Car Rental Charges Code in a Car
For Add/Change:
(138-149) Rental transaction. Car
Rental No Show Indicator • Not required.
set to Y represents no- • If provided, must be numeric.
show charges in a
transaction.
9 Check-out date 9(08) BASE II Date the customer picked For Add/Change:
TCR3 Car up the car or, in case of a
• Not required.
Rental (38- No Show or Pre-paid
43) transaction, the scheduled • If the date format is not valid,
pickup date. the value will be ignored.
10 Weekly Rental 9(16) BASE II Weekly Rental Car Rate of Two decimal places are implied
Rate TCR3 Car a transaction. (1234 = 12.34).
Rental (56-
For Add/Change:
67)
• Not required.
11 Insurance 9(16) BASE II Insurance charges of a Car Two decimal places are implied
Charges TCR3 Car Rental Card transaction. (1234 = 12.34).
Rental (68-
For Add/Change:
79)
• Not required.

FORMAT SOURCE
12 Fuel Charges 9(16) BASE II Fuel charges of a Car Two decimal places are implied
TCR3 Car Rental Card transaction. (1234 = 12.34).
Rental (80-
For Add/Change:
91)
• Not required.
13 Class Code X(02) BASE II Code identifying the class For Add/Change:
TCR3 Car of car provided in a Rental
• Not required.
Rental (92- Car transaction, such as
93) compact or mid-size.
14 One-way Drop-off 9(16) BASE II Total of any charges for Two decimal places are implied
charges TCR3 Car returning the vehicle to a (1234 = 12.34).
Rental (94- different location than the
For Add/Change:
105) Vehicle Pickup location.
• Not required.
15 Renter Name X(40) BASE II Renter’s name for a Car For Add/Change:
TCR3 Car Rental transaction.
• Not required.
Rental (106-
145)
16 Auto Towing 9(16) BASE II Total charges of any Two decimal places are implied
TC50-TCR0 Towing or Roadside (1234 = 12.34).
Car Rental Service expenses.
For Add/Change:
(41-52)
• Not required.
17 Regular Mileage 9(16) BASE II Total Mileage charges Two decimal places are implied
Charges TC50-TCR0 below the mileage limit. (1234 = 12.34).
Car Rental
For Add/Change:
(53-64)
• Not required.
18 Extra-Mileage 9(16) BASE II Total Mileage charges Two decimal places are implied
Charges TC50-TCR0 above the mileage limit. (1234 = 12.34).
Car Rental
For Add/Change:
(65-76)
• Not required.
19 Late Return 9(16) BASE II Total charges of Late Two decimal places are implied
Charges/Hourly TC50-TCR0 Return. (1234 = 12.34).
Rate Car Rental
For Add/Change:
(77-88)
• Not required.

FORMAT SOURCE
20 Return Location X(26) BASE II Destination City where car For Add/Change:
TC50-TCR0 is returned to the Rental
• Not required.
Car Rental company.
(89-113)
21 Total Tax/VAT 9(16) BASE II Total Amount of Tax or Two decimal places are implied
TC50-TCR0 Value Added Tax (VAT). (1234 = 12.34).
Car Rental
For Add/Change:
(114-125)
• Not required.
22 Telephone 9(16) BASE II Total charges for in- Two decimal places are implied
Charges TC50-TCR0 vehicle telephone (1234 = 12.34).
Car Rental expenses, including Daily
For Add/Change:
(126-137) Rental charges, if
applicable. • Not required.
23 Corporate X(16) BASE II The Corporate Client For Add/Change:
Identification TC50-TCR0 Identification.
• Not required.
Car Rental
(150-161)
24 Extra Charge X(06) BASE II Type of additional charges Values:
Code TCR3 Car added to a customer’s bill
Left Space = No extra charge
Rental (28- after checkout. Each
justify
33) position in the field can 0 = No extra charge
indicate a type of charge.
1 = Gas
2 = Extra Mileage
3 = Late Return
4 = One Way Service Fee
5 = Parking Violation
For Add/Change:
• Not required.
• If provided, each field position
must contain a valid code.
25 Days Rented 9(02) BASE II Represents the length of For Add/Change:
TC05-TCR3 rental, measured in
• Not required.
Car Rental number of days charged in
(19-20) transaction. • If provided, must be numeric.
26 Message X(16) BASE II Message Identifier in a For Add/Change:

Identifier TC50-TCR0 transaction. This
• Not required.
(23-37) information could be used
to match enhanced data
with the card transaction.

FORMAT SOURCE
27 Purchase ID X(50) BASE II Number assigned by the For Add/Change:

TC50-TCR0 merchant to the
• Not required.
(COMMGN) transaction.
Generic
It can be a Supplier Order
Data (111-
Number, a Folio Number,
135)
or a Car Rental Agreement
Number.
This information could be
used to match enhanced
data with the card
transaction.
28 Source Amount 9(16) BASE II The total amount, in Two decimal places are implied
TC50-TCR0 source currency, charged (1234 = 12.34).
(COMMGN) to the card account for the
For Add/Change:
Generic transaction.
Data (65-76) • Not required.
used to match enhanced • If provided, must be numeric.
data with the card
transaction.
29 Transaction Date 9(08) BASE II The date of the purchase, For Add/Change:
TC50-TCR0 as indicated in the
• Not required.
(COMMGN) financial record.
Generic • If provided, must be a valid
This information could be date.
Data (61-64)
data with the card
transaction.
30 Merchant 9(04) BASE II The merchant category For Add/Change:
Category Code TC50-TCR0 code for the transaction,
• Not required.
(COMMGN) as indicated in the T5
Generic financial transaction. • If provided, must be a valid
Data (102- Merchant Category Code.
105)
data with the card
transaction.
31 Supplier Name X(26) BASE II The name of the supplier, For Add/Change:
• Not required.
(COMMGN) financial transaction.
Generic
Data (77-
101)
data with the card
transaction.

FORMAT SOURCE
32 Supplier Postal X(14) BASE II Postal code of a supplier, For Add/Change:

Code TC50-TCR0 as indicated in the
• Not required.
Generic
Data (106-
110)
data with the card
transaction.
• Not required.
the financial record to this
addendum record.
If value is present, it will
be used for matching.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Car Rental Summary (T2) Summary Notes

The Car Rental Summary record is used to carry enhanced data (Level II) and Level III) for card-based
transactions with car rental merchants. Fields 26 (Message Identifier) through 33 (Processor Addendum
Key) can all be utilized to match enhanced data, potentially from third party providers, with the card’s
financial transaction details. For a more complete understanding of record types carrying enhanced data,
and how this information might be used, please refer to additional Visa publications.
LINE ITEM DETAIL – Type 7
The Line Item Detail record type contains line-by-line invoice information provided by the supplier for a
Visa commercial card transaction. This record type contains enhanced data, and is provided to enable better
reporting and tracking of commercial card programs.
The line item details carried in this record are relevant to individual line items within a particular transaction.
That transactional line item is uniquely identified by the following Primary Key fields: The Account
Number (Field #2), Posting Date (Field #3), Transaction Reference Number (Field #4), the Sequence
Number (Field #5), and the Item Sequence Number (Field #6). These five fields are required and cannot
be empty, all spaces or zeros. The first five fields listed point to a specific transaction. The last field, Item
Sequence Number, consists of sequential numbers which support the identification of multiple line items
within that transaction. These five fields must uniquely represent a single line item in a valid transaction.
These fields are indicated by a “**” following the field name. All of the data attributes contained in this
record type belong to line items for the transaction (and item number) indicated by the primary key.

For Add:
Reference Number, and Sequence Number) must exist in the transaction.
• The Line Item Detail must not already exist in the application.
For Change:
• The Line Item Detail must exist in the application.
For Visa Europe originated Visa Purchasing transactions, please refer to Appendix D for further
considerations.
Line Item Detail (7)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
or 4.
• Required.
front of the card;
transmitted by BASE II. • Must exist in the application.

FORMAT SOURCE
3 Posting Date** 9(08) Posting Date of For Add/Change:

transaction.
• Required.
4 Transaction X(24) BASE II Reference Number of For Add/Change:
• Required.
Number** 49)
5 Sequence 9(10) This is not Transaction Sequence For Add/Change:
• Required.
number. associated T5 posting • Must be numeric.
process to uniquely
6 Item Sequence 9(05) Sequence Number of an For Add/Change:
Number** item in a line item detail
• Required.
transaction. Sequentially
incremented to indicate • Must be numeric.
the successive order of the
items being listed. Does
not relate to the invoice
line number,
Identifier TC50-TCR0 transaction. An identifying
• Not required.
PURCHL field used to link draft data
(23-37) information with any
related TC50 text message
transactions.
8 Item Commodity X(16) BASE II Classification of purchased For Add/Change:
Code TC50-TCR0 item.
• Not required.
PURCHL
(41-52)
9 Item Descriptor X(26) BASE II Textual description of an For Add/Change:
TC50-TCR0 item purchased in
• Not required.
PURCHL transaction.
(53-78)
10 Quantity 9(16) BASE II Number of units Four decimal places are implied
TC50-TCR0 purchased in transaction. (123456 = 12.3456).
PURCHL
For Add/Change:
(91-102)
• Not required.

FORMAT SOURCE
11 Unit Cost 9(16) BASE II Unit Cost of an item in Four decimal places are implied
TC50-TCR0 transaction. (123456 = 12.3456).
PURCHL
For Add/Change:
(115-126)
• Not required.
12 Unit Measure X(12) BASE II Unit of Measure code used For Add/Change:
TC50-TCR0 for an item in transaction.
• Not required.
PURCHL
(103-114)
13 VAT/Tax Amount 9(16) BASE II Value Added Tax (VAT) Two decimal places are implied
TC50-TCR0 Amount associated with a (1234 = 12.34).
PURCHL line item in a Card
For Add/Change:
(127-138) transaction.
• Not required.
14 Type Supply 9(06) Indicates whether the For Add/Change:
Purchase is of type
• Not required.
‘Goods’ or of type
‘Services’. • If provided, must be numeric.
15 Last Item 9(01) BASE II Indicates whether or not Values:

Indicator TC50-TCR0 the Line Item is the last
0 = Not the last line
PURCHL one for a transaction.
(167) 1 = Last line
For Add:
• Required.
For Change:
• Must be different from ‘\’.
For Add/Change:
value.
16 VAT/Tax Rate 9(09) BASE II Value Added Tax (VAT Four decimal places are implied
TC50-TCR0 rate of a line item in a card (123456 = 12.3456).
PURCHL transaction).
For Add/Change:
(139-142)
• Not required.
17 Item Discount 9(16) BASE II Discount Amount applied Two decimal places are implied
Amount TC50-TCR0 by the merchant to the line (1234 = 12.34).
PURCHL item.
For Add/Change:
(143-154)
• Not required.

FORMAT SOURCE
18 Item Total 9(16) BASE II Total Amount for the line Two decimal places are implied
Amount TC50-TCR0 item. (1234 = 12.34).
PURCHL
For Add/Change:
(155-166)
• Not required.
19 Item Product X(12) BASE II Merchant Product For Add/Change:
Code TC50-TCR0 Identifier.
• Not required.
PURCHL
(79-90)
20 Service Identifier X(06) BASE II Value assigned to identify For Add:
TC50-TCR0 the type of information
• Required. ‘PURCHL’
Purchasing/ contained in the BASE II
(Purchasing Transaction, Line
Lodging/ record.
Item Detail) will be used if no
Car Rental
This information will value is provided.
(17-22)
determine if the line item For Change:
summary is for a Car
Rental, Lodging, or • Cannot start with ‘\’.
Purchasing Transaction.
21 Purchase ID X(50) BASE II Number assigned by For Add/Change:
TC50-TCR0 merchant to transaction.
• Not required
(COMMGN)
Generic
Data (111-
135)
Number.
data with the card
transaction.
For Add/Change:
data with the card
transaction.
• Not required.
Data (61-64)
data with the card
transaction.

FORMAT SOURCE

• Not required.
(COMMGN) as indicated in the
105)
data with the card
transaction.
• Not required.
Generic
Data (77-
101)
data with the card
transaction.
• Not required.
Generic
Data (106-
110)
data with the card
transaction.
• Not required.
addendum record.
If present, it will be used
for matching.
28 Line Item Sales 9(01) Identifies whether a sales Values:
Tax Charged Flag tax amount was charged
0 = Tax not charged
for this line item.
1 = Tax charged
For Add/Change:
• Not required.
value.
29 Item Level Usage X(02) Issuer specific usage field. For Add/Change:
Code • Not required.
30 Line Item Source X(10) Source of line tem detail For Add/Change:
(LID) information.
• Not required.

FORMAT SOURCE

• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Line Item Detail (T7) Summary Notes:
The four fields (Account Number (Field #2), Posting Date (Field #3), Transaction Reference Number
(Field #4), and Sequence Number (Field #5)) uniquely identify a single Transaction (T5). For business
situations in which this transaction involves the purchase, or return, of goods or services, multiple line items
may be involved as part of a single transaction. Iterative uses of this Line Item Detail record, with
appropriate, sequentially-assigned Item Sequence Number (Field #6) values, will allow the user to segregate
the details for each line item which was part of the original transaction.
In addition to the many line item attributes, such as quantity, item description, unit price, etc. there are
several fields in the record which may be utilized to enhance the purchase data. These are fields Service
Identifier (Field #20) through Processor Addendum Key (Field #27). Optional fields at the end of the
record can also be used to carry additional detail relevant to a particular line item.
LINE ITEM SUMMARY – Type 8
The Line Item Summary record type contains supplemental information about a transaction conducted with
a Visa commercial card. Just as Line Item Detail (T7) allows the file to carry information about individual
line items which are part of a larger purchase, Line Item Summary (T8) records provide other
data/information relevant to the entire transaction, which enhances the information carried in the Card
Transaction (T5) records.
The transaction to which this summary information applies is uniquely identified by the following Primary
Key fields: the Account Number (Field #2), Posting Date (Field #3), Transaction Reference Number (Field
#4), and the Sequence Number (Field #5). These four fields are required and cannot be empty, all zeros or
spaces. They must uniquely represent a valid transaction. These fields are indicated by a “**” following the
key.

For Add:
• The Line Item Summary must not already exist in the application.
For Change:
• The Line Item Summary must exist in the application.
Line Item Summary (8)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
or 4.
• Required.
front of the card;

transaction.
• Required.

FORMAT SOURCE
4 Transaction X(24) BASE II Reference Number of a For Add/Change:

• Required.
Number** 49)
• Required.
uniquely identify a
transaction within a
posting run.
• Not required.
(23-37) field used to link draft data
information with any
related TC50 text message
transactions.
7 Discount Amount 9(16) BASE II Discount Amount applied Two decimal places are implied
TC50-TCR0 by the merchant to the (1234 = 12.34).
PURCHA transaction.
For Add/Change:
(41-52)
• Not required.
8 Freight Amount 9(16) BASE II Total of freight or Two decimal places are implied
TC50-TCR0 shipping and handling (1234 = 12.34).
PURCHA charges for the
For Add/Change:
• Not required.
9 Duty Amount 9(16) BASE II Total charges for any Two decimal places are implied.
TC50-TCR0 import/export duty (1234 = 12.34)
PURCHA included in the
For Add/Change:
• Not required.
10 Destination Postal X(14) BASE II Postal code of the ship-to For Add/Change:
Code TC50-TCR0 location.
• Not required.
PURCHA
(77-86)
11 Source Postal X(14) BASE II Postal code of the location For Add/Change:
Code TC50-TCR0 from which goods were
• Not required.
PURCHA shipped.
(87-96)

FORMAT SOURCE
12 Destination 9(05) BASE II International Organization For Add/Change:

Country Code TC50-TCR0 for Standardization (ISO)-
• Not required.
PURCHA assigned code for the
(97-99) country to which goods • If the country code is not
were shipped. valid, the value will be
ignored.
13 VAT Reference X(16) BASE II Unique Value Added Tax For Add/Change:
Number TC50-TCR0 (VAT) Invoice Reference
• Not required.
PURCHA Number of a transaction
(100-114) summary.
For Visa Europe
transactions, must not be
used for Supplier Invoice
Number
14 Order Date 9(08) BASE II Date order was placed For Add/Change:
TC50-TCR0 with merchant.
• Not required.
PURCHA
(115-120) • If the date format is not valid,
15 Freight/Shipping 9(16) BASE II Freight/shipping Value Two decimal places are implied
VAT/Tax Amount TC50-TCR0 Added Tax (VAT) (1234 = 12.34).
PURCHA Amount for a Card
For Add/Change:
(140-151) Transaction.
• Not required.
16 Freight/Shipping 9(09) BASE II Freight/shipping Value Four decimal places are implied
VAT/Tax Rate TC50-TCR0 Added Tax (VAT) Rate (123456 = 12.3456).
PURCHA for a Card Transaction.
For Add/Change:
(152-155)
• Not required.
17 Service Identifier X(06) BASE II Value assigned to identify For Add:
TC50-TCR0 the type of information
• Required. ‘PURCHA’
Purchasing/ contained in the BASE II
(Purchasing Transaction,
Lodging/ record.
Additional Elements) will be
Car Rental
This information will used if no value is provided.
(17-22)
determine if the line item For Change:
summary is for a Car
Rental, Lodging, or • Cannot start with ‘\’.
Purchasing Transaction.
This field supports the
matching of the enhanced
transaction information
with the original financial
data.

FORMAT SOURCE
18 Purchase ID X(50) BASE II Number assigned by For Add/Change:

TC50-TCR0 merchant to transaction.
• Not required.
(COMMGN)
Generic
Data (111-
135)
Number.
data with the card
transaction.
For Add/Change:
data with the card
transaction.
20 Transaction Date 9(08) BASE II The date of purchase, as For Add/Change:
TC50-TCR0 indicated in the financial
• Not required.
(COMMGN) record.
Data (61-64)
data with the card
transaction.
• Not required.
105)
data with the card
transaction.
• Not required.
Generic
Data (77-
101)
data with the card
transaction.

FORMAT SOURCE

• Not required.
Generic
Data (106-
110)
data with the card
transaction.
• Not required.
addendum record.
If value is present it will be
used for matching.
25 Source Country 9(05) BASE II International Organization For Add/Change:
Code TC50-TCR0 for Standardization (ISO)-
• Not required.
PURCHA assigned code for the
(97-99) country to which goods • If the country code is not
were shipped. valid, the value will be
ignored.
26 Destination X(04) State/Province where the For Add/Change:
State/Province package will be delivered.
• Not required.
destination’s country.
27 Source X(04) State/Province from For Add/Change:
State/Province which the package was
• Not required.
shipped.
28 Source X(10) Source of the enhanced For Add/Change:
transaction information.
• Not required.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.

FORMAT SOURCE

• Not required.
to spaces.
Line Item Summary (T8) Summary Notes:
(Field #4), and Sequence Number (Field #5)) uniquely identify a single Transaction (T5). For more
complex business situations, additional information may be required to supplement the transactional data.
This information is carried in the Line Item Summary (T8) records.
In addition to items such as Discount Amount, Duty Amount, etc. there are several fields in the record
which may be utilized to enhance the purchase data. These are fields Service Identifier (Field #17) through
Processor Addendum Key (Field #24). Optional fields at the end of the record can also be used to carry
additional information relevant to the transaction.
LODGING SUMMARY – Type 9
The Lodging Summary record type contains summary information on Visa commercial card transactions
conducted at hotels or places of lodging. The Lodging Summary Record (T9) supports the reporting of
supplemental information about a stay in a lodging facility which was charged to this particular account, and
can be tied back to the particular transaction that carried the charge detail.
The lodging details carried in this record are related to a particular transaction. That transaction is uniquely
identified by the following Primary Key fields: the Account Number (Field # 2), Posting Date (Field # 3),
Transaction Reference Number (Field # 4), and the Sequence Number (Field #5). These four fields are
required and cannot be empty, spaces, or zeros. They must uniquely represent a valid transaction. These
fields are indicated by a “**” following the field name. All attributes contained in this record type belong to
the transaction indicated by the primary key.

For Add:
• The Lodging Summary must not already exist in the application.
For Change:
• The Lodging Summary must exist in the application.
Lodging Summary (9)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
or 4.
• Required.
front of the card;

transaction.
• Required.
Lodging Summary (9)

FORMAT SOURCE

Reference transaction.
• Required.
Number**
• Required.
uniquely identify a
posting run.
6 No Show 9(01) BASE II Indicates transaction due Values:
Indicator TCR3 to no-show charges.
0 = No
Lodging
(27) 1 = Yes
For Add/Change:
• Not required.
value.
7 Check In Date 9(08) BASE II Date customer checked For Add/Change:
TCR3 into hotel, or Scheduled
• Not required.
Lodging Arrival Date in case of a
(38-43) No Show or an Advance • If the date format is not valid,
Lodging. the value will be ignored.
8 Daily Room Rate 9(16) BASE II Daily room rate for hotel Two decimal places are implied
TCR3 in Card transaction. (1234 = 12.34).
Lodging
For Add/Change:
(44-55)
• Not required.
9 Total Other 9(16) BASE II Other charges identified Two decimal places are implied
Charges TC50-TCR0 by the Lodging Extra (1234 = 12.34).
Lodging Charges Code in a
For Add/Change:
• Not required.
If Lodging No Show
Indicator is set to Yes, • If provided, must be numeric.
No-show charges were
assessed in the transaction.
10 Total Tax Amount 9(16) BASE II Total tax amount of a Two decimal places are implied
TCR3 Card transaction for hotel (1234 = 12.34).
Lodging lodging.
For Add/Change:
(56-67)
• Not required.
Lodging Summary (9)

FORMAT SOURCE
11 Total 9(16) BASE II Food and beverage Two decimal places are implied
Food/Beverage TCR3 charges in a Card (1234 = 12.34).
Charges Lodging transaction for hotel
For Add/Change:
(80-91) lodging.
• Not required.
This value does not
include mini-bar charges. • If provided, must be numeric.
12 Total Prepaid 9(16) BASE II Total of any prepaid Two decimal places are implied
Expenses TCR3 amount or deposit applied (1234 = 12.34).
Lodging against the folio.
For Add/Change:
(68-79)
• Not required.
13 Total Folio Cash 9(16) BASE II Total of any cash advances Two decimal places are implied
Advances TCR3 charged against the folio. (1234 = 12.34).
Lodging
For Add/Change:
(92-103)
• Not required.
14 Total Valet 9(16) BASE II Total valet parking charges Two decimal places are implied
Parking Charges TC50-TCR0 of a Card transaction for (1234 = 12.34).
Lodging hotel lodging.
For Add/Change:
(41-52)
• Not required.
15 Total Mini-bar 9(16) BASE II Total charges for in-room Two decimal places are implied
Charges TC50-TCR0 mini-bar food and (1234 = 12.34).
Lodging beverage expenses.
For Add/Change:
(53-64)
• Not required.
16 Total Laundry 9(16) BASE II Total laundry charges in a Two decimal places are implied
Charges TC50-TCR0 Card transaction for hotel (1234 = 12.34).
Lodging lodging.
For Add/Change:
(65-76)
• Not required.
17 Total Telephone 9(16) BASE II Total charges for Two decimal places are implied
Charges TC50-TCR0 telephone expenses, (1234 = 12.34).
Lodging including in-room fax
For Add/Change:
(77-88) machine usage.
• Not required.
Lodging Summary (9)

FORMAT SOURCE
18 Total Gift Shop 9(16) BASE II Total charges of gift shop Two decimal places are implied
Purchases TC50-TCR0 and merchandise (1234 = 12.34).
Lodging purchases.
For Add/Change:
(89-100)
• Not required.
19 Total Movie 9(16) BASE II Total charges for movies Two decimal places are implied
charges TC50-TCR0 and other in-room (1234 = 12.34).
Lodging entertainment expenses.
For Add/Change:
(101-112)
• Not required.
20 Total Business 9(16) BASE II Total charges for copies, Two decimal places are implied
Center Charges TC50-TCR0 faxes, and other Business (1234 = 12.34).
Lodging Center expenses.
For Add/Change:
(113-124)
• Not required.
21 Health Club 9(16) BASE II Total charges for health Two decimal places are implied
Charges TC50-TCR0 club or pool expenses, (1234 = 12.34).
Lodging including court and
For Add/Change:
(125-136) equipment rental and golf
green fees. • Not required.
22 Extra Charge X(06) BASE II Type of additional charges Values:
Code TCR3 applied to a customer’s bill
Space = No extra charge
Lodging after checkout. Each of
(28-33) the six positions in the 0 = No extra charge
code may indicate a type
2 = Restaurant
of charge.
3 = Gift Shop
4 = Mini-bar
5 = Telephone
6 = Other
7 = Laundry
For Add/Change:
• Not required.
• If provided, each field position
must contain a valid value.
Lodging Summary (9)

FORMAT SOURCE
23 Total Room Tax 9(16) BASE II Represents the total Two decimal places are implied
Amount TC05-TCR3 amount of all room taxes (1234 = 12.34).
Lodging applied against this
For Add/Change:
• Not required.
24 Lodging Nights 9(03) BASE II Represents the length of For Add/Change:
TC05-TCR3 stay, measured in number
• Not required.
Lodging of nights.
(104-105) • If provided, must be numeric.
25 Total Non-Room 9(16) BASE II Represents the total of all Two decimal places are implied
Charges TC50-TCR0 non-room related charges. (1234 = 12.34).
Lodging
For Add/Change:
CORPLG
(149-160) • Not required.
Identifier TC50-TCR0 transaction.
• Not required.
(23-37)
data with the card
transaction.
• Not required.
Generic
Data (111-
135)
Number.
data with the card
transaction.
For Add/Change:
data with the card
transaction.
Lodging Summary (9)

FORMAT SOURCE
• Not required.
Data (61-64)
data with the card
transaction.
• Not required.
105)
data with the card
transaction.
• Not required.
Generic
Data (77-
101)
data with the card
transaction.
• Not required.
Generic
Data (106-
110)
data with the card
transaction.
• Not required.
addendum record.
used for matching.
• Not required.
to spaces.
• Not required.
to spaces.
Lodging Summary (9)

FORMAT SOURCE

• Not required.
to spaces.
• Not required.
to spaces.
Lodging Summary (T9) Summary Notes:
complex business situations requiring enhanced data, additional information may be desired to supplement
the transactional data. For transactions involving lodging details, this information is carried in the Lodging
Summary (T9) records.
In addition to items such as Check In and Checkout Dates, specific service charges, etc. there are several
fields in the record which may be utilized to enhance the transactional data. These are fields Message
Identifier (Field #26) through Processor Addendum Key (Field #33). Optional fields at the end of the
record can also be used to carry additional information relevant to the lodging transaction.
PASSENGER ITINERARY – Type 14
The Passenger Itinerary record type contains summary travel information on an air trip or a rail trip paid for
with a Visa commercial card. The Passenger Itinerary Record (T14) supports the reporting of supplemental
information about a trip which was charged to a particular account, and can be tied back to the particular
transaction that carried the charge detail.
The Passenger Itinerary details carried in this record are related to a particular transaction and a particular
trip. That transaction is uniquely identified by the following Primary Key fields: The Account Number
(Field # 2), Posting Date (Field # 3), Transaction Reference Number (Field # 4), and Sequence Number
(Field #5). These four fields are required and cannot be empty, all spaces or zeros. They must uniquely
represent a valid transaction. These fields are indicated by a “**” following the field name. All attributes
contained in this record type belong to the transaction indicated by the primary key.

For Add:
• The Passenger Itinerary must not already exist in the application.
For Change:
• The Passenger Itinerary must exist in the application.
Passenger Itinerary (14)

FORMAT SOURCE

Change transaction
transaction.
For Add/Change:
or 4
• Required.
front of the card;

transaction.
• Required.

FORMAT SOURCE

• Required.
Number**
• Required.
process to uniquely
6 Departure Date 9(08) BASE II Starting Date of travel. For Add/Change:
TCR3
• Not required.
Passenger
Itinerary • If the date format is not valid,
(47-52) the value will be ignored.
7 Travel Agency X(08) BASE II Code identifying the travel For Add/Change:
Code TCR3 agency that supplied the
• Not required.
Passenger ticket.
Itinerary
(84-91)
or TC50-
TCR0
(CORPAI/
COMMAG)
(157-164)
8 Travel Agency X(26) BASE II Name of the travel agency For Add/Change:
Name TCR3 that supplied the ticket.
• Not required.
Passenger
Itinerary
(92-116)
9 Ticket Indicator 9(01) BASE II Indicates whether a ticket Values:
TCR3 is restricted in some way.
0 = No
Passenger
Itinerary 1 = Yes
(117)
For Add/Change:
• Not required.
value.
10 Ticket Number X(14) Ticket Number of an For Add/Change:
airline purchase.
• Not required.

FORMAT SOURCE
11 Passenger Name X(20) BASE II Customer name as For Add/Change:

TCR3 indicated on the ticket
• Not required.
Passenger purchased.
Itinerary
(27-46)
or TC50-
TCR0
(CORPAI/
COMMAG)
(61-80)
12 Exchange Ticket X(14) BASE II Ticket number for which For Add/Change:
Number TC50-TCR0 this ticket was exchanged.
• Not required.
(CORPAI/
COMMAG)
(132-144)
13 Exchange Ticket 9(16) BASE II Credit from ticket or Two decimal places are implied
Amount TC50-TCR0 coupon(s) being used as (1234 = 12.34).
(CORPAI/ payment in an exchange
For Add/Change:
COMMAG) ticket transaction.
14 Internet Indicator 9(01) BASE II Indicates if the ticket was Values:
TC50-TCR0 purchased over the
0 = No
(CORPAI/ Internet.
COMMAG) 1 = Yes
(165-165)
For Add/Change:
• Not required.
value.
15 Total Fare 9(16) BASE II Total fare charged for all Two decimal places are implied
Amount TC50-TCR0 legs of travel. (1234 = 12.34).
(CORPAI/
For Add/Change:
COMMAG)
16 Total Fee Amount 9(16) BASE II Sum of all applicable fees. Two decimal places are implied
TC50-TCR0 (1234 = 12.34).
(CORPAI/
For Add/Change:
COMMAG)

FORMAT SOURCE
17 Total Tax Amount 9(16) BASE II Sum of all taxes charged. Two decimal places are implied
TC50-TCR0 (1234 = 12.34).
(CORPAI/
For Add/Change:
COMMAG)
• Not required.
(23-37)
data with the card
transaction.
19 Endorsement/ X(20) For Add/Change:
Restrictions • Not required.
• Not required.
Generic
Data (111-
135)
Number.
data with the card
transaction.
For Add/Change:
data with the card
transaction.
• Not required.
Data (61-64)
data with the card
transaction.

FORMAT SOURCE

• Not required.
105)
data with the card
transaction.
• Not required.
Generic
Data (77-
101)
data with the card
transaction.
• Not required.
Generic
Data (106-
110)
data with the card
transaction.
26 Processor X(52) A value provided at the For Add/Change:
Addendum Key time of reservation
• Not required.
containing passenger
specific data
27 Passenger X(50) A value provided by the For Add/Change:
Specific Data cardholder at time of
• Not required.
reservation and captured
by the central reservation
system.
Also called: control ID,
travel authorization
number, customer code.
28 Ticket Issue Date 9(08) BASE II Actual date of ticket and For Add/Change:
TC50-TCR0 itinerary issuance.
• Not required.
(CORPAS/
COMMAS) • If provided, must be a valid
(160-167) date.

FORMAT SOURCE
29 Number of Legs 9(02) Total number of trip legs Values:

associated with a
01 to 99
passenger itinerary.
For Add/Change:
• Not required.
value.
30 E-Ticket Indicator 9(01) Identifies if ticket is Values:
electronic.
0 = Is not an electronic ticket.
1 = Is an electronic ticket.
For Add/Change:
• Not required.
value.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
35 Travel Obligation X(13) BASE II A value provided by the For Add/Change:
Number TC50-TCR0 cardholder at time of
• Not required.
(CORPAS/ reservation and captured
COMMAS) by the central reservation
(141-153) system.
Also called: control ID,
travel authorization
number, customer code.
36 TCN Passenger X(50) The passenger name field For Add/Change:
Name as received on the
• Not required.
corresponding TCN airline
record.
Passenger Itinerary (T14) Summary Notes:
the transactional data. For transactions involving air or rail travel, this information is carried in the
Passenger Itinerary (T14) records.
In addition to items such as Departure Date, Travel Agency information, ticketing attributes, total fares and
fees, etc. there are several fields in the record which may be utilized to enhance the transactional data and to
link this information to the corresponding financial transaction. These are fields Message Identifier (Field
#18) through Processor Addendum Key (Field #26). Optional fields at the end of the record can also be
used to carry additional information relevant to the air or rail travel transaction.
LEG-SPECIFIC INFORMATION – Type 15
The Leg-Specific Information record type contains summary travel information on an air trip or a rail trip.
Up to 99 legs can be associated to one Passenger Itinerary transaction. Just as the Passenger Itinerary record
(T14) carries supplemental information about an air or rail travel event, the use of this Leg-Specific
Information Record (T15) allow the user to report additional details where required for more detailed
business reporting. Specific leg-related fees, fares, itinerary details, and ticket attributes can be provided in
this record type.
The Leg-Specific Information details carried in this record are related to a particular transaction containing
charges for a specific trip, and, in particular, charges relating to a leg of that specific trip. That transaction is
uniquely identified by the following Primary Key fields: the Account Number (Field # 2), Posting Date
(Field # 3), Transaction Reference Number (Field # 4), and Sequence Number (Field #5). The specific leg
is identified by the four fields indicated plus the addition of the Leg Number (Field #6). These five fields
are required and cannot be empty, all zeros or spaces. They must uniquely represent a valid transaction,
with a valid trip and leg number of that trip. These fields are indicated by a “**” following the field name.
All attributes contained in this record type belong to the specific travel leg indicated by the primary key.

For Add:
• The corresponding Passenger Itinerary (based on the Account Number, Posting Date, Transaction
Reference Number and Sequence Number) must exist in the application.
• The Leg-Specific Information must not already exist in the application.
For Change:
• The Leg-Specific Information must exist in the application.
Leg-Specific Information (15)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
• Required and must be 1, 3, or
4
• Required.
front of the card;

FORMAT SOURCE

transaction.
• Required.
• Required.
Number**
• Required.
process to uniquely
6 Leg Number** 9(02) Sequence Number for the Values:
specific leg which this Leg-
01 to 99
Specific Information
represents. For Add/Change:
Represents leg 1, leg 2, etc. • Required.
of the ticket. • Must be a valid value.
7 Destination/ X(04) BASE II Destination (for railroad) For Add:
Airport Code TC05-TCR3 or airport (for airline) for
• Required.
Passenger this travel segment.
Itinerary For Add/Change:
transaction
• If the Airport Code or the
or Railroad City Code is not
valid, the “Unknown” code
TC50-TCR0
will be used.
(CORPAS/
COMMAS)
Leg (71-75
or 114-118)
8 Carrier Code X(04) BASE II Alphabetic code for a For Add:
TC05-TCR3 Carrier.
• Required.
Passenger
Itinerary For Add/Change:
transaction
or • If the Carrier Code is not valid,
the “Unknown” code will be
TC50-TCR0 used.
(CORPAS/
COMMAS)
Leg (56-57
or 99-100)

FORMAT SOURCE
9 Service Class X(02) BASE II Passenger class for this For Add/Change:
TC05-TCR3 particular segment of air
• Not required.
Passenger travel or one segment of
Itinerary railroad traveling.
transaction
or
TC50-TCR0
(CORPAS/
COMMAS)
Leg (63-64
or 106-107)
10 Fare Basis X(08) BASE II Extended code describing For Add/Change:
TC05-TCR3 the Fare Class for one
• Not required.
Passenger segment of air travel or for
Itinerary one segment of railroad
transaction travel.
or
TC50-TCR0
(CORPAS/
COMMAS)
Leg (76-83
or 119-126)
11 Date of Travel 9(08) BASE II Date of departure for this For Add/Change:
TC50-TCR0 particular segment of air
• Not required.
Passenger travel or rail travel.
Itinerary • If the date format is not valid,
transaction the value will be ignored.
or
TC50-TCR0
(CORPAS/
COMMAS)
Leg (84-89
or 127-132)
12 Stopover Code 9(01) BASE II Code indicating whether Values:
TC05-TCR3 the destination is a
0 = Stopover allowed (final
Passenger connection point or a final
destination)
Itinerary destination for one
transaction segment of air travel or for 1 = Stopover not allowed
one segment of rail travel. (intermediate stop)
or
For Add/Change:
TC50-TCR0
(CORPAS/ • Not required.
COMMAS) • If provided, must be a valid
Leg (70 or value.
113)

FORMAT SOURCE
13 Coupon Number 9(01) BASE II The coupon number For Add/Change:

TC50-TCR0 within the ticket.
• Not required.
(CORPAS/
COMMAS) • If provided, must be numeric.
Leg (55 or
98)
14 Carrier Reference X(06) BASE II Reference number For Add/Change:
Number TC50-TCR0 assigned by a carrier.
• Not required.
(CORPAS/
For airline travel, it is an
COMMAS)
airline designated flight
Leg (58-62
number for given leg of an
or 99-100)
air travel.
or
TC05-TCR3
Passenger
Itinerary
(146-150,
etc)
15 Departure Time 9(04) BASE II Time flight is scheduled to For Add/Change:
TC50-TCR0 depart for this leg of travel
• Not required.
(CORPAS/
Leg (90-93
or 133-136)
16 Arrival Time 9(04) BASE II Time flight is scheduled to For Add/Change:
TC50-TCR0 arrive for this leg.
• Not required.
(CORPAS/
Leg (94-97
or 137-140)
17 Origination X(04) BASE II The airport or city code For Add/Change:
Airport/Railroad TC50-TCR0 for the point of origination
• Not required.
Code (CORPAS/ of the segment.
COMMAS) • If the Airport Code or the
Leg (65-69 Railroad City Code is not
or 108-112) valid, the “Unknown” code
will be used.
18 Conjunction X(14) BASE II Ties additional tickets to For Add/Change:
Ticket Number TC50-TCR0 the primary ticket.
• Not required.
(CORPAS/
There can be a
COMMAS)
conjunction ticket for each
(42-54)
set of four coupons (legs).

FORMAT SOURCE

• Not required.
(23-37)
data with the card
transaction.
• Not required.
Generic
Data (111-
135)
Number.
data with the card
transaction.
(COMMGN) to the card account for
For Add/Change:
Generic this transaction.
data with the card
transaction.
• Not required.
Data (61-64)
data with the card
transaction.
• Not required.
105)
data with the card
transaction.

FORMAT SOURCE
• Not required.
Generic
Data (77-
101)
data with the card
transaction.
• Not required.
Generic
Data (106-
110)
data with the card
transaction.
• Not required.
addendum record.
used for matching.
27 Domestic/ 9(01) Identifies if the leg is Values:
International between two countries.
0 = Leg stay in the same country.
Indicator
1 = Leg is between 2 countries.
For Add/Change:
• Not required.
value.
28 Arrival Date 9(08) Arrival date of specific leg. For Add/Change:
• Not required.
date.
29 Departure Tax 9(16) Departure tax for specific Two decimal places are implied
leg. (1234 = 12.34).
For Add/Change:
• Not required.
• Not required.
to spaces.

FORMAT SOURCE

• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Leg Specific Information (T15) Summary Notes:
The five fields ((Account Number (Field #2), Posting Date (Field #3), Transaction Reference Number
(Field #4), Sequence Number (Field #5), and Leg Number (Field #6)) uniquely identify a single
Transaction (T5) which has been enhanced with information from a Passenger Itinerary record (14) and is
now being further enhanced by Leg-Specific Information (T15). For more complex business situations
requiring enhanced data, additional information may be desired to supplement the original transactional
data. For transactions involving air or rail travel, this information is carried in the Passenger Itinerary (T14)
records, and in the accompanying Leg-Specific Information records (T15).
The data fields in this record contain such things as Carrier Code, Service Class, Arrival and Departure
Times, etc. which apply to a particular leg of a particular trip. In addition, there are several fields in the
record which may be utilized to enhance the transactional data and to link this information to the
corresponding financial transaction. These are fields Message Identifier (Field #19) through Processor
Addendum Key (Field #26). Optional fields at the end of the record can also be used to carry additional
information relevant to the specifically identified travel leg of an air or rail travel transaction.
SUPPLIER – Type 16
The Supplier record type contains descriptive information related to the supplier. The MIER Reference
Positions (from-to) are subject to revision. Note: this record type is now obsolete for U.S. Issuers, as
the VMPD is used to obtain the most accurate supplier information. Members can provide T16
records, and the T16 records will be loaded and can be forwarded to third parties, but they will not load into
Visa reporting applications.
Since Visa now uses the VMPD to obtain the most accurate supplier information, Visa’s reporting systems
are only using the supplier data provided in the T5 record and ignoring the T16 data.
Details carried in this record are related to a particular merchant or supplier. That supplier is uniquely
identified by an internally generated unique primary key. All attributes contained in this record type belong
to the specific merchant indicated by the primary key.
Supplier (16)

FORMAT SOURCE

Code the action to be taken by 1 = Add the transaction
Visa Systems on this 3 = Change the matching
record: either Add, or transaction
Change. 4 = Add if transaction does not
transaction.
For Add/Change:
or 4.
2 Acquirer BIN 9(06) Acquiring Bank For Add/Change:
Identification Number
• Not Required.
(BIN) of the supplier.
3 Supplier Name X(30) MIER (25- Supplier name included in For Add/Change:
54) a transaction.
• Not Required.
The name under which the
merchant location is
“doing business as.”
4 Supplier City X(14) MIER (55- City of a supplier included For Add/Change:
67) in a transaction.
• Not Required.
5 Supplier X(04) MIER (68- Code of a supplier state or For Add/Change:
State/Province 70) province included in a
• Not required.
Code transaction.
Supplier (16)

FORMAT SOURCE
6 Supplier ISO 9(05) International Organization For Add/Change:

Country Code for Standardization (ISO)-
• Not required.
assigned code of a country
where the supplier is • If provided, must be a valid
located. country code.
If the alphabetic ISO
Country Code is provided,
it will be converted to its
corresponding numeric
code.
7 Supplier Postal X(14) MIER (71- Postal code of the supplier For Add/Change:
Code 79) location included in a
• Not Required.
transaction.
8 Merchant 9(04) MIER (21- Four-digit numeric For Add/Change:
Category Code 24) classification identifier,
• Not Required.
modeled after the
Standard Industrial
Classification (SIC) code,
and designed to group
suppliers in similar lines of
business.
9 Supplier Address X(30) MIER (140- The street address of the For Add/Change:
169) merchant location.
• Not Required.
10 Merchant Profile 9(12) MIER (2- A Visa number assigned to For Add/Change:
Service Identifier 13) each unique merchant
• Required.
(MPS-ID) location.
• Must be a valid MPS-ID.
For Add:
• Must not already exist in the
application.
For Change:
11 Business Legal X(30) MIER (110- Name used by a company For Add/Change:
Name 139) for 1099 Reporting.
• Not required.
12 Alternate Supplier X(30) MIER (80- An alternate name under For Add/Change:
DBA Name 109) which the merchant
• Not required.
location is “doing business
as.”
13 Mailing Address X(30) MIER (202- Street address, including For Add/Change:
231) city, state, and zip code, of
• Not required.
the merchant location that
accepted the Visa
commercial card.
Supplier (16)

FORMAT SOURCE
14 Dun & Bradstreet 9(09) MIER (461- Dun and Bradstreet Code For Add/Change:
Number 469) Number of a supplier.
• Not required.
15 Incorporation 9(01) MIER (274) Code identifying the Values:
Status Code Supplier Organization
1 = Individual / Sole
Structure.
proprietorship
2 = Partnership
3 = Corporation-Chapter S, C
4 = Medical or legal corporation
5 = Associations/estates/trusts
6 = Tax-exempt organizations
(501C)
7 = Government (Federal/state/
local)
8 = International organization
9 = Limited liability company
For Add/Change:
• Not required.
value.
16 Minority Owned X(02) MIER (275- Code indicating the Values:
Status Code 276) Minority-Owned Status of
N = Not Minority-Owned
a business.
AI = Asian Indian
AP = Asian Pacific
BL = Black
HI = Hispanic
NA = Native American
OT = Other (not a default –
indicates other minority).
For Add/Change:
• Not required.
value.
17 Tax Identification 9(09) MIER (264- The IRS assigned number For Add/Change:
Number (TIN) 272) used by this supplier.
• Not required.
Supplier (16)

FORMAT SOURCE
18 Primary Standard X(04) MIER (277- The Standard Industry For Add/Change:
Industrial 280) Category Code primarily
• Not required.
Classification used by the business.
(SIC) Code • If provided, must be numeric.
19 Secondary X(04) MIER (281- The Standard Industry For Add/Change:

Standard 284) Category Code secondarily
• Not required.
Industrial used by the business.
Classification • If provided, must be numeric.
(SIC) Code
20 Supplier Phone X(15) MIER (297- The voice phone for the For Add/Change:
Number 311) participant or business.
• Not required.
May include: punctuation,
country code, extension.
Will normally contain at
least an area code and
number.
21 Sole Proprietor X(25) MIER (312- First name of the sole For Add/Change:
Owner First Name 336) proprietor.
• Not required.
22 Sole Proprietor X(02) MIER (337) Middle initial of the sole For Add/Change:
Owner Middle proprietor
• Not required.
Initial
23 Sole Proprietor X(25) MIER (338- Last name of the sole For Add/Change:
Owner Last Name 362) proprietor.
• Not required.
24 Women Owned X(01) MIER (363) Yes/No Indicator of Values:
Indicator whether or not the
Y = Yes
business is women owned.
N = No
For Add/Change:
• Not required.
value.
25 Sales Volume 9(10) MIER (470- Annual sales amount for No decimal places are implied.
479) the supplier.
For Add/Change:
• Not required.
• If amount is greater than $10
billion, field will be populated
with all 9’s.
26 Employee Count 9(06) MIER (480- The number of employees For Add/Change:
485) at the supplier.
• Not required.
Supplier (16)

FORMAT SOURCE
27 Issuer BIN 9(06) MIER (14- The Bank Identification For Add/Change:
19) Number (BIN) that
• Not required.
identifies the issuing
institution. • If provided, must be numeric.
28 TIN Type Code 9(01) MIER (273) Indicates whether the TIN Values:
is the SSN (Social Security
1 = SSN
Number) or the EIN
(federal Employer 2 = FEIN
Identification Number).
For Add/Change:
• Not required.
value.
29 Supplier E-mail X(40) MIER (364- The e-mail address of the For Add/Change:
Address 403) business.
• Not required.
30 Supplier Fax X(15) The fax number at the For Add/Change:
Number business location.
• Not required.
31 Supplier X(15) MIER (404- The phone number used For Add/Change:
Reservation 418) to make a reservation with
• Not required.
Phone Number the business.
32 Level III Capture X(01) MIER (420) Indicates that the Values:
Indicator Code merchant has sent
addendum data in the Y = Supplier capable
TC50 sales draft. N = Supplier not capable
The TC50 is an addendum For Add/Change:
of the BASE II TC05 sales • Not required.
draft.
value.
For Add:
• “N” will be used if no value is
provided.
33 Level II Capture X(01) MIER (419) Indicates that the Values:
Indicator Code merchant has sent
Y = Code/CRI was sent
Customer Code/
Customer Reference N = Code/CRI was not sent
Identifier (CRI) fields on (default)
the TCR06. The TCR06 is
For Add/Change:
an extension of the BASE
II TC05 sales draft. • Not required.
value.
For Add:
provided.
Supplier (16)

FORMAT SOURCE
34 Parent Visa 9(12) The MPS-ID of a parent Reserved for future use.
Supplier record contained in each
For Add/Change:
Identification duplicate record that is
Number subordinate to that parent. • Not required.
35 Alternate Supplier X(20) MIER (170- Alternate supplier city. For Add/Change:
City 189)
• Not required.
36 Alternate Supplier X(03) MIER (190- Alternate supplier For Add/Change:
State/Province 192) state/province code.
• Not required.
Code
alternate supplier’s country.
37 Alternate Supplier X(14) MIER (193- Alternate supplier postal For Add/Change:
Postal Code 201) code.
• Not required.
38 Supplier Out of 9(08) Indicates the effective date For Add/Change:
Business Date the supplier went out of
• Not required.
business.
date.
39 Supplier 9(08) Indicates the effective date For Add/Change:
Ownership the supplier changed
• Not required.
Change Date ownership.
date.
40 8A Classification X(01) MIER (443) Indicates that the Values:
Indicator merchant is classified by
Y = Yes
the Small Business
Administration for 8A N = No
government contracts.
For Add/Change:
• Not required.
value.
41 8A Expiration 9(08) MIER (444- Indicates the expiration For Add/Change:
Date 453) date for merchant’s 8A
• Not required.
classification.
date.
42 SBA Participant X(01) MIER (454) Indicates that the Values:
Indicator merchant is classified by
Y = Yes
the Small Business
Administration for N = No
Participant status.
For Add/Change:
• Not required.
value.
Supplier (16)

FORMAT SOURCE
43 Disabled Veteran X(01) MIER (457) Indicates that the Values:

Indicator merchant is classified as a
Y = Yes
Disabled Veteran.
N = No
For Add/Change:
• Not required.
value.
44 Veteran Indicator X(01) MIER (458) Indicates that the Values:
merchant is classified as a
Y = Yes
Veteran.
N = No
For Add/Change:
• Not required.
value.
45 Vietnam Era X(01) MIER (459) Indicates that the Values:
Veteran Indicator merchant is classified as a
Y = Yes
Vietnam Era Veteran.
N = No
For Add/Change:
• Not required.
value.
46 Supplier X(01) MIER (460) Indicates that the Values:
Information merchant refused to
N = Did not refuse (Default)
Refusal Indicator provide required data.
Y = Refused
For Add/Change:
• Not required.
value.
For Add:
provided.
47 Incorporation 9(08) MIER (433- A valid date indicating the For Add/Change:
Status Change 442) effective date of a supplier
• Not required.
Date change in incorporation
status. • If provided, must be a valid
date.
Supplier (16)

FORMAT SOURCE
48 Small X(01) MIER (455) Indicates that the Values:

Disadvantaged merchant is registered with
Y = Yes
Business the Small Business
Indicator Administration as a small N = No
disadvantaged business.
For Add/Change:
• Not required.
value.
49 Mailing City X(20) MIER (232- Supplier city for mailing For Add/Change:
251) purposes
• Not Required.
50 Mailing X(04) MIER (252- Supplier state/province For Add/Change:
State/Province 254) code for mailing
• Not required.
51 Mailing Country 9(05) Supplier country code for For Add/Change:
mailing.
• Not required.
country code.
52 Alternate Supplier 9(05) Alternate supplier country For Add/Change:
Country code.
• Not required.
country code.
53 HUB Zone X(01) MIER (456) Indicates that the SBA has Values:
Indicator designated this business as
Y = Yes
being located in a
Historically Underutilized N = No
Business zone.
For Add/Change:
• Not required.
value.
54 Franchise Code X(01) MIER (486) Identifies the franchise Values:
merchant location as being
F = Owned by franchisee or
operated by either a
dealer
corporation or a
franchisee. C = Owned by corporation
For Add/Change:
• Not required.
value.
Supplier (16)

FORMAT SOURCE
55 Primary NAICS 9(06) MIER (285- Identifies the primary For Add/Change:
Code 290) North American Industry
• Not required.
Classification System code.
56 Secondary NAICS 9(06) MIER (291- Identifies the secondary For Add/Change:
Code 296) North American Industry
• Not required.
Classification System code.
57 Visa Commerce X(19) Identifies the Seller ID on For Add/Change:
Seller ID the Visa Commerce
• Not required.
platform.
58 Reserved for X(12) MIER (421- Reserved for Future Use For Add/Change:
Future Use 432)
• Not required.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
63 Austin-Tetra 9(12) Austin-Tetra business For Add/Change:
Number entity identifying number
• Not required.
64 Non-Profit Entity X(1) Identifies the business as a For Add/Change:
not for profit entity
• Not required.
65 Woman Owned X(1) Identifies the business as a For Add/Change:
Small Business woman-owned small
• Not required.
business.
66 Veteran Owned X(1) Identifies the business as a For Add/Change:
Small Business veteran owned small
• Not required.
business
67 Service Disabled X(1) Identifies the business as a For Add/Change:
Veteran Owned service disabled veteran
• Not required.
Small Business owned small business
Supplier (16)

FORMAT SOURCE
68 DOT X(1) Identifies the business as a For Add/Change:

Disadvantaged DOT disadvantaged
• Not required.
Business Business Enterprise
Enterprise
69 Disabled X(1) Identifies the business as For Add/Change:
an Owner-Disabled
• Not required.
business
70 Historically Black X(1) Identifies Historically For Add/Change:
College/Univ - Black College or
• Not required.
Minority University Minority
Institution Institution
71 Merchant Type X(1) Merchant Type Code For Add/Change:
• Not required.
72 Patriot Act X(1) Identifies the merchant as For Add/Change:
Excluded Party part of the Patriot Act
• Not required.
List Indicator Excluded Party List
73 Taxpayer Name X(40) Name of taxpayer For Add/Change:
• Not required.
74 TIN Match X(1) Indicates whether For Add/Change:
Indicator Taxpayer TIN has been
• Not required.
matched
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
80 Level 3 Tier 1 X(1) For Add/Change:
Indicator • Not required.
Supplier (16)

FORMAT SOURCE

Supplier (T16) Summary Notes:
This record contains Visa-acquired information about suppliers accepting Visa commercial cards. Much of
the information is directly obtained from Visa’s merchant databases. For further information on the use of
this merchant data, please contact your Visa representative.
FLEET SERVICE – Type 17
The Fleet Service record type contains information related to Fleet service transactions. Details about Fleet
non-fuel products are discussed in the Fleet Product (Type 18) section. Fleet Service details are pertinent to
a particular card transaction which may contain both fleet fuel and non-fuel purchases.
The Fleet Service details carried in this record are related to a particular transaction containing charges for a
specific fleet-related event. That transaction is uniquely identified by the following Primary Key fields: the
Account Number (Field # 2), Posting Date (Field # 3), Transaction Reference Number (Field # 4), and
Sequence Number (Field #5). These four fields are required and cannot be empty, all spaces or zeros. They
must uniquely represent a valid fleet service transaction. These fields are indicated by a “**” following the
key, and to the fleet event it represents.

For Add:
• The Fleet Service must not already exist in the application.
For Change:
• The Fleet Service must exist in the application.
Fleet Service (17)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;

transaction.
• Required.
Fleet Service (17)

FORMAT SOURCE

• Required.
Number** 49)
• Required.
uniquely identify a
posting run.
6 Purchase Type 9(01) BASE II A code that indicates Values:
TC05-TCR3 whether the transaction
1 = Fuel Purchase
Fleet covers fuel and/or non-
Service (27- fuel elements. 2 = Non-fuel Purchase
27)
3 = Fuel and Non-fuel Purchase
For Add/Change:
• Not required.
value.
Fleet Service (17)

FORMAT SOURCE
7 Fuel Type X(02) Values:
BASE II The type of fuel 1=Unleaded Regular
TC05-TCR3 purchased. Specifies both 2=Unleaded Plus
Fleet fuel type and grade.
Service (28- 3=Unleaded Super
Compliant with October 4=Unleaded 4
29)
2006 PCATS industry
standard 5=Unleaded 5
6=Unleaded Methanol (5.7%
blend)
7=Unleaded Plus Methanol
(5.7% blend)
8=Super Unleaded Methanol
(5.7% blend)
9=Unleaded Methanol (7.7%
blend)
(7.7% blend)
11=Unleaded Ethanol (5.7%
blend)
12=Unleaded Plus Ethanol (5.7%
blend)
13=Super Unleaded Ethanol
(5.7% blend)
14=Unleaded Ethanol (7.7%
blend)
15=Unleaded Plus Ethanol (7.7%
blend)
16=Methanol/Leaded
17=Ethanol/Leaded
18=Leaded
19=Regular Diesel #2
20=Premium Diesel #2
21=Diesel #1
22=Compressed Natural Gas
23=Liquid Propane Gas
24=Liquid Natural Gas
25=M-85
26=E-85
27=Unleaded-Reformulated 1
Fleet Service (17)

FORMAT SOURCE
Fuel Type
7 X(02) Values:
(continued)
32=Diesel Off-Road (#1 and #2
Non-Taxable)
33=Ultra Low Sulfur Diesel Off-
Road (Non-Taxable)
34=Biodiesel Blend Off-Road
(Non-Taxable)
35=Ultra Low Sulfur Biodiesel
Blend Off-Road (Non-Taxable)
36=Racing Fuel
(7.7% Blend)
38=Unleaded Methanol (10%
Blend)
(10% Blend)
(10% Blend)
41-44=Undefined
45=B2 Diesel Blend 2%
BioDiesel
BioDiesel
BioDiesel
BioDiesel
BioDiesel
BioDiesel
BioDiesel
52=Ultra Low Sulfur #1
53=Ultra Low Sulfur #2
Fleet Service (17)

FORMAT SOURCE
Fuel Type
7 X(02) Values:
(continued)
54=Ultra Low Sulfur Premium
Diesel #2
Blend 2%
Blend 5%
Blend 10%
Blend 11%
Blend 15%
Blend 20%
Blend 100%
62-70=Undefined Fuel-Reserved
for PCATS Future Use
71-98=Undefined Fuel-Reserved
for Proprietary Use
99=Miscellaneous Fuel
A0=Jet Fuel
A1=Aviation Fuel Regular
A2=Aviation Fuel Premium
A3=Aviation Fuel JP8
A4=Aviation Fuel 4
A5=Aviation Fuel 5
A6-A7=Undefined Aviation
Fuel-Reserved for PCATS Future
Use
A8=Undefined Aviation Fuel-
Reserved for Proprietary Use
A9=Miscellaneous Aviation Fuel
F0=Kerosene-Low Sulfur
F1=White Gas
F2=Heating Oil
F3=Bottled Propane
Fleet Service (17)

FORMAT SOURCE
Fuel Type
7 X(02) Values:
(continued)
F4=Other Fuel (Non-Taxable)
F5=Kerosene-Ultra Low Sulfur
F6=Kerosene-Low Sulfur (Non-
Taxable)
F7=Kerosene-Ultra Low Sulfur
(Non-Taxable)
F8=Undefined Other Fuel-
Reserved for PCATS Future Use
F9=Miscellaneous Other Fuel
F9=Miscellaneous Other Fuel
M1=Marine Fuel 1
M2=Marine Fuel 2
M3=Marine Fuel 3
M4=Marine Fuel 4
M5=Marine Fuel 5
M6=Marine-Other
M7=Undefined Marine Fuel-
Reserved for PCATS Future Use
M8=Undefined Marine Fuel-
Reserved for Proprietary Use
M9=Miscellaneous Marine Fuel
For Add/Change:
• Not required.
value.
8 Fuel Unit of X(01) BASE II A unit of measure code Values:
Measure Code TC05-TCR3 for fuel transactions.
L = Liter
Fleet
Service (30- G = U.S. Gallon
30)
I = Imperial Gallon
K = Kilo
P = Pound
For Add/Change:
• Not required.
value.
Fleet Service (17)

FORMAT SOURCE
9 Fuel Unit of X(01) BASE II A unit of measure code Values:

Measure Code TC05-TCR3 for fuel transactions.
L = Liter
Fleet
Service (30- G = U.S. Gallon
30)
I = Imperial Gallon
K = Kilo
P = Pound
For Add/Change:
• Not required.
value.
10 Fuel Quantity 9(16) BASE II The quantity of fuel Four decimal places are implied
TC05-TCR3 purchased. (123456 = 12.3456).
Fleet
For Add/Change:
Service (31-
42) • Not required.
11 Fuel Unit Cost 9(16) BASE II The unit cost, including Four decimal places are implied
TC05-TCR3 tax, of the fuel purchased. (123456 = 12.3456).
Fleet
For Add/Change:
Service (43-
12 Fuel Gross 9(16) BASE II The total price for fuel Four decimal places are implied
Amount TC05-TCR3 purchases only. (123456 = 12.3456).
Fleet
For Add/Change:
Service (55-
13 Fuel Net Amount 9(16) BASE II The gross fuel price, less Four decimal places are implied
TC05-TCR3 any taxes exempted. (123456 = 12.3456).
Fleet
For Add/Change:
Service (67-
14 Non-Fuel Gross 9(16) BASE II The total price for non- Four decimal places are implied
Amount TC05-TCR3 fuel purchases. (123456 = 12.3456).
Fleet
For Add/Change:
Service (79-
Fleet Service (17)

FORMAT SOURCE
15 Non-Fuel Net 9(16) BASE II The gross non-fuel price, Four decimal places are implied
Amount TC05-TCR3 less any taxes exempted. (123456 = 12.3456).
Fleet
For Add/Change:
Service (91-
16 Odometer X(08) BASE II The reading of the For Add/Change:
Reading TC05-TCR3 vehicle’s odometer (or
• Not required.
Fleet equivalent for marine or
Service air vehicles) at the time of
(103-109) the transaction.
17 VAT/Tax Rate 9(09) BASE II The rate of VAT or other Four decimal places are implied
TC05-TCR3 tax (expressed in (123456 = 12.3456).
Fleet percentage terms) for the
For Add/Change:
Service fuel purchased.
18 Fuel 9(16) BASE II Four decimal places are implied
Miscellaneous Tax TC05-TCR3 (123456 = 12.3456).
Amount Fleet
For Add/Change:
Service
19 Non-Fuel 9(16) BASE II Four decimal places are implied
Miscellaneous Tax TC05-TCR3 (123456 = 12.3456).
Amount Fleet
For Add/Change:
Service
20 Service Type X(01) BASE II A code that indicates Values:
TC05-TCR3 whether full service or
F = Full Service
Fleet self-service was used for
Service the transaction. S = Self Service
(150-150)
Space = Non-fuel Purchase
For Add/Change:
• Not required.
value.
Fleet Service (17)

FORMAT SOURCE
21 Fuel 9(01) BASE II Indicates if the transaction Values :

Miscellaneous Tax TC05-TCR3 is exempt or non-exempt
0 = Non-Exempt
Exemption Fleet from miscellaneous fuel
Indicator Service tax in accordance with the 1 = Exempt
(151-151) client’s tax status.
For Add/Change:
• Not required.
value.
22 Non-Fuel 9(01) BASE II Indicates if the transaction Values :
Miscellaneous Tax TC05-TCR3 is exempt or non-exempt
0 = Non-Exempt
Exemption Fleet from non-fuel
Indicator Service miscellaneous taxes in 1 = Exempt
(152-152) accordance with the
For Add/Change:
client’s tax status.
• Not required.
value.
• Not required.
Fleet field used to link draft data
Service information with any
COMFLT related TC50 text message
(23-37) transactions.
24 Non-Fuel Federal 9(01) BASE II Indicates if the transaction Values :
Excise Tax TC50-TCR0 is exempt or non-exempt
0 = Non-Exempt
Exemption Fleet from non-fuel federal
Indicator Service Excise Taxes in 1 = Exempt
COMFLT accordance with the
For Add/Change:
(41-41) client’s tax status.
• Not required.
value.
25 Non-Fuel Federal 9(16) BASE II Two decimal places are implied
Excise Tax TC50-TCR0 (1234 = 12.34).
Amount Fleet
For Add/Change:
Service
COMFLT • Not required.
Fleet Service (17)

FORMAT SOURCE
26 Fuel Federal 9(01) BASE II Indicates if the transaction Values :

Excise Tax TC50-TCR0 is exempt or non-exempt
0 = Non-Exempt
Exemption Fleet from fuel federal taxes in
Indicator Service accordance with the 1 = Exempt
COMFLT client’s tax status.
For Add/Change:
(54-54)
• Not required.
value.
27 Fuel Federal 9(16) BASE II Two decimal places are implied
Excise Tax TC50-TCR0 (1234 = 12.34).
Amount Fleet
For Add/Change:
Service
28 State Motor Fuel 9(01) BASE II Indicates if the transaction Values :
Tax Exemption TC50-TCR0 is exempt or non-exempt
0 = Non-Exempt
Indicator Fleet from state motor fuel
Service taxes in accordance with 1 = Exempt
COMFLT the client’s tax status.
For Add/Change:
(67-67)
• Not required.
value.
29 State Motor Fuel 9(16) BASE II Two decimal places are implied
Tax Amount TC50-TCR0 (1234 = 12.34).
Fleet
For Add/Change:
Service
30 County Fuel Sales 9(01) BASE II Indicates if the transaction Values :
0 = Non-Exempt
Indicator Fleet from county fuel sales
Service taxes in accordance with 1 = Exempt
For Add/Change:
(80-80)
• Not required.
value.
31 County Fuel Sales 9(16) BASE II Two decimal places are implied
Tax Amount TC50-TCR0 (1234 = 12.34).
Fleet
For Add/Change:
Service
Fleet Service (17)

FORMAT SOURCE
32 Non-Fuel State 9(01) BASE II Indicates if the transaction Values :

and Local Sales TC50-TCR0 is exempt or non-exempt
0 = Non-Exempt
Tax Exemption Fleet from non-fuel state and
Indicator Service local taxes in accordance 1 = Exempt
COMFLT with the client’s tax status.
For Add/Change:
(93-93)
• Not required.
value.
33 Non-Fuel State 9(16) BASE II Two decimal places are implied
and Local Sales TC50-TCR0 (1234 = 12.34).
Tax Amount Fleet
For Add/Change:
Service
34 County Motor 9(01) BASE II Indicates if the transaction Values :
Fuel Tax TC50-TCR0 is exempt or non-exempt
0 = Non-Exempt
Exemption Fleet from county motor fuel
Indicator Service taxes in accordance with 1 = Exempt
For Add/Change:
(106-106)
• Not required.
value.
35 County Motor 9(16) BASE II Two decimal places are implied
Fuel Tax Amount TC50-TCR0 (1234 = 12.34).
Fleet
For Add/Change:
Service
36 City Fuel Sales 9(01) BASE II Indicates if the transaction Values :
0 = Non-Exempt
Indicator Fleet from city fuel sales taxes in
Service accordance with the 1 = Exempt
For Add/Change:
(119-119)
• Not required.
value.
37 City Fuel Sales 9(16) BASE II Two decimal places are implied
Tax Amount TC50-TCR0 (1234 = 12.34).
Fleet
For Add/Change:
Service
Fleet Service (17)

FORMAT SOURCE
38 City Motor Fuel 9(01) BASE II Indicates if the transaction Values :

0 = Non-Exempt
Indicator Fleet from city motor fuel taxes
Service in accordance with the 1 = Exempt
For Add/Change:
(132-132)
• Not required.
value.
39 City Motor Fuel 9(16) BASE II Two decimal places are implied
Tax Amount TC50-TCR0 (1234 = 12.34).
Fleet
For Add/Change:
Service
40 Secondary State 9(01) BASE II Indicates if the transaction Values :
Fuel Tax TC50-TCR0 is exempt or non-exempt
0 = Non-Exempt
Exemption Fleet from secondary state fuel
Indicator Service taxes in accordance with 1 = Exempt
For Add/Change:
(145-145)
• Not required.
value.
41 Secondary State 9(16) BASE II Two decimal places are implied
Fuel Tax Amount TC50-TCR0 (1234 = 12.34).
Fleet
For Add/Change:
Service
42 Federal Sales Tax 9(01) BASE II Indicates if the transaction Values :
Exemption TC50-TCR1 is exempt or non-exempt
0 = Non-Exempt
Indicator Fleet from federal sales taxes in
Service (5-5) accordance with the 1 = Exempt
client’s tax status.
For Add/Change:
• Not required.
value.
43 Federal Sales Tax 9(16) BASE II Two decimal places are implied
Amount TC50-TCR1 (1234 = 12.34).
Fleet
For Add/Change:
Service (6-
Fleet Service (17)

FORMAT SOURCE

• Not required.
Generic
Data (111-
135)
Number.
This information will be
data with the card
transaction.
For Add/Change:
data with the card
transaction.
• Not required.
This information will be date.
Data (61-64)
data with the card
transaction.
• Not required.
105)
data with the card
transaction.
• Not required.
Generic
Data (77-
101)
data with the card
transaction.
Fleet Service (17)

FORMAT SOURCE

• Not required.
Generic
Data (106-
110)
data with the card
transaction.
• Not required.
addendum record.
used for matching.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
54 Optional Field 4 X(26) Field used between For Add/Change:
processor and receiver for
• Not required.
specific data.
Fleet Service (T17) Summary Notes:
the transactional data. For transactions involving fleet service, this information is carried in the Fleet
Service (T17) records.
In addition to items such as various fuel and non-fuel taxes or exemption indicators, amounts, and service
logistics, there are several fields in the record which may be utilized to enhance the transactional data and to
link this information to the corresponding financial transaction. These are fields Purchase ID (Field #43)
through Processor Addendum Key (Field #49). Optional fields at the end of the record can also be used to
carry additional information relevant to the fleet service transaction.
FLEET PRODUCT – Type 18
The Fleet Product record type contains identifying information about the products related to a single card
transaction. It is currently used to identify the non-fuel product codes included in a Fleet Service
transaction.
The Fleet Product details carried in this record are related to a particular transaction containing charges for a
specific fleet product-related event. In addition, the corresponding Fleet Service (T17) record must exist
and already be loaded into the system. The fleet transaction is uniquely identified by the following Primary
Key fields: the Account Number (Field # 2), Posting Date (Field # 3), Transaction Reference Number
(Field # 4), and Sequence Number (Field #5). These four fields are required and cannot be empty, all zeros
or spaces. They must uniquely represent a valid fleet-related transaction. In addition the Product Sequence
Number (Field #5) is also included in the primary key to differentiate fleet products. These fields are
indicated by a “**” following the field name. All attributes contained in this record type relate to the fleet
products belonging to the transaction indicated by the primary key, and to the fleet event it represents.

For Add:
• The corresponding Fleet Service record (based on the Account Number, Posting Date, Transaction
Reference Number, and Sequence Number) must already exist in the application.
• The Fleet Product must not exist in the application.
For Change:
• The Fleet Product must exist in the application.
Fleet Product (18)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;
Fleet Product (18)

FORMAT SOURCE

transaction.
• Required.
• Required.
Number** 49)
• Required.
process to uniquely
6 Product Sequence 9(02) Sequence Number for the Values:
Number** Card Transaction Product
01 to 99
associated with a Fleet
Service transaction; For Add/Change:
sequentially assigned to
• Required.
differentiate records/
products. Not associated • Must be a valid value.
with invoice or purchase
order sequence number.
Fleet Product (18)

FORMAT SOURCE
7 Product Code X(02) BASE II A code used to indicate Values:

TC05-TCR6 the non-fuel components
30 = Motor Oil
(128-129, of the transaction.
etc.) 31 = Oil Change
32 = Engine Service
33 = Transmission Service
34 = Brake Service
35-38 = Unassigned Repair Values
39 = Miscellaneous Repairs
40 = Tires, Batteries, Accessories
41 = Tires
42 = Batteries
43 = Automotive Accessories
44 = Automotive Glass
45 = Car Wash
46-69 = Unassigned Automotive
Products/Services
70 = Cigarettes/Tobacco
71-77 = Unassigned
Food/Grocery Items
78 = Health/Beauty Aid
79 = Miscellaneous Grocery
80 = Soda
81 = Beer/Wine
82 = Milk/Juice
83-89 = Unassigned Beverage
Items
90 = Miscellaneous
91-99 = Reserved
For Add:
• Required
• Must be a valid value.
8 Message X(16) BASE II The Message Identifier is For Add/Change:
Identifier TC05-TCR6 used to link the TC50
• Not required.
(92-106) acquirer-provided
enhanced data records
with the draft data
transaction.
Fleet Product (18)

FORMAT SOURCE

• Not required.
Generic
Data (111-
135)
Number.
data with the card
transaction.
For Add/Change:
data with the card
transaction.
• Not required.
This information will be date.
Data (61-64)
data with the card
transaction.
• Not required.
105)
data with the card
transaction.
• Not required.
Generic
Data (77-
101)
data with the card
transaction.
Fleet Product (18)

FORMAT SOURCE

• Not required.
Generic
Data (106-
110)
data with the card
transaction.
• Not required.
addendum record.
used for matching.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Fleet Product (T18) Summary Notes:

The primary key fields listed above uniquely identify a single fleet product-related Transaction (T5).
Additional information about multiple non-fuel products that were purchased can be carried in the Fleet
Product (T18) records. Several fields in the record can also be used to enhance the data and to link it to the
corresponding financial transaction. These are fields Message Identifier (Field #8) through Processor
Addendum Key (Field #15). Optional fields at the end of the record can also be used to carry additional
information relevant to the fleet products in the transaction.
Temporary Services – Type 20
The Temporary Services record type contains information received from participating temporary services
agencies. This enhanced data may be utilized for more complex reporting requirements associated with the
hiring of temporary services. This Temporary Services (T20) record contains supplemental information
concerning the temporary service transaction in addition to that found in the corresponding Line Item
Detail record (T7) which must precede it.
The Temporary Services details carried in this record are related to a particular transaction. That transaction
is uniquely identified by the following Primary Key fields: The Account Number (Field # 2), Posting Date
(Field # 3), Transaction Reference Number (Field # 4), and Sequence Number (Field #5). The particular
service event is further defined by the addition of a fifth field: Item Sequence Number (Field #6). These
five fields are required and cannot be empty, all spaces or zeros. They must uniquely represent a valid
transaction, and a valid temporary service-related line item within that transaction. These fields are indicated
by a “**” following the field name. All attributes contained in this record type belong to the transaction
indicated by the primary key and to the Line Item Detail (T7) record which further describes it.

For Add:
• The corresponding Line Item Detail record (based on Account Number, Posting Date, Transaction
Reference Number, Sequence Number, and Item Sequence Number) must already exist in the
application.
• The Temporary Services record must not already exist in the application.
For Change:
• The Temporary Services must exist in the application.
Temporary Services (20)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;

FORMAT SOURCE

transaction.
• Required.
• Required.
Number** 49)
• Required.
process to uniquely
• Required.
assigned value to • Must be numeric.
differentiate items. Not
associated with an invoice
or purchase order line
item.
• Not required.
Line Item field used to link draft data
Detail (23- information with any
37) related TC50 text message
transactions.
8 Start Date 9(08) BASE II Starting date of period For Add/Change:
TC50-TCR1 during which work was
• Not required.
(72-79) performed (first date on
timesheet). • If provided, must be a valid
date.
9 End Date 9(08) BASE II Ending date of period For Add/Change:
TC50-TCR0 during which work was
• Not required.
(66-73) performed (last date on
timesheet). • If provided, must be a valid
date.

FORMAT SOURCE
10 Account X(18) BASE II Cost Center to which For Add/Change:

Code/Cost Center TC50-TCR0 purchase is to be charged.
• Not required.
(74-90)
“Load Transaction –
Temporary Services” as
description.
• If provided, must be active.
11 Description X(26) BASE II Description of the type of For Add/Change:
TC50-TCR0 work the temporary
• Not required.
(91-115) employee is performing.
12 Employee/Temp X(26) BASE II Name of the temporary For Add/Change:
Name TC50-TCR0 employee.
• Not required.
(116-140)
13 Employee/Temp 9(09) BASE II Social Security Number or For Add/Change:
Social Security TC50-TCR0 Tax ID of the temporary
• Not required.
Number (141-149) employee.
14 Rate Indicator 9(05) BASE II Code indicating the rate Values:
TC50-TCR0 used to calculate the
1 = Hour
(150-154) amount being billed.
2 = Flat amount
3 = Daily
4 = Other
For Add/Change:
• Not required.
value.
15 Rate 9(12) BASE II Regular rate of temporary Two decimal places are implied
TC50-TCR0 employee. (1234 = 12.34).
(155-166)
For Add/Change:
• Not required.
16 Regular Hours 9(05) BASE II Number of hours worked Two decimal places are implied
Worked TC50-TCR1 at regular rate. (1234 = 12.34).
(52-56)
For Add/Change:
• Not required.

FORMAT SOURCE
17 Overtime Rate 9(12) BASE II Premium rate applicable to Two decimal places are implied
TC50-TCR1 overtime hours worked. (1234 = 12.34).
(40-51)
For Add/Change:
• Not required.
18 Overtime Hours 9(05) BASE II Number of hours worked Two decimal places are implied
Worked TC50-TCR1 at overtime rate. (1234 = 12.34).
(35-39)
For Add/Change:
• Not required.
19 Job Code X(12) BASE II Code indicating the type For Add/Change:
TC50-TCR1 of work being performed.
• Not required.
(5-16)
20 Miscellaneous 9(12) BASE II Amount of expenses to be Two decimal places are implied
Expense Amount TC50-TCR1 reimbursed to temporary (1234 = 12.34).
(17-28) employee.
For Add/Change:
• Not required.
21 Miscellaneous X(06) BASE II Code used to classify Values:
Expense Indicator TC50-TCR1 miscellaneous amount for
AT = Air travel
(29-34) which the temporary
employee is being GT = Ground transportation
reimbursed. including mileage
PD = Per diem
H = Hotel
I = Insurance
M = Meals
O = Other
For Add/Change:
• Not required.
22 Requester Name X(16) BASE II Name of employment For Add/Change:
or ID TC50-TCR1 agency placing the
• Not required.
(57-71) temporary employee.
23 Subtotal Amount 9(12) BASE II Billable amount before Two decimal places are implied
TC50-TCR1 taxes and discounts are (1234 = 12.34).
(80-91) applied.
For Add/Change:
• Not required.
24 Sales Tax Amount 9(12) BASE II Applicable tax amount. Two decimal places are implied
TC50-TCR1 (1234 = 12.34).
(92-103)
For Add/Change:
• Not required.

FORMAT SOURCE
For Add/Change:
• Not required.
26 Supervisor/ X(26) BASE II Name of supervisor. For Add/Change:
Reported To TC50-TCR1
• Not required.
(116-140)
27 Time Sheet 9(10) BASE II Number identifying For Add/Change:
Number TC50-TCR1 temporary employee’s
• Not required.
(141-150) timesheet.
28 Commodity Code X(12) BASE II For Add/Change:
TC50-TCR1
• Not required.
(151-162)
29 Reimbursement X(02) BASE II For Add/Change:
Attribute TC50-TCR0
• Not required.
(168)
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Temporary Services (T20) Summary Notes:
the transactional data. For transactions involving temporary service details, this information is carried in
the T20 records. A corresponding Line Item Detail (T7) record must be loaded prior to loading Temporary
Services type of records. Details such as start and end dates, employee information, rates etc. are carried in
this record. In addition, a Message Identifier (Field #26) can be used to link this information to other data
in the Visa system. Optional fields at the end of the record can also be used to carry additional information
relevant to the temporary services transaction.
Shipping Services – Type 21
The Shipping Services record type contains information received from participating shipping service
companies. This enhanced data may be utilized for more complex reporting requirements associated with
the purchase of shipping services. This Shipping Services (T21) record contains supplemental information
concerning the shipping-related transaction in addition to that found in the corresponding Line Item Detail
record (T7) which must precede it.
The Shipping Services details carried in this record are related to a particular transaction. That transaction is
uniquely identified by the following Primary Key fields: the Account Number (Field # 2), Posting Date
(Field # 3), Transaction Reference Number (Field # 4), and Sequence Number (Field #5). The particular
service event is further defined by the addition of a fifth field: Item Sequence Number (Field #6). These
five fields are required and cannot be empty, all spaces or zeros. They must uniquely represent a valid
transaction, and a valid shipping service-related line item within that transaction. These fields are indicated
by a “**” following the field name. All attributes contained in this record type belong to the transaction
indicated by the primary key and to the Line Item Detail (T7) record which further describes it.

For Add:
• The corresponding Line Item Detail record (based on Account Number, Posting Date, Transaction
Reference Number, Sequence Number, and Item Sequence Number) must already exist in the
application.
• The Shipping Services record must not already exist in the application.
For Change:
• The Shipping Services must exist in the application.
Shipping Services (21)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;

FORMAT SOURCE

transaction.
• Required.
• Required.
Number** 49)
• Required.
process to uniquely
• Required.
assigned number to • Must be numeric.
differentiate between line
item records. Not
associated with invoice, or
purchase order line
numbers.
• Not required.
Line Item field used to link draft data
Detail (23- information with any
37) related TC50 text message
transactions.
8 Shipping/Courier X(26) BASE II Business name of the For Add/Change:
Name TC50-TCR0 shipping or delivery
• Required.
(66-90) company.
9 Tracking Number X(22) BASE II Package tracking number. For Add/Change:
TC50-TCR0
• Required.
(91-112)
10 Pickup Date 9(08) BASE II Date the package was For Add/Change:
TC50-TCR0 picked up.
• Not required.
(113-120)
date.
11 Origin Zip Code X(14) BASE II Zip code of the location For Add/Change:
TC50-TCR0 from which the package is
• Not required.
(121-129) being sent.

FORMAT SOURCE
12 Origin Country 9(05) BASE II ISO Country Code of the For Add/Change:
Code TC50-TCR0 location from which the
• Not required.
(130-132) package is being sent.
ISO country code.
13 Destination Zip X(14) BASE II Zip code of the location to For Add/Change:
Code TC50-TCR0 which the package is being
• Not required.
(133-141) sent.
14 Destination 9(05) BASE II ISO Country Code of the For Add/Change:
Country Code TC50-TCR0 location to which the
• Not required.
(142-144) package is being sent.
ISO country code.
15 Customer X(17) BASE II For Add/Change:
Reference TC50-TCR0
• Required.
Number (145-161)
16 Number of 9(05) BASE II Number of packages For Add/Change:
Packages TC50-TCR0 included in the shipment.
• Required.
(162-166)
17 Net Amount 9(12) BASE II Cost of shipment, after Two decimal places are implied
TC50-TCR1 any tax and discounts are (1234 = 12.34).
(5-16) applied.
For Add/Change:
• Not required.
18 Tax Amount 9(12) BASE II For U.S.: sales tax amount Two decimal places are implied
TC50-TCR1 included in the (1234 = 12.34).
For Add/Change:
For other countries:
• Not required.
Provincial Sales Tax (PST)
Amount included in the
transaction.
For Add/Change:
• Not required.
20 Service X(24) BASE II Purpose/reason for the For Add/Change:
Description TC50-TCR1 charge.
• Not required.
(41-64)

FORMAT SOURCE
21 Unit of Measure X(03) BASE II Identifies the package Values:

TC50-TCR1 weight unit of measure.
LBS = Pounds
(65-67)
KGS = Kilograms
For Add/Change:
• Not required.
value.
22 Weight 9(05) BASE II Total weight of all Two decimal places are implied
TC50-TCR1 packages in the shipment. (1234 = 12.34).
(68-72)
For Add/Change:
• Not required.
23 Origin Sender X(26) BASE II Name of the sender of the For Add/Change:
Name TC50-TCR1 package
• Not required.
(73-97)
24 Origin Address X(20) BASE II Address of the sender of For Add/Change:
TC50-TCR1 the package.
• Not required.
(98-117)
25 Destination X(26) BASE II Name of the recipient of For Add/Change:
Receiver Name TC50-TCR1 the package.
• Not required.
(118-142)
26 Destination X(20) BASE II Address of the recipient of For Add/Change:
Address TC50-TCR1 the package.
• Not required.
(143-162)
27 Reimbursement X(01) BASE II For Add/Change:
Attribute TC50-TCR0
• Not required.
(168)
28 Origin X(04) State/Province Code For Add/Change:
State/Province where the package was
• Not required.
Code sent.
origin’s country.
29 Destination X(04) State/Province Code For Add/Change:
State/Province where the package will be
• Not required.
Code delivered.
• Not required.
to spaces.

FORMAT SOURCE

• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Shipping Services (T21) Summary Notes:
the transactional data. For transactions involving shipping service details, this information is carried in the
Shipping Services (T21) records. A corresponding Line Item Detail (T7) record must also exist in the
application prior to loading Shipping Services record types.
Details such as pickup date, courier information, origin and destination information, various descriptors
such as number of packages, package weight, tax, discount, and other amounts, etc. are carried in this
record. In addition, a Message Identifier (Field #7) can be used to link this information to other data in the
Visa system. Optional fields at the end of the record can also be used to carry additional information
relevant to the shipping services transaction.
HEADQUARTER RELATIONSHIP – Type 25
The Headquarter Relationship record type contains information about a company’s relationship with its
Headquarters. Companies are initially added via a data load file and the HQ relationship record might be in
the same file. If so, the correct sort sequence will be required during processing of the records. For instance,
the HQ relationship has to be added before data transactions, but after the Company Record. The
Headquarters Relationship record is provided for those business situations where knowledge of such a larger
hierarchical relationship needs to be retained and reported. For additional information as to how to use this
type of enhanced data, please contact your Visa representative.
Headquarter Relationship (25)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
2 Processor 9(10) Processor ID. For Add/Change:
Identification • Required
• Must already exist in the
application.
3 Issuer 9(10) Identification Number of For Add/Change:
Identification the Issuing Bank that • Required.
provides the Corporate or
Purchasing Cards to the • Must already exist in the
client company. application.
4 Company 9(10) Issuer-assigned Company For Add/Change:

Identification Identification. It identifies • Required.
multiple companies in an
issuer’s portfolio. • Must already exist in the
application.
5 HQ Identification 9(10) Headquarter ID as defined For Add:
in MN (multi-national)
• Required.
database.
• Must not already exist in
system.
For Add/Change:
• Required.
• Must already exist in system

FORMAT SOURCE
6 HQ Name X(80) Name of Headquarters. For Add:

• Required.
For Change:
7 Reporting 9(05) ISO Code for reporting For Add:
Currency Code currency.
• Required.
• Must be a valid ISO Currency
code.
For Change:
For Add/Change:
• Must exist as a valid ISO
Currency Code.
8 Lead Bank Flag 9(02) Identifies member bank
role. Applies to the
• Must be 0 or 1
relationship, not the
Member record. • Required.
• 0=No, 1=Yes.
9 Start Date 9(08) Start Date of relationship Must be a valid date
with HQ.
For Add:
• Required.
For Change:
10 Processing Date 9(08) Processing Date Must be a valid date
For Add:
• Required.
For Change:
11 Close Date 9(08) Date MN relationship • Must be a valid date
terminates. • Not required
• Not required.
to spaces.
• Not required.
to spaces.

FORMAT SOURCE

• Not required.
to spaces.
• Not required.
to spaces.
Headquarters Relationship (T25) Summary Notes:
The Headquarters Relationship record is intended to facilitate more complex business reporting needs. In
addition to the identifying information found within the record, there are optional fields at the end of the
record that can also be used to carry additional information relevant to the headquarters relationship.
Also, note that the Processing Date (Field #10) is not updateable.
LODGING DETAIL – Type 26
The Lodging Detail record type contains detailed information on Visa commercial card transactions
conducted at hotels or places of lodging. These charges are specific to a particular account, and to the
particular transaction that carried the charge detail. In addition, the corresponding Lodging Summary (T9)
must already be present in the application.
The lodging details carried in this record are related to a particular transaction. That transaction is uniquely
Transaction Reference Number (Field # 4), and the Sequence Number (Field #5). Two additional fields,
Date of Charge (Field #6) and Item Sequence Number (Field #7) are used to identify the particular line
charge being detailed. These six fields are required and cannot be empty, all zeros or spaces. They must
uniquely represent a valid transaction and a valid item within the transaction. These fields are indicated by a
“**” following the field name. All attributes contained in this record type belong to the transaction line item
indicated by the primary key.

For Add:
• The corresponding Lodging Summary (based on the Account Number, Posting Date, Transaction
Reference Number, and Sequence Number) must already exist in the application.
• The Lodging Detail must not already exist in the application.
For Change:
• The Lodging Detail must exist in the application.
Lodging Detail (26)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;
Lodging Detail (26)

FORMAT SOURCE

transaction.
• Required.
• Required.
Number**
• Required.
process to uniquely
6 Date of Charge** 9(08) Date account was charged For Add/Change:
for service provided.
• Required.
7 Item Sequence 9(05) Sequence number of an For Add:
Number** item in a hotel folio
• Required.
incremented value to • Must be numeric.
identify successive records.
Not associated with a
particular line item in a
bill.
8 Room Rate 9(16) Daily room rate for a hotel Two decimal places are implied
transaction. (1234 = 12.34).
For Add/Change:
• Not required.
9 Discount Rate 9(16) Daily discount room rate Two decimal places are implied
for a hotel transaction. (1234 = 12.34).
For Add/Change:
• Not required.
10 Food/Beverage 9(16) Food and beverages Two decimal places are implied
Charges charges in a Card (1234 = 12.34).
transaction for hotel
For Add/Change:
lodging.
• Not required.
This value does not
include mini-bar charges. • If provided, must be numeric.
Lodging Detail (26)

FORMAT SOURCE
11 Folio Cash 9(16) Cash advances charged Two decimal places are implied
Advances against the folio. (1234 = 12.34).
For Add/Change:
• Not required.
12 Valet Parking 9(16) Valet parking charges of a Two decimal places are implied
Charges Card transaction for hotel (1234 = 12.34).
lodging.
For Add/Change:
• Not required.
13 Mini-Bar Charges 9(16) Charges of in-room mini- Two decimal places are implied
bar food and beverage (1234 = 12.34).
expenses.
For Add/Change:
• Not required.
14 Laundry Charges 9(16) Laundry charges in a Card Two decimal places are implied
transaction for hotel (1234 = 12.34).
lodging.
For Add/Change:
• Not required.
15 Telephone 9(16) Charges of telephone Two decimal places are implied
Charges expenses, including in- (1234 = 12.34).
room fax machine usage.
For Add/Change:
• Not required.
16 Gift Shop 9(16) Charges of gift shop and Two decimal places are implied
Purchases merchandise purchases. (1234 = 12.34).
For Add/Change:
• Not required.
17 Movie Charges 9(16) Charges for movies and Two decimal places are implied
other in-room (1234 = 12.34).
entertainment expenses.
For Add/Change:
• Not required.
Lodging Detail (26)

FORMAT SOURCE
18 Business Center 9(16) Charges for copies, faxes, Two decimal places are implied
Charges and other Business Center (1234 = 12.34).
expenses.
For Add/Change:
• Not required.
19 Health Club 9(16) Charges for health club or Two decimal places are implied
Charges pool expenses, including (1234 = 12.34).
court and equipment
For Add/Change:
rental and golf green fees.
• Not required.
20 Room Tax 9(16) The amount of room tax Two decimal places are implied
Amount applied against this (1234 = 12.34).
transaction.
For Add/Change:
• Not required.
21 Room Tax 2 9(16) The amount of room tax 2 Two decimal places are implied
transaction.
For Add/Change:
• Not required.
transaction.
For Add/Change:
• Not required.
transaction.
For Add/Change:
• Not required.
24 Other Charge 9(16) The amount of another Two decimal places are implied
charge defined by the (1234 = 12.34).
supplier.
For Add/Change:
• Not required.
25 Description of X(20) The description of the For Add/Change:
Other Charge other charge defined by
• Not required.
the supplier.
Lodging Detail (26)

FORMAT SOURCE
26 Other Charge X(05) The code used by the For Add/Change:

Code supplier for the other
• Not required.
charge.
• Not required.
(23-37)
data with the card
transaction.
• Not required.
Generic
Data (111-
135)
Number.
data with the card
transaction.
• Not required.
addendum record.
used for matching.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Lodging Detail (T26) Summary Notes:
The six primary key fields (Account Number (Field #2), Posting Date (Field #3), Transaction Reference
Number (Field #4), Sequence Number (Field #5), Date of Charge (Field #6) and Item Sequence Number
(Field #7)) uniquely identify a single Transaction (T5) and a single Lodging Summary (T9). For more
the transactional data. For transactions involving lodging details, this information can be carried in the
Lodging Detail (T26) records.
This record allows for additional details such as multiple separate charges for various types of taxes, etc. In
addition, there are several fields in the record which may be utilized to enhance the transactional data.
These are fields Message Identifier (Field #27), Purchase ID (Field #28), and Processor Addendum Key
(Field #39). Optional fields at the end of the record can also be used to carry additional information
relevant to the lodging details.
CAR RENTAL DETAIL – Type 27
The Car Rental Detail record type contains detailed information on Visa commercial card transactions
conducted at car rental merchants. This record provides additional details for those card transactions with
respect to car rental-related charges.
The primary key to this record consists of five fields: Account Number (Field #2), Posting Date (Field #3),
Transaction Reference Number (Field #4), Sequence Number (Field #5), and Item Sequence Number
(Field #6). These records are indicated below with a “**” following the field name. The combination of
these five fields must uniquely identify a transaction record (T5) for the underlying transaction with the car
rental merchant and a Car Rental Summary Record (T2).
The following rules apply to the primary key fields in the Car Rental Detail record:
For Add:
• The corresponding Car Rental Summary (based on the Account Number, Posting Date, Transaction
• The Car Rental Detail must not already exist in the application.
For Change:
• The Car Rental Detail must exist in the application.
Car Rental Detail (27)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;
transmitted by Base II. • Must exist in the application.

transaction.
• Required.

FORMAT SOURCE

• Required.
Number**
• Required.
associated T5 posting • Must be numeric.
process to uniquely
6 Item Sequence 9(05) Sequence number of an For Add:
Number** item in a car rental detail
• Required.
assigned value to • Must be numeric.
differentiate successive
records. May be use to
differentiate rental days.
7 Daily Rental Rate 9(16) BASE II Daily Car Rental Rate of a Two decimal places are implied
TCR3 Car Card transaction. (1234 = 12.34).
Rental (44-
For Add/Change:
55)
• Not required.
8 Insurance 9(16) BASE II Insurance charges of a Car Two decimal places are implied
Charges TCR3 Car Rental Card transaction. (1234 = 12.34).
Rental (68-
For Add/Change:
79)
• Not required.
9 Auto Towing 9(16) BASE II Total charges of any Two decimal places are implied
TC50-TCR0 Towing or Roadside (1234 = 12.34).
Car Rental Service expenses.
For Add/Change:
(41-52)
• Not required.
10 Extra-Mileage 9(16) BASE II Total charges for Mileage Two decimal places are implied
Charges TC50-TCR0 above the mileage limit. (1234 = 12.34).
Car Rental
For Add/Change:
(65-76)
• Not required.

FORMAT SOURCE
11 Telephone 9(16) BASE II Total charges for in- Two decimal places are implied
Charges TC50-TCR0 vehicle telephone (1234 = 12.34).
Car Rental expenses, including Daily
For Add/Change:
(126-137) Rental charges, if
applicable. • Not required.
12 Other Charge 9(16) Represents the amount of Two decimal places are implied
another charge defined by (1234 = 12.34).
the supplier.
For Add/Change:
• Not required.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Car Rental Detail (T27) Summary Notes:
Number (Field #4), Sequence Number (Field #5), Date of Charge (Field #6) and Item Sequence Number
(Field #7)) uniquely identify a single Transaction (T5) and a single Car Rental Summary (T2). For more
the transactional data. For transactions involving car rental details, this information is carried in the Car
Rental Detail (T27) records.
There are also four optional fields at the end of the record can also be used to carry additional information
relevant to the car rental details.
ALLOCATION – Type 28
The Allocation record type contains Cost Allocation information linked to a Visa commercial card
transaction. This record is intended to support those clients with more sophisticated allocation reporting
requirements than may exist for most corporate card clients.
The primary key to this record consists of five fields: Account Number (Field #2), Posting Date (Field #3),
Transaction Reference Number (Field #4), Sequence Number (Field #5), and Allocation Sequence Number
(Field #6). These fields are indicated below with a “**” following the field name. The combination of these
five fields must uniquely identify a transaction record (T5) for the underlying transaction.
The following rules apply to the primary key fields in the Allocation record:
For Add:
• The Allocation must not already exist in the application.
For Change:
• The Allocation must exist in the application.
Allocation (28)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;

transaction.
• Required.
• Required.
Number**
Allocation (28)

FORMAT SOURCE

• Required.
posting process to • Must be numeric.
uniquely identify a
posting run.
6 Allocation 9(05) Sequence number of For Add:
Sequence allocation.
• Required.
Number**
7 G/L Sub-account X(76) G/L Sub-account number For Add/Change:
Number allocated to the
• Required.
transaction.
8 G/L Sub-account X(50) Description of the G/L For Add/Change:
Description Sub-account number.
• Not required.
9 Cost Center Code X(76) Cost Center code allocated For Add/Change:
to the transaction.
• Required.
10 Cost Center X(50) Description of the Cost For Add/Change:
Description Center Code.
• Not required.
11 Allocated Amount 9(16) Amount to be allocated. Two decimal places are implied
(1234 = 12.34).
For Add/Change:
• Required.
12 Allocated 9(03) Percentage of transaction Values:
Percentage to be reallocated.
0 to 100
For Add/Change:
• Not required.
value.
13 Tax 1 Amount 9(16) Tax 1 amount allocated. Two decimal places are implied
(1234 = 12.34).
For Add/Change:
• Not required.
14 Tax 2 Amount 9(16) Tax 2 amount allocated. Two decimal places are implied
(1234 = 12.34).
For Add/Change:
• Not required.
Allocation (28)

FORMAT SOURCE
15 Final Allocation 9(01) Indicates that the Values:

Flag transaction has been
0 = The allocation has not been
extracted for accounting
extracted in a final cost
purposes.
allocation extract.
1 = The allocation has been
extracted in a final cost
allocation extract.
For Add/Change:
• Not required.
value.
• If not provided, 0 will be
implied.
16 Description X(100) Description assigned to an For Add/Change:
allocation.
• Not required.
17 Allocated Date 9(08) Date that reallocation was For Add/Change:
performed.
• Required.
18 Allocation X(150) Accounting code for For Add/Change:
Accounting Code reallocation.
• Not required.
19 Original X(150) Original accounting code For Add/Change:
Accounting Code assigned, either by default
• Not required.
or by rules.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Allocation (T28) Summary Notes:
The five primary key fields (Account Number (Field #2), Posting Date (Field #3), Transaction Reference
Number (Field #4), Sequence Number (Field #5), and Allocation Sequence Number (Field #6) uniquely
identify a single Transaction (T5) which the user intends to apportion among one or more cost centers or
G/L accounts.
relevant to the details of the allocation.
ALLOCATION DESCRIPTION – Type 29
The Allocation Description record type contains information for one Cost Allocation line. This record is
intended to support those clients who have a need for additional supporting allocation-related information
associated with their transactions.
The primary key to this record consists of six fields: Account Number (Field #2), Posting Date (Field #3),
Transaction Reference Number (Field #4), Sequence Number (Field #5), Allocation Sequence Number
(Field #6), and Item Sequence Number (Field #7). These fields are indicated below with a “**” following
the field name. The combination of the first five fields must uniquely identify a transaction record (T5) for
the underlying transaction, and with the addition of the sixth field, a corresponding Allocation Record
(T28).
The following rules apply to the primary key fields in the Allocation record:
For Add:
• The corresponding Allocation (based on the Account Number, Posting Date, Transaction Reference
Number, Sequence Number, and Allocation Sequence Number) must exist in the application.
• The Allocation Description must not already exist in the application.
For Change:
• The Allocation Description must exist in the application.
Allocation Description (29)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;

transaction.
• Required.
Allocation Description (29)

FORMAT SOURCE

• Required.
Number**
• Required.
uniquely identify a
posting run.
6 Allocation 9(05) Sequence number of For Add:
Sequence allocation.
• Required.
Number**
7 Item Sequence 9(05) Sequence number of the For Add:
Number** item.
• Required.
8 Description X(100) A description assigned to For Add/Change:
the transaction, such as a
• Required.
Project Code.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Allocation Description (T29) Summary Notes:
Number (Field #4), Sequence Number (Field #5), Allocation Sequence Number (Field #6), and Item
Sequence Number (Field #7)) uniquely identify a single Transaction (T5) and a single Allocation record
(T28) which the user intends to apportion among one or more cost centers or G/L accounts.
RELATIONSHIP – Type 30
The Relationship record type contains information required for linking different objects together. For more
complex hierarchical relationships (reporting, accounting, or other), the Relationship Record (T30) can be
utilized to carry relevant details.
Relationship (30)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
2 Object Type 9(02) Identifies the record type Values:
of the object being linked
03 = Card Account
from.
04 = Cardholder
10 = Organization
For Add/Change:
• Required and must be a valid
value.
3 Field Value X(40) Contains the value of the For Add/Change:
following field:
• Required
Card Account if Object • Must be a valid value.
Type = 03
Cardholder ID if Object
Type = 04
Hierarchy Node if Object
Type = 10
4 Tree ID X(02) Identifies the hierarchy For Add/Change:
tree this node is related to.
• Required if Object Type = 10
Currently Visa does not Organization.
support multiple Tree • If not provided, the default
IDs in the Organization tree will be implied.
Record.
Relationship (30)

FORMAT SOURCE
5 Parent Object 9(02) Identifies the record type Values:

Type of the object being linked 03 = Card Account
to. 04 = Cardholder
10 = Organization
For Add/Change:
value.
6 Parent Field Value X(40) Contains the value of the For Add/Change:
following field:
Card Account if Object • Required
Type = 03 • Must be a valid value.
Cardholder ID if Object
Type = 04
Hierarchy Node if Object
Type = 10
7 Parent Tree ID X(02) Identifies the hierarchy For Add/Change:
tree the parent node is
• Required if Parent Object
related to.
Type = 10 Organization.
• If not provided, the default
tree will be implied.
8 Effective Date 9(08) Date when this relation is For Add/Change:
effective.
• Required
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Relationship (T30) Summary Notes:
The Relationship Record (T30) is intended to support multiple, hierarchical relationships, and, as such, is
not applicable for many standard VCF 4.0 business situations.
PHONE– Type 31
The Phone record type contains information on transactional charges associated with calling cards. This
record allows the user to carry phone-related details such as call-to and call-from information, connection
time, rate and amounts charged, etc. The Phone Record (T31) is specifically designed to carry these relevant
details.
The Phone details carried in this record are related to a particular transaction. That transaction is uniquely
Transaction Reference Number (Field # 4), and the Sequence Number (Field #5). These four fields are
required and cannot be empty, all spaces or zeros. They must uniquely represent a valid transaction. These
fields are indicated by a “**” following the field name. All attributes contained in this phone record type
belong to the transaction indicated by the primary key.

For Add:
• The Phone data must not already exist in the application.
For Change:
• The Phone data must exist in the application.
Phone (31)

FORMAT SOURCE

Change. transaction
transaction.
For Add/Change:
4.
• Required.
front of the card;

transaction.
• Required.
• Required.
Number**
Phone (31)

FORMAT SOURCE

• Required.
uniquely identify a
posting run.
6 Call To Number 9(15) Destination phone For Add/Change:
number.
• Not required.
7 Call To City X(14) Destination city. For Add/Change:
• Not required.
8 Call To X(04) Destination state/province For Add/Change:
State/Province code.
• Not required.
Code
Call To country.
9 Call To Country 9(05) Destination country. For Add/Change:
• Not required.
country code.
10 Call From Number 9(15) Origination phone For Add/Change:
number.
• Not required.
11 Call From City X(14) Origination city. For Add/Change:
• Not required.
12 Call From X(04) Origination state/province For Add/Change:
State/Province code.
• Not required.
Code
Call From country.
13 Call From Country 9(05) Origination country. For Add/Change:
• Not required.
country code.
14 Duration 9(06) Call duration. Format HHMMSS
For Add/Change:
• Not required.
• If provided must be a valid
time.
Phone (31)

FORMAT SOURCE
15 Connection Time 9(06) Identifies what time the Format HHMMSS

call was initiated.
For Add/Change:
• Not required.
• If provided, must be a valid 24
hours time.
16 Call Type X(02) Identifies the type of call. For Add/Change:
• Not required.
17 Rate Period X(06) Identifies the rate in effect For Add/Change:
during the call.
• Not required.
18 Discount Amount 9(16) Discount amount applied Two decimal places are implied
to the call. (1234 = 12.34).
For Add/Change:
• Not required.
19 Tax Amount 9(16) Tax amount applied to the Two decimal places are implied
call. (1234 = 12.34).
For Add/Change:
• Not required.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
• Not required.
to spaces.
Phone (T31) Summary Notes:
The four primary key fields (Account Number (Field #2), Posting Date (Field #3), Transaction Reference
Number (Field #4), and Sequence Number (Field #5)) uniquely identify a single Transaction (T5). For
business situations requiring enhanced data relating to telephone charges, additional information may be
desired to supplement the transactional data. For transactions involving telephone calls, this information is
carried in the Phone (T31) records.
relevant to the Phone details.
REFERENCE DATA– Type 99
The Reference Data record type contains information on reference data that an application might use. This
record type is intended for the advanced user of the application, and can be structured to meet individual
business needs. Reference data can be carried for various types of information such as airline, country,
commodity, or other. Please contact your Visa representative for additional details as to how this reference
data can be utilized.
Reference data (99)

FORMAT SOURCE

Change, transaction
transaction.
For Add/Change:
4.
2 Reference Type 9(02) Identifies which reference Values:
data is being updated
1 = Airline
2 = Airport
3 = Commodity Code
4 = Country
5 = Currency
6 = Fleet Product
7 = MCC
8 = State/Province Code
For Add/Change:
value.
3 Key Field X(10) Identifies the Key field of For Add/Change:
the reference data.
• Required.
• Must be a valid format for the
type.
4 Description 1 X(50) Identifies optional field For Add/Change:
of the reference data.
• Not required.
• Not required.
Reference data (99)

FORMAT SOURCE

• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
• Not required.
19 Inactive Flag 9(01) Specifies whether this Values:
reference data code is
0 = Code is still active
obsolete or valid.
1 = Code is inactive
For Add/Change:
value.
• If not provided, 0 is implied.
20 Effective Date X(24) Date that this reference For Add/Change:
information is effective.
• Required.
Reference Data (T99) Summary Notes:
This record type is intended for the advanced user who wants to provide and report on enhanced detail
information with respect to reference data. Its use should be restricted to those situations, and is intended
for future use.
Appendix A: Changes from VCF 3.0 to VCF 4.0
The upgrade from VCF 3.0 to 4.0 expands Visa’s Enhanced Data capabilities. The following table
summarizes all data format changes from VCF 3.0 (InfoSpan 3.0 Format) to VCF 4.0. Besides changes to
existing fields, most record types include new fields. Eight new record types were also added. These changes
are summarized in the table below. Changes incorporated into the VCF 4.0 specification to bring it to
its current revision of 4.3 are found following this table.
One change affects almost all record types: the format of the Account Number field has changed from 9(19)
to X(19). Although the 16-digit card account must still be numeric, this change allows more flexibility for
populating the remaining 3 positions in the field. Account number fields using less than 19 positions and
using field padding should left justify and pad spaces to the right. Account numbers in VCF should never
use zeros for padding.
Revisions to Data Formats in Visa Commercial Format 4.0

RECORD TYPE FIELD CHANGE
(1) Account Balance (2) Account Number Changed format from 9(19) to X(19)
(9) Past Due Count Added one new value (6 = 6 Billing
cycles) and changed value 5 definition to
“5 Billing Cycles” in the edit criteria
(17) Amount Past Due Five Billing Cycles has been renamed
from Past Due four Plus Cycles Amount
(18) – (35) Added non-required fields
(2) Car Rental Summary (2) Account Number Changed format from 9(19) to X(19)
(32) Supplier Postal Code Changed format from X(10) to X(14)
(3) Card Account (3) Account Number Changed format from 9(19) to X(19)
(9) Card Type Has four new values (4, 5, 6, 7) and one
definition change (3 = Business Credit
instead of Small Business)
(15) Billing Account Number Changed format from 9(19) to X(19)
(4) Cardholder (12) Postal Code Changed format from X(10) to X(14)
(19) E-mail Address Changed format from X(254) to X(128)
(5) Card Transaction (2) Account Number Changed format from 9(19) to X(19)
(32) Customer Code/CRI Now represents the true Customer
Code/CRI
(33) Purchase ID Now represents the true Purchase ID
(37) Order Type Code Has a new value (9) in the edit criteria
(40) – (76) Added fields
(6) Company (9) Postal Code Changed format from X(10) to X(14)
(12) Card Type Has four new values (4, 5, 6, 7) and one
(7) Line Item Detail (2) Account Number Changed format from 9(19) to X(19)
(8) Line Item Summary (2) Account Number Changed format from 9(19) to X(19)
(10) Destination Postal Code Changed format from X(10) to X(14)
(11) Source Postal Code Changed format from X(10) to X(14)
(9) Lodging Summary (2) Account Number Changed format from 9(19) to X(19)
(9), (11), (12), (13), (14), These field names have had “Total”
(15), (16), (17), (18), (19), added
and (20)
(24) Lodging Nights Changed format from 9(02) to 9(03)
(10) Organization (21) Contact Postal Code Changed format from X(10) to X(14)
(24) Contact E-mail Address Changed format from X(254) to X(140)
(11) Period (4) Card Type Has four new values (4, 5, 6, 7) and one
(14) Passenger Itinerary (2) Account Number Changed format from 9(19) to X(19)
(15) Leg-Specific (2) Account Number Changed format from 9(19) to X(19)
Information
(12) Stopover Code Definitions have been revised in the edit
criteria
(16) Supplier (4) Supplier City Changed format from X(13) to X(14)
(5) Supplier State/Province Changed format from X(03) to X(04)

Code
(6) Supplier ISO Country Code Changed format from 9(03) to 9(05)
(7) Supplier Postal Code Changed format from 9(09) to X(14)
(9) Supplier Address Description has been added
(10) Merchant Profile Service Name has been changed from Visa
Identifier (MPS-ID) Supplier Identification Number
(13) Mailing Address Changed format from X(62) to X(30)
(22) Sole Proprietor Owner Changed format from X(01) to X(02)
Middle Initial
(28) TIN Type Code Changed format from X(01) to 9(01)
(30) Supplier Fax Number Changed format from 9(15) to X(15)
(31) Supplier Reservation Changed format from 9(15) to X(15)
Phone Number
(37) Alternate Supplier Postal Changed format from X(09) to X(14)
Code
(41) 8A Expiration Date Changed format from 9(10) to 9(08)
(47) Incorporation Status Changed format from X(08) to 9(08)
Change Date
(17) Fleet Service (2) Account Number Changed format from 9(19) to X(19)
(20) Fuel Miscellaneous Tax Changed format from X(01) to 9(01)
Exemption Indicator
(18) Fleet Product (2) Account Number Changed format from 9(19) to X(19)
(6) Product Sequence Number Changed the edit criteria to accept values
from 01 to 99 instead of 01 to 08
(7) Product Code Changed format from X(04) to X(02)
(20) Temporary Services (2) Account Number Changed format from 9(19) to X(19)
(10) Account Code/Cost Changed format from X(17) to X(18)
Center
(11) Description Changed format from X(25) to X(26)
(12) Employee/Temp Name Changed format from X(26) to X(26)
(22) Requester Name or ID Changed format from X(15) to X(16)
(26) Supervisor/Reported To Changed format from X(25) to X(26)
(29) Reimbursement Attribute Changed format from X(01) to X(02)

(21) Shipping Services (2) Account Number Changed format from 9(19) to X(19)
(8) Shipping/Courier Name Changed format from X(25) to X(26)
(11) Origin Zip code Changed format from X(09) to X(14)
(12) Origin Country Code Changed format from X(03) to 9(05)
(13) Destination Zip Code Changed format from 9(09) to X(14)
(14) Destination Country Code Changed format from X(03) to 9(05)
(23) Origin Sender Changed format from X(25) to X(26)
(25) Destination Receiver Changed format from X(25) to X(26)
Name
(25) Headquarter Added record type
Relationship
(26) Lodging Detail Added record type
(27) Car Rental Detail Added record type
(28) Allocation Added record type
(29) Allocation Description Added record type
(30) Relationship Added record type
(31) Phone Added record type
(99) Reference Data Added record type
Header/Trailer (Log) (5) Record Type code Has new values in the edit criteria to
support the new record types.
(8) Load File Format Must be 4.0 when producing a VCF 4.0
file layout
(9) – (12) Added required fields
Differences between VCF 4.0 Revision 1 and Revision 2

The primary focus of the modifications to the VCF 4.0 specification was the addition of explanatory
information about the structuring of a VCF 4.0 transaction file and its structural components. The manual
was also separated into a Basic Record Types section and an Enhanced Record Types section for ease of
understanding. The descriptions of fields within each record type were clarified, and, in some cases, notes
describing the field’s applicability (or non-applicability) to a specific Region were added. Clearer notations
were made about the primary key field(s) for each record type.
Additional supporting materials included in this new release are:
o Terminology and Key Concept sections
o Explanatory detail on billing periods and the use of individual accounts versus billing accounts, as
well as ramifications for the VCF transaction file structure
o Enhanced information on structural hierarchies
o Information on the use of dual currency in the Latin America and Caribbean region
o Additional information concerning the building of a VCF 4.0 transaction file and the differences
between Starter Data, Financial Data, and Enhanced Data.
o Expanded description of the VCF 4.0 file organization and structure
o Supplemental information on VCF 4.0 file certification and the processes required to successfully
complete a certification
o Additional detail on the meaning and use of the Header/Trailer Sequence Number
o Descriptive information on the system processes necessary to produce VCF 4.0 transaction files
o Definitions of VCF file formats and delimiters, including formatting examples
o Summary Notes following each Record Type discussing key fields and key concepts to be noted in
records of that specific record type
o Information on the use of the Item Sequence Number field and a description of its use
o An Appendix detailing Visa’s multi-byte capabilities
o An Appendix describing Visa Europe’s data requirements
o A chart detailing where each VCF 4.0 field is found within the set of VCF 4.0 record types
o An Appendix clarifying the referential integrity of a VCF 4.0 transaction file
o Supplementary clarifying information on the use of the VAT- and tax-related fields in the Card
Transaction Record Type (T5)
Differences between VCF 4.0 Revision 2 and Revision 3

There is one modification for Revision 3. Effective with the April 2009 VisaNet Business Enhancements
release, Visa Fleet fuel product codes were modified to align with the industry standard published by the
Petroleum Convenience Alliance for Technology Standards (PCATS). This new fuel product code list is
under record type Fleet Service (17), number 7, field name Fuel Type.
Appendix B: VCF Data Fields / VCF Records
Basic Records Enhanced Records
VCF 4.0 T1 T3 T4 T5 T6 T10 T11 T2 T7 T8 T9 T14 T15 T16 T17 T18 T20 T21 T25 T26 T27 T28 T29 T30 T31 T99
8A Classification Indicator X
8A Expiration Date X
Account Close Date X
Account Code/Cost Center X
Account Number X X X X X X X X X X X X X X X X X X
Account Open Date X
Account Type Flag X
Acquirer BIN X
Acquiring BIN X X
Address Line 1 X
Address Line 2 X X
Address Line 3 X X
Allocated Amount X
Allocated Date X
Allocated Percentage X
Allocation Accounting Code X
Allocation Sequence Number X X
Alternate Supplier City X
Alternate supplier Country X
Alternate Supplier DBA Name X
Alternate Supplier Postal
X
Code
Alternate Supplier
X
State/Province Code
Amount Past Due Five Billing
X
Cycles
Amount Past Due Four Billing
X
Cycles
Amount Past Due One Billing
X
Cycle
Amount Past Due Plus Billing
X
Cycles
Amount Past Due Six Billing
X
Cycles
Amount Past Due Three
X
Billing Cycles
Amount Past Due Two Billing
X
Cycles
Annual Fee Flag X
Annual Fee Month X
Arrival Date X
Arrival Time X
Austin-Tetra Number X
Authorization Number X
Authorized User 1 X
Authorized User 2 X
Authorized User 3 X
Auto Towing X X
Billing Account Number X X
Billing Amount X
Billing Currency Code X X
Business Center Charges X
Business Legal Name X
Call From City X
Call From Country X
Call From Number X
Call From State/Province
X
Code
Call to City X
Call To Country X
Call To Number X
Call To State/Province X
Call Type X
Calling Card/Phone Type X
Card Acceptor ID X
Card Expire Date X
Card Receipt Verification Flag X
Card Type X X X
Cardholder Identification X X
Cardholder Transaction
X
Approval
Carrier Code X
Carrier Reference Number X
Cash Limit Amount X
Charge-Off Amount X
Charge-Off Date X
Check In Date X
Check Indicator X
Check-out date X
City X X
City Fuel Sales Tax Amount X
City Fuel Sales Tax
X
Exemption Indicator
City Motor Fuel Tax Amount X
City Motor Fuel Tax
X
Exemption Indicator
City Pair Program Indicator X
Class Code X
Close Date X
Closing Date X
Commodity Code X X
Company Identification X X X X X
Company Name X
Conjunction Ticket Number X
Connection Time X
Contact Address Line 1 X
Contact City X
Contact Country Code X
Contact E-mail address X
Contact Fax Number X
Contact First Name X
Contact Last Name X
Contact Phone Number X
Contact Postal Code X
Contact State/Province Code X
Corporate Identification X
Corporation Payment Indicator X
Cost Center X X
Cost Center Code X
Cost Center Description X
County Fuel Sales Tax
X
Amount
County Fuel Sales Tax
X
Exemption Indicator
County Motor Fuel Tax
X
Amount
County Motor Fuel Tax
X
Exemption Indicator
Coupon Number X
Credit Limit X
Credit Rating X
Credit Rating Date X
Current Amount Due X
Current Balance X
Customer Code / CRI X
Customer Reference Number X
Customer VAT Number X
Daily Rental Rate X X
Daily Room Rate X
Date of Charge X
Date of travel X
Days Rented X
DDA Number X
DDA Savings Number X
Departure Date X
Departure Tax X
Departure Time X
Description X X X X
Description 1 X
Description 10 X
Description 11 X
Description 12 X
Description 13 X
Description 14 X
Description 15 X
Description 2 X
Description 3 X
Description 4 X
Description 5 X
Description 6 X
Description 7 X
Description 8 X
Description 9 X
Description of Other Charge X
Destination Address X
Destination Country Code X X
Destination Postal Code X
Destination Receiver Name X
Destination State/Province X
Destination State/Province
X
Code
Destination Zip Code X
Destination/Airport Code X
Disabled X
Disabled Veteran Indicator X
Discount Amount X X X X
Discount rate X
Dispute Amount X
Dispute Date X
Dispute Reason Code X
Dispute Status Code X
Disputed Amount X
Domestic/International
X
Indicator
DOT Disadvantaged Business
X
Enterprise
Dun & Bradstreet Number X
Duration X
Duty Amount X
Effective Date X X X X X
E-mail Address X
Emboss Line 1 X
Emboss Line 2 X
Employee Count X
Employee ID X
Employee/Temp Name X
Employee/Temp Social
X
Security Number
End Date X X
Endorsement/ Restrictions X
Enriched Transaction Flag X
E-Ticket Indicator X
Exchange Ticket Amount X
Exchange Ticket Number X
Extra Charge Code X X
Extract ID X
Extra-Mileage Charges X X
Fare Basis X
Fax Number X
Federal Organization Indicator X
Federal Sales Tax Amount X
Federal Sales Tax Exemption
X
Indicator
Field Value X
Final Allocation Flag X
First Name X
Fiscal Year Date X
Fleet Service Indicator X
Folio Cash Advances X
Food/Beverage Charges X
Franchise code X
Freight Amount X
Freight/Shipping VAT/Tax
X
Amount
Freight/Shipping VAT/Tax
X
Rate
Fuel Charges X
Fuel Federal Excise Tax
X
Amount
Fuel Federal Excise Tax
X
Exemption Indicator
Fuel Gross Amount X
Fuel Miscellaneous Tax
X
Amount
Fuel Miscellaneous Tax
X
Exemption Indicator
Fuel Net Amount X
Fuel Quantity X
Fuel Type X
Fuel Unit Cost X
Fuel Unit of Measure Code X
G/L Sub-account X X
G/L Sub-account Description X
G/L Sub-account Number X
Gift Shop Purchases X
Health Club Charges X X
Hierarchy Node X X X
High Balance X
Historically Black College /
X
Univ - Minority Institution
Home Phone Number X
HQ Identification X
HQ Name X
HUB Zone Indicator X
Inactive Flag X
Incorporation Status Change
X
Date
Incorporation Status Code X
Insurance Charges X X
Internet Indicator X
ISO Country Code X X
Issuer BIN X
Issuer Identification X
Issuer Name X
Issuer-Defined Usage Code X
Item Commodity Code X
Item Descriptor X
Item Discount Amount X
Item Level Usage Code X
Item Product Code X
Item Sequence Number X X X X X X
Item Total Amount X
Job Code X
Key Field X
Last Credit Limit Change Date X
Last Item Indicator X
Last Maintenance Date NAR X
Last Name X
Last Payment Amount X
Last Payment Date X
Last Revision Date X
Late Return Charges/Hourly
X
Rate
Laundry charges X
Lead Bank Flag X
Leg Number X
Level 3 Tier 1 Indicator X
Level II Capture Indicator
X
Code
Level III Capture Indicator
X
Code
Line Item Matched Indicator X
Line Item Sales Tax Charged
X
Flag
Line Item Source X
Load Transaction Code X X X X X X X X X X X X X X X X X X X X X X X X X X
Lodging Nights X
Lost/Stolen Date X
Mail Stop X
Mailing Address X
Mailing City X
Mailing Country X
Mailing State/Province X
Manager First Name X
Manager Last Name X
Manager Phone Number X
Manager Title X
Manager Training Date X
Matched Indicator X
Memo Post Flag X
Merchant Category Code X X X X X X X X X X
Merchant Profile Service
X
Identifier
Merchant Profile Service
X
Identifier (MPS-ID)
Merchant Type X
Message Identifier X X X X X X X X X X X X
Middle Name X
Mini-bar charges X
Minority Owned Status Code X
Miscellaneous Expense
X
Amount
Miscellaneous Expense
X
Indicator
Miscellaneous Field 1 X
Miscellaneous Field 1
X
Description
Miscellaneous Field 2 X
Miscellaneous Field 2
X
Description
Movie charges X
Net Amount X
No Show Indicator X X
Non-Fuel Federal Excise Tax
X
Amount
Non-Fuel Federal Excise Tax
X
Exemption Indicator
Non-Fuel Gross Amount X
Non-Fuel Miscellaneous Tax
X
Amount
Non-Fuel Miscellaneous Tax
X
Exemption Indicator
Non-Fuel Net Amount X
Non-Fuel State and Local
X
Sales Tax Amount
Non-Fuel State and Local
X
Sales Tax Exemption Indicator
Non-Profit Entity X
Number of Legs X
Number of Packages X
Object Type X
Odometer Reading X
One-way Drop-off charges X
Optional Field 1 X X X X X X X X X X X X X X X X X X X X X X X X X X
Order Date X
Order Type Code X
Organization Hierarchy
X
Management Indicator
Origin Address X
Origin Country Code X
Origin Sender Name X
Origin State/Province Code X
Origin Zip Code X
Original Accounting Code X
Origination Airport/Railroad
X
Code
Other Charge X X
Other Charge Code X
Other Charges X
Overtime Hours Worked X
Overtime Rate X
Parent Field Value X
Parent Hierarchy Node X
Parent Object Type X
Parent Tree ID X
Parent Visa Supplier
X
Identification Number
Passenger Name X
Passenger Specific Data X
Past Due Amount X
Past Due Count X
Past Due Cycles Count X
Past Due Five Billing Cycles
X
Count
Past Due Four Billing Cycles
X
Count
Past Due One Billing Cycle
X
Count
Past Due Plus Billing Cycles
X
Count
Past Due Six Billing Cycles
X
Count
Past Due Three Billing Cycles
X
Count
Past Due Two Billing Cycles
X
Count
Patriot Act Excluded Party List
X
Indicator
Payment Due Date X
Period X X X
Period Complete Indicator X
Phone Number X
Pickup Date X
Postal Code X X
Posting date X X X X X X X X X X X X X X X X X
Pre-funded Indicator X
Previous Balance X
Primary NAICS code X
Primary Standard Industrial
X
Classification Code (SIC)
Processing Date X
Processor Addendum Key X X X X X X X X X X
Processor Identification X
Product Code X
Product Sequence Number X
Purchase ID X X X X X X X X X
Purchase Identification X
Purchase Identification Format X
Purchase Type X
Quantity X
Rate X
Rate Indicator X
Rate Period X
Reason Status Code X
Reference Type X
Regular Hours Worked X
Regular Mileage Charges X
Reimbursement Attribute X X
Renter Name X
Reporting Currency Code X
Requester Name or ID X
Reserved Field X
Reserved for future use X
Return Location X
Room Rate X
Room Tax 2 Amount X
Room Tax 3 Amount X
Room Tax 4 Amount X
Room Tax Amount X
Routing Number X
Sales Tax Amount X
Sales Volume X
SBA Participant Indicator X
Second hierarchy node
X
representation
Secondary NAICS code X
Secondary Standard Industrial
X
Classification Code (SIC)
Secondary State Fuel Tax
X
Amount
Secondary State Fuel Tax
X
Exemption Indicator
Sequence Number X X X X X X X X X X X X X X X X
Service Class X
Service Description X
Service Disabled Veteran
X
Owned Small Business
Service Identifier X X
Service Type X
Shipping/Courier Name X
Small Disadvantaged
X
Business Indicator
Sole Proprietor Owner First
X
Name
Sole Proprietor Owner Last
X
Name
Sole Proprietor Owner Middle
X
Initial
Source X X
Source Amount X X X X X X X X X
Source Country Code X
Source Currency Code X X
Source Postal Code X
Spending Limit X X
SSN Other ID X
Start Date X X X
State Motor Fuel Tax Amount X
State Motor Fuel Tax
X
Exemption Indicator
State/Province Code X X
Statement Date X
Statement Type X
Status Code X
Status Date X
Stopover Code X
Subtotal Amount X
Supervisor/Reported To X
Supplier Address X
Supplier City X X
Supplier Email Address X
Supplier Fax Number X
Supplier Information Refusal
X
Indicator
Supplier ISO Country Code X X
Supplier Name X X X X X X X X X X
Supplier Order Number X
Supplier Out of Business Date X
Supplier Ownership Change
X
Date
Supplier Phone Number X
Supplier Postal Code X X X X X X X X X X
Supplier Reservation Phone
X
Number
Supplier State/Province Code X X
Supplier VAT Number X
Task Order Number X X
Tax 1 Amount X
Tax 2 Amount X
Tax 2 Amount Included Code X
Tax Amount X X X
Tax Amount Included Code X
Tax Identification Number
X
(TIN)
Tax2 Amount X
Taxpayer Name X
TCN Passenger Name X
Telephone Charges X X X
Third hierarchy node
X
representation
Ticket Indicator X
Ticket Issue Date X
Ticket Number X
Time Sheet Number X
TIN Match Indicator X
TIN Type Code X
Total Business Center
X
Charges
Total Fare Amount X
Total Fee Amount X
Total Folio Cash Advances X
Total Food/Beverage Charges X
Total Gift Shop Purchases X
Total Laundry Charges X
Total Mini-bar Charges X
Total Movie Charges X
Total Non-Room Charges X
Total Other Charges X
Total Prepaid Expenses X
Total Room Tax Amount X
Total Tax Amount X X
Total Tax/VAT X
Total Telephone Charges X
Total Valet Parking Charges X
Tracking Number X
Training Date X
Transaction Cycle Limit X
Transaction Daily Limit X
Transaction Date X X X X X X X X X
Transaction Reference
X X X X X X X X X X X X X X X X
Number
Transaction Spending Limit X
Transaction Time X
Transaction Type Code X
Transfer Account Number X
Travel Agency Code X
Travel Agency Name X
Travel Obligation Number X
Tree ID X X
Type Supply X
Unit Cost X
Unit Measure X X
Usage Code X
User Data 1 X
User Data 1 description X
User Data 2 X
User Data 3 X
User Data 4 X
User Data 5 X
Valet Parking Charges X
VAT / Tax Rate X X
VAT Amount X
VAT Reference Number X
VAT/Tax Amount X
Vehicle ID X
Veteran Indicator X
Veteran Owned Small
X
Business
Vietnam Era Veteran Indicator X
Visa Commerce Buyer ID X
Visa Commerce Batch ID X
Visa Commerce Seller ID X
Vise Commerce Payment
X
Instruction Date
Weekly Rental Rate X
Weight X
Woman Owned Small
X
Business
Women Owned Indicator X
Appendix C: Record Types and Relationships
The fields listed

beneath each
record are the key
fields for that
record.
Arrows show
dependencies: A
box (Record Type)
above and pointing
to another box
(Record Type)
must be created
before the box it
points to.
The enhanced record types are dependent on the Card Transaction Record (T5), which must be loaded prior
to the enhanced data associated with it. That representation is found in the figure below:
Appendix D: Visa Europe Data Requirements
The table in this section lists the fields that are of use for Visa Europe Regions originating Visa Purchasing
transactions. If you have any questions regarding this section, and are a Visa member or financial
institution, please contact Visa Europe at your country specific number, or e-mail us at
[email protected]
Record No Field Proposed Source Comments

Type Name Content
5 67 VAT E or N or Issuer VAT reporting decision Defines whether transaction is VAT Evidence [E];
status flag X process Not VAT Evidence (failed validation) [N] or Not
from a VP VAT capable merchant [X]
5 69 Optional VGIS – Contains VGIS element Ref NCT

Field 1 InvoiceSummary\ActualPaym
ent\Ref”NCT”
5 70 Optional SVAT / LID – TC50 PurchA Norway VAT requirement – Delivery address
Field 2 (100-114)
5 71 Optional SVAT / LID – TC50 PurchA Norway VAT requirement – Delivery postcode
Field 3 (77-86)
5 72 Optional VGIS – Invoice Currency Code

Field 4 InvoiceHeader\Currency
5 73 Reserved GIL, GLL, VGIS – Tax Treatment

Field NIL, NLL, InvoiceHeader\TaxTreatment
NON
5 74 Reserved Not Evidence Reason Where transaction is Not Evidence (Record Type 5
Field Field 67 = N) provide narrative reason
5 75 Reserved SVAT / LID – TC50 PurchA Netherlands VAT requirement – Supplier Post
Field (87-96) Code
5 76 Reserved SVAT / LID – TC50 PurchA Netherlands VAT requirement – Supplier Street
Field (100-114) number
7 31 Optional VGIS – Line level customer specified reference / PO Line

Field 1 InvoiceDetails\POLineNum number. Additional to Item Product Code
7 32 Optional VGIS – Line Level Percent Discount

Field 2 InvoiceDetails\LineDiscountI
nfo\DiscountPercent
8 13 VAT N/A Must not be used for Supplier Invoice Number

Reference
Number
Appendix E: VCF 4.0 Multi-Byte Capabilities
Visa supports processing of VCF 4.0 variable length tab-delimited inbound in multi-byte characters
(Simplified Chinese or Traditional Chinese only). The inbound file will be validated, loaded and processed to
generate and deliver a VCF 4.0 tab-delimited outbound.
The table in this section lists the fields that support multi-byte data in BIG5 (for Traditional Chinese),
GB2312 (for Simplified Chinese) and UTF-8 character sets. Please note that field-length is in number of
bytes. Since one multi-byte character can take more than one byte, actual number of characters that fit into a
particular field will be less than the field-length specified in number of bytes. Any overflow characters will
be truncated to fit into specified field-length.
Multi-byte Table
Field Byte
Record # VCF Field Name Length Comments
T1 - Account
Balance 32 OPTIONAL FIELD 1 X(26)
33 OPTIONAL FIELD 2 X(26)
T2 - Car Rental TRANSACTION

Summary 4 REFERENCE NUMBER X(24)
15 RENTER NAME X(40)
20 RETURN LOCATION X(26)
CORPORATE
23 IDENTIFICATION X(16)
An identifying field used to link draft

data with related TC50 text message
26 MESSAGE IDENTIFIER X(16) transactions
Number assigned by the merchant to

the transaction. May be car rental
27 PURCHASE ID X(50) agreement number.
31 SUPPLIER NAME X(26)
32 SUPPLIER POSTAL CODE X(14)
Value used to link the T5 to this record.

PROCESSOR ADDENDUM If present, this field will be used for
33 KEY X(52) matching.
Field Byte
T2 - Car Rental
Summary 34 OPTIONAL FIELD 1 X(26)
T3 - Card Account 4 HIERARCHY NODE X(40)
16 COST CENTER X(50)
17 G/L SUB ACCOUNT CODE X(76)
26 TASK ORDER NUMBER X(26)
40 EMBOSS LINE 1 X(50)
41 EMBOSS LINE 2 X(50)
47 OPTIONAL FIELD 4 X(26) .
T4 - Cardholder 4 HIERARCHY NODE X(40)
5 FIRST NAME X(20)
6 LAST NAME X(20)
7 ADDRESS LINE 1 X(40)
9 CITY X(20)
12 POSTAL CODE X(14)
Field Byte
T4 - Cardholder 14 MAIL STOP X(14)
15 PHONE NUMBER X(14)
16 FAX NUMBER X(14)
17 SSN OTHER ID X(20)
19 E-MAIL ADDRESS X(128)
20 AUTHORIZED USER 1 X(26)
23 EMPLOYEE ID X(10)
24 HOME PHONE NUMBER X(14)
25 MIDDLE NAME X(30)
26 VISA COMMERCE BUYER ID X(19)
27 VEHICLE ID X(20)
28 MISCELLANEOUS FIELD 1 X(16)
MISCELLANEOUS FIELD 1
29 DESCRIPTION X(26)
30 MISCELLANEOUS FIELD 2 X(16)
MISCELLANEOUS FIELD 2
T5 - Card TRANSACTION
Transaction 4 REFERENCE NUMBER X(24)
8 CARD ACCEPTOR ID X(26)
Field Byte
T5 - Card
Transaction 9 SUPPLIER NAME X(26)
10 SUPPLIER CITY X(14)
26 SUPPLIER VAT NUMBER X(20)
27 SUPPLIER ORDER NUMBER X(25)
28 CUSTOMER VAT NUMBER X(14)
32 CUST CODE/CRI X(50)
33 PURCHASE ID X(76)


54 USER DATA 1 X(20)
USER DATA 1
USER DATA 2
USER DATA 3
USER DATA 4
USER DATA 5
64 VISA COMMERCE BATCH ID X(20)
68 SOURCE X(10)
Field Byte
T5 - Card
Transaction 70 OPTIONAL FIELD 2 X(256)
73 RESERVED FIELD 1 X(30)
T6 - Company 3 COMPANY NAME X(80)
6 CITY X(20)
9 POSTAL CODE X(14)
13 ISSUER NAME X(40)
T7 - Line Item TRANSACTION


8 ITEM COMMODITY CODE X(16)
9 ITEM DESCRIPTOR X(26)
12 UNIT MEASURE X(12)
Field Byte
T7 - Line Item
Summary 19 ITEM PRODUCT CODE X(12)
the transaction. May be Supplier Order
21 PURCHASE ID X(50) number.

30 LINE ITEM SOURCE X(10)
T8 - Line Item TRANSACTION

Detail 4 REFERENCE NUMBER X(24)
DESTINATION POSTAL
10 CODE X(14)
11 SOURCE POSTAL CODE X(14)
13 VAT REFERENCE NUMBER X(16)

the transaction. May be Supplier Order

28 SOURCE X(10)
Field Byte
T8 - Line Item
Detail 30 OPTIONAL FIELD 2 X(26)
T9 - Lodging TRANSACTION


27 PURCHASE ID X(50) the transaction. May be Folio number.

T10 - Organization 3 HIERARCHY NODE X(40)
4 PARENT HIERARCHY NODE X(40)
6 DESCRIPTION X(40)
7 MANAGER FIRST NAME X(20)
8 MANAGER LAST NAME X(20)
9 MANAGER TITLE X(40)
11 MANAGER PHONE NUMBER X(14)
12 TASK ORDER NUMBER X(26)
Field Byte
T10 - Organization 13 CONTACT FIRST NAME X(20)
14 CONTACT LAST NAME X(20)
15 CONTACT ADDRESS LINE 1 X(40)
18 CONTACT CITY X(20)
21 CONTACT POSTAL CODE X(14)
22 CONTACT PHONE NUMBER X(16)
23 CONTACT FAX NUMBER X(16)
CONTACT E-MAIL
24 ADDRESS X(140)
SECOND HIERARCHY
25 NODE REPRESENTATION X(56)
THIRD HIERARCHY NODE

26 REPRESENTATION X(56)
28 COST CENTER X(50)
29 G/L SUBACCOUNT X(76)
T11 - Period 8 OPTIONAL FIELD 1 X(26)
Field Byte
T14 - Passenger TRANSACTION

Itinerary 4 REFERENCE NUMBER X(24)
8 TRAVEL AGENCY NAME X(26)
10 TICKET NUMBER X(14)

PASSENGER SPECIFIC
11 DATA X(20)
EXCHANGE TICKET
12 NUMBER X(14)
ENDORSEMENT
19 RESTRICTIONS X(20)
the transaction. May be used for
20 PURCHASE ID X(50) matching.

PASSENGER SPECIFIC
27 DATA X(50)
TRAVEL OBLIGATION
35 NUMBER X(13)
36 TCN PASSENGER NAME X(50)
T15 - Leg-specific TRANSACTION

Information 4 REFERENCE NUMBER X(24)
10 FARE BASIS X(08)

CARRIER REFERENCE
14 NUMBER X(06)
Field Byte
T15 - Leg-specific CONJUNCTION TICKET

Information 18 NUMBER X(14)

the transaction. May be used for
20 PURCHASE ID X(50) matching.

T16 - Supplier 3 SUPPLIER NAME X(30)
4 SUPPLIER CITY X(14)
9 SUPPLIER ADDRESS X(30)
11 BUSINESS LEGAL NAME X(30)
ALTERNATE SUPPLIER DBA

12 NAME X(30)
13 MAILING ADDRESS X(30)
20 SUPPLIER PHONE NUMBER X(15)
SOLE PROPRIETOR
21 OWNER FIRST NAME X(25)
This field is only 2 bytes long and in

most instances cannot hold any
multibyte data. If the first multibyte
character for owner middle initial in the
inbound file takes more than 2 bytes,
then only a "blank" will appear in this
SOLE PROPRIETOR field in database as well as in the
22 OWNER MIDDLE NAME X(02) outbound file.
Field Byte
SOLE PROPRIETOR
T16 - Supplier 23 OWNER LAST NAME X(25)
SUPPLIER E-MAIL
29 ADDRESS X(40)
30 SUPPLIER FAX NUMBER X(15)

SUPPLIER RESERVATION
31 PHONE NUMBER X(15)
ALTERNATE SUPPLIER
35 CITY X(15)
ALTERNATE SUPPLIER
37 POSTAL CODE X(14)
49 MAILING ADDRESS X(20)

VISA COMMERCE SELLER
57 ID X(19)
RESERVED FOR FUTURE
58 USE X(12)
73 TAXPAYER NAME X(40)
TRANSACTION
T17 - Fleet Service 4 REFERENCE NUMBER X(24)
15 ODOMETER READING X(08)

Field Byte

the transaction. May be supplier order
T17 - Fleet Service 43 PURCHASE ID X(50) number.

T18 - Fleet TRANSACTION

Product 4 REFERENCE NUMBER X(24)


the transaction. May be supplier order

T20 - Temporary TRANSACTION

Services 4 REFERENCE NUMBER X(24)
Field Byte
T20 - Temporary An identifying field used to link draft

Services 7 MESSAGE IDENTIFIER X(15) transactions
ACCOUNT CODE/COST
10 CENTRE X(18)
12 EMPLOYEE/TEMP NAME X(26)
19 JOB CODE X(12)
22 REQUESTOR NAME OR ID X(16)
SUPERVISOR/REPORTED
26 TO X(26)
28 COMMODITY CODE X(12)
T21 - Shipping TRANSACTION

Services 4 REFERENCE NUMBER X(24)

8 SHIPPING/COURIER NAME X(26)
9 TRACKING NUMBER X(22)
11 ORIGIN ZIP CODE X(14)
13 DESTINATION ZIP CODE X(14)
CUSTOMER REFERENCE
15 NUMBER X(17)
20 SERVICE DESCRIPTION X(24)
23 ORIGIN SENDER NAME X(26)
24 ORIGIN ADDRESS X(20)
Field Byte
T21 - Shipping DESTINATION RECEIVER

Services 25 NAME X(26)
26 DESTINATION ADDRESS X(20)
T25 - Headquarter
Relationship 6 HQ NAME X(80)
T26 - Lodging TRANSACTION

DESCRIPTION OF OTHER
25 CHARGE X(20)


28 PURCHASE ID X(50) the transaction. May be Folio number.

Field Byte
T27 -Car Rental TRANSACTION

TRANSACTION
T28 - Allocation 4 REFERENCE NUMBER X(24)
G/L SUB-ACCOUNT
7 NUMBER X(76)
G/L SUB-ACCOUNT
8 NUMBER DESCRIPTION X(50)
9 COST CENTRE CODE X(76)
COST CENTRE
ALLOCATION ACCOUNTING
18 CODE X(150)
ORIGINAL ACCOUNTING
19 CODE X(150)
T29 - Allocation TRANSACTION

Description 4 REFERENCE NUMBER X(24)
Field Byte
T29 - Allocation
Description 11 OPTIONAL FIELD 3 X(26)
T30 - Relationship 3 FIELD VALUE X(40)
6 PARENT FIELD VALUE X(40)
TRANSACTION
T31 - Phone 4 REFERENCE NUMBER X(24)
7 CALL TO CITY X(14)
11 CALL FROM CITY X(14)
INDEX
A E
Account Balance record type, 31 Effective Date, 9, 41, 51, 78, 83, 84, 87, 90, 96, 97, 200, 206
Account Number, 10, 25, 27, 31, 37, 39, 40, 43, 44, 50, 51, 58, 59, 78, 102, 108, 113, End Date, 10, 20, 25, 32, 82, 94, 96, 172
114, 119, 120, 126, 127, 133, 134, 140, 152, 165, 166, 171, 175, 176, 180, 184, Enhanced Data, 6
189, 190, 192, 193, 196, 197, 198, 201, 204, 208, 209, 210, 211 Enhanced Data Record Types, 101
Additional References, 23
Allocation Description record type, 197
Allocation record type, 193
F
Field, 8
B field format, 26
Financial records, 14
Basic Record Types, 30 Financials Process, 24
Billing Account, 11, 12, 13, 32, 33, 38, 43, 44, 52, 73, 208 Fleet Product record type, 166
Billing Cycles, 12, 14, 34, 35, 36, 208 Fleet Service record type, 152
Block, 8, 18, 20, 25, 97, 99 Formatting examples, 27
C G
Car Rental Detail record type, 190 General data requirements, 20
Car Rental Summary record type, 102
Card Account record type, 39
Card Transaction record type, 58
H
Card Type, 42, 51, 82, 84, 92, 93, 94, 95, 96, 208, 209 Header / Trailer Sequence Number, 19
Cardholder Identification, 8, 39, 40, 51, 53, 54, 56, 57 header and trailer, 12, 19, 22, 30, 97, 99
Cardholder record type, 53 Headquarters Relationship record type, 181
Company ID, 8, 43, 53, 57, 80, 85, 92, 95, 97, 181 Hierarchy, 9, 40, 41, 51, 53, 54, 57, 58, 59, 83, 85, 86, 87, 89, 90, 199, 200
Company Identification, 8, 53, 80, 85, 92, 181 Hierarchy Node, 40, 41, 51, 53, 54, 57, 58, 59, 85, 86, 87, 89, 90, 199, 200
Company record type, 80
Corporation Payment Indicator, 43, 44, 52
Creating a Visa Commercial Format 4.0 Transaction File, 21
L
Cycle Process, 25 Leg-Specific Information record type, 134
Level I Data, 6
D Level II Data, 6
Level III Data, 7
Dual Currency, 13 Line Item Detail record type, 108
Line Item Summary record type, 114
Lodging Detail record type, 184
Lodging Information record type, 120, 127 Relationship record type, 199
M S
Monthly billing cycle, 14 Shipping Services record type, 176
Start Date, 10, 41, 51, 87, 90, 94, 96, 172, 182
Starter Process, 24
O Starter records, 14, 15
Organization record type, 85 Supplier record type, 141
System Processing Routines, 24
P
T
Passenger Itinerary record type, 127
Period, 10, 12, 13, 14, 20, 24, 30, 32, 37, 42, 51, 59, 60, 78, 84, 92, 93, 94, 95, 96, Temporary Services record type, 171
98, 203, 209
Period record type, 92 U
Phone record type, 201
Primary Key, 8, 21, 27, 31, 39, 53, 58, 80, 85, 92, 97, 108, 114, 120, 127, 134, 152, Upgrade from VCF 3.0 to 4.0, 208
166, 171, 176, 184, 201
V
R
VCF File Formats and Delimiters, 27
Record formats, 20
Record Type, 7
Reference Data record type, 205

Visa - Commercial - Format - 4 - 0 - Revision - 3 1

Uploaded by

Copyright:

Available Formats

Visa - Commercial - Format - 4 - 0 - Revision - 3 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Visa - Commercial - Format - 4 - 0 - Revision - 3 1

Uploaded by

Copyright:

Available Formats

Interface Specifications Guide

4.1 Minor clarifications and corrections

4.2 September Global Product Added supplemental processing

4.3 April 2009 Commercial Updated Fuel Types to be inline with

© 2009 Visa Inc. All rights reserved.

Visa Commercial Format

Understanding the Visa Commercial Format 4.0

Block Header / Block Trailer

End Date 3 = Start Date 4 – 1 day

Start Date 2 End Date 2 = Start Date 3 – 1 day

Dual Currency in the Latin America and Caribbean Region

Changing Information in VIS

Fundamentals of the VCF 4.0 File Structure

Architecture at the Record Group Level

Logical Sequence of the Groups

VCF File Types - US and International

Company data is sent to Visa on each company’s scheduled frequency, daily,

Õ Each company in a file represents a Transaction Set.

Õ All Blocks in a transaction set must belong to a single company

A Transaction Set is delimited by a header

Header / Trailer Sequence Number

Records and Data Requirements

General data requirements

• Numeric fields can only contain the ten digits (0 to 9).

Creating a Visa Commercial Format 4.0 Transaction File

Important Points to Remember:

For information about ISO 4217 Currency Codes, click on

Starter Process: This is triggered under the following situations:

• T6 Company record may be sent in any file.

Cycle Process: This is triggered under the following situations:

VCF File Formats and Delimiters

Variable length, Tab delimited files:

Examples of valid records for US Members

• Account Balance (T1)

• Card Account (T3)

• Card Transaction (T5)

The following requirements exist for the primary key values:

Account Balance (1)

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

1 Load Transaction 9(01) Code which determines Values:

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

3 Closing Date** 9(08) Closing Date of the Billing For Add/Change

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

25 Past Due Six 9(05) Number of times payment For Add/Change:

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

Account Balance (T1) Summary Notes:

The following requirements exist for the primary key values:

Card Account (3)

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

1 Load Transaction 9(01) Code which determines Values:

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

2 Cardholder X(20) Identification number For Add:

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

5 Effective Date 9(08) Represents the date when For Add:

NO. FIELD NAME FIELD DATA DESCRIPTION EDIT CRITERIA

7 Account Close 9(08) Date the Card Account For Add: