1 of 1

File Data Validation

Which Documents Get Validated

Corastone provides the option of validating the content of the following investor documents against the data for the corresponding investor:

W-9
W-8 BEN
W-8-BEN-E

This validation helps ensure that subscription requests proceed "in good order", with required for fields completed and matching corresponding fields in the request or an existing investor record. For example, Corastone can parse the investor's W9 to ensure that the investor's name matches the name provided in the subscription request.

To enable investor file validation for a subscription request:

include the file information in the investor section of the request
set bypassFileDataValidation to false
set dryRun to false

Example Payload

The following payload from a Create Asset request provides the fileId for a W9 that has already been uploaded to the platform.

{
  "transactionData": {
    "securityId": "CDGP1D3LESYA",
    "amount": 500000,
    "signer": {
      "email": "[email protected]",
      "name": "someone"
  }},
  "investors": [{
    "documents": [
        {
          "fileId": "CDWM1BT94KD1"
        }
      ],
    "data":{
        "type":"individual",
        "accreditationLevel": "qualifiedEligibleParticipant",
        "hasKYCPassed": true,
        "isComplianceApproved": true,
        "name": "Ken Smith",
        "individualInfo": {
            "name": "Ken Smith",
            "dateOfBirth": "1957-06-10",
            "taxId": "987654523",
            "isUsPerson": true
        } }}],

    "account": {
      "data": {
        "name": "Individual Account",
        "type": "Individual",
        "relationshipType": "Advisory",
        "bankAccount": {
          "accountName": "savings account",
          "bankABA": "555525555",
          "bankName": "Test Bank"
        },
        "authorizedSigners": [
          {
          "name": "Jane Doe",
          "primary": true
        }
      ]}},
  "bypassFileDataValidation": false,
  "dryRun": false
}

When Validation Fails

File data validation is an asynchronous process initiated by the Create Asset request. Therefore, you need to check the error log for validation errors. For example, you can use the Sequencer API to retrieve the events that occurred within the relevant timeframe.

{{URL}}/external/v1/sequencer?fromDate="2025-04-10"

Here's a typical error associated with file data validation:

{
            "error": {
                "errorId": "08ce57ef-7249-4304-b623-1e44e7fd5ce3",
                "action": {
                    "id": "CEPM001",
                    "name": "Create Digital Asset",
                    "httpData": {
                        "url": "/external/v1/primary/asset",
                        "method": "POST"
                    }
                },
                "timestamp": "2025-04-10T23:04:25.338Z"
            }
        },

Get the details for the errorId to retrieve the validation errors:

{{URL}}/external/v1/error-log?errorIdsFilter=08ce57ef-7249-4304-b623-1e44e7fd5ce3

Parser errors like the following describe the validation errors:

 {
                "message": "TIN on tax document (ID: 'CDWM172F441T') does not match any investor provided as input",
                "type": "businessRuleValidations",
                "code": "PE0031",
                "context": {
                    "entities": {
                        "processIds": [
                            "45cda088-b1be-4f90-b3e0-021da14c587b"
                        ],
                        "orchestrationIds": [
                            "bd6ac60e-f0ab-482b-b987-aa28790105cf"
                        ]
                    }
                },