This section describes how to create and approve a remittance batch. The remittance process initiates the transfer of funds from the credit card issuer to your bank for each receipt. You create remittance batches to remit both manually entered and automatic receipts.
To create a remittance batch for credit card transactions, you must specify the receipt class and receipt method that you used to flag your transactions for credit card payment. See: Creating Credit Card Transactions.
If you do not specify a credit card receipt method when you submit the Automatic Remittances program, then Receivables will not create a remittance batch for your credit card transactions.
When you approve a remittance batch, the program calls Oracle Payments to authorize each receipt.
If authorization details already exist on a receipt in a remittance batch, then authorization has already occurred and Receivables will not call Payments to try to reauthorize a receipt.
If the program does not authorization details on a receipt in a remittance batch, then Receivables calls Payments to perform both authorization and capture for the receipt in one step. For each receipt that receives authorization, Receivables records the details on the receipt (you can view this information in the Payment Details region on the Receipts window).
The authorization details could be null if you created a manual receipt with an automatic receipt method, because manual receipts are not authorized until they are remitted. See: Creating Manual Receipts.
The Approve Remittances program then calls Payments to request capture for the authorized receipts from the credit card issuer via the third party payment processor. Capture indicates that the credit card issuer has reserved the receipt amount and agrees to remit the payment to your bank. The credit card processor returns either a success or failure status to Payments, which then transfers the status of each request to Receivables.
Receivables marks successfully captured receipts as Remitted. Receipts that fail authorization or capture are removed from the batch and appear as exceptions on the Automatic Receipts and Remittances Execution report. Receivables automatically creates this report whenever you create or approve a remittance batch.
Suggestion: Approve your remittance batches promptly because credit card approval codes expire shortly after they are issued (the actual number of days varies by credit card issuer).
See: Creating Remittance Batches.
If the approval code has expired, then you must manually delete the authorization details from the receipt before you resubmit the Automatic Remittances process. Otherwise, the Remittances program will continue to reject the receipt, rather than try to reauthorize it.