> 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/opening-balances-inventory/sepa_direct_debit_mandate_import.md).

# SEPA Direct Debit Mandate Import

Use this template to import customer DD mandate information. These records are needed in order to produce Direct Debit files from Bevica.

### Before you start

Start here:

* [Customer Bank Accounts](/bevica-select/bevica-select-data-migration/bevica_select_-_data_migration_and_go-live-templates/customer_bank_accounts.md)
* [Configuration Worksheet](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#configuration-worksheet)
* [Excel Template Data Migration](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#excel-template-data-migration)

### When to use this template

The customer DD mandate template is a pre-formatted spreadsheet with the fields you need to create customer DD mandates in order to process direct debit collections. You can access the template from the **Configuration Worksheet** page, **Customer DD Mandates** line.

### Step-by-step

{% stepper %}
{% step %}

### Export the template

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

{% step %}

### Populate rows

1. Create one row per mandate.
2. Make sure the customer exists.
3. Make sure the customer bank account exists.\n
   {% 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 the customer.
2. Confirm the mandate is available for direct debit processing.
   {% endstep %}
   {% endstepper %}

### Field reference (template columns)

The template has the following fields:

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="148">Field ID / Field Name</th><th width="135">Related Table</th><th width="125">Field Type</th><th>Note</th></tr></thead><tbody><tr><td>1 <code>ID</code></td><td></td><td>Code 35 (Mandatory)</td><td>The DD mandate ID.</td></tr><tr><td>2 <code>Customer No.</code></td><td>Customer (18)</td><td>Code 20 (Mandatory)</td><td>The customer must already exist.</td></tr><tr><td>3 <code>Customer Bank Account No.</code></td><td>Customer Bank Account (287)</td><td>Code 20 (Mandatory)</td><td>The customer's bank account code that you created when importing customer bank accounts, e.g. DD.</td></tr><tr><td>4 <code>Valid From</code></td><td></td><td>Date (No)</td><td></td></tr><tr><td>5 <code>Valid To</code></td><td></td><td>Date (No)</td><td></td></tr><tr><td>6 <code>Date of Signature</code></td><td></td><td>Date (Mandatory)</td><td>Date the DD mandate was signed. DD collections cannot be taken unless this field is populated.</td></tr><tr><td>7 <code>Type of Payment</code></td><td></td><td>Option (Mandatory)</td><td>Set to Recurrent or One-Off.</td></tr><tr><td>8 <code>Blocked</code></td><td></td><td>Boolean (No)</td><td></td></tr><tr><td>9 <code>Expected No. of Debits</code></td><td></td><td>Integer (Mandatory)</td><td>Must be greater or equal to 1. To be used in conjunction with 'Ignore Exp. Number of Debits'.</td></tr><tr><td>10 <code>Debit Counter</code></td><td></td><td>Integer (Mandatory)</td><td>Number of DDs already collected. Use in conjunction with 'Expected No. of Debits' and 'Ignore Exp. Number of Debits'.</td></tr><tr><td>12 <code>Closed</code></td><td></td><td>Boolean (No)</td><td></td></tr><tr><td>13 <code>Ignore Exp. Number of Debits</code></td><td></td><td>Boolean (No)</td><td>Set this if the DD Counter can go above the 'Expected No. of Debits'.</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/opening-balances-inventory/sepa_direct_debit_mandate_import.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.