Payment Imports
- Brian Dixon
- Amber Cowles (Deactivated)
- 1 Capability
- 2 Fields
- 2.1 Account Number (GLA)
- 2.2 Method of Payment
- 2.3 Description
- 2.4 Payment Date
- 2.5 Amount
- 2.6 Batch Number (Payment Batch)
- 2.7 Remarks
- 3 UDF Associations
- 4 Errors
Capability
This Import allows the User to INSERT new records into the Payment grid. There is no way to determine if a payment is unique and the identification of duplicate payments is not possible. For more information on Payments, see the AR Payment Wiki page.
It is not possible for PCR-360 employees to fix multiple accidental uploaded records.
Fields
Account Number (GLA)
Required
Datatype is Hierarchical String.
Method of Payment
Required
Datatype is String
This must match a value within the PAYMENT_METHOD List (not case sensitive). See the List Values wiki page for more information.
Description
Datatype is String
Payment Date
Required
Datatype is String
Amount
Required
Datatype is String
This should be a positive, non-zero value
Batch Number (Payment Batch)
Datatype is String
If used, it must match an preexisting pending Batch Number.
Batch Number must be in Pending Status
Remarks
Datatype is String
UDF Associations
User Defined Fields on any given Import are all handled the same way with Conditional Logic. For more information about adding a UDF to the Import see the section of the Imports main page.
Errors
When an Import Line fails, it is usually because the Line falls into one of the following categories:
The value provided from another table was not found within the Database
The value provided is not acceptable for the record type being created