For our America's market, we are introducing an in-built solution for generating NACHA and CPA formatted electronic fund transfer files, facilitating seamless bank integrations and payment processing. The EFT NACHA conversion capability empowers users to transform EFT information into a specific payment file format compliant with a National Automated Clearinghouse Association, also known as NACHA standards. This tailored format includes unique formatting and additional fields required by NACHA and CPA. It supports standard formats and offers the flexibility to manipulate or create new mappings, ensuring adaptability to evolving payment requirements. Once generated, this file is ready for transmission or upload to a bank portal, facilitating the execution of mass payment batches efficiently while streamlining the user experience. To execute a batch supplier payment online in North America, payment details must be uploaded to a financial institution in a specific format, as stipulated, for example, by the National Automating Clearinghouse Association, better known as NACHA. Before data can be extracted to a specific payment file format, this format must be defined. EFT file formats may be maintained in a new EFT File Format Maintenance Program. Note that you will not have access to this program if you are not licensed for the new EFT NACHA file. To simplify the creation of a file format for North America, SYSPRO is shipped with predefined templates. The operator can base their EFT file format on any of these templates. The file format may consist of different record types, for example, a header record or a batch control record, where each record may have its own line definitions. Each line may be mapped to a specific data field in SYSPRO, or it may be a fixed value, or it may be a calculation. Should the stipulations from NACHA change, these changes can be affected in this program by a SYSPRO partner or customer without having to request changes from the SYSPRO Central Development Team. To support the new file format maintenance, new fields have also been added to supplier maintenance to record data needed for these EFT files. For example, the ABA routing number. In your EFT Bank Control Maintenance Program, you will link your EFT file format to the relevant SYSPRO bank, where you wish to create a batch payment file. This is also where you determine a location where your payment file should be exported. You can choose between a location on the server or the client if you run a client server environment. You can secure the export file through an operator activity that may disallow certain users from exporting the payment file to their local machine. You can also enter the file path for the payment file. Note that if you have chosen your payment file location to be on the client and the operator is exporting the payment file in the web UI, the file will always be exported to the operator's download folder. Now you are ready to create a payment file. The process starts with a standard supplier payment cycle, the payment type set to EFT. This happens in the existing Payment Cycle Maintenance program. Once your payment cycle is complete, you will use the existing EFT Payments Extract program to create your file. If you have previously created your payment file, you can also choose to re-extract your batch using this existing EFT Payments Extract Program. Once the payment file has been extracted, you can pick it up from your chosen file location. By implementing electronic fund transfers, you eliminate manual check processing. This saves the business precious time. By further automating the transformation of payment data into specific file formats, more time is saved Plus, it significantly reduces the opportunity for human error in the execution of payments. Altogether, the efficiency in payment file creation means the business can take better advantage of early payment discounts by supporting on-time payment execution.