> 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-outcomes/bevica_select_training_outcomes_-_cash_management.md).

# Outcomes - Cash Management

Checklist to validate Cash Management skills in Bevica Select. Work through bank postings and reconciliation, then verify entries and balances.

Use this checklist after the [Cash Management](/bevica-select/bevica_select_training/bevica_select_training_-_cash_management.md) training.

It helps you prove you can run bank postings and reconciliations end-to-end.

### Before you start

You need:

* Access to Bevica Select (ideally a test company)
* [Introduction to Business Central](/bevica-select/bevica_select_training/bevica_select_training_-_introduction_to_business_central.md)
* [General Ledger Part 1](/bevica-select/bevica_select_training/bevica_select_training_-_general_ledger_part_1.md)
* [Sales Ledger](/bevica-select/bevica_select_training/bevica_select_training_-_sales_ledger.md)
* [Purchase Ledger](/bevica-select/bevica_select_training/bevica_select_training_-_purchase_ledger.md)
* [Cash Management](/bevica-select/bevica_select_training/bevica_select_training_-_cash_management.md)

Recommended:

* Capture evidence (statement numbers, bank ledger entry numbers, G/L registers).

### Completion criteria (what “done” looks like)

You’re done when:

* You can trace bank postings into both **Bank Ledger Entries** and **G/L Entries**.
* You can reconcile a statement and explain what “reconciled” means in the system.
* You can recover from common mistakes (wrong match, wrong statement).

### Bank accounts

#### Create a bank account and validate posting setup

**Do**

1. Create a bank account.
2. Create a bank account posting group and a G/L control account (if needed).

**Check**

* You can post to the bank account without setup errors.
* You understand which G/L account is the bank control account.

#### Understand bank ledger entries

**Do**

1. Identify when **Bank Ledger Entries** are created.
2. Review currency fields, **Amount**, and **Amount (LCY)**.

**Check**

* You can explain why Amount vs Amount (LCY) may differ.

#### Find unreconciled entries

**Do**

1. Open the bank account.
2. View the unreconciled bank ledger entries.

**Check**

* You can filter to “not reconciled” entries quickly.

### Bank entries and transfers

#### Post transfers and review what posted

**Do**

1. Post a general journal to transfer money between two bank accounts.
2. Post a foreign currency bank transfer:
   * either change the exchange rate
   * or enter the LCY amount so the system calculates the rate
3. Post a bank transfer that includes a bank charge.

**Check**

* You can review:
  * the **Bank Ledger Entries**
  * the matching **G/L Entries**
* You can explain the charge posting (where it hit the G/L).

### Bank reconciliation

#### Reconcile, post, and recover from mistakes

**Do**

1. Create a bank reconciliation using:
   * **Suggest Lines**, or
   * **Import Bank Statement** (if configured)
2. Manually apply and unapply statement lines to bank ledger entries.
3. Transfer missing statement lines to a journal.
4. Post the bank reconciliation.
5. Undo a posted statement (posted in error).

**Check**

* You can find the posted statement from the bank account card.
* You can explain what changed on the bank ledger entries after posting.

#### Find the statement a bank entry was reconciled on

**Do**

1. Open the specific **Bank Ledger Entry**.
2. Use Page Inspection to find **Statement No.**.

Useful reference: [Page Inspection](/documentation/guides/getting-started-and-navigation/page_inspection.md).

### Useful external references (optional)

* [Perform a bank reconciliation (Microsoft Learn)](https://learn.microsoft.com/en-us/training/modules/bank-reconciliation-dynamics-365-business-central/)


---

# 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-outcomes/bevica_select_training_outcomes_-_cash_management.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.