Minimum Version Required: 23.01
Pre-Conditions
Minimum requirements:
Payment Invoice ID/PaymentInvoiceNum
Invoice ID/InvoiceNum
AmountApplied
Receipt from payment Invoice (even if not changing)
PaymentDate/Invoice Date
Optional Fields:
Payment_ImportGroupID
Invoice_ImportGroupID
ARAccountID
CustomerID
PaymentARNote
PaymentCheckNum
PaymentCreatedBy
InvoicePaymentsID
InvoicePaymentsHistID
Steps
System Behavior: AccountsRecPaymentApplication is to directly update the receipt record on Invoice and directly insert payment data in the invoicePayment table.
Note:
If we do not map Payment Invoice ID/PaymentInvoiceNum, we need map Customer ID or ARAccount ID
If you really want to import against InvoicePayments directly then that works but need to make sure to recalculate Open Balances after. because in the logic of the AccountsRecPaymentApplication EDBL, we did not call the Set_Invoice_OpenDebitCredit method of recalculating OpenDebit and OpenCredit,the user needs to manually run the Scheduled Task Update_OpenCredit_OpenDebit after execution.
AccountsRecPaymentApplication doesn’t care about InvoicePaymentHist/InvoicePayment, If the value in the import file is 200, then the inserted invoicePayment is 200
Fields And Definitions
Best used for:
Importing and applying historical AR
Data conversions
Best Practices
Import routines are an incredibly powerful tool and if used incorrectly, can affect alot 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 setup? Contact our professional services to team to assist.