> 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_-_payment_methods.md).

# Payment Methods

Set up Payment Methods in Bevica Select to control how customer and vendor payments are posted, applied, and shown on documents.

Payment Methods are setup data used on customer and vendor records.

They help you standardise payment processing and reporting. Example: direct debit vs card.

Set them up before you import customers and vendors, if you plan to populate **Payment Method Code** on those templates.

### Create or edit payment methods

1. Use search, open **Payment Methods**.
2. Add a new line, or edit an existing one.
3. Populate:
   * `Code`
   * `Description`
4. Close the page. Changes save automatically.

### Common examples (typical)

Keep your codes short and consistent. A few common patterns:

* `BACS` = bank transfer
* `CARD` = card payment
* `CASH` = cash
* `DD` = direct debit
* `CHQ` = cheque

### Optional: auto-post balancing account

Only populate these if you want the payment method to drive posting behaviour.

* `Bal. Account Type`: **G/L Account** or **Bank Account**
* `Bal. Account No.`: the account to use

{% hint style="info" %}
If you’re migrating these via templates, check **Configuration Worksheet** for a payment method-related line with a **Package Code**.

If it exists, you can use **Excel** → **Export to Template** / **Import from Template** on that line.
{% endhint %}

### Verify

1. Open a customer or vendor card.
2. Set `Payment Method Code`.
3. Create a test invoice and confirm payment processing behaves as expected.


---

# 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_-_payment_methods.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.