What's new: Accounts payable features

مقالة
11/29/2021

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

We have changed and added functionality in the Accounts payable area for Microsoft Dynamics AX 2012. For more information, see the tables that apply to your version of the product.

What’s new in AX 2012

What’s new	Description
The sign of the invoice quantity must match the sign of the ordered quantity.	The sign of the invoice quantity on a vendor invoice must match the sign of the ordered quantity on the purchase order. In earlier versions, you could enter a negative invoice quantity to record the return of a product. To provide better accounting control, this functionality is no longer available. Instead, you can issue a credit note for the purchase order line as a separate purchase order line. In other words, you can enter a purchase order line that has a negative quantity. For more information, see Correct a vendor invoice that was matched to the wrong product receipt line.
A unit price that is based on an inventory cost price is updated only one time for a customer invoice.	The unit price on an intercompany purchase order and an intercompany sales order is updated for changes only when the first customer invoice for the intercompany sales order is entered. The update occurs only if the unit cost price is changed in Inventory management, and this update occurs automatically. If a subsequent customer invoice is entered, the unit price for that customer invoice does not come from the cost of the item. Instead, the unit price comes from the intercompany purchase order. For more information, see About changing intercompany orders.
Changes to the Accounts payable invoice table	In earlier versions, unposted purchase order invoices that were entered in the Posting invoice form were stored in the same tables as information about updating purchase orders, receipts lists, and packing slips. In this version, unposted purchase order invoices, which are now known as vendor invoices, are stored in a separate set of tables. For more information, see Key tasks: Vendor invoices.
Changes to invoice matching for line items that are identified by descriptions and categories	You can match an invoice line that is identified by a description and a category to a corresponding purchase order line and product receipt line. This feature is based on the functionality that you use to enter lines that are identified by a description and a category on a purchase order, product receipt, and invoice. Additionally, you can use this feature together with purchasing policies that are assigned to line items that are identified by descriptions and categories. For more information, see About Accounts payable invoice matching.
Create vendor invoices and credit notes from electronic invoices.	A new service for Microsoft Dynamics AX Application Integration Framework (AIF), VendVendInvoiceService, creates vendor invoices and credit notes from invoices that are received electronically. The service also lets vendors request and retrieve unposted invoice information in Accounts payable. For more information, see About integration ports for vendor invoices.
In the Vendor invoice form, enter vendor invoice lines that are not related to a purchase order.	You can enter vendor invoice lines in the Vendor invoice form, even if the lines are not related to a purchase order. The same vendor invoice can include a combination of lines that are related to purchase orders and lines that are not related to purchase orders. The following lines are examples of vendor invoice lines that are not related to a purchase order: Subscription dues Conference event registrations Catering services Cleaning services You can enter vendor invoice lines that are not related to a purchase order and do not create inventory transactions. However, inventoried or stocked lines are not supported on vendor invoice lines that are not related to a purchase order. For more information, see Key tasks: Vendor invoices.
Invoice matching: Price total matching	If the parameter that enables price total matching in the Accounts payable parameters form is selected, the net amount of an invoice line plus the net amount of any pending invoice lines and previously posted invoice lines is compared with the purchase order line. If the variance amount in the accounting currency exceeds the tolerance percentage, amount, or percentage and amount for price total matching, the user receives a message that warns about a matching discrepancy. This type of variance can occur when partial invoices individually meet quantity and price tolerances, but when these invoices are combined, they exceed a specified percentage or currency value that is defined by the legal entity. Tolerances for price total matching can be set up per legal entity. For more information, see About Accounts payable invoice matching and Set up Accounts payable invoice matching.
Invoice matching: Enhancements to charge matching	If the option to use charges matching is selected in the Accounts payable parameters form, charges on a vendor invoice can be compared with the expected charges from the purchase order. If the variance exceeds the tolerance percentage for charges, an indicator is displayed to warn the user about the matching discrepancy. Charge tolerances can be set up per company or for individual charges codes. For more information, see About Accounts payable invoice matching and Set up Accounts payable invoice matching.
Invoice matching: Invoice total matching	Invoice totals on a vendor invoice are compared with the expected totals, based on the purchase order information. If the variance exceeds the tolerance percentage for invoice total matching, an indicator is displayed to warn the user about the matching discrepancy. Tolerances for invoice total matching can be set up per legal entity or for individual vendor. For more information, see About Accounts payable invoice matching and Set up Accounts payable invoice matching.
Workflow for vendor invoice processing	By using two new workflow types, VendProcessInvoice and VendProcessInvoiceLine, users can create user-defined workflows for vendor invoices that are typically entered in the Vendor invoice form and other forms that use the InvoiceInfo* tables as the data source. The workflow process operates on data that is imported into the InvoiceInfo* tables, and can be used to model the processing steps for the vendor invoices. The workflow types contain the following elements: Approval elements for creating approval tasks A task element that is used when vendor invoices are completed and corrected Automated tasks that can be run programmatically without user intervention to perform selected validations and post the vendor invoices. Validations of vendor invoice, such as matching, are performed programmatically when the workflow is run. The validations use the settings of relevant Accounts payable parameters. Security is used to determine the behavior that is supported while an active workflow instance is associated with the vendor invoice. The standard workflow infrastructure in Microsoft Dynamics AX that lets a user create workflows, that determines the run-time behavior of the associated workflow instances, and that creates workflow history is used. For more information, see Set up vendor invoice workflows.
Invoice matching: Two-way and three-way line matching policy	The line matching policy can be set up as follows: Three-way – Matching compares the invoice, purchase order, and product receipt. Two-way – Matching compares the invoice and purchase order. Not required – Unit price matching and price totals matching are not performed. The line matching policy can be set up per legal entity, and also for items, vendors, or combinations of items and vendors. For more information, see About Accounts payable invoice matching.
Invoice matching task for workflow	Invoice matching is now available as a workflow task that can be performed without user intervention. The workflow can be started based on a business event in Microsoft Dynamics AX. For example, the workflow can be started when new records are created by using the vendor invoice service. Vendor portal scenarios and import scenarios in which vendor invoices are processed without user intervention are supported. In Microsoft Dynamics AX 2009, invoice matching was performed automatically through the user interface when an invoice was created, modified, or retrieved. The new tasks use the same underlying logic that the user interface uses to perform invoice matching. For more information, see Set up vendor invoice workflows.
In the Vendor invoice form, enter vendor invoices that are not for a purchase order.	Invoice header fields have been added to the Vendor invoice form, so that you can use this form to enter a category-based invoice line that is not related to a purchase order. For more information, see Key tasks: Vendor invoices.
Postdated checks	You can issue and receive checks that have a check date in the future. These checks are also known as postdated checks. Postdated checks are used as a common business practice in Asia, Africa, and many other parts of the world. Many businesses use checks as the primary way to make and receive payments. You can create postdated checks in payment journals in both Accounts receivable and Accounts payable. Postdated checks use standard functionality in Microsoft Dynamics AX, such as payment journals, financial dimensions, check printing, centralized payments, settlements, and banking. Postdated checks are not considered legal in certain parts of the world, such as Southeast Asia, Australia, and New Zealand, but are sometimes still used as a business practice in those countries/regions. To support this business practice but still comply with applicable laws, you can choose whether the check amount is reflected in your accounting books until the maturity date of the check is reached. If financial posting for postdated checks is turned off, the checks are documented for record-keeping purposes, and the financial transaction occurs only when the maturity date of the check is reached. For more information, see Set up postdated checks, and Register and post a postdated check for a vendor.
Improved forms for creating and posting invoices	The forms for creating and posting invoices are easier to understand and use, and you can now enter all the required information in one form. For more information, see Vendor invoice (form).
Verify the receipt of W-9 forms from vendors.	Before you post a document, you can verify whether a vendor has provided a W-9 form. If the vendor has not provided a W-9 form, you can hold the document while you wait for the form from the vendor. For more information, see Accounts payable parameters (form).
Advance payments on vendor invoices	When you have to pay a vendor before goods are delivered or a service is performed, you can create a vendor invoice line that includes a category and the amount that must be paid in advance. You can validate the amount of the advance payment that is listed on the vendor invoice against the amount that is listed on the purchase order. You can also apply the vendor invoice for the advance payment against the vendor invoice for the items or service. For more information, see Prepay for product or service overview.
Vendor self-service	Vendors can create and modify their invoices directly from the vendor self-service portal in Enterprise Portal for Microsoft Dynamics AX. Vendors can create an invoice from a purchase order, or they can create an invoice and add a purchase order to it. For more information, see Create or maintain your vendor invoices.
Add open purchase orders and purchase order lines to an invoice.	You can use the Retrieve purchase orders form to create one invoice for selected purchase orders and purchase order lines. In a list in the Retrieve purchase orders form, you can select the open purchase orders and lines to combine on the same invoice. For more information, see Key tasks: Vendor invoices and Retrieve purchase orders (form).
Improved forms for creating and posting invoices, purchase orders, receipt lists, and packing slips	The forms for creating and posting invoices, purchase orders, receipt lists, and packing slips are easier to understand and use. For each document type, you can now enter all the required information in one form. For more information, see Vendor invoice (form) and Purchase posting (form).
Create payment invoice groups, and pay a group of invoices by using the same payment.	You can group invoices by a common code. Then, if one invoice in the payment group is paid, the other invoices in the group are included in the same payment. For more information, see Add invoices to payment groups.
Print copies of payments as nonnegotiable checks.	You can print copies of payments, such as checks, promissory notes, and electronic payments. The copies are printed as nonnegotiable checks. For more information, see Print copies of payments as non-negotiable checks.
Set up prenotes to validate customer and vendor bank accounts for electronic funds transfer (EFT).	You can now set up prenotes for customer and vendor bank accounts for EFT. For electronic payments, banks use prenotes to verify the accuracy of account data, such as routing numbers and account numbers. For more information, see Set up prenotes.
Put Accounts payable payments on hold.	You can put Accounts payable payments on hold until a specified release date. You can also put these payments on hold indefinitely by leaving the release date blank. You can use holds to stop Accounts payable payments either by holding all payments for a vendor or by holding the payment of a selected invoice. When you put a payment on hold, you can prevent an approved invoice from generating a payment until the release date, if a release date is specified. For more information, see Place an Accounts payable payment on hold.
Organize invoices into groups to simplify retrieval and handling.	You can now group invoices by a common code, so that you do not have to use an exact query to retrieve a set of similar invoices. After you have retrieved the invoice group, you can easily post all the invoices at the same time. For more information, see Add invoices to invoice groups.
Create a confirming purchase order for unplanned vendor purchases (Public sector).	In an emergency or special circumstance, you can create an order that circumvents the usual purchasing process. For example, you can authorize an order that has only a purchase order number instead of a printed purchase order document. You can use the Confirming PO code field to track these unplanned purchases. For more information, see Confirming PO codes (form) (Public sector)
Select among multiple remittance addresses.	You can select among multiple remittance addresses for your organization. You can use a default remittance address for specific invoices, or you can use a different address that you selected for an invoice or a payment.
Create invoices from the vendor self-service portal.	Vendors can create and modify their invoices directly from the vendor self-service portal in Enterprise Portal. Vendors can create an invoice from a purchase order or packing slip, or they can create an invoice and add a purchase order to it. For more information, see Create or maintain your vendor invoices.
Transfer encumbrance entries for purchase orders from the closing fiscal year to the new fiscal year.	If you encumber purchase orders, you can process year-end closing entries to the general ledger and against budget reserves at the end of each fiscal year. When a new fiscal year is created, a new set of adjusting entries is made to correctly reflect the encumbrances in the new fiscal year. These entries guarantee that the purchase orders are correctly represented on the year-end financial statements. For more information, see Process purchase orders at year end.
Create flexible rules for vendor invoices.	Business rules for vendor invoices are now more flexible. You can enforce your business rules across all operating legal entities, but still allow for local variations that are based on criteria such as currency and country/region. For more information, see Key tasks: Vendor invoice policies.

