Posted Transaction File
A summary of all transactions which have posted for a given day.
This is a master file
This is the master transaction file. All transactions which posted in a given day will appear in this file. For certain transaction types, there are additional data points that are not included in this file. To get the additional data points you can match the
TransactionIdfound in this file with the sameTransactionIdin the extension files. For additional card transaction data, see the Card Transaction File. For additional ACH transaction data, see the ACH Transaction File
Posted Transaction File Definition
The Posted Transaction File is created by Helix on a daily basis. It has the following properties:
- Fixed-length
- ANSI encoded
- Line endings are Windows-style CarriageReturn + LineFeed (
\r\n, or0x0D0A) - File will be available in the relative directory of
/PostedTransaction - File name follows a specific, case-sensitive pattern of:
yyyyMMddhhmm_POSTEDTRANSACTION.TXT
Format Disclaimer
Helix reserves the right to append new field(s) to the end of any Header or Content line without notice. This is to allow new data points to be added as needed in a timely fashion.Implementation Note
Your code should be written such that unexpected characters after the "last" field but prior to the end of each line should be ignored. That is, if the file is documented as being 872 bytes per line, receiving a file with 984 bytes per line should not disrupt your processing. This applies to both Header and Content lines.File Name Disclaimer
The date in file name should be used as a guideline for human eyes only. Any date-related programmatic dependencies should rely on theFileCreatedDateorFileEffectiveDatecontained within the header line of each file, as these will be precise to the second and will be in the appropriate timezone.
Header Row
| Property | Data Type (Length) | Alignment | Start Position | Description |
|---|---|---|---|---|
RecordType | string (1) | Left | 1 | The flag for the header row. Will always be H. |
FileName | string (50) | Left | 2 | The name of this request file excluding path. Format: yyyyMMddhhmm_POSTEDTRANSACTION.TXTExample: 201410210215_POSTEDTRANSACTION.TXT |
RecordCount | integer (10) | Right | 52 | The number of records represented within the file. This field is zero-padded on the left side. Example: 0000000872 |
FileCreatedDate | datetime (34) | Left | 62 | The date the file was created. Follows same format as API. Example: 2014-10-20T10:30:31.456-05:00See data format guidelines |
FileEffectiveDate | datetime (34) | Left | 96 | The date to which the data in the file pertains. Follows same format as API. Example: 2014-10-20T23:59:59.999-05:00See data format guidelines |
Content Row
| Property | Data Type (Length) | Alignment | Start Position | Description |
|---|---|---|---|---|
CustomerId | integer (10) | Right | 1 | The Helix-assigned unique identifier for a customer. This field is zero-padded on the left side. Example: 0000000872 |
CustomerTag | string (50) | Left | 11 | The client-supplied unique identifier for the customer, aka the tag property on the customer object. This may be empty as it is an optional property. |
AccountId | integer (10) | Right | 61 | Deprecated; use DebitAccountId and CreditAccountId instead. |
AccountTag | string (50) | Left | 71 | Deprecated; use DebitAccountId and CreditAccountId in conjunction with the Account Balance File and External Account File |
AccountName | string (50) | Left | 121 | Deprecated; use DebitAccountId and CreditAccountId in conjunction with the Account Balance File and External Account File |
TransactionId | long integer (19) | Right | 171 | The unique identifier for the transaction. This field is zero-padded on the left side. Example: 0000000000008309285 |
TransactionTag | string (50) | Left | 190 | The client-supplied unique identifier for the transaction. See transaction object definition for details. |
TransactionTypeCode | string (6) | Left | 240 | The typeCode of the transaction object. |
TransactionAmount | integer (10) | Right | 246 | The amount of funds that was transferred. This field is zero-padded on the left side and two decimals will be assumed, e.g., 000000000000832 represents an amount of $8.32. |
Action | string (1) | Left | 256 | Will be C if the Helix account is being credited, D if debited. |
TransactionDescription | string (255) | Left | 257 | The Helix-generated description for this transaction. |
NachaDescription | string (255) | Left | 512 | The NACHA-supplied description for this transaction. |
CreatedDate | datetime (34) | Left | 767 | The date the transaction was created. Follows same format as API. Example: 2014-10-20T10:30:31.456-05:00See data format guidelines |
SettledDate | datetime (34) | Left | 801 | The date the transaction was settled / is projected to settle. Follows same format as API. Example: 2014-10-20T10:30:31.456-05:00See data format guidelines |
AvailableDate | datetime (34) | Left | 835 | The date the transaction was made available / is projected to be made available. Follows same format as API. Example: 2014-10-20T10:30:31.456-05:00See data format guidelines |
MasterId | long integer (19) | Right | 869 | A Helix-generated key that groups related transactions together. If a transaction directly relates to one or more other transactions, they will all have the same value for the masterId property. |
ReturnCode | string (3) | Left | 888 | The ACH return code associated with the transaction, e.g., R01, R10 etc. |
FeeCode | string (3) | Left | 891 | The fee code the transaction represents. See the feeCode property on the transaction object definition for possible values. |
ExternalAccountId | integer (10) | Right | 894 | Deprecated; use DebitAccountId and CreditAccountId instead. |
ReturnedTransactionId | long integer (19) | Right | 904 | The unique identifier of the transaction on which an ACH return was performed. i.e. This line item's transaction is returning another transaction, and this property specifies exactly which transactionId that is. Note the MasterId value should match for both this line item and the one represented by ReturnedTransactionId. Also, these will typically not appear in the same file, as returns of ACH transactions tend to happen days apart. |
DebitAccountId | string (10) | Right | 923 | The unique identifier for the account from which funds will be withdrawn. This field is zero-padded on the left side. Example: 0008309285This is NOT an account number. It is the accountId of an account or an externalAccountId of an externalAccount object. |
CreditAccountId | string (10) | Right | 933 | The unique identifier for the account to which funds will be credited. This field is zero-padded on the left side. Example: 0008309285This is NOT an account number. It is the accountId of an account or an externalAccountId of an externalAccount object. |
productId | integer (10) | Right | 943 | The unique identifier of the product of which the account the transaction posted against is associated. |
SECCode | string (3) | Left | 953 | The ACH Standard Entry Class (SEC) Code associated with the transaction (e.g., CCD). |
cardholderCustomerId | integer (10) | Right | 956 | Identifies the business customer performing card transactions on a business account with multiple cardholders |
Take me to the Example Posted Transaction File
Updated 6 months ago