Alireza Eshaghzadeh Business Consultant

One collect customer payment file (Camt.054) from net bank and import in Customer Payment journal. Sometimes the payment file that be generated from net bank does not contain just customer payment. If it is related to a project (e.g. Interest from a project and actually it is not customer payment), one can choose the account type 'Project' and enter "Category" to post the payment against the project. It would be great that one can post direct to project in customer payment journal so it would be no need to post against a dummy ledger account and clear the dummy account to project. Per today, One can post customer payment journal for Customer, Vendor, Ledger, Bank and Fixed asset but not Project.

It seems that credit note invoice (Sales and Projects) lacks bank account information that is related to the company (Organisation administration > Legal entities > Bank account information > Bank account). Lacking bank account numbers on the credit note in the xml causes that the financial systems (i.e. for customer) do not get hits on the correct supplier as they often take control of the organization number and account number. Thus, the credit notes that lack the account number in a manual step to find the correct supplier. Although the creditnote E-Invoice verified via VEFA Validator in Norway for PEPPOL BIS Billing 3.0, Norwegain customer desire to get bank account information as well as sales invoices in order to pave the way for payment and reconciliation and reduces confusion for payment. The latest OIOUBL Sales credit note from Microsoft repository (version 50.14) does not have any tagging for cac:PaymentMeans.

It is normal to differentiate project fees on different activities on fee journals while we do have not this possibility on free text invoices when we want to post against a project. In Dynamics 365 Finance & Operations, on Free text invoice 'Line detail', we can just choose 'Project' and 'Project category' and NOT 'Activity. It would be great if 'Activity' could be added to the Free Text invoice 'Line detail' when a user wants to post a Free Text invoice against a project. At the same time, it is desired that posted free text invoices (with activity), can be shown in Project posted transactions with project, project category, and activity.

Ref. to article "https://docs.microsoft.com/en-us/dynamics365/finance/general-ledger/one-voucher" , It seems that Microsoft did not take Norway localization needs into consideration. Norwegian companies must apply Norwegian accounting practice in their business routines. In this regard, they must use one-voucher for several purposes. We have listed out some of them as follows:

1-Payments in / out We sum up deposits and payments per. file received as the number of payments is many and the amount must correspond to the amounts the bank delivers on bank statements. As an example a customer which has thousands of payments per. day and many hundreds of payments per. day.

2-One-voucher prevents posting of vouchers such as incoming invoice against several postings. One voucher does provide the opportunity to split an posting of incoming invoices on several project categories or several projects, several fixed assets, etc. This happens quite often with our customers. This should/must be taken into consideration that companies using Project Management & Accounting must be able to split the invoice amount into several projects. One cannot expect the vendor to split invoices pr. project that are supposed to "share" the invoice amount. They have not necessarily the knowledge of how their customer will do the accounting. This is also a relevant scenario on Fixed Assets. Example is an invoice regarding 100 computers, where each and one of them are supposed to be separate assets. The ability to split vendor invoices must kept for several sub-ledgers

3-Some customers used One-Voucher on the old ERP solution that they had and the ERP solution that they have right now. Example that is common in the shipping industry: the need to post to both customer and supplier on the same document: D customer, K supplier, K finance.

4-Accruals and periodic journal are common routines that are done with One-Voucher

5-Customers which have moved from AX2009 and AX2012 to D365FO, They still use One-Voucher according to their business routines.

6-Several integrations are built up according to One-Voucher as the request of customers. For example. Incoming invoice approval. We use arrival registration and invoice approval journal in D365FO where we in the approval journal differentiate costs against several financial accounts, financial account per financial dimensions, projects or project categories