When a batch of transactions is prepared and successfully posted, it assumes a status known as "EFT Posting in Progress." Essentially, this status signifies that the batch has been dispatched to the bank for processing but has not yet been officially posted, either within Cashbook or on the bank's records. It exists in a transitional state awaiting further processing.
In cases where errors are encountered within the batch or modifications become necessary, there is a function known as "Reset EFT Batch." This feature allows for the deletion of the batch, provided the bank has not yet initiated processing. It provides an opportunity to start afresh.
If an attempt is made to repost the batch while the response file is still in the process of being generated, it is advisable to check back later.
In cases where the response time exceeds expectations, an option arises. Users can choose to proceed with posting again, thereby overriding the response file. A prompt will seek confirmation for this action.
Provided there are no errors, the batch is successfully retrieved and posted within Cashbook.
If you log out while your batch is in Provisional Posting or while awaiting a Response File from your bank, the Reminder List will automatically open upon logging back into your company. This feature offers instant visibility into any pending response files, ensuring you are promptly informed of waiting files.
Note: The "EFT Posting in Progress" status only applies to banks If the user has selected ‘Obtain Response File from Bank’ in EFT Setup. Otherwise posting is the same as it was.
The bank’s computer operates independently. Once the bank processes the file on its system, it sends an email to the client with proof of payments. This email confirmation is unrelated to the batch posted in Cashbook.
The batch remains unposted in Cashbook until the response file is received and the batch is manually posted.
While the batch status displays "EFT Posting In Progress", this mechanism ensures that double posting is avoided, guaranteeing the batch is posted correctly only after the response file is received. Proof of payment emails pertain solely to the bank's system and do not influence Cashbook’s batch posting.
Note: If a timeout occurs due to excessive retries, the batch remains unposted in Cashbook. Once the response file reaches the server, reposting the batch will correctly process it, completing the EFT posting workflow.
Resetting an EFT batch is a handy feature, but it comes with specific conditions. Here's a clearer breakdown:
Resetting a Batch in the "Out" Folder: If your EFT batch is still in the "Out" folder – meaning it hasn't yet undergone provisional posting or hasn't been processed by the bank – you can reset it. This action effectively reverts the batch to its initial state.
Reset Limitation for Processed Batches: However, if the batch has already reached the provisional posting stage or if the original file can't be located, a reset isn't possible. In this scenario, you'll receive the following message: "EFT batch cannot be reset as the EFT File [File Name] has already been accepted by the bank for processing."
If the reset process succeeds, and the batch reverts to a "ready to post" state, it is then feasible to proceed.
In essence, resetting is an option when the batch is still in your control and hasn't yet progressed to the processing stage by the bank. Once it's been accepted and processed, the reset functionality is no longer applicable.
If the user has selected ‘Obtain Response File from Bank’ in EFT Setup then the log files PSEFTSecure.log and pseftaud_xxxx.log are written to at the time of posting. (xxxx = Bank Code)
PSEFTSecure.log is created in the default download directory for the Cloud version and to the Export Path setup in EFT Bank Setup for the On-premise version. This log file will create an audit of each time a file is uploaded or downloaded from SFTP and report if the connection was successful or not.
pseftaud_xxxx.log is written to the directory associated with the specified database eg C:\Sage\Sage Accpac\SharedData\Company\SAMLTD. This log file is written to when a file is uploaded to the bank and when the response file is downloaded from the bank. This file must not be deleted. If it is deleted, posting will not continue. The program uses this log file to check that no duplicate batches are uploaded to the bank. This could occur if the user restores a database and reposts a batch that has already been uploaded to the bank.
Only batches that require response files will be sent to the scheduler, prompting the user to obtain the response file.
When working with EFT Batches, it's essential to be cautious, especially when dealing with restored backups. If you attempt to process a batch that was previously processed and conflicts with the ongoing audit of a batch, a warning message will appear.
Message: "An EFT file has already been created for this batch and bank. This could result in a duplicate file being sent to the bank. Please contact your dealer."
This message serves as a precautionary measure, indicating that processing this batch could potentially lead to the creation of a duplicate file sent to the bank. To avoid such situations and maintain the integrity of your financial transactions, it's advisable to reach out to your dealer for further guidance and resolution. This proactive step ensures that your EFT processing remains error-free and aligned with your banking requirements.