Merge pull request #1398 from MicrosoftDocs/master

Doc refresh

Author: jswymer

business-central/LocalFunctionality/Czech/best-practices.md

@@ -1,6 +1,6 @@
 ---
-title: Czech Local Functionality - Small Regulatory Features and Best Practices | Microsoft Docs
-description: This section describes local functionality - Small Regulatory Features and Best Practices
+title: Small Regulatory Features and Best Practices in the Czech Version
+description: Learn about built-in support for best practices and small regulatory features in the Czech version of Business Central.
 author: ACMartinKunes
 
 ms.service: dynamics365-business-central
@@ -11,7 +11,7 @@ ms.reviewer: v-pejano
 ms.author: v-pejano
 ---
 
-# Small Regulatory Features and Best Practices
+# Small Regulatory Features and Best Practices in the Czech Version
 
 Smaller regulatory features and local practices of Czech companies include the following features:
 - G/L account groups – for multi-circuit accounting

business-central/LocalFunctionality/Denmark/oioubl-electronic-invoicing-overview.md

@@ -1,6 +1,6 @@
 ---
     title: OIOUBL Electronic Invoicing Overview | Microsoft Docs
-    description: Companies must send sales invoices, credit memos, finance charge memos, and reminders to the Danish public sector electronically in the Offentlig Information Online UBL (OIOUBL) format. If a company does not send these documents electronically, the authorities can deny payment.
+    description: Learn about how Business Central support you in the requirement for sending sales documents to the Danish public sector electronically in the OIOUBL format.
     author: edupont04
 
     ms.service: dynamics365-business-central

business-central/LocalFunctionality/Denmark/ui-extensions-oioubl.md

@@ -1,6 +1,6 @@
 ---
-    title: OIOUBL Extension for Electronic Invoicing | Microsoft Docs
-    description: This extension makes it easy to send electronically send sales and service invoices, credit memos, finance charge memos, and reminders to customers in the Danish public sector in an Offentlig Information Online UBL (OIOUBL) format.
+    title: OIOUBL Extension for Electronic Invoicing
+    description: This extension makes it easy to send sales documents electronically to customers in the Danish public sector in the OIOUBL format.
     author: bholtorf
 
     ms.service: dynamics365-business-central

business-central/LocalFunctionality/Finland/how-to-print-vat-information-on-invoices.md

@@ -26,10 +26,10 @@ You can use posting groups to print VAT information for each item on the sales i
 3.  Select **Print VAT info on Invoice** to print the VAT information for each item on the respective sales invoice.  
 4.  Create and post a sales invoice. Choose the **Preview** button to review the invoice and verify that it contains VAT information for each row from the posting group.  
 
-## See Also  
- [Electronic Banking in Finland](electronic-banking-in-finland.md)  
- [Setting Up Posting Groups](../../finance-posting-groups.md)   
- [Setting Up Value-Added Tax](../../finance-setup-vat.md)
+## See Also
 
+[Electronic Banking in Finland](electronic-banking-in-finland.md)  
+[Set Up Posting Groups](../../finance-posting-groups.md)  
+[Set Up Calculations and Posting Methods for Value-Added Tax](../../finance-setup-vat.md)  
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

business-central/LocalFunctionality/Germany/how-to-export-and-print-intrastat-reports.md

@@ -1,6 +1,6 @@
 ---
-    title: How to Export and Print Intrastat Reports
-    description: Intrastat reporting is required throughout the European Union (EU) and must follow local requirements, such as specific formats and files. All companies in the EU must report their trade with other EU countries.
+    title: Export and Print Intrastat Reports (DE)
+    description: Business Central supports Intrastat reporting according to German requirements. You can meet the requirement to report your trade with other EU countries.
     author: SorenGP
 
     ms.service: dynamics365-business-central

business-central/LocalFunctionality/Germany/how-to-issue-delivery-reminders.md

@@ -1,6 +1,6 @@
 ---
     title: Issue Delivery Reminders in the German Version
-    description: After you have created delivery reminders, you must issue and print them so that you can send reminders to vendors in the German version. Before you issue the delivery reminders, you can print a test report.
+    description: Read about how you issue and print delivery reminders so that you can send reminders to vendors in the German version of Business Central.
     author: SorenGP
 
     ms.service: dynamics365-business-central

business-central/TOC.md

@@ -110,6 +110,7 @@
 #### [Set Up Reminder Terms and Levels](finance-setup-reminders.md)
 #### [Set Up Finance Charge Terms](finance-setup-finance-charges.md)
 #### [Set Up Value-Added Tax (VAT)](finance-setup-vat.md)
+#### [Set Up Calculations and Posting Methods for Value-Added Tax (VAT)](finance-setup-vat.md)
 #### [Set Up Unrealized VAT for Cash-Based Accounting](finance-setup-unrealized-vat.md)
 #### [Validate VAT Registration Numbers](finance-how-validate-vat-registration-number.md)
 #### [Setting Up Source Codes and Reason Codes for Audit Trails](finance-setup-trail-codes.md)
