Traci Kirkpatrick Client Care Coordinator

When a Purchase Invoice is used and Get Receipt Lines is used as a separate billing document, the Posting of the Purchase Invoice will not result in a deletion of the related Purchase Order - even if the PO is fully Received and Invoiced for all lines. This needs to be changed. Why make the link available if it does not complete the cycle.?

We need to use purchase invoices as we do not want the purchase order to go back through the workflow process for adding freight and tax that the purchaser would not have at the time of entry.

We have a client that adds freight and tax at the time they are paying the purchase order. Since they are using workflows for approval on their PO's, adding these lines would require the po is processed through the workflow again. There needs to be a way for the Payables team to add freight and tax at the time of payment WITHOUT requiring approval again.

When Get Receipt Lines is used and Purchase Invoice is used as a separate billing document, posting the Purchase Invoice will not result in the deletion of the associated Purchase Order.

We need to use this method since we all freight and taxes after the purchase order is received as this information is not available to the purchaser. Once the invoice is received from the vendor, we then add freight and tax. This allows us to process the invoice without needed to send the PO back through a workflow approval.

When you pay more than 25 vendor invoices and show remittances on the checks, if there is a 2nd page, the system will void the following check number and then print the continuation on page 2. Some vendors our client pays have 75+ invoices per week that are paid. This causes them to have multiple voided check numbers. It would be preferred if Business Central had an option not to void the overflow and instead prompt to insert a 2nd or additional pages as Great Plains does. Clients do not like checks being voided.

Our client is using GP18.5. On workflows, the reminder and escalation emails are not sent to the approvers. This is disappointing to the client as they expect this feature to work. After extensive research and testing, we have found that when you do something with workflow and emailing in the front-end of GP, it uses Modern Authentication; however, the reminder and escalation notifications come from the SQL Agent jobs that use SMTP.

The SMTP isn't working anymore, most likely because it is being deprecated by the Exchange Online team, as mentioned in the blog posts that I have read and been provided by support.

What is concerning is that I would have thought that since Basic authentication is being deprecated, reminder and escalation emails should be using Modern Auth as the front end is when the first email is sent out advising the approvers they have a batch to approve in the workflow.