You use the Accounts Receivable Configuration screen to configure system behavior for Accounts Receivable. Typically, this information is configured one time and rarely changed. It is important to understand the implications of changing any system configuration as changes can have substantial impact to how the system behaves in certain scenarios. If you need further clarification on how changing a particular system setting may impact your system, contact your regional Client Care Team.
Click the Accounts Receivable Configuration link on the Main Menu to access the configuration screen. The screen has four tabs: General, Advanced, Credit Card Processing and Access Privileges. See below for information about the options within the Advanced tab.
- Ignore Order # on application Transactions - If checked, the order number is not stamped on the application (XAP) transaction. This may require, in certain cases, that users manually move payments between orders to get the desired affected in the order displays. If unchecked, the application (XAP) transaction is stamped with the order number of the related from or to transaction in an attempt to synchronize the amount due on the order with the transaction and applications in accounts receivable. Whether checked or unchecked, the accounts receivable records reflect the same amounts due/open on payments and invoices. This option only affects how the order number is stored on the application transactions.
- Advanced Payment Surcharges Enabled - If checked, you can configure credit card surcharges. See Credit Card Surcharges (Non-Registration) and Credit Card Surcharges (Registration) for more information.
- Shipping Charges Resource - Resource to use as the shipping charge item for each shipment.
- Default Customer for Recon Transaction - Account the cash control batch reconciliation transaction is attached to. The account must exist in the Accounts screen prior to attempting a cash control batch reconciliation. If the account selected does not exist, you cannot reconcile cash control batches.
- Set Voucher Status to Inactive When Closed - If checked, an accounts receivable voucher becomes inactive when the remaining balance reaches 0 (zero).
Back Office Payment Portal Section
- Payment Portal Configuration - Payment portal configuration to use in back office. If a valid configuration is selected, the Add Web Payment action is available in back office and opens the payment portal configuration in administrator mode.
Credit Card Order Reports Section
- Service Order - Default report the Credit Card Authorization screen prints to the default printer when a credit card transaction is approved for service orders. If no report is selected or an invalid report is selected, the Credit Card Authorization screen does not display a report and users have to select their choice from the drop-down list of service order reports.
- Registration - Default report the Credit Card Authorization screen prints to the default printer when a credit card transaction is approved for registration orders. If no report is selected or an invalid report is selected, the Credit Card Authorization screen does not display a report and users have to select their choice from the drop-down list of registration order reports.
- Fulfillments - Default report the Credit Card Authorization screen prints to the default printer when a credit card transaction is approved for fulfillment orders. If no report is selected or an invalid report is selected, the Credit Card Authorization screen does not display a report and users have to select their choice from the drop-down list of fulfillment order reports.
- Memberships - Default report the Credit Card Authorization screen prints to the default printer when a credit card transaction is approved for membership orders. If no report is selected or an invalid report is selected, the Credit Card Authorization screen does not display a report and users have to select their choice from the drop-down list of membership order reports.
Lockbox Batches Section
- Record Location - Location the lockbox application is placing the lockbox records. The path must exist and available to the workstation running the import process. If this path does not exist or contains an invalid path, the import process does not execute.
- Processing Location - Directory where the lockbox import files are processed. If the directory does not exist or is invalid, the lockbox import process does not execute. The directory is needed to ensure that all lockbox records in the import file are processed and no lockbox records are added to the import file while the file is processing.
- Log Location - Path where the lockbox records are placed by the lockbox import process after processing is complete. The path must exist and available to the workstation running the import process. If this path does not exist or is invalid, the import process does not execute.
Comments
0 comments
Please sign in to leave a comment.