@@ -1535,14 +1536,15 @@
 
 # Security, Privacy, Compliance
 ## Security and Protection
-### [Security and Protection Overview](/dynamics365/business-central/dev-itpro/security/security-and-protection?toc=/dynamics365/business-central/toc.json)
+### [Security and Protection Overview (in English only)](/dynamics365/business-central/dev-itpro/security/security-and-protection?toc=/dynamics365/business-central/toc.json)
 ## Privacy
 ### [Privacy (microsoft.com)](https://www.microsoft.com/en-us/trust-center/privacy)
 ## Compliance
 ### [Compliance Overview](compliance/compliance-overview.md)
 ### [Application Compliance](compliance/compliance-application-compliance.md)
 ### [Service Compliance](compliance/compliance-service-compliance.md)
 ### [Certifications](compliance/compliance-certifications.md)
+## [Service Overview (in English only)](/dynamics365/business-central/dev-itpro/service-overview?toc=/dynamics365/business-central/toc.json)
 
 # Development and Administration
 ## [Get started with development and administration documentation](/dynamics365/business-central/dev-itpro/index?toc=/dynamics365/business-central/toc.json)

business-central/across-working-with-powerbi.md

@@ -34,7 +34,7 @@ If you're using [!INCLUDE[prod_short](includes/prod_short.md)] on-premises, it m
 
 Sign up for the Power BI service. If you haven't already signed up, go to [https://powerbi.microsoft.com](https://powerbi.microsoft.com). When you sign up, use your work email address and password.
 
-## Connect to Power BI - one time only
+## <a name="connect"></a>Connect to Power BI - one time only
 
 When you first sign into [!INCLUDE [prod_short](includes/prod_short.md)], you might see an empty Power BI part on some page, as shown in the previous figure. The first thing to do is to connect to your Power BI account. Once connected, you can see reports. You only have to do this step once.
 
@@ -47,7 +47,7 @@ During the connecting process, [!INCLUDE [prod_short](includes/prod_short.md)] c
 
 ##### From [!INCLUDE [prod_short](includes/prod_short.md)] on-premises
 
-Connecting to Power BI from [!INCLUDE [prod_short](includes/prod_short.md)] is similar to online. However, you'll be prompted on the **AZURE ACTIVE DIRECTORY SERVICE PERMISSIONS** page to grant access to Power BI Services. To grant access, select **Authorize Azure Services**, and then **Accept**.
+Connecting to Power BI from [!INCLUDE [prod_short](includes/prod_short.md)] is similar to online. However, you might be prompted on the **AZURE ACTIVE DIRECTORY SERVICE PERMISSIONS** page to grant access to Power BI Services. To grant access, select **Authorize Azure Services**, and then **Accept**.
 
 Once connected, you can select a report from the Power BI part on pages.
 

business-central/admin-cds-missing-option-values.md

@@ -14,9 +14,11 @@ ms.date: 10/01/2020
 # Handling Missing Option Values
 [!INCLUDE[prod_short](includes/cc_data_platform_banner.md)]
 
-[!INCLUDE[prod_short](includes/cds_long_md.md)] contains only three option set fields that contain option values that you can map to [!INCLUDE[prod_short](includes/prod_short.md)] fields of Option type<!-- Option type, not enum? @Onat can you vertify this? --> for automatic synchronization. During synchronization, non-mapped options are ignored and the missing options are appended to the related [!INCLUDE[prod_short](includes/prod_short.md)] table and added to the **CDS Option Mapping** system table to handle manually later. For example, by adding the missing options in either product and then updating the mapping. This section describes how that works.
+This topic is intended for a technical audience. The processes it describes require the help of a developer.
 
-The **Integration Table Mapping** page contains three maps for fields that contain one or more mapped option values. After a full synchronization, the **CDS Option Mapping** page contains the non-mapped options in the three fields respectively.
+[!INCLUDE[prod_short](includes/cds_long_md.md)] contains three option set fields that contain values that you can map to [!INCLUDE[prod_short](includes/prod_short.md)] fields of the Option type for automated synchronization. During synchronization, non-mapped options are ignored and the missing options are appended to the related [!INCLUDE[prod_short](includes/prod_short.md)] table and added to the **Dataverse Option Mapping** system table to handle manually later. For example, by adding the missing options in either product and then updating the mapping.
+
+The **Integration Table Mapping** page contains three fields that contain one or more mapped option values. After a full synchronization, the **Dataverse Option Mapping** page contains the non-mapped options in the three fields.
 
 |         Record             | Option Value | Option Value Caption |
 |----------------------------|--------------|----------------------|
@@ -34,7 +36,7 @@ The **Integration Table Mapping** page contains three maps for fields that conta
 | Shipping Agent: FULLLOAD   | 6            | Full Load            |
 | Shipping Agent: WILLCALL   | 7            | Will Call            |
 
