Forwarded Electronic Confirmation

Understand electronic confirmation with "Routing Enabled" feature.

This feature can be Enabled/Disabled within the Company Preferences / Routing.

The setting is saved into company-settings database, company-preferences collection.

When the setting is "Enabled", by default all files received by GEN are routed.

 

 

To exclude a subset/or all of the documents from a specific counterparty from being routed: a routing rule is required. The implementation of routing rules is unlimited in numbers and specifications.

A routing rule is defined by:

  • Receiver EIC

  • Transactiontype

  • Commodity

  • Deliverypoint

  • Active From -> it must start at least the day prior to the TradeDate of the document in order to be effective

  • Status - enabled/disabled (as required by the user)

 

Processing difference between routed and non-routed documents:

  • GEN does not send notification emails for Routed Documents

  • GEN does not generate PDF

  • GEN does not publish its own generated -> BoxResults, MatchingStatement via SFTP

  • GEN does not allow any automatic change of the document state

  • GEN user can either "Terminate" Routed Document (= cancel) or change over to "Email" (give the counterparty the possibility to confirm via email)

  • GEN sends specific emails only if company has set up Counterparty Private Data (on new document, Reminder, On cancellation request)

  • GEN user can submit message via chat only if company has set up Counterparty Private Data

 

In a Forward-to-Confirm use case, the XML version of the Confirmation is the binding one.

Typically, the GEN-Company and the Non-GEN-Company have an eCM addendum concluded under an EFET frame agreement.

 

Consult further specific information within these articles:

-> https://support.fidectus.com/en/how-does-ecm-routing-work

-> https://support.fidectus.com/en/setting-up-a-routing-rule-for-a-new-company