> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/bevica-select/bevica-select-data-migration/bevica_select_-_data_migration_and_go-live-templates/customer_bank_accounts.md).

# Customer Bank Account Template

Excel template to import customer bank accounts into Bevica Select for payment automation scenarios (where enabled).

Use this template to import **Customer Bank Accounts**.

You typically need these records for SEPA Direct Debit. They’re also useful for customer reporting.

### Before you start

You need:

* ​[Excel Template Data Migration​](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#excel-template-data-migration)
* ​[Configuration Worksheet](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#configuration-worksheet)

### When to use this template

Export it from **Configuration Worksheet** on the **Customer Bank Accounts** line.

Customers must already exist.

### Step-by-step

{% stepper %}
{% step %}

### Export the template

1. Open **Configuration Worksheet**.
2. Select the **Customer Bank Accounts** line.
3. Select **Excel** → **Export to Template**.
   {% endstep %}

{% step %}

### Populate rows

1. Create one row per customer bank account.
2. Format **Customer No.** as **Text** in Excel.
3. Use a consistent **Code** (for example `DD`).
   {% endstep %}

{% step %}

### Import and apply

1. Select **Excel** → **Import from Template**.
2. Fix any errors in the preview.
3. Select **Apply Data**.
   {% endstep %}

{% step %}

### Verify

1. Open a customer card.
2. Open **Bank Accounts**.
3. Confirm the code and IBAN/BIC values.
   {% endstep %}
   {% endstepper %}

### Field reference (template columns)

The template has the following fields:

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="141">Field ID / Name</th><th width="119">Related Table</th><th width="162">FieldType</th><th>Note</th></tr></thead><tbody><tr><td>1 <code>Customer No.</code></td><td>(18) Customer</td><td>Code 20 (Mandatory)</td><td>The customer must already exist.</td></tr><tr><td>2 <code>Code</code></td><td></td><td>Code 20 (Mandatory)</td><td>Enter a unique reference for this customer bank account, e.g. DD.</td></tr><tr><td>3 <code>Name</code></td><td></td><td>Text 100</td><td>The name of the bank account.</td></tr><tr><td>13 <code>Bank Branch No.</code></td><td></td><td>Text 20</td><td>The customer's sort code.</td></tr><tr><td>14 <code>Bank Account No.</code></td><td></td><td>Text 30</td><td>The customer's bank account no.</td></tr><tr><td>24 <code>IBAN</code></td><td></td><td>Code 40 (Mandatory)</td><td>The customer's bank account IBAN.</td></tr><tr><td>25 <code>SWIFT Code</code></td><td></td><td>Code 20 (Mandatory)</td><td>The customer's bank account Swift/BIC code.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/bevica-select/bevica-select-data-migration/bevica_select_-_data_migration_and_go-live-templates/customer_bank_accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.