import { Callout } from "zudoku/ui/Callout"; # Suggest vendor payments What 365 business Banking changes in the standard Suggest Vendor Payments function: payment reference, payment method and recipient bank account. You do not have to switch to the [extended payment suggestion](payment-suggestion.mdx). You can continue to work with the standard **Suggest Vendor Payments** action of Microsoft Dynamics 365 Business Central. 365 business Banking adjusts the suggested lines so that they can be carried out with **Carry Out Payment**. ## Standard functionality in Business Central **Suggest Vendor Payments** in the payment journal suggests vendor ledger entries that are due for payment, with options for payment discounts (also by payment discount date), vendor priority, available amount and **Summarize per Vendor**. See [Microsoft Learn: Suggest vendor payments](https://learn.microsoft.com/en-us/dynamics365/business-central/payables-how-suggest-vendor-payments). ## What 365 business Banking adds | Area | What changes | |---|---| | Banking payment method and payment method code | In a banking journal, the lines get the banking payment method of 365 business Banking. If a line has no **Payment Method Code**, the journal batch's code is set. | | Different payment method | Entries whose payment method is neither blank nor the journal batch's are skipped (from Business Central version 26, see below). At the end, Business Central reports "… Vendor Ledger Entries have been skipped due to payment method does not match current Payment Journal. Do you want to show the entries?" | | Recipient bank accounts not released | If the vendor's bank account still has the status *New*, the suggestion does not ask per line whether you want to release it. The line is created without a **Recipient Bank Account**, the run continues, and at the end Business Central reports: "… line(s) were created without a recipient bank account, because the bank account of the recipient is not released for payments. …" **Carry Out Payment** refuses these lines until you release the bank account and select it on the line. See [Recipient bank accounts](recipient-bank-accounts.mdx). | | Payment reference per entry | Without summarizing, **Message to Recipient** contains the document type and the external document number, for example `Invoice INV-0815`. If the entry has its own message from the purchase invoice (**Diff. Message to Recipient**), that message is used instead. | | Payment reference when summarizing | With **Summarize per Vendor**, the external document numbers of all entries are listed; an entry with its own message appears in the list with that message. If 140 characters are not sufficient, the **Purpose Exceed Option** applies: split the payment or create a remittance advice, as in the extended payment suggestion. See [Summarize payments](payment-suggestion/purpose.mdx). When splitting, all lines keep the vendor's **Document No.**; they differ by their **Applies-to ID**: the first line keeps it, each further line gets the document number with the suffix `-2`, `-3` and so on, and the vendor ledger entries it pays carry that ID. | | Remit-to address | If the line has a remit-to code and a bank account is stored on the remit-to address, it is taken over as the recipient's bank account. See [Remit-to address](recipient-bank-accounts.mdx#remit-to-address). | 365 business Banking runs on Business Central version 25 and later. Skipping entries with a different payment method, and the related message, are only available from version 26. In version 25, such entries are suggested regardless of their payment method; the banking payment method is still set, and lines without their own payment method get the journal batch's. **Carry Out Payment** rejects a line with a different payment method because its payment method code does not match the journal batch. Delete or adjust the line. ## Notes - When summarizing, the payment reference names the document type before the first entry and again whenever the document type changes or an entry with its own message came in between, for example `Invoice INV-0815, INV-0816, Credit Memo CM-12, Invoice INV-0820`. A credit memo is therefore always identified as a credit memo and is never listed under "Invoice". The extended payment suggestion groups by document type instead. - The **Diff. Message to Recipient** of a purchase invoice takes precedence. See [Diff. Message to Recipient](recipient-bank-accounts.mdx#diff-message-to-recipient). - **Suggest Vendor Payments** does not cover employees, customers or netting. For these, use the [extended payment suggestion](payment-suggestion.mdx). ## Choosing a suggestion | You want to … | Then … | |---|---| | pay vendors only and work with the familiar options of the standard | **Suggest Vendor Payments** | | pay vendors, customers and employees in one run | [Extended payment suggestion](payment-suggestion.mdx) | | reuse settings as a template | [Extended payment suggestion](payment-suggestion.mdx) | | net receivables against payables and send a statement | [Customer-vendor netting](payment-suggestion/netting.mdx) | ## See also - [Payment journal](../payment-journal.mdx) - [Payment discount in the extended payment suggestion](payment-suggestion/payment-discount.mdx) - [Carry out payment: process per bank connection](carry-out-payment.mdx)