What’s new in Microsoft Dynamics AX 2012 R2

What’s new	Description
Adjust taxes on an invoice line.	You can adjust the taxes that are calculated on an invoice line before you post the invoice. For more information, see Revise the sales tax amount on a transaction before posting.
Integrate a payment calendar to control due dates for payments.	New functionality for a payment calendar in the Accounts receivable and Accounts payable areas replaces similar functionality that was previously available only for certain countries/regions. When the payment calendar is used together with rules for due dates, companies can specify non-business days for countries and regions, and additional holidays at the state and province levels. Companies can also specify non-business days for any other purpose, such as non-banking days. This functionality helps guarantee that due dates for payments on vendor and customer invoices are not set for non-business days. When a payment is due on a non-business day, the new due date control moves the date to the nearest business day either before or after the default date, based on options that you select. You can also use the due date control together with the payment calendar to make sure that calculations of grace periods for interest and fees for payments start on the nearest business day. This functionality can be used, for example, to enhance the due date and payment date control in Accounts payable. You can then avoid any unplanned interest or fees for late vendor payments. Additionally, payment processing is easier, because due dates are always on a processing day. For more information, see About payment calendars.

Adjust taxes on an invoice line.

You can adjust the taxes that are calculated on an invoice line before you post the invoice.

For more information, see Revise the sales tax amount on a transaction before posting.

