This release went live on the evening of August 18, 2023.


Define requirements for vendors to ensure compliance

The 2023 R3 release introduces a feature in which you can define vendor compliance requirements and validate that vendors have provided required documents. For example, you might require contractors to have adequate liability insurance or a specific license. In R3 you can define compliance requirements in the insurance and miscellaneous categories, specify whether to validate by document or expiration date, and optionally prevent bill payments to out-of-compliance vendors. You create compliance records to apply your requirements to specified vendors and track their compliance.

NOTE: To enable the Vendor Compliance subscription, first enable Accounts Payable, Purchasing, and Construction. Vendor compliance is available only for Construction at this time.

For more information, see:

Accounts Receivable

Single payments for multiple customers — Early Adopter

The 2023 R3 release introduces a new early adopter feature: the ability to receive payments for multiple customers in a single request. You can use this feature at times when you need to receive a single payment, but apply the payment to invoices that belong to different customers. For example, when an insurance company submits a single payment for multiple patients at a facility. To learn more about this feature, see Receive a payment for multiple customers. If you would like to consider being an early adopter of this capability, contact Customer Support.

After this feature is enabled and set up, you can create an ARPYMT to receive payments for multiple customers in a single request as follows:

  • Do not include CUSTOMERID in the header of the ARPYMT request.
  • Instead, pass the new PAYERNAME field in the header of the ARPYMT request. This field should contain the name of the payer who is paying the invoices on behalf of multiple customers.
  • Then include the payment details for each customer.

For more information, see Create AR Payment.

When you read an ARPYMT as described in Get AR Payment and that AR payment includes payments for multiple customers:

  • The RECORDTYPE field returns a value of rl.
  • Several header level tags are blank, including: CUSTOMERRECORDNO, CUSTOMERID, CUSTOMERNAME, ARPYMTENTRIES.
  • Payment details include a new system-generated field, MULTIENTITYPYMTKEY, that contains the record number of the parent record when payment for multiple customers has been received.

Document sequencing

Starting with 2023 R3, you can establish the sequence number for your Accounts Receivable payment documents. To learn more about how to set up Document Sequencing, see Configure Accounts Receivable.

If Document Sequencing is enabled, when you read an ARPYMT as described in Get AR Payment, the RECORDID field in the payment details contains the document number based on the sequence you established. If Document Sequencing is not enabled, the RECORDID field in the payment details does not contain a value.

New field to designate an existing summary for AR advances

With the 2023 R3 release, you can now post an AR advance to an existing summary using the PRBATCH field or the new PRBATCHKEY field. See Create AR Advance and Update AR Advance for more information.

Accounts Payable

Vendor approvals

A new read-only STATE field in the VENDOR object shows the approval state of the vendor. Possible values are A (approved) and S (submitted). Vendors in submitted state cannot be paid until approved.

Provide feedback