Skip to main content

Populate the Settings tab for a customer record

A guide to completing the Settings tab on a customer record, covering transaction defaults, VAT types, bank details, direct debits, and additional configuration options such as, Head Office, and email templates.

Updated over a week ago

The Settings tab, you can set up transaction defaults, bank details, and currency information for your customer.

To populate the settings tab for a new customer.

  1. Click Debtors then click Customers.

  2. Click + New Record.

  3. Click the Settings tab which contains different sections:

    • Defaults and VAT

    • Transaction Defaults

    • Bank Details

    • Direct Debits

    • Information

    • EDI

    • Head Office

    • Email Templates

Each section is explained below

Section

Description

Defaults and VAT

  • The three options are:

    • Home

    • EU

    • Non-EU

  • Select the correct VAT Type for the customer by clicking on the desired record from the from the VAT Type list. For more information on creating an any currency customer, follow our article on an any currency customer.

  • If you select EU State, you need to select the Country from the country list or alternatively type in the country name.

    • This list is hard coded in your database and cannot be changed.

  • If you select non-EU State, the country list displays all non-EU State countries available in your database.

  • Both EU and non-EU State country records are created within System or Options module.

    • The selection that you make here are used to validate the VAT rates entered on transactions for this customer.

    • The selection that you make for both scenarios are used to validate the VAT rates entered on transactions for this customer and also allows you to be able to select the correct Sales and Bank Analysis.

  • You can only select a valid VAT code.

    • For a GBP VAT customer all non-EU VAT codes are valid.

    • For an EU VAT customer all codes are valid expect VAT codes X and Y exist as default records in every database.

    • For a non-EU VAT customer all non-EU VAT codes are valid.

  • You can only select valid sales analysis records.

    • All active sale type analysis records that match the customer currency are valid.

    • When using an Any Currency customer, all active sales type analysis records of all currencies within your database are valid.

  • You can only select valid bank analysis records.

    • All active bank type sales analysis records that match the customer currency are valid.

    • When using an Any Currency customer, all active bank type analysis records of all currencies within your database are valid.

Transaction Defaults

  • You can optionally select or enter a Sales and Bank Analysis which records your sales to this customer.

    • The analysis set on the customer pulls through as default to all your Sales Transactions.

  • You can also optionally select or enter a VAT Code for this customer.

    • The VAT code set on the customer pulls through as default to all your Sales Transactions.

    • Leaving these fields blank results in the system default being pulled through for the Transactions.

  • You can only select valid analysis records.

    • All active Bank type sales analysis records that match the customer currency are valid.

    • When using an Any Currency customer, then all active bank type analysis records of all currencies within your database are valid.

Bank

Here you can record:

  • Sort Code

  • Account Number

  • Account Name

  • Bank Name


Additionally, where required, you can record:

  • BACS Reference

  • IBAN Number - IBAN is earlier than SWIFT/BIC and is covered by a separate ISO Standard

  • SWIFT/BIC Code - These are ISO standard formats that are unique identifiers for international financial institutions.

Direct Debit

  • Only available where your Financials is integrated with the Direct Debit Module.

  • Collection Type - Defaults to Auddis, but you can change it to Sepa.

  • Days to Elapse - Pulls through default if one set up, otherwise blank.

  • Status - A list of Direct Debit statuses defaulting to No Direct Debit.

  • Mandate ID / Date of Signature - Insert as appropriate once the instruction has been set up.

Information

  • This section is set up for communication purposes and you are also able to set a customer to be Inactive by toggling the Inactive buttons from No - default, to Yes.

  • You won't be able to set a customer to be inactive if they have transactions saved in the batch.

EDI

  • EDI stands for Electronic Data Interchange.

  • EDI is a standard electronic format that replaces paper-based documents such as purchase orders or invoices.

  • By automating paper-based transactions, organisations can save time and eliminate costly errors caused by manual processing.

Head Office

  • The Head Office set up allows you to Invoice a Head Office for an order that has been placed by a Sub Office.

Email Templates

  • There are standard email templates defined when a new database is created.

  • You are able to add new ones within the System Module which is permission driven.

  • You can set the email template for the following:

    • Sales Order Invoice

    • Statement

    • Sales Invoice or Credit Note

    • Sales Order Confirmation

  • If your database has several templates set up for each option, you can select the relevant one from the drop-down list.

Contra Settings

  • The Contra Settings section only becomes visible once you save a customer, or if you're editing an existing one. It won't be available when creating a new customer.

  • You can use the Contra Settings when you have a customer who also buys from you and you wish to offset any money owed by this customer against money that you owe them. To set up a contra relationship between a supplier and a customer, you have to have existing supplier records in the Creditors or Purchase Ledger module.

  • For more information on how to link a customer to a supplier record, follow our article on setting up a customer and supplier relationship.

Did this answer your question?