Integrate a payment calendar to control due dates for payments.

New functionality for a payment calendar in the Accounts receivable and Accounts payable areas replaces similar functionality that was previously available only for certain countries/regions. When the payment calendar is used together with rules for due dates, companies can specify non-business days for countries and regions, and additional holidays at the state and province levels. Companies can also specify non-business days for any other purpose, such as non-banking days. This functionality helps guarantee that due dates for payments on vendor and customer invoices are not set for non-business days. When a payment is due on a non-business day, the new due date control moves the date to the nearest business day either before or after the default date, based on options that you select.

You can also use the due date control together with the payment calendar to make sure that calculations of grace periods for interest and fees for payments start on the nearest business day. This functionality can be used, for example, to enhance the due date and payment date control in Accounts payable. You can then avoid any unplanned interest or fees for late vendor payments. Additionally, payment processing is easier, because due dates are always on a processing day.

For more information, see About payment calendars.

What’s new in cumulative update 6 for Microsoft Dynamics AX 2012 R2

What’s new	Description
Generate positive pay files to help banks prevent check fraud.	Set up positive pay to generate an electronic list of checks every time that checks are printed. When a check is presented to the bank, the bank compares the check with the list of checks that was previously submitted. If the check matches a check in the list, the bank clears the check. If the check does not match a check in the list, the bank holds the check for review. Positive pay is also known as SafePay. For more information, see the following topics: Set up positive pay Generate and print vendor checks Issue worker payments Create a positive pay file for multiple legal entities and bank accounts Void unposted checks
Prepay 100 percent of a purchase order amount.	In AX 2012, you can create prepayments for the line amounts on a purchase order. However, charges and taxes are not included in prepayments. In cumulative update 6 for Microsoft Dynamics AX 2012 R2, you can prepay either 100 percent or a fixed amount that is equal to the purchase order total. The prepayment can include taxes and charges that have a type of Customer/Vendor. For example, if the amount of a purchase order line is 1,000.00, and the sales tax amount is 125.00, the default entry for the prepayment is 1,125.00. In AX 2012, the default prepayment amount was 1,000.00.
Recover pending invoices that have unsaved changes.	In AX 2012, if the application stops responding when you are entering a vendor invoice, you receive the following message when you restart Microsoft Dynamics AX and open the Vendor invoice form: A pending invoice cannot be displayed because it is in use. In cumulative update 6 for Microsoft Dynamics AX 2012 R2, this message is replaced with a form that lets you delete pending invoices that have unsaved changes, so that you can continue to work with the invoice.

