SA Table Code Value Setup - Payment Type field descriptions
Fields are organized by section.
General
- Type
-
If you are creating a payment type, specify a two-digit number that is not already used. The maximum number of payment types is 99.
- Description
-
Specify a description. For example, CenPOS VISA.
Required
- Overpayment Refund Type
-
Use this field to specify how an overpayment should be refunded when processing credit, including credit cards. The list is based on existing SA Table Code Value Setup-Payment Type records. In most cases, the overpayment refund type is the same as the initial payment type. However, there may be instances where you choose to refund in cash or by check, rather than the initial payment type.
- Bank
-
Select a bank for this payment type. This should be the bank where the payment type is deposited. The bank for each payment type may differ if you have set up bank accounts for cash deposits versus credit card deposits, for example. Banks are set up in CR Bank Setup.
- Payment Type is a Credit Card
-
Select this option if you are setting up a payment type for a credit card. If this option is not selected, standard tendering occurs, not CenPOS tendering.
- Payment Type is ACH
-
Select this option to identify a payment type as an ACH. Your customers can pay for sales orders using an ACH direct transfer from the customer's bank account to your bank account. The Credit Card Interface supports ACH processing in conjunction with CenPOS payment technology. Your customers can use ACH for a one-time transaction, or, preferably, you can set up customers for recurring ACH transactions.
If you do not select this option, standard Distribution SX.e tendering occurs.
- Payment Type is Credit ACH
-
Select this option if you are setting up a payment type for electronic AP payment remittance. Electronic AP payment remittance is used to send your vendor payments to the bank electronically through CenPOS. CenPOS manages the bank relationships and certifications and sends data directly to the vendor’s bank for processing of a payment. This option is best for distributors who must meet NACHA formatting requirements. CenPOS handles the NACHA formatting.
Notice that saving the record also selects the Payment Type is ACH option. Both options are required to process Credit ACH payment request transactions correctly.
Credit Card
- Payment Type is a Credit Card
- Payment Type is ACH
- Payment Type is Credit ACH
- Processor
-
If you are setting up a credit card payment type, select the appropriate processor from the list. Processors are set up in SA Credit Card Processor Setup.
- Edit Type
-
Select the appropriate type. Use this option to verify that the number entered during Sales Order Entry-Collect Payment is a valid card number for the type selected. The selection does not affect validation by CenPOS because CenPOS validates all cards entered. Select Do Not Perform Validation to prevent this verification by Distribution SX.e.
Additional Information
- Payment Type is a Credit Card
- Payment Type is ACH
- Tendering G/L Account
-
Specify the General Ledger account number. This account is updated when payments are posted using this payment type. We recommend that you use a separate Tendering G/L Account for credit card tendering.
- Credit Card A/R Account #
-
If you select Post to A/R at Invoicing, you must specify the A/R General Ledger account number to update. This keeps track of the number of charges for a credit card type.
If you have selected the option, SASTT Allow ROA to Post to AR Account, in SA Administrator Options-Documents-Sales Orders-Approval Process, you can post Receive on Account (ROA) payments to this AR Control account. Invoice or scheduled payments are applied to this AR Control account. Unapplied Cash is applied to the customer's AR account.
- Addon
-
Specify an addon value, if you assign an addon charge when a credit card payment type is used. Addons are added to the sales order total and are included when the transaction is authorized. This is only an estimate of the expected addon amount. After shipping and invoice processing, the amount on the credit card transaction is adjusted to match the actual addon.
This field is only intended for minor changes and adjustments to the order, such as addons, freight, shipping charge. This field should not be used to cover large adjustments that would create a new transaction, such as line fill, backorder suffix creation or fill.
- Addon Type
-
If you specified an addon percentage in the Addon field, select Percentage. If you specified an addon amount, select Amount.
- Post to A/R at Invoicing
-
Use this option to create an Accounts Receivable transaction for the credit card company.
- Select this option to require a Credit Card A/R customer number when posting a credit card payment. This reverses the original transaction made during tendering, but posts the offset to the A/R account for the credit card customer. The process creates an open Customer Transaction Entry transaction for the credit card customer's account. This transaction is then processed through normal cash receipts when the cash is received from the credit card company.
- Uncheck this option to post the transaction for the credit card to Cash during invoice processing. The account code specified in the Bank field in the Required section is used.
- Days Allowed for B/O Auth
-
Specify the number of days before a credit card authorization expires.
When a back order occurs and the authorization has expired, a new authorization is initiated. This information is determined by bank rules and the credit card company. Typically, authorizations expire on the 7th day. We recommend setting this value to 6 or 7 to ensure funds are held.
Note: If the order is placed on hold because the credit card authorization is expired, the order is displayed on the Sales Entry Processing Back Order Fill Report exception report with an "A" hold, indicating a hold from the back order processing. The order is displayed in Sales Credit Release Inquiry and is automatically pick up for reauthorization by invoice processing. Reauthorization will not occur by filling the order manually.CenPOS manages the expiration date, not Distribution SX.e. Ensure the authorization days allowed do not exceed the credit card's expiration date. For example, a card could expire in 2 days, but your authorization may exist for 7 days. You can mitigate these situations by making use of CenPOS reports. Contact your CenPOS representative.