Public Profile
  • France: ISO20022 Credit transfer - Structured payment information

    French banking organization and standardization committee (CFONB) recommendation is to use Unstructred payment information for payments based on pain.001 format. The current design of generating pain.001 files in Operations is based on this recommendation. The suggestion here is to allow user to choose wheather to use Structured or Unstructed payment information when generating the paymen file. If structured is chosen and the payment id is available, the payment id is transferred to the payment file as Structured payment information.

  • Deposit slip function for vendors

    User should be able to summarize vendor payment transactions in the same way as user can do for customer payments. On the customer side the feature is called Deposit slip. Deposit slip - see https://docs.microsoft.com/en-us/dynamics365/unified-operations/financials/accounts-receivable/tasks/deposit-customer-payments.

  • Generating payments for multiple bank accounts

    Company may have more than one bank account in the same bank. User should be able to generate one payment file including different debit bank accounts. ISO20022 Credit Transfer format accepts this. However, in Finance & Operations user is not able to leave the field Bank account blank in order get all payments for different company bank accounts empty to get all payments included in the payment file. Suggestion: user is able leave the field for bank account blank when generating payment file(s) and get payments from different bank accounts transferred to the payment file.
  • ISO20022 Credit transfer for customer payments

    ISO20022 credit transfer is implemented for vendor payments in Dynamics Finance. User must be able to generate payment file for payments to customers. We need ISO20022 file format for customer payments. Reimbursement feature is not designed for scenarios where paying back to customers is part of ordinary business routines instead of one time action.

  • Norway SAF-T (NO) GL accounts mapping to Income statement (Næringslivskoder)

    Options for mapping of Accounts and mapping of VAT codes The mapping of The Chart of Accounts must be by choice of one of the following: - The SAF-T Financial Standard Accounts (2 or 4 digit). - The Income Statement for the type of business. For municipalities, the mapping of the accounts must be to the KOSTRA Arts accounts. For Norwegian Governmental State Enterprises, the mapping must be to the standard accounts (2 or 4 digit). These enterprises uses a standard accounting plan that is similar. Source: https://www.skatteetaten.no/globalassets/bedrift-og-organisasjon/starte-og-drive/rutiner-regnskap-og-kassasystem/saf-t-regnskap/norwegian-saf-t-financial-data---documentation.pdf The feature in Finance & Operations - SAF-T (NO) - supports only the mapping to Standard accounts and does not include the feature for mapping General ledger accounts to Income statement (Næringslivskoder). The feature should include also this missing mapping.

  • Sales tax reconciliation report repeats purchase invoice transactions per Project funding source

    Setup project contract with more than one funding source with corresponding allocation rule Register and post purchase invoice on the project Run Sales tax reconciliatin report Actual result Same base for sales tax and tax is reported as many times as there are funding sources Expected result Base and sales tax amount is the same as posted purchase invoice.
  • Denmark: Multiple EAN numbers on Danish customer

    A Danish customer is set up to receive OIOUBL invoice (eInvoice=YES) and Main EAN number is entered on customer as well as TAX exempt number


    However, the customer is University and have several EAN numbers and one Tax Exempt number, so user must be able to register more than one EAN number for the customer.


    User must be able to select the EAN number when registering and posting the invoice. The EAN value must be stored and fetched from invoice header when generating the eInvoice file.