Previous | Next | Contents | Index | Navigation | Glossary | Library |
Receivables checks the customer's profile to determine whether it should include invoices that are in dispute. Receivables uses the number of Lead Days that you enter for your payment method to determine when an invoice is eligible for the creation of automatic receipts. The lead days is the number of days before the invoice due date that this invoice can be selected for automatic receipt. A batch of automatic receipts can only have one payment method, thus one lead days value. Receivables compares the invoice due date and lead days with the batch date.
Suggestion: Set the lead days to a high value for automatic receipts that require confirmation. This will give you the additional time required to send the receipts to your customer and for the customer to confirm them. Receipts that will be factored should also have the lead days set to a high number as they are often remitted long before their maturity date.
Receivables uses the GL date to determine the accounting period in which the automatic receipts will post to your general ledger. Receivables does not let you enter a GL date for a new batch if the receipt class requires confirmation as a separate step. This is because Receivables does not create accounting entries when you approve receipts, but do not confirm them. See: Accounting for Automatic Receipts and Remittances.
Lastly, Receivables validates that the receipt amount is more than or equal to the Minimum Receipt Amount that you specified for your remittance bank and customer profile class. You can assign minimum receipt amounts for your remittance bank accounts in the Receipt Classes window and for your Customers in the Customer Profile Classes or Customer windows. If the total of the transactions does not match the larger of the two minimum receipt amounts, no receipts will be created. These transactions will appear in the Exception section of the Create Automatic Receipt Execution report. See: Automatic Receipts and Remittances Execution Report.
Depending upon the function security options set up by your system administrator, you may be able to create, format, and approve automatic receipt batches in one step. See: Function Security in Receivables.
You can delete a batch of Automatic Receipts only if the batch has not yet been approved and its status is Creation Completed. When you delete a batch, all transactions within the batch become available for selection the next time you submit the Automatic Receipt creation program.
Suggestion: Set the Receipts per Commit and Invoices per Commit system options to a large number to avoid intermediate saves in the program. You should use numbers that are large enough to handle your largest automatic receipt and remittance batches. To help determine the numbers to use, look at the end of the log file for your largest Automatic Receipt Creation Batch; this will give you the number of receipts marked for this batch. Assign this number to Auto Receipts Invoices per Commit. Look at the log file for your largest Remittance Creation batch to derive the Auto Receipts Receipts per Commit number. You should only reduce these numbers if you run out of rollback segments. See: Defining Receivables System Options.
Note: If your automatic receipt batch has a status of Started Creation, but the concurrent process terminates, you must delete the batch and resubmit the automatic receipt creation process for this batch.
Suggestion: You can also use the Automatic Receipt Batch Management Report to review the status of your automatic receipt batches. See: Automatic Receipt Batch Management report.
Manually Entering Automatic Receipts
Automatic Receipts Awaiting Confirmation Report
Automatic Receipt Batch Management Report
Previous | Next | Contents | Index | Navigation | Glossary | Library |