Matching Types (Settlement Hub)
The "Matching type" explains how a document was matched in GEN. It shows which settlement or matching workflow was used to complete the match.
|
Matching type |
How it works |
|---|---|
|
Email-to-Settle |
Settlement matching happens by email, the same way as Email-to-Confirm → your counterparty replies to "Confirm" or "Dispute" → GEN reads the response. |
|
Click-to-Settle |
You and your counterparty complete settlement matching or acceptance directly in the GEN interface. |
|
PDF-to-Settle |
Your counterparty sends back a settlement document as a PDF → GEN reads it and matches it automatically. |
|
PDF-to-Settle workflow |
Matching runs through your organization's own configured PDF settlement workflow (match-manually). |
|
Standard-eSettlement |
You and your counterparty each submit structured settlement data → GEN electronically compares and matches them. |
|
Advanced-eSettlement |
Covers more complex matching: one document matched against several corresponding documents (one-to-many), or a flexible schema → GEN applies the right logic automatically. |
|
Forwarded-eSettlement |
Matching happens outside GEN, on an external platform such as Equias → the result is forwarded into GEN and recorded as matched. |
|
PDF-to-net |
GEN identifies netting matches automatically — settlement documents created through automation or under a netting agreement. |
|
None |
No matching type has been assigned yet — check the matching status for the current result. |
Matching type vs. matching status
-
The matching type tells you how the settlement document was matched.
-
The matching status tells you the current result or position of the document in the settlement matching process.
For example, a document can have the matching type Standard-eSettlement, while its matching status shows its current state in the process.