Monika Kowalka ESCAL ENG

Bank - Exchange Adjustment (FIFO and LIFO) count exchange adjustment on the Bank accounts according to polish requirements.

Sometimes, there are transactions that shoudl not be taken into account and are excluded (overnight deposits etc)

Unfoetunetelly, if user make a mistake and run it, there is no possibility to reverse such exchange adjustment.

IN Dynamics 365 there is a possibility to reverse different types of transactions and reversal features are coming in next releases.

So we shoudl improve as well localization part and give a chance to reverse FIFO/LIFO exchange adjustment.

Please note that 'recalculation' is not always an option.

Hi,

Under ID 620564 - we have released a XML format for VAT EU for Poland, but we did not cover correction format.

Details for issue 620564 (dynamics.com)

So, please also consider to support correction of VAT EU

If we add a column where the book code is set to Budget control, there is no possibility to view transaction details and jump to budget control statistic form.

On Actual column it will drill down to ledger account transactions on Budget it will open budget entries form.

Thanks,

Please consider supporting below scenarios for report "Report sales tax for settlement period" (Sales tax (Itay)):

Scenario 1

[ITA] Customer is using the functionality of Invoice register and Invoice pool in an Italian legal entity.

Register and pool are processed on the same date and the same voucher.

Once the user runs Sales tax book report it is showing wrong base amount and tax amount (doubled).

Scenario 2

[ITA] Customer is using the functionality of Invoice register and Invoice Approval in an Italian legal entity. It might happen that the invoice approval is done in the next month, while the previous month is “on hold”. In this scenario, invoice approval is posted with a different voucher than the invoice registers and it is not shown in the sales tax book report.

Split payment rules cannot be set for procurement category

If Customer use pending vendor invoices with procurement category, for which we cannot use split payment item group to minimize the rule to specific items/services. 

If we just put threshold, it will be for ALL above the amount which is not true as the rule should be limited to specific services (or items)

Split payment item group is only for products - with type item or service, but procurement category is not there. 

Report fixed asset roll forward cannot be used for entities that have specific transaction types, i.e. for Poland/Czech where we have pre acquisition or OB depreciation transaction type.

This was reported under:

Details for issue 675780 (dynamics.com)

Details for issue 573222 (dynamics.com)

with the information that this is standard report and Customer can customize this thru GER, but that's not possible because data are retrieved by the class\AssetRollForwardDP which ignores country-specific transaction type.

This request is valid not only for Poland or Czech companies, but as well for all international companies that need to create consolidated reports for HQ.

All transaction types should be included like on the Valuation card or other fixed asset reports.

Hi,

Please enable - Revaluate foreign currency for advance holders (Russia) for Poland, as the advance holders in general are already available for Poland.

Revaluate foreign currency for advance holders (Russia) - Finance | Dynamics 365 | Microsoft Docs

Company uses the functionality “royalty contract management” and 'broker contract management' across different entities and want to use it as well in Polish entity but cannot post the vendor invoice due to mandatory “receive document date” during royalty claim /broker claim processing or sales order invoicing (if the claim does not require approval).

Error:

In order XXX Receive document date is not specified

Posting of order canceled

This has been reports under but Rejected for fixing:

Details for issue 752345 (dynamics.com)

Details for issue 757357 (dynamics.com)

Settle and post sales taxes does not consider the functionality “Vat report date codes” and cause that the company pay wrong taxes.

Issue was escalated under ID 756139 but it was rejected for now due to fact that the 'vat report date codes' were never supported by the "sales tax payment"

Link to LCS: Details for issue 756139 (dynamics.com)