Use Cases
      Back to home
      1. Fidectus Support Center
      2. Product documentation
      3. Use Cases

      Confirmation: Email-to-Confirm

      Description

      A GEN-Company can send and match their (outgoing) Confirmations with their counterparties and/or their customers, which are Non-GEN-Companies via Email. This applies when the Non-GEN-Company is not yet onboarded or not ready to onboard to Confirmation Hub. Typically, a GEN-Company uses one or multiple PDF-Templates in this use case. The PDF and the xml versions of the outgoing Confirmation are automatically attached to an outgoing email to the inbound email address of the Non-GEN-Company.

       

      In an Email-to-Confirm use case, the PDF version of the Confirmation is the binding one. The xml version and data are considered the metadata necessary for (automated) electronic processing and matching of the Confirmation via the Confirmation Hub. In case of an eCM addendum concluded between the GEN-Company and the Non-GEN-Company under an EFET frame agreement, the xml version of the Confirmation is the binding one.

       

      Prerequisites of Setup for GEN-Company

      • Have an active company and an authorized user;

      • Fill in My company private data & Counterparty private data;

      • Set applicable PDF template/s via PDF Template Builder;

      • Fill in required Static data and Contact details for Outbound Confirmations to Non-GEN-Company in Counterparty private data;

      • Optionally enable Notifications;

      • Optionally enable Routing and Gatekeeper; 

       

      Process Flow Summary and Diagram

      • GEN-Company issues Confirmation to Non-GEN-Company (e.g. with XML and PDF attached);

      • Non-GEN Company receives email from GEN-Company;

      • Non-GEN-Company looks at incoming Confirmation attached;

      • Non-GEN-Company chooses to either: 

        • Accept the Confirmation by answering email to GEN. This leads the Confirmation into a Matched status;

        • Dispute the Confirmation by answering email to GEN. This leads the Confirmation into a Mismatched status and starts the dispute process;

        • Optionally there is the feature of chat which enables collaboration for exchanging information and files with the purpose of solving dispute process;

      • GEN-Company receives status updates of Confirmation based on the Non-GEN-Company's answer via email notification, UI or optionally SFTP and RESTful API.

         

       

      Step-by-Step User View

      GEN-Company 

      Non-GEN-Company 

      The user issues Confirmation to Non-GEN-Company (e.g. with XML and PDF attached).

      n/a

      n/a

      		 The user receives email from GEN-Company.

      n/a

      		 The user looks at incoming Confirmation attached.

      n/a

      The user chooses to optionaly address clarifications via email. The email thread will be updated with the entire message history.

      The user sees the reply on the dedicated document chat feature and can extend the conversation with further clarifications from the same chat. These type of interactions can imply exchange of conversations or file attachements.

      n/a

      n/a

      The user receives the reply on the dedicated email thread, where all history is saved.

      n/a

      The user accepts the Confirmation by answering email to GEN with 'CONFIRM' always typed with capital letters. This leads the Confirmation into a Matched status.

       

      n/a

      The user disputes the Confirmation by answering email to GEN with 'DISPUTE' always typed with capital letter. This leads the Confirmation into a Mismatched status and starts the dispute process.

      The user receives status updates of Confirmation based on the Non-GEN-Company's answer via email notification, UI or optionally SFTP and RESTful API.  

      n/a