Analyzing Results and Matches

Once FVRs have been registered and their status retrieved, they will be in one of the below statuses.

In the case of either REDU or DFIN, an FVR is considered a DUPLICATE, which is to say that it contains a document that has been submitted at least twice by the same financing applicant. There will be a document within this FVR has a match_type of EXCT.

Below is the matching information returned by GET /status or GET /financing-validation-request. All the details of the documents submitted as part of that request or FVR will be returned to the user, along with the below additional matching information.

{
  "financing_request_status": "DFIN",
  "financing_request_duplicate_report": [
    {
      "match_identification": "e48548ef-406d-42d8-b6a7-dbd4a9d98a1c",
      "match_type": "EXCT",
      "matched_financing_request_status": "FNCD",
      "matched_financing_request_amount": {
        "currency": "SGD",
        "amount": "145000.00"
      },
      "matched_date_time": "2021-05-03T13:50:23.002Z",
      "proprietary_matching_details": {
        "proprietary_description": "CRITICAL_RISK"
      },
      "related_document_match_identifications": [
        "f8e7d3c7-cb61-4917-b354-c9cb7c67948b"
      ]
    }
  ]
}

Above we see the status of our own FVR (DFIN) as well as the status of the counterparty’s FVR (FNCD). We can also see the amount requested for financing, and the match_type (EXCT) of the matching document within these FVRs.

An FVR in the REGU state may also contain document level matches, but is not considered a duplicate as there are some differences in the data submitted. This may be that the documents within have only PART match_types, or there may be an EXCT matching document from a different financing applicant. This is to ensure that documents that have legitimately changed hands throughout the trade finance cycle are not incorrectly identified as attempts at duplicate financing.

Below is an example of document level match information. We can see that this is an EXCT match type, and each of the elements of the document (in this case, an invoice), are matching, with a MACH status. If the financing applicant on the FVR containing this document is the same as the matching FVR and both are in the registered state, then the status of these FVRs will be REDU. If one is then financed, it will update to FNCD, and the other FVR will then be in the DFIN state.

Alternatively, if the FVRs have different financing applicants and there is no other EXCT matching document within them, they will be in the REGU state.

This line by line matching information is retrieved using the GET /document-matches endpoint

{
  "match_identification": "b58d89d8-55c3-4860-a50e-dcfd25dd9f0e",
  "match_type": "EXCT",
  "matched_date_time": "2021-05-03T13:50:23.002Z",
  "matching_report": [
    {
      "element_name": "invoice_number",
      "matching_status": "MACH"
    },
    {
      "element_name": "total_invoice_amount",
      "matching_status": "MACH"
    },
    {
      "element_name": "seller_identification",
      "matching_status": "MACH"
    },
    {
      "element_name": "buyer_identification",
      "matching_status": "MACH"
    },
    {
      "element_name": "issue_date",
      "matching_status": "MACH"
    }
  ],
  "proprietary_matching_details": {
    "proprietary_description": "CRITICAL_SIMILARITY"
  }
}

Below is an example of a partially matched document. The match_type is PART, indicating a partial match, and the invoice_number element is NMAT, indicating that the invoice number differs between the two matching documents. This value could also be UMAT, which indicates unavailable or missing data from one of the documents rather than a true mismatch between the fields.

{
  "match_identification": "2c735535-4bd0-460e-b5df-b75be2ce7ce3",
  "match_type": "PART",
  "matched_date_time": "2021-05-03T13:50:23.002Z",
  "matching_report": [
    {
      "element_name": "invoice_number",
      "matching_status": "NMAT"
    },
    {
      "element_name": "total_invoice_amount",
      "matching_status": "MACH"
    },
    {
      "element_name": "seller_identification",
      "matching_status": "MACH"
    },
    {
      "element_name": "buyer_identification",
      "matching_status": "MACH"
    },
    {
      "element_name": "issue_date",
      "matching_status": "MACH"
    }
  ],
  "proprietary_matching_details": {
    "proprietary_description": "HIGH_SIMILARITY"
  }
}

Next > Glossary

Previous < Monitoring Activity and Polling