2024 Release 3

This release went live on August 9, 2024.

Accounts Receivable

New AR invoice fields identify original transaction documents

Sage Intacct applications provide customizable workflows that enables users to set up various transaction definitions according to their business needs. When creating a workflow, users can configure multiple potential entry and exit points. This flexibility can make it cumbersome to identify:

  • The source document in the conversion workflow
  • The lines associated with the final child document

To improve visibility into document conversions, the 2024 R3 release includes several new fields that are returned in read request results for the AR invoice (ARINVOICE) object. These new fields are returned for invoice objects that reference a transaction in Order Entry. The new fields include:

  • ORIGDOCKEY - Record number of the originating document in the workflow conversion.
  • ORIGDOCLINEKEY - Record number of the line item in the originating document in the workflow conversion.
  • ORIGDOCID - ID of the originating document in the workflow conversion.
  • ORIGDOCLINEID - ID of the line item in the originating document in the workflow conversion.

Apply custom discounts to received payments

Starting with the 2024 R3 release, users can apply custom discounts to an invoice when receiving a payment. Custom discounts streamline the process of applying a discount because, unlike existing term discounts, they don’t require that you first create an AR term that includes the discount details. The flexibility of custom discounts allows you to dynamically adjust a discount when you receive payment.

To activate custom discounts, go to the Accounts Receivable settings and select the option named Enable custom discounts. When this Accounts Receivable setting is enabled, you can use the new TRX_TOTALDISCOUNTTOAPPLY parameter to apply a custom discount in the payment details when creating a new payment or updating a draft payment.

Note the following restrictions for custom discounts:

  • Custom discounts and term discounts cannot be combined for the same invoice.
  • When a custom discount is applied to an invoice, term discounts cannot be used for subsequent payments on that same invoice.
  • You can apply custom discounts in combination with a cash or credit payment, but discounts alone are not allowed.
  • You cannot apply a custom discount that is equal to the total amount of the invoice.

Because custom discounts and term discounts cannot be combined, do not include a DISCOUNTDATE in AR payment details when using the TRX_TOTALDISCOUNTTOAPPLY parameter. If you provide a value for both DISCOUNTDATE and TRX_TOTALDISCOUNTTOAPPLY in the payment details, the request to create the payment fails.

For more information, see Create AR Payment and Update AR Payment.

Change in behavior for term discounts

In addition to the introduction of custom discounts, term discount behavior has also been changed. Now if you provide two or more discount dates for separate invoice lines in the payment details of a payment request, the payment request will fail. In the past when multiple discount dates were provided in the payment details, the first discount date supplied in the request was used and any additional dates were ignored. Starting with this release, that behavior has been changed so that only one discount date is expected and any additional dates provided cause the payment request to fail with an error.

Accounts Payable

New AP bill fields identify original transaction documents

Sage Intacct applications provide customizable workflows that enable users to set up various transaction definitions according to their business needs. When creating a workflow, users can configure multiple potential entry and exit points. This flexibility can make it cumbersome to identify:

  • The source document in the conversion workflow
  • The lines associated with the final child document

To improve visibility into document conversions, the 2024 R3 release includes several new fields that are returned in read request results for the AP bill (APBILL) object. These new fields are returned for bill objects that reference a transaction in Purchasing. The new fields include:

  • ORIGDOCKEY - Record number of the originating document in the workflow conversion.
  • ORIGDOCLINEKEY - Record number of the line item in the originating document in the workflow conversion.
  • ORIGDOCID - ID of the originating document in the workflow conversion.
  • ORIGDOCLINEID - ID of the line item in the originating document in the workflow conversion.

AP adjustment line item fields no longer supported

When creating or updating an AP adjustment using the legacy create_apadjustment or update_apadjustment function, note that two lineitem fields are no longer supported:

  • totalpaid
  • totaldue

If you include these fields in the line items of a create_apadjustment or update_apadjustment request, the provided values are ignored.

Unapply credit-only payments

Starting with the 2024 R3 release, you can unapply credit-only payments using the legacy reverse_appayment function. When reversing a credit-only payment, supply the record number of the credit-only payment and the date that the payment should be reversed. For more information, see Reverse AP Payment (Legacy).

Changes in behavior for credit-only payments

In addition to the ability to unapply credit-only payments, there are several changes in behavior for credit-only payments, including:

  • If you issue a request to create a credit-only payment with ACH as the payment method, the payment request succeeds regardless of whether ACH payments are configured for your company.
  • If an invalid payment method is included in your request to create a credit-only payment, the payment request fails. For a credit-only payment, the payment method can be omitted or can be a valid value. In cases where the payment method is omitted, the default AP payment method from the company’s configuration is used.
  • If an invalid financial entity is included in your request to create a credit-only payment, the payment request fails. For a credit-only payment, the financial entity can be omitted or can be a valid value.
  • When you issue a request to create a credit-only payment, the response now includes a record number (RECORNO).
  • If your company is configured to use the Intacct Daily exchange rate, you issue a request to create a credit-only foreign currency payment, and you supply a future payment date in the request, the payment fails. You must change the date to the current or an earlier date so that the Intacct Daily exchange rate is known.

Changes in behavior for payments

