Method OrigPrecheck

On loans applications whose processing method requires a compliance check, the OrigPrecheck Web Service will allow lenders who do not use the Web pages to perform a compliance pre-check. The lender will input the standard loan origination XML configuration (same as would be sent to Originate3), however all optional fields can be left blank. The minimum requirement is that the loan must have at least 1 Primary Borrower with 1 Principal. The application will not go to funding. If the pre-check is successful, it will be left in Application In-Process status. Applications which fail the pre-check are left in Application In-Process (Failed Precheck Compliance). The response XML will contain the resulting Loan Application number which was submitted for pre-check.

API Documentation
SOAP Component: https://catweb.sba.gov/elend/ws/elend.wsdl
SOAP Method: SharedEntryPoint, only input is structure Inputs
Or: SharedEntryString, only input is JSON string InputString that decodes to a structure
REST Component: /rest/elend/flexible
REST Method: /rest/elend/flexible/SharedEntryPoint, only input is structure Inputs
Or: /rest/elend/flexible/SharedEntryString, only input is JSON string InputString
Keys of the Input Structure:
  • MethodNamePhysical
    		•  Mandatory. Must be “OrigPrecheck”.
  • CLSUsername
    		•  Mandatory. CLS login’s username with update permissions in Origination.
  • CLSPassword
    		•  Mandatory. CLS login’s password with update permissions in Origination.
  • CLSPIN
    		•  Mandatory. PIN generated by Generate_PIN using the same login.
  • EMail
    		•  Mandatory. EMail address to receive funding email.
  • RequestData
    		•  Mandatory. XML or JSON in SBA_ETran format.
  • SoftwareVendorCode
    		•  Mandatory. A private code that authorizes use of SoftwareVendorName.
  • SoftwareVendorName
    		•  Mandatory. Value from Code Tables, Vendor Table.
  • ErrTyp
    		•  Optional. 1 (English) or 2 (XML, default) names in validation error messages.
  • FormatIn
    		•  Optional. Format of RequestData. XML or JSON. See Format IN/OUT Defaults
  • FormatOut
    		•  Optional. Format of ResponseData. XML or JSON. See Format IN/OUT Defaults
    Keys of the Output Structure:
  • ErrorMessageEnglish
    		•  Should be nullstring. If not, a generally-worded error message.
  • ErrorMessageTechnical
    		•  Should be nullstring. If not, a more helpful error message, but scarier to some users.
  • PasswordUpdateRequired
    		•  “Yes”, “No”, number of days till expiration or “TBD” (prior to validating login).
  • ResponseData
    		•  XML or JSON in SBA_ETran_Response.xsd format.

    For examples of calling flexible, structured methods, see Flexible Structure of Inputs For an explanation of REST calls, see Calling Rest Methods

    See “Notes on SBA_ETran_Response formatted XML or JSON”, Notes on SBA_ETran_Response