OHEF - TXP
Standardized electronic format for tax payments
Required for electronic payment or ACH-credit payment of tax, per NACHA operating rules and standards. The standard record includes hard-coded structure of the Addenda Record Type "7" (Field 1) to tag the record as an entry detail addenda record, addenda type "05" (Field 2), Segment ID of "TXP" (Field 3), use of a separator "*" and a segment terminator "\" (the standard content may be customized). Within the makeup of the TXP format is your tax ID, payment code and tax type – all defined within this code's setup below per your local, state, federal and/or financial institution. Additional information will come in from the systems AP transaction: the tax period (field 9) will be APOHUPTR's due date (or see Associated Code 3 below to make the pay date the end of the pay period date); the Amount (Field 13) is APOHUPTR's Extended Amount.
Example of ACH-Credit Payment 705TXP*001280123456789*00001*130131*1*01\
The table below translates the string into useful bits of information:
From Example | How Referenced within Text | How to Customize | Typical Length |
7 | Field 1 (Record Type) | Hard-code | 1 |
05 | Field 2 (Addenda Type) | Hard-code | 2 |
TXP | Field 3 (Segment) | Hard-code | 3 |
001280123456789 | Field 5 (TIN) | OHEF/TXP 1st Assoc Descriptions | 15 |
00001 | Field 7 (Tax Type) | OHEF/TXP 1st Assoc Codes | 5 |
130131 | Field 9 (Tax Period) | APOHUPTR's Due Date or modify in OHEF/TXP 3rd Assoc Code | 6 |
1 | Field 11 (Pay Code) | OHEF/TXP 2st Assoc Codes or OHEF/TXPPC### | 1 |
01 | Field 13 (Amount) | APOHUPTR's Extended Amount | 10 |
* | Field 4, 6, 8, 10 and 12 | Separators; hard-code | 1 |
|n/a | Terminator; hard-code | 1 |
Note: Set up and verify your TXP file per your local, state, federal guidelines, and ACH-Credit program setup per your bank. Submitting a test file before use is recommended.
Code Category: OHEF
Code Value: TXP
Short Description: Not required. Used to describe the common code.
Medium Description: Not required. Used to describe the common code.
Long Description: Not required. Used to describe the common code.
Associated Numeric Values
1-5: Reserved for future use.
Associated Codes
1: Field 7 – tax type code (typically 5 alphanumeric characters long, in columns 24 – 28). Define a lookup table within OHEF / TXPTT### where ### is a consecutive number starting with 001 when defining more than 5 lookups, such as TXPTT001, TXPTT002, TXPTT003, and so on. When using the lookup created by TXPTT###, the value placed within Associated Codes (1) will be a default value placed in the TXP record when the lookup process fails to find a match.
2: Field 11 – payment code (typically 1 numeric character long, in column 37). Define a lookup table within OHEF / TXPPC### where ### is a consecutive number starting with 001 when defining more than 5 lookups, such as TXPPC001, TXPPC002, TXPPC003, and so on. When using the lookup created by TXPPC###, the value placed within Associated Codes (2) will be a default value placed in the TXP record when the lookup process fails to find a match.
3: Field 9 – add "PAYPERIOD" to change the Tax Period date to the pay date at the end of the pay period date (otherwise will default to invoice date). Pay date is set within PYUPPR.
4-5: Reserved for future use.
Associated Descriptions
1: Field 5 - Sender's Tax ID (typically 15 alphanumeric characters long, in columns 8 - 22). This value will be the default Tax ID displayed within an EFT file. Reference an alternate Tax ID that is unique to the transaction's Vendor by placing an Association code of TXPTAXID within the vendor's PEUPPE record. First define the PE Association using the NU Common Code with a Code Category / Value of PEAS / TXPTAXID. Then within the PE Record (PEUPPE), Association tab, add the Code "TXPTAXID" and place the Tax ID in the Association's Description field.
2-5: Reserved for future use.