The following changes have been implemented for AP payments in this release:

  • If you issue a request to create a payment and you attempt to apply an inline credit from a bill that has an unpaid balance to a different bill, the payment request fails. You cannot apply inline credits from a bill that has a remaining positive balance.
  • If you issue a request to create a payment and specify a charge card ID for the financial entity (FINANCIALENTITY), but do not provide a corresponding payment method (PAYMENTMETHOD), the request fails.

New status field for payment provider method

When you read a payment provider method object, PROVIDERPAYMENTMETHOD, a new status field is returned to indicate whether the method is active or inactive. To learn more about reading this object, see Get Payment Provider Payment Method.

Purchasing

New transaction detail fields identify original transaction documents

Sage Intacct applications provide customizable workflows that enable users to set up various transaction definitions according to their business needs. When creating a workflow, users can configure multiple potential entry and exit points. This flexibility can make it cumbersome to identify:

  • The source document in the conversion workflow
  • The lines associated with the final child document

To improve visibility into document conversions, the 2024 R3 release includes several new fields that are returned in read request results for the Purchasing transaction (PODOCUMENT) and Order Entry transaction (SODOCUMENT) objects. The new fields include:

  • ORIGDOCKEY - Record number of the originating document in the workflow conversion.
  • ORIGDOCLINEKEY - Record number of the line item in the originating document in the workflow conversion.
  • ORIGDOCID - ID of the originating document in the workflow conversion.
  • ORIGDOCLINEID - ID of the line item in the originating document in the workflow conversion.

Upcoming revision to draft transaction definition validation

In an upcoming release, changes will be implemented so that validations on draft transaction definitions occur when a transaction posts rather than when a transaction is created. These changes will allow users to create draft transaction definitions that contain minimal information to act as placeholders for accounting transactions. Performing transaction validation when a transaction posts rather than when it is created will improve workflow automation by allowing users to match draft placeholder transactions to incoming purchasing documents.

All transaction definitions, Order Entry, Purchasing, and Inventory Control, will be updated to support creation of draft documents without validation. More details about these planned changes will be provided in future release notes.

Construction

New joint checks and joint payees

In construction and some other fields, companies hire subcontractors to work on part or all of their projects. In some cases, the subcontractor that is hired also hires their own subcontractors to complete the contracted work. In these cases, joint checks can be issued for a primary vendor (subcontractor) and their secondary vendor (the subcontractor’s subcontractor). This ensures that the secondary subcontractor is paid for their work and can help avoid unnecessary churn and possible liens against projects by unpaid secondary vendors.

A new Joint Payee object (APBILLJOINTPAYEE) lets you define joint payees and associate them with specific AP bills. When paying a bill that has associated joint payees, you can create separate payment detail objects for each payee as needed, such as for the primary vendor and each secondary vendor.

For more details, see the page on the new Joint Payee object.

Other objects that have been updated to support joint checks:

APPYMT

  • New value for the PAYMENTMETHOD field: Joint Check
  • New read-only fields: JOINTPAYEENAME, JOINTPAYEEPRINTAS

APPYMTDETAIL

  • New field to select a joint payee: JOINTPAYEEPRINTAS
  • New read-only field: JOINTPAYEENAME

APPAYMENTREQUEST

  • New read-only fields: JOINTPAYEENAME, JOINTPAYEEPRINTAS

New user type for construction managers

You can now create, update, or query for a construction manager user type in the Users object’s USERTYPE field. The construction manager user type tracks Sage Construction Management (CM) and Intacct Construction usage without impacting the project manager user type.

NOTE: Available only with a subscription to Construction.

For more information, see:

Purchasing multi-document conversion

When creating a purchasing transaction you can now specify a source document to convert from at the line level instead of at the transaction level. You can specify different source documents and source document lines for each transaction line in the purchasing transaction, allowing you to convert from multiple documents in a single transaction.

Valid conversions must conform to these rules:

  • The purchasing transaction being created must have the same vendor ID as the source documents.
  • Conversion must be allowed by the specified transaction definition.
  • Source documents must be in a valid document state that allows conversions, typically Pending or Partially Converted.
  • The source documents must use the same currency as the current downstream document.
  • The source documents must belong to the same entity as the purchasing transaction.
  • Fully converted lines can be included in a multi-document conversion if the quantity or amount to convert is set to 0.

For more information, see the sourcedocid and sourcedoclineid fields at the bottom of the potransitem table on the Purchasing Transactions page.

Item is now optional when creating a project change order

The ITEMID field has been made optional when creating a project change order, and it can be deleted when updating a change order. It must point to an active, non-inventory item for billing.

For more information, see Project Change Orders.

Construction tax enhancements

These read-only tax-related fields have been added to order entry transaction line objects (SODOCUMENTENTRY) and purchasing transaction line objects (PODOCUMENTENTRY):

  • PERCENTVAL - The aggregated tax rate for all the tax details assigned to a line
  • TAXABSVAL - The aggregated tax amount for all the tax details assigned to a line
  • LINETOTAL - The sum of extended transaction price plus tax amount
  • TRX_LINETOTAL - Transaction totals amount for the line
  • TAXABLEAMOUNT - Taxable amount of the line
  • EXTENDEDPRICENETRETAINAGE - Extended transaction price net retainage
  • EXTENDEDBASEPRICENETRETAINAGE - Extended base price net retainage

Provide feedback