Show/Hide All
Click a question below to view the answer.
If you're enrolled in the Sage 100 Direct Deposit service, you do not need to generate an ACH file and send it to your bank. Instead, you sync your payroll information with the service, and Sage takes care of generating and sending an ACH file that meets your bank's requirements.
If you generate ACH files and manually send them to your bank, you must find out your bank's requirements for the ACH file and enter them in Direct Deposit Interface Setup. When you generate an ACH file, it's saved in the folder specified in Payroll Options. You can then follow your bank's instructions to send the file.
For more information, see Set Up Direct Deposit.
Yes. Yes. Each time that you update the Pre-Note Selection Register, a batch of records is created in the Payroll Direct Deposit Transaction file. Only records that exist in this file are used when paying employees using direct deposit.
If you are using the Sage 100 Direct Deposit service, you must run the Pre-Note Selection Register and then sync date with the service to send the prenotes and then sync again after the prenotes are approved by the bank. For more information, see Set Up Employees for the Sage 100 Direct Deposit Service.
If you are generating ACH files and manually sending them to your bank, you must update the Pre-Note Selection Register and then update the Pre-Note Approval Register after the prenotes are approved by the employees’ banks.
Yes. Each time the Check Register is updated, a batch of records is created in the Payroll Direct Deposit Transaction file. Only records that exist in the direct deposit transaction file are used when generating the interface file.
Purge Direct Deposit Files purges the Direct Deposit Transaction file (PR_03) only. If you are generating ACH files to manually send to your bank, those ACH files are not purged.
The frequency of purging data is at your discretion. Files can be purged after the bank has completed the direct deposit transaction, because the information is not needed again. The only time this file might be needed is if you regenerate the interface file.
Note There are instances when the payroll journal cannot be updated due to a duplicate batch. Purging will correct this issue if you set a purge date that is early enough.
Yes, as long they are using the same company code. Currently, there is no method to mix payroll batches for multiple company codes.
No, only one bank code can be processed for any payroll cycle. If you want to separate bank codes for regular checks and direct deposit checks, it requires that different payroll cycles be processed, one for each bank code.
The following questions apply only if you are generating ACH files and manually sending them to your bank.
Yes. One interface file is often submitted to the bank per payroll processing cycle. Check with your bank to determine the requirements for receiving the Automated Clearing House (ACH) file. Pre-notes are processed prior to the regular payroll processing and the Pre-Note Selection Register is updated. Before generating the interface file for these pre-note transactions, the normal payroll cycle is completed and the check register updated. If Only Batches Never Transmitted is selected in the Batches to Include in Transmission field in the Generate Direct Deposit Interface File window, an interface file with both pre-note and payroll cycle transactions is created. For more information, see Generate Direct Deposit Interface File - Fields.
In the Generate Direct Deposit Interface File window, in the Batches to Include in Transmission field, select Only Batches Previously Transmitted. In the Transmission Date fields, enter a range that encompasses the batches that were included in the file that you want to regenerate. For more information, see Generate Direct Deposit Interface File - Fields.
Yes, if you specified a folder in Payroll Options. You can create an interface file other than the Payroll data folder.
