Invoice in Job Stream with Rejected EFT

Scenario: An EFT payment is rejected while running in a job stream (JS25) that executes IN43 and IN44. When this occurs, IN43 cannot complete until the rejected EFT payment is corrected in AR39.

Invoices with rejected EFTs are taken out of the batch, allowing IN43 to complete and the Invoice Register (IN44) to print, thereby completing the invoice cycle.

  • In the case that the invoice is removed from the batch due to a rejected EFT, the Invoice Register lists the rejected invoice on the Payment Authorization Log page with a combination of messages, for example: "Rejected: 1016 Completion No Match. Rejected: Authorization Rejected, invoice taken out of current batch."

  • Once the rejected EFT payment is corrected in AR39, the affected invoice is included with the next invoice cycle.

  • Note: The invoice with the rejected EFT will print when IN42 runs. Once the EFT payment is corrected in AR39 and IN42 is run again, the invoice will print again. It is possible that the invoice will be sent out twice therefore it is important to monitor the invoices in this scenario.

  • If the rejected EFT payment has not been corrected prior to the next IN42 run, the invoice will be listed in the List of Invoices/Credits not printed dialog box with a reason of 'Not Authorized'. You must correct the invoice in AR39 before the invoice cycle can be completed. Please refer to the AR39 help for details on how to correct the rejected EFT invoice.

  • If the authorization for the invoice was obtained using the Authorize Now function in AR39, a new Authorization Code prints for the invoice on the Invoice Register (IN44) on the following pages:

    1. EFT Register
    2. Prepayment Authorization Log

    The invoice now has a "Forced Authorization" type assigned to it.

IN43 Rules for Moving an Invoice into a New Batch:

Invoiced orders will be removed from the current batch under the following conditions:

  1. IN43/44 is run as part of a Job Stream (JS25).

  2. The EFT payment preauthorized by an automated gateway (BluePay).

  3. The rejected EFT must be on an invoiced order, not a direct bill or credit note.

  4. If there are multiple EFT payments on an invoice and the rejected EFT is for a manual gateway but an accepted EFT payment is for an automated gateway, the invoice will not be removed from the batch. Note: The problem invoice must be resolved before IN43 can be completed.

  5. If the invoice has both payment methods (payment 1 and 2) with EFT payments for an automated gateway (BluePay), and one of the payment methods is authorized and the other is rejected, the invoice will not be removed from the batch. Note: The problem invoice must be resolved before IN43 can be completed.

  Back