The Check Object is utilized by both the Payology Mobile Check Capture and Payology Check Scanning Apps. It is technically the most important of all records, holding the check image, remittance item image (if available), check data (amount, MICR, etc.), and status of transmission and/or return. The status field is functional, invoking the generation of the Payment Submission Queue record and subsequent submission to the Check21.com Payment Gateway. It may relate to a Check Batch or have related Check Allocation records.
|Account||Lookup (Account)||Salesforce Account ID used to relate the Account to the Check Record.|
|Account Number||Text (Encrypted - 25)||User entered/confirmed Account Number.|
|Adjustment Amount||Currency (16,2)||If the check amount (deposit) is adjusted by the Clients Financial Institution, the "real" value of the check will be presented here.|
|Amount||Currency (16,2)||User entered/confirmed Amount of Check.|
|API Account Number||Text (Encrypted - 25)||Account Number extracted from Check by OCR.|
|API Account Number SHA512||Text (255)||HASH'd Account Number extracted from Check by OCR.|
|API Amount||Currency (16,2)||Amount of check extracted by OCR.|
|API Check Number||Text (15)||Check Number extracted from Check by OCR.|
|API Date on Check||Text (Encrypted - 20)||OCR Captured Date on Check|
|API MICR Line||Text (Encrypted - 65)||MICR line extracted from Check by OCR.|
|API MICR Line Confidence Ratio||Text (4)||Confidence Ratio between 0 and 1000 of the OCR captured MICR line.|
|API Routing Number||Text (9)||Routing Number extracted from Check by OCR.|
|Batch||Lookup (Check Batch)||When using the Mobile|
|Capture Check Status||Picklist||If using the Payology Mobile Check Capture App, this field can be used by the user to determine the status of the Capture.|
1. Not Applicable - This value (or blank) will be displayed if the check was not captured by the Mobile Check Capture solution.
2. Pending Front - The front check image has not yet been captured.
3. Pending Rear - The front check image has been captured but the rear has not.
4. Failed - The check capture process has failed.
5. Completed - The check capture process has completed successfully.
|Check Identification HASH||Text (150)||The Check Identification HASH is utilized by the Payology Check Scanning solution as a way to streamline the A/R process. The HASH is comprised of the routing number and account number found on a check. Based on the custom developer Auto-Fill Class (Payology Check Scanning APEX class), this field will help identify incoming checks, matching them to accounts, policies, households, etc.|
|Check Name||Auto Number||Unique name assigned by Salesforce to the Check Record created.|
|Check Number||Text (15)||User entered/confirmed Check Number.|
|Check Submission Status||Picklist||This status field is indicative of the submission to the Check21.com Payment Gateway.|
1. Pending - The Check has not yet been submitted to the
2. Transmitting - The Check is in the process of being Submitted to the Gateway.
3. Completed - The Check has been successfully transmitted to the Gateway.
4. Failed - The Check has failed to transmit to the Gateway.
|Client Account ID||Lookup (Client Account)||This field determines the bank account which will be used to deposit the Check item.|
|Conflict||Picklist (Multi-Select)||If Conflict validation is active on Payology Settings, this field will indicate whether the user entered values differ from the values extracted by the OCR engine. The possible conflicting values may be:|
1. Routing Number
2. Account Number
3. Check Number
|Contact||Lookup (Contact)||Salesforce Contact ID used to relate the Contact to the Check Record.|
|Created By||Lookup (User)||Salesforce User ID used in the creation of the Check Record.|
|Customer Account ID||Text (10)||Unique ID returned by the Check21.com Payment Gateway on Submission of a check item.|
|Customer ID||Text (10)||Unique ID returned by the Check21.com Payment Gateway on Submission of a check item.|
|Date on Check Confidence Ratio||Text (4)||Confidence Ratio between 0 and 1000 of the OCR captured Date.|
|Deposit Date||Date||Deposit Date value returned by the Check21.com Payment Gateway upon query of the Check Status (changes when Pending Deposit transitions to Deposited). This is indicative of the date in which the Check was transmitted to the clients financial institution.|
|Deposit ID||Text (50)||File ID value returned by the Check21.com Payment Gateway upon query of the Check Status (changes when Pending Deposit transitions to Deposited). This is indicative of the File ID assigned to the file on transmission to the Financial Institution by the Check21.com Payment Gateway.|
|Error Report||Long Text Area (32768)||Field used to store errors received on submissions to the Check21.com Payment Gateway.|
|Is From MCC||Checkbox||Is used to determine whether the check was scanned using the Payology Check Scanning App, in which case the value would be "False" or captured using the Payology Mobile Check Capture App, in which case the value would be "True".|
|Last Modified By||Lookup (User)||Salesforce User ID used in the modification of the Check Record.|
|MICR Line||Text (Encrypted - 65)||Confirmed/Updated MICR line based on User entered/confirmed values.|
|Owner||Lookup (User, Group)||Salesforce User ID assigned as owner of the Check Record.|
|Payer City||Text (128)||OCR Captured City of Payer of Check.|
|Payer Name 1||Text (100)||OCR Captured Payer Name on Check.|
|Payer Name 2||Text (100)||OCR Captured Payer Name 2 on Check.|
|Payer Phone||Text (25)||OCR Captured Phone Number on Check.|
|Payer PO Box||Text (20)||OCR Captured PO Box on Check.|
|Payer State||Text (20)||OCR Captured State on Check.|
|Payer Street||Text (255)||OCR Captured Street on Check.|
|Payer Zip Code||Text (10)||OCR Captured Zip Code on Check.|
|Return Date||Date||This value will appear only if the Check item has returned from the financial institution and is indicative of the date in which the return was delivered to the Check21.com Payment Gateway.|
|Return ID||Text (50)||Unique ID assigned my the|
|Return Type ID||Lookup (Return Type)|
|Routing Number||Text (9)||User entered/confirmed Routing Number.|
|Sequence Number||Number (18,0)||Used solely by the Payology Check Scanning App, the sequence number refers to the sequence in which a check was scanned within a batch (i.e. first check scanned has #1, third check scanned has #3).|
6. Bypass Conflict Validation
7. In Conflict
|TempId||Text (255)||Unique Temporary ID provided by the Image Processor for rear image submission by the Payology Mobile Check Capture App.|
|Transaction ID||Text (50)||Unique ID returned by the Check21.com Payment Gateway upon submission of a Check item.|
|Transaction Status||Picklist||1. Pending Check Review|
2. Pending Deposit
4. Pending API Submission
6. Pending Transmission
9 Transaction Overlimit
10. Account Closed
11. Test Transaction
13. Pending Validation Review
14. Administrative Deletion
|Usability Endorsement||Checkbox||If Endorsement Validation is Enabled, this field can be used to determine whether the rear check image has been endorsed.|
|User Account Number SHA512||Text (255)||User entered/confirmed Account Number HASH'd.|
|User ID||Lookup (User)||Salesforce User ID used to relate the User to the Check Record.|
With an understanding of the Check object, Salesforce Administrators and Developers should continue in the path, next focusing on the Check Allocation Object. For detailed information related to the Check Allocation object, please see the next section, labeled The Check Allocation Object.
Updated almost 2 years ago