Generate positive pay files to help banks prevent check fraud.

Set up positive pay to generate an electronic list of checks every time that checks are printed. When a check is presented to the bank, the bank compares the check with the list of checks that was previously submitted. If the check matches a check in the list, the bank clears the check. If the check does not match a check in the list, the bank holds the check for review.

Positive pay is also known as SafePay.

For more information, see the following topics:

Prepay 100 percent of a purchase order amount.

In AX 2012, you can create prepayments for the line amounts on a purchase order. However, charges and taxes are not included in prepayments.

In cumulative update 6 for Microsoft Dynamics AX 2012 R2, you can prepay either 100 percent or a fixed amount that is equal to the purchase order total. The prepayment can include taxes and charges that have a type of Customer/Vendor. For example, if the amount of a purchase order line is 1,000.00, and the sales tax amount is 125.00, the default entry for the prepayment is 1,125.00. In AX 2012, the default prepayment amount was 1,000.00.

Recover pending invoices that have unsaved changes.

In AX 2012, if the application stops responding when you are entering a vendor invoice, you receive the following message when you restart Microsoft Dynamics AX and open the Vendor invoice form: A pending invoice cannot be displayed because it is in use.

In cumulative update 6 for Microsoft Dynamics AX 2012 R2, this message is replaced with a form that lets you delete pending invoices that have unsaved changes, so that you can continue to work with the invoice.

What’s new in cumulative update 7 for Microsoft Dynamics AX 2012 R2

What’s new	Description
New options for configuring workflows for vendor invoices	The following options for vendor invoice workflows are added: You can create conditions that are based on values in purchase order fields. The Vendor invoice lines.Procurement category property now includes hierarchical operators for contains, begins with, is, and is not. For more information about vendor invoice workflows, see Set up vendor invoice workflows.

New options for configuring workflows for vendor invoices

The following options for vendor invoice workflows are added:

You can create conditions that are based on values in purchase order fields.
The Vendor invoice lines.Procurement category property now includes hierarchical operators for contains, begins with, is, and is not.

For more information about vendor invoice workflows, see Set up vendor invoice workflows.

What’s new in Microsoft Dynamics AX 2012 R3 Cumulative Update 8

What’s new	Description
(Public sector) Create one or more one-time vendor accounts at the same time as you create invoices for those vendors.	When approval or a contract in the form of a purchase order is not required, you can quickly create invoices at the same time as you create records for the vendors. You can generate an account for a vendor directly from the invoice form. You can also import a CSV file that has information about multiple one-time vendors and corresponding invoices, and create vendor accounts and accompanying invoices. For more information, see Create a one-time vendor and invoice (Public sector) and Import and create one-time vendors and invoices (Public sector).

(Public sector) Create one or more one-time vendor accounts at the same time as you create invoices for those vendors.

When approval or a contract in the form of a purchase order is not required, you can quickly create invoices at the same time as you create records for the vendors. You can generate an account for a vendor directly from the invoice form. You can also import a CSV file that has information about multiple one-time vendors and corresponding invoices, and create vendor accounts and accompanying invoices.

For more information, see Create a one-time vendor and invoice (Public sector) and Import and create one-time vendors and invoices (Public sector).

مشاركة عبر