How Dealflo can be used for B2B transactions as well as B2C
In this week’s Whiteboard Tuesday, Conor Hickey explains how Dealflo supports multiple signatories for B2B and B2C transactions.
The video covers the main differences between B2B and B2C transactions, and how Dealflo can be used for both scenarios.
Head of Solution Architecture, Dealflo
Hi, my name is Conor Hickey. I’m lead solution architect here at Dealflo. One of the questions that were commonly asked is:
how does Dealflo support multiple signatories for B2B and B2C transactions?
In previous whiteboard videos we’ve covered how an e-Sign workflow can be used to support multiple signatories. Today, we’ll concentrate on how that workflow can be used in the context of both B2B and B2C transactions. We will also cover the main differences between B2B and B2C transactions, and how Dealflo can be used for both scenarios.
We will start by recapping on the workflow for multiple signatories. To recap:
- A single e-Sign URL is passed to multiple signatories – a primary customer and guarantor.
- The e-Sign URL was passed to the signatories.
- The signatories can click on the URL which will launch the e-sign ceremony.
- The first page in the signing ceremony asks the signatory to select themselves from a list of applicable signatories. In this scenario, the primary customer and guarantor will be shown their names.
- The primary customer picks themselves and they will be expected to carry out e-PYC to prove that it is, in fact, them who is active in the signing ceremony. Only on passing that will they be allowed to sign any documentation.
- Similarly, the guarantor goes through the same signing ceremony.
We can take that process and apply it to B2B and B2C scenarios.
We will address B2C first because it is the simpler of the two and the easiest to understand. In a B2C scenario we could have one or many signatories (n-number of signatories). We then apply the same steps as the multiple signatory process. With a B2C transaction, if we are given n-number of signatories to sign a document, all those signatories need to sign that document for the document to be completed and executed.
B2B is a slightly more complex variation on that signing ceremony. For B2B, even though the contract is between a business and a business, it is an individual who is signing the contract (somebody is signing the contract on behalf of the company).
The difference between the workflow for B2C and B2B is that for B2B, although n-number of directors may be allowed to sign a contract on behalf of a company, only one of those directors may be required to sign the contract, and it may not be known at any particular point which of those directors is going to sign.
Dealflo solves for this in the following way. Prior to the e-Sign ceremony, credit checks will be done on the company to make sure it’s creditworthy and a search will be done on Companies House to retrieve the names of the directors who are able to sign on behalf of that company. The client may do that themselves, or Dealflo can help to facilitate that through one of our integrations in the verification hub.
A list of appropriate signatories is available and passed to Dealflo in the initiate transaction. This means that when the e-Sign URL is generated it can be distributed to all those directors. Although all directors are listed, typically only one of those directors is expected to sign, so one director will go through the signing ceremony and the workflow can be configured to be executed once one director has signed.
That’s the slight difference between B2B and B2C. It uses the same workflow, it’s still an individual signing, but it’s configured differently because there’s different scenarios in signing.
I hope that explains how the Dealflo solution can be used for multiple signatories in a B2B and B2C scenarios. Thanks very much for watching.
OTHER VIDEOS YOU MIGHT LIKE