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

# Outcomes - General Ledger Part 2

Checklist to validate General Ledger Part 2 skills in Bevica Select. Test periods, budgets, reporting, and confirm posting results.

Use this checklist after the [General Ledger Part 2](/bevica-select/bevica_select_training/bevica_select_training_-_general_ledger_part_2.md) training.

It helps you prove you can control periods, close the month, and produce finance reporting.

### 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)
* [General Ledger Part 2](/bevica-select/bevica_select_training/bevica_select_training_-_general_ledger_part_2.md)

Recommended:

* Run month-end tests with the finance super user.
* Use a realistic posting date range and document mix.

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

You’re done when:

* You can control who can post to which periods.
* You can complete core month-end checks and reconciliations.
* You can produce and explain core management reports.
* You can close a year and recover cleanly from late postings.

### Month end

#### Control posting periods

**Do**

1. Update allowed posting dates for the majority of users.
2. Update allowed posting dates for an individual user.

**Check**

* “Normal users” are blocked outside the window.
* Finance users can post where intended.

#### Reconcile subledgers back to the G/L

**Do**

1. Reconcile **Aged Accounts Receivable** back to the customer control account.
2. Reconcile **Aged Accounts Payable** back to the vendor control account.

**Check**

* You can explain any differences and correct 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).

#### Adjust exchange rates

**Do**

1. Run **Adjust Exchange Rates**.
2. Review what posted.

**Check**

* You can find the exchange rate adjustment register.
* You can explain the impact on:
  * **Customer Ledger Entries**
  * **Vendor Ledger Entries**
  * **Bank Ledger Entries**
  * **G/L Entries**

External: [Adjust exchange rates (Microsoft Learn)](https://learn.microsoft.com/en-us/training/modules/adjust-exchange-rates-dynamics-365-business-central/).

#### Inventory valuation

**Do**

1. Run **Bevica Inventory Valuation**.
2. Reconcile it to the stock accounts in the **Chart of Accounts**.

**Check**

* You can explain timing differences (for example, receipt vs invoice).

Useful reference: [Inventory](/bevica-select/bevica_select_training/inventory.md).

### Year end

#### Close the year end-to-end

**Do**

1. Create a fiscal year.
2. Close a fiscal year.
3. Run **Close Income Statement** and post the resulting journal.

**Check**

* You understand which entries are “closing entries”.
* You can explain retained earnings posting.

External: [Close a fiscal year (Microsoft Learn)](https://learn.microsoft.com/en-us/training/modules/close-fiscal-year-dynamics-365-business-central/).

#### Prove you understand “C dates”

**Do**

1. Run a P\&L report to show balances “as at year end”.
   * Example: `..31/12`
2. Run the same report to show a zeroed P\&L “as at year end”.
   * Example: `..C31/12`

**Check**

* You can explain when you’d use each view.

#### Late postings to a closed year

**Do**

1. Post an adjustment into a closed fiscal year.
2. Re-run **Close Income Statement**.
3. Post the new resulting journal.

**Check**

* You can explain what changed and why.

### G/L budgets (if used)

#### Create, import, and maintain budgets

**Do**

1. Create a budget manually.
2. Create a budget from **G/L Entries**.
3. Copy an existing budget.
4. Import a budget from Excel.
5. Amend a budget.

**Check**

* You can validate totals by account and by period.

External: [Create G/L budgets (Microsoft Learn)](https://learn.microsoft.com/en-us/training/modules/budgets-exchange-rates-dynamics-365-business-central/).

### Reporting

#### Trial balance and Chart of Accounts drill-down

**Do**

1. Run a trial balance and filter by:
   * posting date
   * G/L account
   * dimension (where relevant)
2. In **Chart of Accounts**, apply a date filter.
3. Drill down on **Net Change**, **Balance**, and **Balance at Date**.

**Check**

* You can follow the trail back to the underlying entries.

#### Dimension filters and analysis views

**Do**

1. Apply a dimension filter in **Chart of Accounts**.
2. Explain how you would do the same for a dimension that is not global.
   * Hint: **Analysis Views**.

**Check**

* You can build an analysis view that supports your reporting.

#### Financial Reports (BEV-PL / BEV-BSHEET)

**Do**

1. Run **BEV-PL** and **BEV-BSHEET**.
2. Apply date filters and dimension filters.
3. Switch **Column Layouts** and confirm you understand the differences.

**Check**

* You can explain how a line is calculated (accounts included, signs).
* You know what to update if you add new G/L accounts.

External: [Configure financial reports (Microsoft Learn)](https://learn.microsoft.com/en-us/training/modules/configure-financial-reports-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_-_general_ledger_part_2.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.