-The content of the **CDS Option Mapping** page is based on enum values in the **CDS Account** table. In [!INCLUDE[prod_short](includes/cds_long_md.md)], the following fields on the account table are mapped to fields on the customer and vendor records:
+The content of the **Dataverse Option Mapping** page is based on enum values in the **CRM Account** table. In [!INCLUDE[prod_short](includes/cds_long_md.md)], the following fields on the account table are mapped to fields on the customer and vendor records:
 
 - **Address 1: Freight Terms** of data type Enum, where values are defined as follow:
 
@@ -52,7 +54,6 @@ enum 5335 "CDS Shipment Method Code"
 
 ```
 enum 5336 "CDS Shipping Agent Code"
-enum 5336 "CDS Shipping Agent Code"
 {
     Extensible = true;
     value(0; " ") { Caption = ' '; }
@@ -107,7 +108,7 @@ enumextension 50100 "CDS Payment Terms Code Extension" extends "CDS Payment Term
 ### Update [!INCLUDE[prod_short](includes/cds_long_md.md)] Option Mapping
 Now you can recreate the mapping between [!INCLUDE[prod_short](includes/cds_long_md.md)] options and [!INCLUDE[prod_short](includes/prod_short.md)] records.
 
-On the **Integration Table Mapping** page, choose the line for the **Payment Terms** map, and then choose the **Synchronize Modified Records** action. The **CDS Option Mapping** page is updated with the additional records below.
+On the **Integration Table Mapping** page, choose the line for the **Payment Terms** map, and then choose the **Synchronize Modified Records** action. The **Dataverse Option Mapping** page is updated with the additional records below.
 
 |         Record                 | Option Value   | Option Value Caption |
 |--------------------------------|----------------|----------------------|
@@ -118,7 +119,7 @@ On the **Integration Table Mapping** page, choose the line for the **Payment Ter
 | **Payment Terms: CASH PAYME**  | **779800001**  | **Cash Payment**     |
 | **Payment Terms: TRANSFER**    | **779800002**  | **Transfer**         |
 
-The **Payment Terms** table in [!INCLUDE[prod_short](includes/prod_short.md)] will then have new records for the [!INCLUDE[prod_short](includes/cds_long_md.md)] options. In the following table new options are in bold font . Italic rows represent all options that can now be synchronized. Remaining rows represent options are not in use and will be ignored during synchronization. You can remove them or extend CDS options with the same names.)
+The **Payment Terms** table in [!INCLUDE[prod_short](includes/prod_short.md)] will then have new records for the [!INCLUDE[prod_short](includes/cds_long_md.md)] options. In the following table new options are in bold font . Italic rows represent all options that can now be synchronized. Remaining rows represent options are not in use and will be ignored during synchronization. You can remove them or extend Dataverse options with the same names.)
 
 | Code       | Due Date Calculation | Discount Date Calculation | Discount % | Calc. Pmt. Disc. on Cr. Memos | Description       |
 |------------|----------------------|---------------------------|------------|-------------------------------|-------------------|

business-central/admin-manage-documents.md

@@ -43,7 +43,13 @@ You can compress the following types of data in [!INCLUDE [prod_short](includes/
   After the compression, with the **Retain Field Contents** facility, you can retain the contents of the **Document No., Our Contact**, **Global Dimension 1 Code**, and **Global Dimension 2 Code** fields.
 * Vendor ledger entries
 
-  After the compression, the contents of the following fields are always retained: **Posting Date**, **Vendor No.**, **Document Type**, **Currency Code**, **Posting Group**, **Amount**, **Remaining Amount**, **Original Amt. (LCY)**, **Remaining Amt. (LCY)**, **Amount (LCY)**, **Purchase (LCY)**, **Inv. Discount (LCY)**, **Pmt. Disc. Given (LCY)**, and **Pmt. Disc. Possible**.
+> [!NOTE]
+> Compressed entries for customers, vendors, bank, and FA subledgers are posted slightly differently than standard posting. This is to reduce the number of new general ledger entries created by date compression, and is especially important when you keep information such as dimensions and document numbers. Date compression creates new entries as follows:
+>* On the **General Ledger Entries** page, new entries are created with new entry numbers for the compressed entries. The **Description** field contains **Date Compressed** so that the compressed entries are easy to identify. 
+>* On ledger pages, such as the **Customer Ledger Entries** page, one or more entries are created with new entry numbers. 
+> The posting process creates gaps in the number series for entries on the **General Ledger Entries** page. Those numbers are assigned to the entries on the ledger pages only. The number range that was assigned to the entries is available on the **G/L Register page**  in the **From Entry No.** and **To Entry No.** fields. 
+
+After the compression, the contents of the following fields are always retained: **Posting Date**, **Vendor No.**, **Document Type**, **Currency Code**, **Posting Group**, **Amount**, **Remaining Amount**, **Original Amt. (LCY)**, **Remaining Amt. (LCY)**, **Amount (LCY)**, **Purchase (LCY)**, **Inv. Discount (LCY)**, **Pmt. Disc. Given (LCY)**, and **Pmt. Disc. Possible**.
 
   With the **Retain Field Contents** facility, you can also retain the contents of these additional fields: **Document No.**, **Buy-from Vendor No.**, **Purchaser Code**, **Global Dimension 1 Code**, and **Global Dimension 2 Code**.