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

# Outcomes - Sales Ledger

Checklist to validate Sales Ledger skills in Bevica Select. Post customer documents and payments, then verify ledger entries and posting results.

Use this checklist after the [Sales Ledger](/bevica-select/bevica_select_training/bevica_select_training_-_sales_ledger.md) training.

It helps you prove you can invoice, collect, and control customer balances.

### 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)

Recommended:

* Work through this with a finance user.
* Capture evidence (posted document numbers, entry numbers, and what you checked).

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

You’re done when:

* You can invoice and credit safely (stock and finance-only).
* You can apply/unapply payments confidently.
* You can reconcile aged receivables back to the control account.

### Customer setup

#### Create and validate a customer record

**Do**

1. Create a new customer.
2. Populate key fields, including default dimensions.
3. Create a ship-to address.
4. Add document email addresses (Document Layouts).
5. Create a customer contact.

**Check**

* Posting groups are set so documents post without errors.
* Default dimensions flow onto documents.
* The correct email addresses are used for document sending.

Useful reference: [Creating Customers](/documentation/guides/sales/working_with_sales_orders.md).

### Invoicing customers (from sales orders)

If you need the operational flow, see [Sales Order Processing](/bevica-select/bevica_select_training/bevica_select_training_-_sales_order_processing.md).

#### Ship and invoice, then prove the posting

**Do**

1. **Ship and Invoice** a single sales order.
2. Ship and invoice a batch of sales orders.
3. Email a single posted sales invoice.
4. Email a batch of posted invoices.

**Check**

* You can review a posted sales invoice and explain:
  * **Customer Ledger Entries**
  * **G/L Entries**
  * **VAT Entries** (if used)
  * **Item Ledger Entries** and **Value Entries** (stock impact)

Useful reference: [Email sales invoices and credit memos](/bevica-select/faqs/email-sales-invoices-and-credit-memos.md).

### Finance-only sales invoices and sales credit memos

**Do**

1. Post a financial sales invoice (G/L-only).
2. Credit that invoice with a financial sales credit memo.

**Check**

* You can explain why this is different from stock corrections.
* You can find and review the posted entries created.

Optional deeper reading:

* [Non-Stock Sales Invoices and Credit Memos](/documentation/guides/finance-and-cash/non-stock_sales_invoices_and_credit_memos.md)
* [Finance Only Price Discrepancies](/documentation/guides/finance-and-cash/finance_only_price_discrepancies.md)

### Credit control

#### Control customer risk

**Do**

1. Set a credit limit.
2. Set **Credit Status** and confirm the impact on new sales orders.
3. Block a customer from creating new sales orders but allow payments.
4. Block a customer from posting any transactions.
5. Put an invoice on hold (dispute).
6. Report on invoices on hold.
7. Remove an invoice hold.

**Check**

* Users see the intended warnings and blocks.
* You can explain “block for posting” vs “block for sales orders”.

Useful reference: [Put customer ledger entries on hold](/bevica-select/faqs/put-customer-ledger-entries-on-hold.md).

#### Statements

**Do**

1. Email a statement to one customer.
2. Email statements in bulk.

**Check**

* The statement layout and email body are correct.

Useful reference: [Email customer statements](/bevica-select/faqs/email-customer-statements.md).

### Customer payments

#### Post, apply, and unapply payments

If you have demo data, use the training customers.

**Do**

1. Post and apply a payment to a single invoice.
2. Apply a payment to multiple invoices and trigger payment tolerance.
3. Post and apply a foreign currency payment (change exchange rate).
4. Post a payment, then apply it from **Customer Ledger Entries**.
5. Unapply a posted payment.

**Check**

* You can see the effect on:
  * **Customer Ledger Entries** (Open / Remaining Amount)
  * **Bank Ledger Entries**
  * **G/L Entries**
* You can explain what changed after apply/unapply.

### Prepayments (if used)

Skip this section if you don’t use customer deposits.

**Do**

1. Post a prepayment invoice from a sales order.
2. Review posted prepayment entries.
3. Post a cash receipt journal to pay the prepayment invoice.
4. Correct a posted prepayment invoice.

**Check**

* You understand how the prepayment links to the final invoice.

Useful reference: [Prepayment Invoicing](/documentation/guides/finance-and-cash/prepayment_invoicing.md).

### Reporting

#### Aged Accounts Receivable (reconcile to the G/L)

**Do**

1. Run **Aged Accounts Receivable** as at a date.
2. Confirm which ageing method you are using (Due Date / Document Date / Posting Date).
3. Reconcile the total back to the customer control account in the **Chart of Accounts**.

**Check**

* You can explain any differences and fix the cause.

Useful reference: [Reconcile aged receivables and payables to the general ledger](/bevica-select/faqs/reconcile-aged-receivables-and-payables-to-the-general-ledger.md).


---

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