Dynamics 365 Finance

The idea I would like to present is to prevent the error message from appearing when attempting to post a correction with the "Credit Correction" option selected and with posting validation configured on the credit side. The error appears when, in the General ledger > Chart of accounts > Accounts > Main accounts, I configure the account used for revenue posting to allow only credit postings. Setting this validation helps ensure that the system prevents posting transactions on the debit side, which is beneficial for maintaining data integrity. Next, when I attempt to create a credit note (invoice correction), I go to the Invoice tab in the top menu, then select Cancel > Create credit note. A form appears where I select the invoice to be corrected and check the Create credit note lines option. After confirming the form with the OK button, I proceed to post the invoice with the Credit Correction option selected. przetłumacz na polski At this point, upon clicking OK, the following error message appears: "The main account on combination (general ledger account) is set up to be used only for credit transactions. You must select a main account that is set up only for debit transactions, or that has no debit or credit requirements." However, according to Polish regulations, the Credit Correction option is intended to post the correction on the same side as the original transaction. Therefore, this error is problematic, as it incorrectly suggests that the system is attempting to post on the debit side, which is not the case.

Thanks,

Regards,

Rafał

Idea Summary:

In Microsoft Dynamics 365 Finance and Operations, within the Advanced Bank Reconciliation functionality, the matching rules allow users to perform automatic actions such as "Generate Voucher." However, when using this action type, it is currently not possible to input or assign a financial tag (also known as a financial dimension tag).

Proposed Enhancement:

Extend the capabilities of the "Generate Voucher" action in reconciliation matching rules to allow users to specify a financial tag. This would ensure that vouchers generated during reconciliation are properly classified and aligned with financial reporting requirements.

Business Value:

• Improved accuracy in financial reporting through better tagging and classification of generated vouchers.
• Enhanced automation by reducing the need for manual voucher adjustments post-reconciliation.
• Consistency in financial tagging across all types of transactions, including those created automatically via reconciliation rules.

Use Case:

A company that uses financial tags extensively for internal reporting needs to ensure that all transactions, including automatically generated vouchers during bank reconciliation, carry the correct tag.

Suggested Implementation:

• Add the Financial Tag field as an editable input option when configuring the “Generate Voucher” action within the reconciliation matching rule setup.
• Ensure this tag is applied to the resulting voucher transactions.

When lines are generated from the budget plan import, the system does not automatically perform a budget check. Currently, the system runs budget checks correctly only when the lines are entered manually.

With the current system behavior, the withholding tax amount is currently deducted from the payment. However, as per legal requirement in Australia referencing Documents quoting supplier's ABN | Australian Taxation Office, withholding tax should be calculated and recorded into the system based on gross amount of payment. 

For instance, Vendor A issues an invoice for 100 AUD with a 5% WHT for Buyer B. When making the payment, Buyer B pays Vendor A the full 100 AUD and 5 AUD to the tax authority. This means the 5 AUD withholding liability is recorded as a WHT expense. The offset account for the journal should be Accounts Payable to Tax Authority, to be settled by the end of the month. 

It should be possible to import a return file that contains payments for several legal entities. This was possible until version 10.0.35 (update 831854).

Now, when importing a return file that contains payments for several legal entities, the file can be imported into one company, but fails in all the others. The file must either be split manually to be able to import it in the other companies, or the payments must be manually updated.

When printing Vendor payment advice with Use print management and Batch processing enabled, the system throws the following confusing warning message:

“A report running in batch can't print to the screen. Screen output will be automatically sent to the print archive instead”

Although the report is sent to the correct destination setup in Print management, users still receive a message that the report cannot be printing to the destination showed in the report dialog

With the new Customer prepayment feature it should be possible, that if the customer pays only a partial amount of the prepayment invoice, to apply this in the Sales order invoice.

What we expect:

We should have the possibility

• to correct the first prepayment invoice
• to apply the real payment in the sales order

Suggested solution 1:

When the partial Payment is settled with the prepayment invoice

• the old Prepayment Invoice should be reversed
• a new prepayment invoice will be automatically generated in the amount of the real payment.
• In all steps the tax should be corrected.
• The corrected prepayment invoice should be available in the sales order invoice

Suggested solution 2:

When we post the sales order invoice we wish to have an automatically reverse of the first prepayment invoice and creation of the new prepayment invoice with the paid amount. And in this way the tax should also be corrected.

Right now, there's only a duty available to Maintain vendor master. This includes:

• Maintaining vendor details
• Create/Update/Delete Vendor bank accounts
• Submit Vendor bank account changes for approval
• Approve Vendor bank account changes

This is not SOx compliant! Approval should be moved to a separate duty and privilege for approval of vendor bank accounts. Auditors currently indicate this risk with a high severity level, as employees are able to fill in their private bank account details, without anyone noticing or checking these modifications.

When the automatic ledger settlement is enabled, a debit transaction and a credit transaction can be automatically matched only if their amounts in the accounting currency are equal. A debit amount of $1.00 can be automatically matched to a credit amount of $1.00. However, a debit value of $1.00 can't be automatically matched to two credits, each of which is valued at $0.50.

The improvement would be that, when the total of the account is 0 (respecting the rules of the setup), the system would settle all the transactions into one.