From a68287e92003109ca6a7c0b1e248dfff0ef31de5 Mon Sep 17 00:00:00 2001 From: jill-kotel-andersson <56507949+jill-kotel-andersson@users.noreply.github.com> Date: Fri, 17 Sep 2021 16:20:50 +0200 Subject: [PATCH 1/2] 386270 - design-details-inventory-adjustment-value-entry-posting-date has poor ratings (#1705) * Split the doc WIP --- business-central/TOC.md | 5 +- ...tment-value-entry-allowed-posting-dates.md | 75 +++ ...ory-adjustment-value-entry-posting-date.md | 472 ++---------------- ...ory-adjustment-value-entry-source-entry.md | 362 ++++++++++++++ 4 files changed, 472 insertions(+), 442 deletions(-) create mode 100644 business-central/design-details-inventory-adjustment-value-entry-allowed-posting-dates.md create mode 100644 business-central/design-details-inventory-adjustment-value-entry-source-entry.md diff --git a/business-central/TOC.md b/business-central/TOC.md index 2e6bb6d85..76176a995 100644 --- a/business-central/TOC.md +++ b/business-central/TOC.md @@ -41,7 +41,10 @@ ##### [Design Details: Item Application](design-details-item-application.md) ##### [Design Details: Known Item Application Issue](design-details-inventory-zero-level-open-item-ledger-entries.md) ##### [Design Details: Cost Adjustment](design-details-cost-adjustment.md) -##### [Design Details: Posting Date on Adjustment Value Entry](design-details-inventory-adjustment-value-entry-posting-date.md) +##### Design Details: Posting Date on Adjustment Value Entry +###### [Design Details: Posting Date on Adjustment Value Entry](design-details-inventory-adjustment-value-entry-posting-date.md) +###### [Error Message "Posting Date is not within your range of allowed posting dates"](design-details-inventory-adjustment-value-entry-allowed-posting-dates.md) +###### [Posting Date on Adjustment Value Entry Compared to the Source Entry](design-details-inventory-adjustment-value-entry-source-entry.md) ##### [Design Details: Expected Cost Posting](design-details-expected-cost-posting.md) ##### [Design Details: Average Cost](design-details-average-cost.md) ##### [Design Details: Variance](design-details-variance.md) diff --git a/business-central/design-details-inventory-adjustment-value-entry-allowed-posting-dates.md b/business-central/design-details-inventory-adjustment-value-entry-allowed-posting-dates.md new file mode 100644 index 000000000..87c6ce313 --- /dev/null +++ b/business-central/design-details-inventory-adjustment-value-entry-allowed-posting-dates.md @@ -0,0 +1,75 @@ +--- +title: Error Message "Posting Date is not within your range of allowed posting dates" +description: Resolve the error behind the message "Posting date is not within your range of allowed posting dates" when running the Adjust Cost - Item Entries batch job. +author: edupont04 + +ms.service: dynamics365-business-central +ms.topic: conceptual +ms.devlang: na +ms.tgt_pltfrm: na +ms.workload: na +ms.search.keywords: +ms.date: 09/17/2021 +ms.author: edupont + +--- + +# Error message: "Posting Date is not within your range of allowed posting dates…" + +When using the **Adjust Cost - Item Entries** batch job you may run into the following error message: + +**Posting date is not within your range of allowed posting dates** + +This error message indicates that the user is not allowed to post entries for the date in question, and this can be remedied by changing the user setup. + +## Change the user setup + +|User ID |Allow Posting From | Allow Posting To | +|---------|---------|--------| +|EUROPE | 2020-09-11 |2020-09-30 | + +The user in this case has an allowed posting date range from September 11th to September 30th and is therefore not allowed to post the Adjustment Value Entry with Posting Date September 10th. + +### Overview of involved posting date setup + +#### Inventory Periods + +|Ending Date |Name |Closed | +|---------|---------|---------| +|2020-01-31 |January 2020 | Yes | +|2020-02-28 |February 2020 | Yes | +|2020-03-31 |March 2020 | Yes | +|2020-04-30 |April 2020 | Yes | +|2020-05-31 |May 2020 | Yes | +|2020-06-30 |June 2020 | Yes | +|2020-07-31 |July 2020 | Yes | +|2020-08-31 |August 2020 | Yes | +|2020-09-30 |September 2020 | | +|2020-10-31 |October 2020 | | +|2020-11-30 |November 2020 | | +|2020-12-31 |December 2020 | | + +#### General Ledger Setup + +|Field|Value| +|---------|---------| +|Allow Posting From: | 2020-09-10 | +|Allow Posting To: | 2020-09-30 | +|Register Time: | | +|Local Address Format:| Post Code | + +#### User Setup + +|User ID |Allow Posting From | Allow Posting To | +|---------|---------|--------| +|USERNAME | 2020-09-10 |2020-09-30 | + +Assigning a wider allowed posting date range, as in Inventory Period or General Ledger Setup, makes it possible to avoid the conflict that causes the error message. The Adjustment Value Entry with Posting Date September 10th will be posted successfully with this setup. + +## See Also + +[Design Details: Posting Date on Adjustment Value Entry](design-details-inventory-adjustment-value-entry-posting-date.md) +[Design Details: Inventory Costing](design-details-inventory-costing.md) +[Design Details: Item Application](design-details-item-application.md) + +[!INCLUDE[footer-include](includes/footer-banner.md)] diff --git a/business-central/design-details-inventory-adjustment-value-entry-posting-date.md b/business-central/design-details-inventory-adjustment-value-entry-posting-date.md index 7676a5f45..9955cdce2 100644 --- a/business-central/design-details-inventory-adjustment-value-entry-posting-date.md +++ b/business-central/design-details-inventory-adjustment-value-entry-posting-date.md @@ -9,42 +9,37 @@ ms.devlang: na ms.tgt_pltfrm: na ms.workload: na ms.search.keywords: -ms.date: 08/19/2021 +ms.date: 09/17/2021 ms.author: edupont --- -# Design Details: Posting Date on Adjustment Value Entry +# Design Details: Posting Date on Adjustment Value Entry -This article provides guidance for users of the Inventory Costing functionality in [!INCLUDE[prod_short](includes/prod_short.md)]. The specific article is providing guidance in how the **Adjust Cost - Item Entries** batch job identifies and assigns a posting date to the value entries that the batch job is about to create. +This article provides guidance for users of the Inventory Costing functionality in [!INCLUDE[prod_short](includes/prod_short.md)], and in particular for how the **Adjust Cost - Item Entries** batch job identifies and assigns a posting date to the value entries that the batch job is about to create. -First the concept of the process is reviewed, how the batch job identifies and assigns the Posting Date to the Value Entry to be created. Thereafter there are some scenarios shared that we in the support team come across from time to time and finally there is a summary of the concepts used. - -## The Concept +## How posting dates are assigned The **Adjust Cost – Item Entries** batch job assigns a posting date to the value entry it is about to create in the following steps: -1. Initially the Posting Date of the entry to be created is the same date as the entry it adjusts. - -2. The Posting Date is validated against Inventory Periods and/or General Ledger Setup. +1. Initially the Posting Date of the entry to be created is the same date as the entry it adjusts. -3. Assignment of Posting Date; If the initial Posting Date is not within allowed posting date range the batch job will assign an allowed Posting Date from either General Ledger Setup or Inventory Period. If both Inventory Periods and allowed posting dates in General Ledger Setup are defined, the later date of the two will be assigned to the Adjustment Value Entry. +2. The Posting Date is validated against Inventory Periods and/or General Ledger Setup. - Let’s review this process more in practice. Assume we have an Item Ledger Entry of Sale. The item was shipped on September 5, 2020 and it was invoiced the day after. +3. Assignment of Posting Date; If the initial Posting Date is not within allowed posting date range the batch job will assign an allowed Posting Date from either General Ledger Setup or Inventory Period. If both Inventory Periods and allowed posting dates in General Ledger Setup are defined, the later date of the two will be assigned to the Adjustment Value Entry. +Let’s review this process more in practice. Assume we have an Item Ledger Entry of Sale. The item was shipped on September 5, 2020 and it was invoiced the day after. -**Item Ledger Entry** -Date format YYYY-MM-DD +#### Item Ledger Entry |Entry No. |Item No. |Posting Date |Entry Type | Document No. |Location Code |Quantity |Cost Amount (Actual) |Invoiced Quantity |Remaining Quantity | |---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| |319 |A |2020-09-05 | Sale |102033 | Blue | -1 | -11 |-1 | 0 | -Below, the first Value Entry (379) represents the shipment and carry the same Posting Date as the parent Item ledger Entry. - -The second Value Entry (381) represents the invoice. +Below are the related value entries: -The third Value Entry (391) is an Adjustment of the invoicing Value Entry (381). - +- **Entry No. 379** represents the shipment and carry the same Posting Date as the parent Item ledger Entry. +- **Entry No. 381** represents the invoice. +- **Entry No. 391** is an Adjustment of the invoicing Value Entry (Entry No. 381 above). |Entry No. |Item No. |Posting Date |Item Ledger Entry Type |Entry Type |Document No. |Item Ledger Entry No. |Location Code |Item Ledger Entry Quantity |Invoiced Quantity |Cost Amount (Actual) |Cost Amount (Expected) |Adjustment |Applies-to Entry |Source Code | |---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|--------|---------|---------|---------|---------| @@ -52,17 +47,15 @@ The third Value Entry (391) is an Adjustment of the invoicing Value Entry (381). |381 | A | 2020-09-06 | Sale | Direct Cost | 103022 |319 | Blue | 0 |-1 |-10 | 10 | No |0 | Sales | |391 | A | 2020-09-10 | Sale | Direct Cost | 103022 |319 | Blue | 0 |0 |-1 | 0 |Yes | 181 | INVTADJMT | -Posting Date on Adjustment entry is initially set to the same Posting date of the entry it adjusts. +To assign the posting date for **Entry No. 391** the following steps were applied: - Step 1: Adjustment Value Entry to be created is assigned same Posting Date as the entry it adjusts, illustrated above by Value entry 391. - - Step 2: Validation of initial assigned Posting Date. +1. The **Adjustment Value Entry** to be created (**Entry No. 391**) is assigned same **Posting Date** as the entry it adjusts. -The **Adjust Cost – Item Entries** batch job determines if the initial Posting Date of the Adjustment Value Entry is within allowed posting date range based upon Inventory Periods and/or General Ledger Setup. +2. The **Adjust Cost – Item Entries** batch job determines if the initial Posting Date of the Adjustment Value Entry is within allowed posting date range based upon Inventory Periods and/or General Ledger Setup. Let’s review the above mentioned Sale by adding setup of allowed posting date ranges. -**Inventory Periods** +#### Inventory Periods |Ending Date |Name |Closed | |---------|---------|---------| @@ -72,16 +65,16 @@ Let’s review the above mentioned Sale by adding setup of allowed posting date |2020-04-30 |April 2020 | Yes | |2020-05-31 |May 2020 | Yes | |2020-06-30 |June 2020 | Yes | -|2020-07-31 |July 2020 | Yes | -|2020-08-31 |August 2020 | Yes | +|2020-07-31 |July 2020 | Yes | +|2020-08-31 |August 2020 | Yes | |2020-09-30 |September 2020 | | |2020-10-31 |October 2020 | | |2020-11-30 |November 2020 | | |2020-12-31 |December 2020 | | -First allowed posting date is the first day in the first open period. September 1, 2020. +The first allowed posting date is the first day in the first open period, which is September 1, 2020. -**General Ledger Setup** +#### General Ledger Setup |Field|Value | |---------|---------| @@ -90,437 +83,34 @@ First allowed posting date is the first day in the first open period. September |Register Time: | | |Local Address Format:| Post Code | - First allowed posting date is the date stated in field Allow Posting From: September 10, 2020. - If both Inventory Periods and allowed posting dates in General Ledger Setup are defined, the later date of the two will define the allowed posting date range. +The first allowed posting date is the date stated in field **Allow Posting From**: September 10, 2020. If both Inventory Periods and allowed posting dates in **General Ledger Setup** are defined, the later date of the two will define the allowed posting date range. + +**Assignment of an allowed posting date** - Step 3: Assignment of an allowed posting date; +The initial assigned Posting Date was September 6 as illustrated in step 1. However, in the second step the Adjust Cost – Item entries batch job identifies that earliest allowed Posting Date is September 10 and thereby assigns September 10 to the Adjustment Value Entry (**Entry No. 391**), below. - The initial assigned Posting Date was September 6 as illustrated in step 1. However, in the second step the Adjust Cost – Item entries batch job identifies that earliest allowed Posting Date is September 10 and thereby assigns September 10 to the Adjustment Value Entry, below. - |Entry No. |Item No. |Posting Date |Item Ledger Entry Type |Entry Type |Document No. |Item Ledger Entry No. |Location Code |Item Ledger Entry Quantity |Invoiced Quantity |Cost Amount (Actual) |Cost Amount (Expected) |Adjustment |Applies-to Entry |Source Code | |---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| |379 | A | 2020-09-05 | Sale | Direct Cost | 102033 |319 | Blue | -1 |0 | 0 | -10 |No |0 |Sales | |381 | A | 2020-09-06 | Sale | Direct Cost | 103022 |319 | Blue | 0 |-1 |-10 | 10 | No |0 | Sales | |391 | A | **2020-09-10** | Sale | Direct Cost | 103022 |319 | Blue | 0 |0 |-1 | 0 |Yes | 181 | INVTADJMT | - We have now reviewed the concept for assigning Posting Dates to Value Entries created by the Adjust Cost - Item entries batch job. - - Let’s continue to review some scenarios that we in the support team comes across from time to time in relation to assigned Posting Dates in the Adjust Cost – Item entries batch job and related setups. - -## Scenario I: “Posting Date is not within your range of allowed posting dates…” - - This is a scenario where a user is experiencing mentioned error message when the Adjust Cost – Item entries batch job is run. - - In the previous section, describing the concept of assigning posting dates, the intention of the Adjust Cost – Item entries batch job is to create a Value Entry with Posting Date September 10th. - -![Error message about posting date.](media/helene/TechArticleAdjustcost6.png "Error message about posting date") - - We follow up on the User Setup: - -**User Setup** - -Sorting: User ID - -|User ID |Allow Posting From | Allow Posting To | -|---------|---------|--------| -|EUROPE | 2020-09-11 |2020-09-30 | - - The user in this case has an allowed posting date range from September 11 to September 30 and is thereby not allowed to post the Adjustment Value Entry with Posting Date September 10th. - -### Overview of involved posting date setup: - -**Inventory Periods** - -|Ending Date |Name |Closed | -|---------|---------|---------| -|2020-01-31 |January 2020 | Yes | -|2020-02-28 |February 2020 | Yes | -|2020-03-31 |March 2020 | Yes | -|2020-04-30 |April 2020 | Yes | -|2020-05-31 |May 2020 | Yes | -|2020-06-30 |June 2020 | Yes | -|2020-07-31 |July 2020 | Yes | -|2020-08-31 |August 2020 | Yes | -|2020-09-30 |September 2020 | | -|2020-10-31 |October 2020 | | -|2020-11-30 |November 2020 | | -|2020-12-31 |December 2020 | | - -**General Ledger Setup** - -|Field|Value| -|---------|---------| -|Allow Posting From: | 2020-09-10 | -|Allow Posting To: | 2020-09-30 | -|Register Time: | | -|Local Address Format:| Post Code | - -**User Setup** - -|User ID |Allow Posting From | Allow Posting To | -|---------|---------|--------| -|USERNAME | 2020-09-10 |2020-09-30 | - - Assigning the user a wider (or same) allowed posting date range as in Inventory Period or General Ledger Setup, mentioned conflict will be avoided. The Adjustment Value Entry with Posting Date September 10th will be posted successfully with this setup. - -An older Knowledge Base article [952996](https://support.microsoft.com/topic/information-about-inventory-adjustment-posting-dates-in-microsoft-dynamics-nav-99e22b2b-5b79-a9b2-3b43-7f3484fa31d9) discusses more scenarios related to the mentioned error message. - -## Scenario II: Posting Date on Adjustment Value Entry versus Posting Date on entry causing the adjustment such as Revaluation or Item charge. - -### Revaluation scenario: - - Prerequisites: - - Inventory setup: -me -- Automatic Cost Posting = Yes - -- Automatic Cost Adjustment = Always - -- Average Cost Calc. Type = item - -- Average Cost Period = Day - - General Ledger Setup: - -- Allow Posting From = January 1, 2021 - -- Allow Posting To = empty - - User Setup: - -- Allow Posting From = December 1, 2020 - -- Allow Posting to = empty - -### To test the scenario - -1. Create item TEST: - - Base unit of measure = PCS - - Costing Method = Average - - Select optional posting groups. - -2. Open Item Journal, create, and post a line as follows: - - Posting Date = December 15, 2020 - - Item = TEST - - Entry Type = Purchase - - Quantity = 100 - - Unit Amount = 10 - -3. Open Item Journal, create, and post a line as follows: - - Date = December 20, 2020 - - Item = TEST - - Entry Type = Negative Adjustment - - Quantity = 2 - -4. Open Item Journal, create, and post a line as follows: - - Date = January 15, 2021 - - Item = TEST - - Entry Type = Negative Adjustment - - Quantity = 3 - -5. Open Revaluation Journal, create, and post a line as follows: - - Item = TEST - - Applies-to Entry = select Purchase entry posted at step 2. The Posting Date of the revaluation will be the same as the entry it adjusts. - - Unit Cost Revalued = 40 - -The following **Item Ledger** and **Value Entries** have been posted: - -**Item Ledger Entry - purchase**: -Date format YYYY-MM-DD - -|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | -|---------|---------|---------|---------|---------|---------|---------|---------| -|317 |TEST |2020-12-15 |Purchase |T00001 |100 |4000 |95 | - -**Value Entries** - -|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. |Item Number Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies to Entry |Source Code | -|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -|376 |TEST| 2020-12-15 |317 |Purchase |Direct Cost |T00001 |100 |1 000,00 |1 000,00 |No |0 |ITEMNL | -|379 |TEST |**2020-12-15** |317 |Purchase |Revaluation |T04002 |0 |3 000,00 |3 000,00 |No |0 |REVALINL | - -**Item Ledger Entry - negative adjustment, Step 3** - -|Entry No. |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | -|---------|---------|---------|---------|---------|---------|---------|---------| -|318 |TEST |2020-12-20 |Negative Adjmt. |T00002 |-2 |-80 | 0 | - -**Value Entries** - -|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. |Item Number Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies to Entry |Source Code | -|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -|377 |TEST| 2020-12-20 |318 |Negative Adjmt. |Direct Cost |T00002 |-2 |-20 |-20 |No |0 |ITEMNL | -|380 |TEST |**2021-01-01** |318 |Negative Adjmt. |Direct Cost |T04002 |0 |-60 |-60 |Yes |377 |INVTADAMT | - -**Item Ledger Entry - negative adjustment, Step 4** - -|Entry No. |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | -|---------|---------|---------|---------|---------|---------|---------|---------| -|319 |TEST |2021-01-15 |Negative Adjmt. |T00003 |-3 |-120 | 0 | - -**Value Entries** - -|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. |Item Number Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies to Entry |Source Code | -|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -|378 |TEST| 2021-01-15 |319 |Negative Adjmt. |Direct Cost |T00003 |-3 |-30 |-30 |No |0 |ITEMNL | -|381 |TEST |**2021-01-15** |319 |Negative Adjmt. |Direct Cost |T04003 |0 |-90 |-90 |Yes |378 |INVTADAMT | - -The Adjust Cost – Item entries batch job has recognized a change in cost and adjusted the Negative Adjustments. - -**Review of Posting Dates on created adjustment value entries:** The earliest allowed Posting Date the Adjust Cost - Item Entries batch job has to relate to is January 1, 2021 as stated in the General Ledger Setup. - -**Negative Adjustment in step 3:** assigned Posting Date is January 1, provided by General Ledger Setup. The Posting Date of the Value Entry in scope for adjustment is December 20, 2020. According to General Ledger Setup, the date is not within allowed posting date range. Therefore the Posting Date stated in the Allow Posting From field in the General Ledger Setup is assigned to the Adjustment Value Entry. - -**Negative Adjustment in step 4:** assigned Posting Date is January 15. The Value Entry in scope of adjustment has Posting Date January 15, which is within the allowed posting date range according to General Ledger Setup. - -The adjustment made for the Negative Adjustment in step 3 causes discussion. The favorable Posting Date for the Adjustment Value Entry would have been December 20 or at least within December as the revaluation causing the change in COGS was posted in December. +## Common problems with the "Adjust Cost - Item entries"-batch job -To achieve adjustment in December of the Negative Adjustment in step 3, the General Ledger Setup, Allow Posting From field, need to state a date in December. +There are two scenarios that the support team encounters frequently enough for them to warrant their own problem resolution articles. -**Conclusion:** +### Error message: "Posting Date is not within your range of allowed posting dates…" -With the experiences from this scenario, considering most suitable setup of allowed posting date range for a company, you might want to consider the following information: As long as you allow changes in inventory value to be posted in a period, December in this case, the setup that the company uses for allowed posting date ranges should be aligned with this decision. The Allow Posting From in the General Ledger Setup, stating December 1, would allow the revaluation made in December to be forwarded to affected outbound entries in the same period. +If you encounter this error you need to adjust the dates for which the user is allowed to post entries. To learn more, see [Error Message "Posting Date is not within your range of allowed posting dates"](design-details-inventory-adjustment-value-entry-allowed-posting-dates.md). -User groups not allowed to post in December but in January, which was probably intended to be limited by the General Ledger Setup in this scenario, should instead be addressed via the User setup. +### Posting Date on Adjustment Value Entry versus Posting Date on entry causing the adjustment such as Revaluation or Item charge -### Item charge scenario: - - Prerequisites: - - Inventory setup: - -- Automatic Cost Posting = Yes - -- Automatic Cost Adjustment = Always - -- Average Cost Calc. Type = item - -- Average Cost Period = Day - - General Ledger Setup: - -- Allow Posting From = December 1, 2020. - -- Allow Posting To = empty - - User Setup: - -- Allow Posting From = December 1, 2020. - -- Allow Posting to = empty - - -### To test the scenario - -1. Create item charge: - - Base unit of measure = PCS - - Costing Method = Average - - Select optional posting groups. - -2. Create new purchase order - - Buy-from Vendor No.: 10000 - - Posting Date = December 15, 2020 - - Vendor Invoice No.: 1234 - - On the purchase order line: - - Item = CHARGE - - Quantity = 1 - - Direct Unit Cost = 100 - - Post Receive and Invoice. - -3. Create new sales order: - - Sell-to Customer No.: 10000 - - Posting Date = December 16, 2020 - - On the sales order line: - - Item = CHARGE - - Quantity = 1 - - Unit Price = 135 - - Post Ship and Invoice. - -4. General Ledger Setup: - - Allow Posting From = January 1, 2021 - - Allow Posting To = blank - -5. Create new purchase order: - - Buy-from Vendor No.: 10000 - - Posting Date = January 2, 2021 - - Vendor Invoice No.: 2345 - - On the purchase order line: - - Item Charge = JB-FREIGHT - - Quantity = 1 - - Direct Unit Cost = 3 - - Assign Item Charge to Purchase Receipt from step 2. - - Post Receipt and Invoice. - - -**Status Item Ledger Entry of purchase step 2**: - -|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | -|---------|---------|---------|---------|---------|---------|---------|---------| -|324 |CHARGE |2020-12-15 |Purchase |107030 |1 |105 |0 | - -**Value Entries** - -|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | -|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -|397 |CHARGE| 2020-12-15 |324 |Purchase |Direct Cost |108029 | |1 |100 |100 |NO |0 | -|399 |CHARGE |2021-01-02 |324 |Purchase |Direct Cost |108009 |JBFREIGHT |0 |3 |3 |NO |0 | - - -**Status Item Ledger Entry sale**: - -|Entry No. |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | -|---------|---------|---------|---------|---------|---------|---------|---------| -|325 |CHARGE |2020-12-16 |Sale |102035 |-1 |-105 |0 | - -**Value Entries** - -|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | -|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -|398 |CHARGE| 2020-12-16 |325 |Sale |Direct Cost |109024 | |-1 |-100 |-100 |NO |0 | -|400 |CHARGE |2021-01-01 |325 |Sale |Direct Cost |109024 | |0 |-3 |-3 |Yes |398 | - - -6. On work date January 3, a purchase invoice arrives, containing an additional item charge to the purchase made in step 2. This invoice has document date December 30 and is therefore posted with Posting Date December 30, 2020. - - Create new purchase order: - - Buy-from Vendor No.: 10000 - - Posting Date = December 30, 2020 - - Vendor Invoice No.: 3456 - - On the purchase order line: - - Item Charge = JB-FREIGHT - - Quantity = 1 - - Direct Unit Cost = 2 - - Assign Item Charge to Purchase Receipt from step 2 - - Post Receipt and Invoice. - - -**Status Item Ledger Entry of purchase**: - -|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | -|---------|---------|---------|---------|---------|---------|---------|---------| -|324 |CHARGE |2020-12-15 |Purchase |107030 |1 |105 |0 | - -**Value Entries** - -|Entry No. |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | -|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -|397 |CHARGE |2020-12-15 |324 |Purchase |Direct Cost |108029 | |1 |100 |100 |No |0 | -|399 |CHARGE |2021-01-02 |324 |Purchase |Direct Cost |108030 |JBFREIGHT |0 |3 |3 |No |0 | -|401 |CHARGE |**2020-12-30** |324 |Purchase |Direct Cost |108031 |JBFREIGHT |0 |2 |2 |No |0 | - -**Status Item Ledger Entry sale**: - -|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | -|---------|---------|---------|---------|---------|---------|---------|---------| -|325 |CHARGE |2020-12-16 |Sale |102035 |-1 |-105 |0 | - -**Value Entries** - -|Entry No. |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | -|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -|398 |CHARGE |2020-12-16 |325 |Sale |Direct Cost |103024 | |-1 |-100 |-100 |No |0 | -|400 |CHARGE |2021-01-01 |325 |Sale |Direct Cost |103024 | |0 |-3 |-3 |Yes |398 | -|402 |CHARGE |**2021-01-01** |325 |Sale |Direct Cost |103024 | |0 |-2 |-2 |Yes |398 | - -Inventory Valuation report is printed as of Date December 31, 2020 - -![Content of the Inventory Valuation report.](media/helene/TechArticleAdjustcost13.png "Content of the Inventory Valuation report") - - **Summary of scenario:** - - The described scenario ends up with an Inventory Valuation report demonstrating Quantity = 0 while the Value = 2. The Item charge posted in step 11 is part of the Inventory Increase value of December while the Inventory Decrease of the same period is not affected. - - Having the General Ledger Setup stating Allow Posting From January 1 was a good thing for the first Item charge. The costs of the Inventory Increase and Decrease was recorded in the same period. For the second Item charge however, the General Ledger Setup causes the change in COGS to be recognized in the period after. - - **Conclusion:** - - It’s a challenge to have the Inventory Valuation report to demonstrate Quantity = 0 while the Value <> 0. In this case it’s also more difficult to express the optimal settings, having purchase invoices arriving the same day but addressing different periods or even fiscal years. Crossing to a new fiscal year usually requires some planning and as part of that the insight of Adjust Cost – Item entries process, recognizing COGS, is to be considered. - - In this scenario one option could have been to have the General Ledger Setup, field Allow Posting From, stating a date in December for a couple of more days and the posting of the first item charge postponed to allow all costs for the previous period/fiscal year to be recognized for the period they belong to first, having the Adjust Cost – Item entries batch job run and thereafter move the allowed posting date to the new period\/fiscal year. The first item charge with posting date January 2 could then be posted. - -## History of Adjust Cost – Item entries batch job - - Below is a summary of the concept assigning Posting Dates to Adjustment Value Entries by the Adjust Cost – Item entries batch job. - -### About the request form posting date: - - There is no longer a posting date to be stated in the request form of the Adjust Cost - Item entries batch job. The batch job runs through all necessary changes and creates value entries with the posting date of the value entry it adjusts. If the posting date is not within allowed posting date range the posting date in the Allow Posting From field in the General Ledger Setup, OR if the Inventory periods are used, the later date of the two will be used. See described concept above. - -## History of Post Inventory cost to G/L batch job - - The Post Inventory Cost to G/L batch job is closely related to the Adjust Cost – Item entries batch job why the history of this batch job is summarized and shared here as well. - -![Actual cost versus expected cost.](media/helene/TechArticleAdjustcost14.png "Actual cost versus expected cost") - -### About the posting date - - There is no longer a posting date to be stated in the request form of the Post Inventory Cost to G/L batch job. The G/L entry is created with the same Posting Date as the related value entry. In order to complete the batch job, the allowed posting date range must allow the Posting Date of the created G/L entry. If not, the allowed posting date range must be temporarily reopened by changing or removing the dates in the Allow Posting From and To fields in the General Ledger Setup. To avoid reconciliation issues, it is required that Posting Date of the G/L Entry corresponds to the Posting Date of the Value Entry. - - The batch job scans Table 5811 - Post Value Entry to G/L, to identify the Value Entries in scope for posting to General Ledger. After a successful run, the table is emptied. +To learn more, see [Posting Date on Adjustment Value Entry Compared to the Source Entry](design-details-inventory-adjustment-value-entry-source-entry.md). ## See Also [Design Details: Inventory Costing](design-details-inventory-costing.md) [Design Details: Item Application](design-details-item-application.md) - [!INCLUDE[footer-include](includes/footer-banner.md)] diff --git a/business-central/design-details-inventory-adjustment-value-entry-source-entry.md b/business-central/design-details-inventory-adjustment-value-entry-source-entry.md new file mode 100644 index 000000000..52a933465 --- /dev/null +++ b/business-central/design-details-inventory-adjustment-value-entry-source-entry.md @@ -0,0 +1,362 @@ +--- +title: Posting Date on Adjustment Value Entry Compared to the Source Entry +description: Learn about scenario "Posting Date on Adjustment Value Entry versus Posting Date on entry causing the adjustment such as Revaluation or Item charge" when running the Adjust Cost - Item Entries batch job identifies. +author: edupont04 + +ms.service: dynamics365-business-central +ms.topic: conceptual +ms.devlang: na +ms.tgt_pltfrm: na +ms.workload: na +ms.search.keywords: +ms.date: 09/17/2021 +ms.author: edupont + +--- + +# Posting Date on Adjustment Value Entry Compared to the Source Entry + +This article compares the Posting Date on the Adjustment Value Entry with the Posting Date on the entry causing the running of the Adjust Cost - Item Entries batch job, in particular a Revaluation scenario and an Item Charge scenario. + +The **Adjust Cost - Item Entries** batch job will process your data depending on your scenario and configuration of [!INCLUDE[prod_short](includes/prod_short.md)]. In this section, we describe two separate processes, and for each one we show the type of impact the Adjust Cost - Item Entries batch job has on the data. + +## Revaluation scenario + +### Prerequisites + +Please enter the following values: + +**Inventory setup**: + +- Automatic Cost Posting = Yes + +- Automatic Cost Adjustment = Always + +- Average Cost Calc. Type = Item + +- Average Cost Period = Day + +**General Ledger Setup**: + +- Allow Posting From = January 1, 2021 + +- Allow Posting To = Empty + +**User Setup**: + +- Allow Posting From = December 1, 2020 + +- Allow Posting To = Empty + +### To test the scenario + +Test this scenario by carrying out the following steps. + +1. Create an **Item** called TEST with the following values: + + - Base unit of measure = PCS + + - Costing Method = Average + + - Select optional posting groups. + +2. Open an **Item Journal**, then create a new entry, and post a line as follows: + + - Posting Date = December 15, 2020 + + - Item = TEST + + - Entry Type = Purchase + + - Quantity = 100 + + - Unit Amount = 10 + +3. Open an **Item Journal**, then create a new entry, and post a line as follows: + + - Date = December 20, 2020 + + - Item = TEST + + - Entry Type = Negative Adjustment + + - Quantity = 2 + +4. Open an **Item Journal**, then create a new entry, and post a line as follows: + + - Date = January 15, 2021 + + - Item = TEST + + - Entry Type = Negative Adjustment + + - Quantity = 3 + +5. Open an **Item Revaluation Journal**, then create a new entry, and post a line as follows: + + - Item = TEST + + - Applies-to Entry = select Purchase entry posted at step 2. The Posting Date of the revaluation will be the same as the entry it adjusts. + + - Unit Cost (Revalued) = 40 + +The following **Item Ledger** and **Value Entries** have been posted: + +**Item Ledger Entry - purchase**: + +|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | +|---------|---------|---------|---------|---------|---------|---------|---------| +|317 |TEST |2020-12-15 |Purchase |T00001 |100 |4000 |95 | + +**Value Entries** + +|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. |Item Number Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies to Entry |Source Code | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +|376 |TEST| 2020-12-15 |317 |Purchase |Direct Cost |T00001 |100 |1 000,00 |1 000,00 |No |0 |ITEMNL | +|379 |TEST |**2020-12-15** |317 |Purchase |Revaluation |T04002 |0 |3 000,00 |3 000,00 |No |0 |REVALINL | + +**Item Ledger Entry - negative adjustment, Step 3** + +|Entry No. |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | +|---------|---------|---------|---------|---------|---------|---------|---------| +|318 |TEST |2020-12-20 |Negative Adjmt. |T00002 |-2 |-80 | 0 | + +**Value Entries** + +|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. |Item Number Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies to Entry |Source Code | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +|377 |TEST| 2020-12-20 |318 |Negative Adjmt. |Direct Cost |T00002 |-2 |-20 |-20 |No |0 |ITEMNL | +|380 |TEST |**2021-01-01** |318 |Negative Adjmt. |Direct Cost |T04002 |0 |-60 |-60 |Yes |377 |INVTADAMT | + +**Item Ledger Entry - negative adjustment, Step 4** + +|Entry No. |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | +|---------|---------|---------|---------|---------|---------|---------|---------| +|319 |TEST |2021-01-15 |Negative Adjmt. |T00003 |-3 |-120 | 0 | + +**Value Entries** + +|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. |Item Number Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies to Entry |Source Code | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +|378 |TEST| 2021-01-15 |319 |Negative Adjmt. |Direct Cost |T00003 |-3 |-30 |-30 |No |0 |ITEMNL | +|381 |TEST |**2021-01-15** |319 |Negative Adjmt. |Direct Cost |T04003 |0 |-90 |-90 |Yes |378 |INVTADAMT | + +The **Adjust Cost – Item Entries** batch job has recognized a change in cost and adjusted the Negative Adjustments. + +**Review of Posting Dates on created adjustment value entries:** The earliest allowed Posting Date the Adjust Cost - Item Entries batch job has to relate to is January 1, 2021 as stated in the General Ledger Setup. + +**Negative Adjustment in step 3:** assigned Posting Date is January 1, provided by General Ledger Setup. The Posting Date of the Value Entry in the scope for adjustment is December 20, 2020. According to the General Ledger Setup, the date is not within the allowed posting date range. Therefore the Posting Date stated in the Allow Posting From field in the General Ledger Setup is assigned to the Adjustment Value Entry. + +**Negative Adjustment in step 4:** assigned Posting Date is January 15. The Value Entry in scope of adjustment has Posting Date January 15, which is within the allowed posting date range according to General Ledger Setup. + +The adjustment made for the Negative Adjustment in step 3 causes discussion. The favorable Posting Date for the Adjustment Value Entry would have been December 20 or at least within December as the revaluation causing the change in COGS was posted in December. + +To achieve adjustment in December of the Negative Adjustment in step 3, the General Ledger Setup, Allow Posting From field, needs to state a date in December. + +### Conclusion + +With the experience gained in this scenario, when considering the most suitable setup for an allowed posting date range for a company, you might want to consider the following. As long as you allow changes in the inventory value to be posted in a period, such as December in this case, the setup that the company uses for allowed posting date ranges should be aligned with this decision. The Allow Posting From in the General Ledger Setup, stating December 1, would allow the revaluation made in December to be forwarded to affected outbound entries in the same period. + +User groups not allowed to post in December but in January, which was probably intended to be limited by the General Ledger Setup in this scenario, should instead be addressed via the User setup. + +## Item charge scenario + +### Prerequisites + +Please enter the following values: + +**Inventory setup**: + +- Automatic Cost Posting = Yes + +- Automatic Cost Adjustment = Always + +- Average Cost Calc. Type = Item + +- Average Cost Period = Day + +**General Ledger Setup**: + +- Allow Posting From = December 1, 2020. + +- Allow Posting To = Empty + +**User Setup**: + +- Allow Posting From = December 1, 2020. + +- Allow Posting to = Empty + +### To test the scenario + +Test this scenario by carrying out the following steps: + +1. Create an **Item** Charge with the following values: + + - Base unit of measure = PCS + + - Costing Method = Average + + - Select optional posting groups. + +2. Create a new **Purchase Order** with the following values: + + - Buy-from Vendor No.: 10000 + + - Posting Date = December 15, 2020 + + - Vendor Invoice No.: 1234 + + On the Purchase Order Line select the following values: + + - Item = CHARGE + + - Quantity = 1 + + - Direct Unit Cost = 100 + + To complete the step, Post the document as Received and Invoiced. + +3. Create a new **Sales Order** with the following values: + + - Sell-to Customer No.: 10000 + + - Posting Date = December 16, 2020 + + On the Sales Order Line: + + - Item = CHARGE + + - Quantity = 1 + + - Unit Price = 135 + + To complete the step, Post the document as Received and Invoiced. + +4. Enter values for the **General Ledger Setup** page: + + - Allow Posting From = January 1, 2021 + + - Allow Posting To = blank + +5. Create a new **Purchase Order** with the following values: + + - Buy-from Vendor No.: 10000 + + - Posting Date = January 2, 2021 + + - Vendor Invoice No.: 2345 + + On the Purchase Order Line: + + - Item Charge = JB-FREIGHT + + - Quantity = 1 + + - Direct Unit Cost = 3 + + - Assign the Item Charge to the Purchase Receipt from step 2. + + To complete the step, Post the document as Received and Invoiced. + + +**Status Item Ledger Entry of purchase step 2**: + +|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | +|---------|---------|---------|---------|---------|---------|---------|---------| +|324 |CHARGE |2020-12-15 |Purchase |107030 |1 |105 |0 | + +**Value Entries** + +|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +|397 |CHARGE| 2020-12-15 |324 |Purchase |Direct Cost |108029 | |1 |100 |100 |NO |0 | +|399 |CHARGE |2021-01-02 |324 |Purchase |Direct Cost |108009 |JBFREIGHT |0 |3 |3 |NO |0 | + +**Status Item Ledger Entry sale**: + +|Entry No. |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | +|---------|---------|---------|---------|---------|---------|---------|---------| +|325 |CHARGE |2020-12-16 |Sale |102035 |-1 |-105 |0 | + +**Value Entries** + +|Entry Number |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +|398 |CHARGE| 2020-12-16 |325 |Sale |Direct Cost |109024 | |-1 |-100 |-100 |NO |0 | +|400 |CHARGE |2021-01-01 |325 |Sale |Direct Cost |109024 | |0 |-3 |-3 |Yes |398 | + +6. On work date January 3, a purchase invoice arrives containing an additional item charge to the purchase made in step 2. This invoice has document date December 30, and is therefore posted with Posting Date December 30, 2020. + + Create a new **Purchase Order** with the following values: + + - Buy-from Vendor No.: 10000 + + - Posting Date = December 30, 2020 + + - Vendor Invoice No.: 3456 + + On the Purchase Order Line select the following values: + + - Item Charge = JB-FREIGHT + + - Quantity = 1 + + - Direct Unit Cost = 2 + + Assign Item Charge to the Purchase Receipt from step 2 + + To complete the step, Post the document as Received and Invoiced. + + +**Status Item Ledger Entry of purchase**: + +|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | +|---------|---------|---------|---------|---------|---------|---------|---------| +|324 |CHARGE |2020-12-15 |Purchase |107030 |1 |105 |0 | + +**Value Entries** + +|Entry No. |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +|397 |CHARGE |2020-12-15 |324 |Purchase |Direct Cost |108029 | |1 |100 |100 |No |0 | +|399 |CHARGE |2021-01-02 |324 |Purchase |Direct Cost |108030 |JBFREIGHT |0 |3 |3 |No |0 | +|401 |CHARGE |**2020-12-30** |324 |Purchase |Direct Cost |108031 |JBFREIGHT |0 |2 |2 |No |0 | + +**Status Item Ledger Entry sale**: + +|Entry Number |Item No. |Posting Date |Entry Type |Document No. |Quantity |Cost Amount (Actual) |Remaining Quantity | +|---------|---------|---------|---------|---------|---------|---------|---------| +|325 |CHARGE |2020-12-16 |Sale |102035 |-1 |-105 |0 | + +**Value Entries** + +|Entry No. |Item No. |Posting Date |Item Ledger Entry No. |Item Ledger Entry Type |Entry Type |Document No. | Item Charge No. | Item Ledger Entry Quantity |Cost Amount (Actual) |Cost Posted to G/L |Adjustment |Applies-to Entry | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +|398 |CHARGE |2020-12-16 |325 |Sale |Direct Cost |103024 | |-1 |-100 |-100 |No |0 | +|400 |CHARGE |2021-01-01 |325 |Sale |Direct Cost |103024 | |0 |-3 |-3 |Yes |398 | +|402 |CHARGE |**2021-01-01** |325 |Sale |Direct Cost |103024 | |0 |-2 |-2 |Yes |398 | + +Inventory Valuation report is printed as of Date December 31, 2020 + +![Content of the Inventory Valuation report.](media/helene/TechArticleAdjustcost13.png "Content of the Inventory Valuation report") + +**Summary of scenario:** + +The described scenario ends up with an Inventory Valuation report demonstrating Quantity = 0 while the Value = 2. The Item charge posted in step 6 is part of the Inventory Increase value of December while the Inventory Decrease of the same period is not affected. + +Having the General Ledger Setup stating Allow Posting From January 1 was a good thing for the first Item charge. The costs of the Inventory Increase and Decrease was recorded in the same period. For the second Item charge however, the General Ledger Setup causes the change in COGS to be recognized in the period after. + +**Conclusion:** + +It is a challenge to get the Inventory Valuation report to demonstrate Quantity = 0 while the Value <> 0. In this case it is also more difficult to express the optimal settings, having purchase invoices arriving the same day but addressing different periods or even fiscal years. Crossing to a new fiscal year usually requires some planning and as part of that the insight into Adjust Cost – Item entries process, recognizing COGS, is to be considered. + +In this scenario one option could have been to have the General Ledger Setup, field Allow Posting From, stating a date in December for a couple of more days and the posting of the first item charge postponed to allow all costs for the previous period/fiscal year to be recognized for the period they belong to first, having the Adjust Cost – Item entries batch job run and thereafter move the allowed posting date to the new period\/fiscal year. The first item charge with posting date January 2 could then be posted. + +## See Also + +[Design Details: Posting Date on Adjustment Value Entry](design-details-inventory-adjustment-value-entry-posting-date.md) +[Design Details: Inventory Costing](design-details-inventory-costing.md) +[Design Details: Item Application](design-details-item-application.md) + +[!INCLUDE[footer-include](includes/footer-banner.md)] From fe73ce187814419b26fcd775bc861ffe63955201 Mon Sep 17 00:00:00 2001 From: Brent Holtorf Date: Mon, 20 Sep 2021 17:17:01 +0200 Subject: [PATCH 2/2] removed list of extensions --- business-central/ui-extensions.md | 26 -------------------------- 1 file changed, 26 deletions(-) diff --git a/business-central/ui-extensions.md b/business-central/ui-extensions.md index 9008974c7..b0ccace3a 100644 --- a/business-central/ui-extensions.md +++ b/business-central/ui-extensions.md @@ -49,32 +49,6 @@ If you uninstall an extension, and you then change your mind, you can install it Some extensions are provided by Microsoft, and other extensions are provided by [other companies](ui-extensions-other.md). All extensions are tested before they are made available to you, but we recommend that you access the links that are provided with each extension to learn more about the extension before you choose to install it. -Microsoft provides the following extensions: - -* [AMC Banking 365 Fundamentals Extension](ui-extensions-amc-banking.md) -* [Ceridian Payroll](ui-extensions-ceridian-payroll.md) -* [Company Hub](ui-extensions-company-hub.md) -* [Dynamics GP Data Migration](ui-extensions-dynamicsgp-data-migration.md) -* [Envestnet Yodlee Bank Feeds](ui-extensions-yodlee-bank-feeds.md) -* [Essential Business Insights](ui-extensions-essential-business-insights.md) -* [Image Analyzer](ui-extensions-image-analyzer.md) -* [Intelligent Cloud](ui-extensions-data-replication.md) -* [Intelligent Cloud Base](ui-extensions-intelligent-cloud.md) -* [Late Payment Predictions](ui-extensions-late-payment-prediction.md) -* [Microsoft Pay](ui-extensions-microsoft-pay-payments.md) -* [PayPal Payments Standard](ui-extensions-paypal-payments-standard.md) -* [QuickBooks Data Migration](ui-extensions-quickbooks-data-migration.md) -* [QuickBooks Online Data Migration](ui-extensions-quickbooks-online-data-migration.md) -* [Quickbooks Payroll File Import](ui-extensions-quickbooks-payroll.md) -* [Sales and Inventory Forecast](ui-extensions-sales-forecast.md) -* [VAT Group](ui-extensions-vat-group.md) -* [WorldPay Payments Standard](ui-extensions-worldpay-payments-standard.md) -* [DK - C5 Data Migration](ui-extensions-c5-data-migration.md) -* [DK - Payments and Reconciliations](ui-extensions-payments-reconciliation-formats-dk.md) -* [DK - Tax File Formats](ui-extensions-tax-file-formats-dk.md) -* [The GetAddress.io UK Postcodes Extension](LocalFunctionality/UnitedKingdom/ui-extensions-getaddressio.md) -* [US/CA/UK/AU/NZ/ZA - Send Remittance Advice](ui-extensions-send-remittance-advice.md) - > [!NOTE] > You can keep an eye out for new extensions from Microsoft and other suppliers at [AppSource.microsoft.com](https://appsource.microsoft.com/marketplace/apps?product=dynamics-365%3Bdynamics-365-business-central&page=1).