# ACH CTX Addenda Format Question **URL:** \ **Category:** Kinetic ERP\ **Tags:** nacha, ach\ **Created:** [April 14, 2026, 6:31pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134 "2026-04-14T18:31:37Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![dgross](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9fc29f/32.png) [@dgross](https://www.epiusers.help/u/dgross)\ **Post date:** [April 14, 2026, 6:31pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/1 "2026-04-14T18:31:37Z")
I am looking for some clarification on the ACH CTX Addenda format. Hoping someone can help. We are using the CTX Addenda record and adding the APTran.Description which isn’t included in the standard Payment\_US\_ACH\_Domestic. I want to include the yellow highlighted fields in the CTX Addenda record for each Invoice Payment. ![image](https://www.epiusers.help/uploads/default/original/3X/a/1/a1b1b3a806821ad47781ed9add57da44dc03b7bd.png) Should my Addenda record look like example 1 or 2? My confusion is when to use the \ separator. I know it needs to be at the end of each line. But in example 2 there is a \ in between the Invoice number and Description for the same line. example 1: ![image](https://www.epiusers.help/uploads/default/original/3X/e/f/efc54437e734160967386588d17128e663c0af7c.png) example 2: ![image](https://www.epiusers.help/uploads/default/original/3X/4/d/4d20b63ea5e63a26fbafcb466526796fd809b3e1.png) ---
**Author:** ![HLalumiere](https://www.epiusers.help/letter_avatar_proxy/v4/letter/h/bc8723/32.png) [@HLalumiere](https://www.epiusers.help/u/HLalumiere)\ **Post date:** [April 14, 2026, 7:51pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/2 "2026-04-14T19:51:03Z")
Not sure which format exactly you are working with, but here are some examples of ACH094 files: [https://developer.gs.com/docs/services/transaction-banking/ach-transaction-examples/](https://developer.gs.com/docs/services/transaction-banking/ach-transaction-examples/) Typically it’s example 1 for domestic payments and example 3 for IAT international payments. Neither looks like your format though. I do a LOT of these with a bunch of different (Canadian) formats, and I have never seen any file formatted like yours. I suggest you get the PDF file that describes the format from your bank, and go from there. ACH094 is a fixed-length records format, so you need to pad/truncate your fields left or right with spaces or zeroes. Some banks also require special routing headers… ---
**Author:** ![dgross](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9fc29f/32.png) [@dgross](https://www.epiusers.help/u/dgross)\ **Post date:** [April 14, 2026, 8:10pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/3 "2026-04-14T20:10:57Z")
> [@HLalumiere](#): > > I suggest you get the PDF file that describes the format from your bank Thanks but I do have a pdf from the bank. My example is only one record in the file which is the CTX Addenda record. We are using the Payment\_US\_ACH\_Domestic.cs program in Epicor. My question is in a field that is 80 characters for Payment Related Information so can contain various data. Positions 04-83 in the screen shot from my bank PDF. ![image](https://www.epiusers.help/uploads/default/original/3X/d/8/d8a5985bb6654a0528f30f5fc0153f4064a54a29.png) ---
**Author:** ![HLalumiere](https://www.epiusers.help/letter_avatar_proxy/v4/letter/h/bc8723/32.png) [@HLalumiere](https://www.epiusers.help/u/HLalumiere)\ **Post date:** [April 14, 2026, 8:15pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/4 "2026-04-14T20:15:32Z")
So according to that you pack your elements inside the field with asterisks, and then pad the field with spaces to the right up to 80 characters length: ```auto 705ELEMENT1*ELEMENT2*ELEMENT3\ 0001... ``` You can see how that works with the 716 addenda in example 3 of the link I posted. ---
**Author:** ![dgross](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9fc29f/32.png) [@dgross](https://www.epiusers.help/u/dgross)\ **Post date:** [April 14, 2026, 8:24pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/5 "2026-04-14T20:24:14Z")
Thanks - this is what I was thinking but this is a new area for me so was 2nd guessing myself. ![image](https://www.epiusers.help/uploads/default/original/3X/a/5/a5f825a8b478a152d850eac1e8570772f4bd718b.png) ---
**Author:** ![HLalumiere](https://www.epiusers.help/letter_avatar_proxy/v4/letter/h/bc8723/32.png) [@HLalumiere](https://www.epiusers.help/u/HLalumiere)\ **Post date:** [April 14, 2026, 8:25pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/6 "2026-04-14T20:25:00Z")
Happy to help! There’s no asterisk after 705 though. 🙂 ---
**Author:** ![dgross](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9fc29f/32.png) [@dgross](https://www.epiusers.help/u/dgross)\ **Post date:** [April 14, 2026, 8:25pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/7 "2026-04-14T20:25:51Z")
Oh…thanks for catching that. ---
**Author:** ![dgross](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9fc29f/32.png) [@dgross](https://www.epiusers.help/u/dgross)\ **Post date:** [April 14, 2026, 8:27pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/8 "2026-04-14T20:27:46Z")
I think I got it now… ![image](https://www.epiusers.help/uploads/default/original/3X/4/e/4e0f29decdfc9c1f0e8dd4e8b1dacb3432d8a36b.png) ---
**Author:** ![DaveOlender](https://www.epiusers.help/user_avatar/www.epiusers.help/daveolender/32/260_2.png) [@DaveOlender](https://www.epiusers.help/u/DaveOlender)\ **Post date:** [April 14, 2026, 8:36pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/9 "2026-04-14T20:36:20Z")
I must confess I have given up on trying to get the Epicor NACHA to work with banks. These days companies change banks like changing sox. I have found that most banks have a Payment Portal that allows uploading Excel,CSV,Etc files. So I use a BAQ to create the fields for whatever the “Bank of the Day” is and format the fields. Example one bank wanted the dollar amount with 3 decimals, no tri-state indicator - commas and the supplier name limited to 43 characters with no commas. DaveO ---
**Author:** ![HLalumiere](https://www.epiusers.help/letter_avatar_proxy/v4/letter/h/bc8723/32.png) [@HLalumiere](https://www.epiusers.help/u/HLalumiere)\ **Post date:** [April 14, 2026, 8:44pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/10 "2026-04-14T20:44:17Z")
I still use the Epicor system, although I no longer use the “stock” .cs files. Instead I wrote a “universal” electronic interface that offloads file creation to a UBAQ. The code in the .cs file calls the UBAQ through REST using parameters passed through from the Payment Method through electronic interface properties. This way we only got one .cs file to upload everywhere, and one UBAQ to which we add modes to. Each “mode” is a file format, for example ACP005, ACH094IAT, ISO20022, etc… Each mode has a matching GetList BPM in the UBAQ, and each BPM is responsible for building file lines. The generated lines are returned to the electronic interface code, and then that code can remove accents or special characters as needed, write the file with the chosen encoding (ANSI, UTF8, UTF8-BOM, etc). So instead of having to manage a million versions of a million different .cs files, we only have one .cs file, and one UBAQ to keep updated. It has dramatically helped, because before that managing EFT for all our customers was a giant clusterf\*\*k… ---
**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\ **Post date:** [April 16, 2026, 2:17pm UTC](https://www.epiusers.help/t/ach-ctx-addenda-format-question/134134/11 "2026-04-16T14:17:07Z")
> [@HLalumiere](#): > > Instead I wrote a “universal” electronic interface that offloads file creation to a UBAQ. Would be nice if Epicor dropped the .cs file thing, and just let you set it up to route to a function.