Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Events/Attendees/NewAcctWalkIn.htm

## Creating New Accounts from Walk-in Attendees

For tracking purposes, walk-in attendees need to be reconciled to an account in Vault CRM before the event can be closed. If an existing account is not found during reconciliation, users can create a new account\_\_v record directly within Events Management to reconcile the walk-in attendee. Information from the walk-in attendee is used to automatically populate fields in the new account\_\_v record to streamline the creation process.

The process to create a new account is identical to the configured account creation process, including account-specific configurations that create additional records related to the new account, for example address\_\_v, tsf\_\_v or account\_territory\_loader\_\_v records.

This feature can also be used in instances requiring users to submit data change requests (DCRs) for new accounts, for example New Account DCRs or Creating Unverified Records.

**Who can use this feature?**

* End Users - Browser, iPad
* [Creating an Account from a Walk-in Attendee](#Creating)
* [Reviewing DCRs for New Accounts from Reconciled Walk-in Attendees](#Reviewin)
* Users require an Events Management License

### Configuring Creating Accounts from Walk-in Attendees for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure this feature:

1. Ensure the following features are configured:

   * [Configuring Events Management](../Configuration/Config.htm)
   * [New Account Wizard](../../Accounts/AcctWizards/New_Account_Wizard.htm)
   * [Reconciling Walk-in Attendees to Existing Accounts](Walk_inAttendees.htm)
2. Navigate to the **Event Rules** section of the appropriate em\_event\_configuration\_\_v record.
3. Select the **Sign In Rules** type event rule created as part of [Defining Walk-in Attendee Fields](Walk_inAttendees.htm#Defining).
4. Ensure the list of em\_attendee\_\_v fields listed in the **walk\_in\_fields\_\_v** field can be used to create new account\_\_v and address\_\_v records. This enables fields to automatically populate in the new records based on the following mapping:

   | em\_attendee\_\_v Field | account\_\_v Field | address\_\_v Field |
   | --- | --- | --- |
   | first\_name\_\_v | first\_name\_cda\_\_v | n/a |
   | last\_name\_\_v | last\_name\_cda\_\_v | n/a |
   | address\_line\_1\_\_v | n/a | name\_\_v |
   | address\_line\_2\_\_v | n/a | street\_address\_2\_cda\_\_v |
   | city\_\_v | n/a | city\_cda\_\_v |
   | state\_province\_\_v | n/a | state\_province\_\_v |
   | zip\_\_v | n/a | postal\_code\_cda\_\_v |
   | license\_\_v\* | n/a | license\_\_v |
   | Custom fields\*\* | Custom fields with matching API names | n/a |

   \* Capturing license information is only supported and automatically mapped when [Capturing State License Information in Account Wizards](../../Accounts/AcctWizards/State_License_Information_in_Account_Wizards.htm) is enabled.

   \*\* Custom fields are only supported and automatically mapped when [Previewing an Account During Creation](../../Accounts/CreatingAccounts/PreviewinganAccountDuringCreation.htm) is enabled.

#### Optional Configuration

The following configuration is optional, depending on your company's specific business needs, or if the Vault CRM instance is integrated with Veeva Network:

1. Ensure the following features are configured:

   * [Decoupled Data Change Requests](../../Accounts/ManagingAccountInfo/Decoupled_Data_Change_Requests.htm)
   * [Decoupled Unverified Records](../../Accounts/ManagingAccountInfo/DecoupledUnverifiedRecords.htm)
   * [Data Change Requests Overview](../../Integration/Network_Integration/Data_Change_Requests/Data_Change_Requests_Overview.htm) – For instances integrated with Veeva Network
   * [Creating Unverified Records](../../Integration/Network_Integration/Data_Change_Requests/CreatingUnverifiedRecords.htm) – For instances integrated with Veeva Network
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions. This is only required when using DCRs:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | data\_change\_request\_\_v | CRE | * account\_\_v * address\_\_v | em\_attendee\_\_v | Edit |
6. Ensure the following values on the walk\_in\_status\_\_v field on the em\_attendee\_\_v object are selected as available for all applicable em\_attendee\_\_v object types. This is only required when using DCRs:

   * reconciliation\_rejected\_\_v
   * pending\_verification\_\_v
   * reconciled\_to\_customer\_master\_\_v

   ![](../../../Resources/Images/Events/Attendees/NewAcctWalkInConfig.png)

### Creating an Account from a Walk-in Attendee as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To create a new account from a walk-in attendee:

Browser
iPad

1. Navigate to the **Attendee Reconciliation** modal in the event.
2. Select the appropriate walk-in attendee. The walk-in attendee cannot already be reconciled.
3. Select **Search for Matches** and search for a match. Users must first search before the New Account button is available.

   ![](../../../Resources/Images/Events/Attendees/NewAcctWalkInBrowser.png)
4. Select **New Account** to launch the New Account Wizard. If the following processes are enabled in the org, the New Account Wizard in the Attendee Reconciliation page reflects these features:

   * [Parent Account Wizard](../../Accounts/AcctWizards/Parent_Account_Wizard.htm)
   * [Auto-Creating Affiliations in Account Wizards](../../Accounts/AcctWizards/AffiliationAutoCreate.htm)
   * [Capturing State License Information in Account Wizards](../../Accounts/AcctWizards/State_License_Information_in_Account_Wizards.htm)
   * [Previewing an Account During Creation](../../Accounts/CreatingAccounts/PreviewinganAccountDuringCreation.htm)
5. Populate the necessary fields for the new account. Fields on the new account\_\_v record, as well as the resulting new address\_\_v record automatically populate based on matching fields from the walk-in attendee.
6. Select **Save**.

1. Navigate to the **Attendee Reconciliation** page in the event.
2. Select the appropriate walk-in attendee. The walk-in attendee cannot already be reconciled.
3. Select **Search for Matches** and search for a match. Users must first search before the + button is available.

   ![](../../../Resources/Images/Events/Attendees/NewAcctWalkIniPad.png)
4. Select the **+** button. This button respects the same new account configuration as the [My Accounts tab](../../Accounts/MyAccounts/MyAccountsOverview.htm).
5. Select the appropriate object type for the new account.
6. Select **Continue**. The New Account Wizard in the Attendee Reconciliation page reflects account creation processes configured in other areas of Vault CRM.
7. Populate the necessary fields for the new account. Fields on the new account\_\_v record, as well as the resulting new address\_\_v record automatically populate based on matching fields from the walk-in attendee.
8. Select **Save**.

After saving, the walk-attendee is updated based on the new account configuration and resulting data. Depending if [New Account DCR](../../Integration/Network_Integration/Data_Change_Requests/iPad_DCR_Process.htm) and [Creating Unverified Records](../../Integration/Network_Integration/Data_Change_Requests/CreatingUnverifiedRecords.htm) are enabled, the new account is created.

* When an account\_\_v record is created without a DCR, the following fields on the walk-in attendee update:
* walk\_in\_status\_\_v – Updates to reconciled\_to\_new\_account\_\_v
* account\_\_v – Updates to reference the new account
* When a DCR is created, the following fields update:
* The walk\_in\_status\_\_v field on the walk-in attendee – Updates to pending\_verification\_\_v
* The em\_attendee\_\_v field on the DCR – Updates to reference the walk-in attendee

### Reviewing DCRs for New Accounts from Reconciled Walk-in Attendees as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

When walk-in attendees are reconciled as pending\_verification\_\_v due to a data change request, the walk-in attendee automatically updates based on the result of the DCR. This is supported for both Network and Decoupled DCRs. If the combination of the DCR’s status\_\_v and result\_\_v does not match any of the rows below, the walk-in attendee is not updated and remains pending\_verification\_\_v.

| status\_\_v of the DCR | result\_\_v of the DCR | walk\_in\_status\_\_v of the Attendee |
| --- | --- | --- |
| processed\_\_v | Any value except change\_rejected\_\_v | reconciled\_to\_new\_account\_\_v |
| processed\_\_v | change\_rejected\_\_v | reconciliation\_rejected\_\_v |
| pending\_\_v | n/a | No Change |
| cancelled\_\_v | n/a | reconciliation\_rejected\_\_v |

If the DCR is rejected, users can attempt to reconcile the attendee again.

The walk-in attendee reconciled to the new account displays with a status of Reconciled to New Account.

The account\_\_v field on the walk-in attendee also updates to reference the new account.

### Related Topics

[Reconciling Walk-in Attendees to Existing Accounts](Walk_inAttendees.htm)

[New Account Wizard](../../Accounts/AcctWizards/New_Account_Wizard.htm)

[Data Change Requests Overview](../../Integration/Network_Integration/Data_Change_Requests/Data_Change_Requests_Overview.htm)