Skip to content
English
Go to Tickets
  • There are no suggestions because the search field is empty.

Matching Types (Confirmation Hub)

The "Matching type" explains how a document was matched in GEN. It shows which confirmation or matching workflow was used to complete the match.

For example, whether the counterparty replied by email, confirmed through the GEN interface, or the match came through an external platform like Equias. Below, each matching type is explained step by step, so you can see exactly what happened for your document.

Matching type

How it works

Email-to-Confirm

You send a confirmation → your counterparty replies to the confirmation email with "Confirm" or "Dispute" → GEN reads the reply and updates the status automatically.

When your counterparty is not a GEN user

Click-to-Confirm

You send a confirmation → your counterparty confirms or disputes it directly in the GEN interface (no email reply needed).

When your counterparty is a GEN user

PDF-to-Confirm

Your counterparty sends back a PDF confirmation, with or without a GEN QR code → GEN reads it and matches it against your original confirmation automatically.

PDF-to-Confirm workflow

Matching runs through your organization's own configured PDF confirmation workflow (match-manually).

Standard-eConfirmation

You and your counterparty each submit a structured confirmation document → GEN electronically compares and matches them automatically.

Advanced-eConfirmation

Like Standard-eConfirmation, but also covers structured XML confirmations sent by email, or matching against a pre-agreed mismatch tolerance → GEN applies the right logic and matches automatically.

Forwarded-eConfirmation

Matching happens outside GEN, on an external platform such as Equias → the result is forwarded into GEN and recorded as matched.

Force match

You (the sender) record the trade as matched yourself → you attach evidence in the "Comment" section that confirmation was received outside GEN's normal response flow.

Agreed match

You propose that two documents should be matched → your counterparty reviews and accepts the proposal in GEN, completing the match.

When your counterparty is a GEN user

No reconfirmation

You send an outgoing PDF confirmation to a counterparty set up (in Static data) not to require a response → GEN marks it matched without waiting for a reply from your counterparty.

E-Signature

You send the document for signature via Skribble → your counterparty (and any other signers) sign electronically → once everyone has signed, GEN creates the counter-document; the signed PDF is your confirmation evidence.

None

No matching type has been assigned yet — check the document's matching status to see where it stands.

Matching type vs. matching status

  • The matching type tells you how the document was matched.

  • The matching status tells you where the document currently stands in the matching process.

For example, a document can have the matching type Standard-eConfirmation and a matching status indicating that it is currently matched.

Related articles