Minimum Version Required: 23.01
Pre-Conditions
Minimum requirements:
Invoice Num or PO Num
InvoiceDate
PaymentAmount
CustomerID/CustomerID_Translation or ARAccountID/ARAccountID_Translation
RouteNum or RoutID or RouteID_Translation
Optional Fields:
PONum
AbleCreateMultiDeposits
DepositID
AutoBalance (default value = True, we can set to false)
PaymentTypeID
PaymentTypeID_Translation
PaymentPONum
PaymentLoadSheetDate
DoNotRequireInvoiceNums
PaymentARNote
LocationID/LocationID_Translation
CheckNum
AutoARWriteOffProductID
ProductName
Steps
System Behavior: Remittance is to generate payment Invoice to pay.
Note: the user needs AccountsRecApply Permission
Note:
When creating the payment Invoice, the payment Invoice should be created separately according to the Memo field in the import file
If customers want to run Remittance EDBL import on the same day and generate multiple LoadSheets, please Add Static Value AbleCreateMultiDeposits=1 in Import Fields. if you only want to generate one Loadsheet, please do not set the value of AbleCreateMultiDeposits.
Remittance EDBL: Add Load Sheet Status field to set the status of the created Load Sheet
Fields And Definitions
Best used for:
Importing payments to pay open invoices
Custom remittance processes
Importing lockbox files
Best Practices
Import routines are an incredibly powerful tool and if used incorrectly, can affect a lot of data. Test thoroughly on small data sets before importing.
If you are running into setup issues or have questions, reach out to Encompass Support.
Do you have a complex process that consists of a report and import routines that you do not want to set up? Contact our professional services team to assist.