2024 Release 2

This release is scheduled to go live on May 10, 2024.

Accounts Receivable

Receive draft payments

Starting with the 2024 R2 release, users with appropriate permissions can create, edit, and delete Accounts Receivable payments in a draft state using the XML API or the Sage Intacct user interface. Draft payment functionality provides more control, flexibility, and accuracy when managing payments, especially when working with bulk payments and imports. Draft payments save time and reduce errors because they allow you to make changes before finalizing payments rather than reversing those payments. When draft payments are finalized, you can submit those payments for processing.

To create a draft payment, you must have Accounts Receivable – Manage payments - Add permissions. To submit a draft payment for processing, you must have Accounts Receivable – Manage payments – Post permissions.

  • To create Accounts Receivable payments in draft state, specify Draft in the new ACTION parameter as described in Create AR Payment.
  • When draft payments are finalized, update and submit those payments by specifying Submit in the new ACTION parameter as described in Update AR Payment.

You can only update a payment that is in Draft state (D). If a payment has been submitted and is Complete (C), it cannot be updated. You can update a draft payment to change header information or revise payment details. For more information about updates and the details to include for each type of update, see Update AR Payment.

You can also delete payments that are in Draft state (D). To learn more, see Delete AR Payment.

Get invoices

When you issue requests to read invoices as described in Get Invoice, the responses to those requests will no longer include the DEPT or LOCATION fields for invoice items that involve allocations to distribute amounts to those dimensions. This is due to a change in how split General Ledger entries are handled for transaction allocations.

If the transaction that an invoice item represents does not involve allocations to department or location, there is no change in the fields returned for the read response. Additionally, if an allocation rule allocates to only one of these dimensions, then only that field is omitted from the read response. For example, if a rule allocates to location and project, the DEPT field is returned in the read response for an invoice, but the LOCATION field is not.

Taxes

Capture payment tax (France only)

A new field that captures payment tax for a transaction line item has been added to both Purchase Order and Order Entry legacy transactions. This new field applies only to French companies and entities. If you set the new paymenttaxcapture field to true when you create or update an Order Entry or Purchasing transaction, the VAT tax record for that transaction line item is generated when the transaction line is paid.

For more information, see:

Purchasing

Add Notes and Project information in vendor compliance records

You can now include a note in and associate a project with a compliance record. Store information related to purchase orders and subcontract primary documents, and access everything from the record. For manually created compliance records, the project is retrieved from the Primary document header when the user selects the primary document. For auto-created compliance records (including Primary document lien waiver, Primary document insurance, or Primary document miscellaneous compliance records), the project is retrieved from the primary document header and automatically added to compliance records that are auto-generated for the primary document. If no project is selected on the Primary document header, the compliance record is auto-generated with no project.

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

We added four new fields for this feature, but only PROJECTID and NOTES have user-supplied values. The other two fields are read-only.

  • NOTES - Text field for user-added notes. Use 4000 or fewer characters.
  • PROJECTKEY - Foreign key reference to the Project table.
  • PROJECTID - Unique user-defined project identifier. Should refer to an existing, active project record or, on updates, an active or inactive one. If the compliance record is manually created, when the user selects the primary document, the project is retrieved from the Primary document commitment header.
  • PROJECTNAME- The project name, which is derived from the PROJECTKEY field.

For more information, see:

Inventory

Default conversion type for items

Starting with the 2024 R2 release, non-inventory type items included in transaction workflows can be converted by price or quantity. To take advantage of this capability, the following configuration options must be enabled for Order Entry and Purchasing:

  • Enable price conversion
  • Enable override on transaction conversion type

With the preceding configuration options enabled, you can use the new DEFAULT_CONVERSIONTYPE field to specify the conversion type for non-inventory items. Non-inventory items can be converted by price or by quantity. This new field is supported for 3.0 XML API create and update item functions. To learn more, see:

Customization Services

List Smart Event Log Records (Legacy) to be deprecated

We want to let you know about a change that’s coming later this year: The smarteventlog object and get_list will be deprecated. For R2, you can continue to use the object. Users will be able to obtain Smart Event audit information by using a report based on the Audit Trail and adding it to an application menu for easy access. Learn more here: Use an Audit History report.

Construction

Line-level tax schedule assignment

Customers who use Advanced Tax, Multi-tax with VAT, or custom VAT can now assign tax schedules to individual document entry lines in both Purchase Order documents and Order Entry documents.

  • The new option to “Enable override of tax schedule on document entry” must be enabled in Purchasing and Order Entry configuration.
  • The TAXSCHEDULEID in PODOCUMENTENTRY and SODOCUMENTENTRY can be set to the ID of the tax schedule to apply to that line. If no value is supplied for this field, the tax schedule is assigned based on the tax schedule map logic as in previous releases.
  • The TAXSCHEDULEID field is a read-only field unless the new configuration option is enabled.
  • This option doesn’t apply to Simple Tax or to Avalara.

Accounts Payable

Get bills

When you issue requests to read bills as described in Get Bill, the responses to those requests will not include the DEPT or LOCATION fields for bill items that involve allocations to distribute amounts to those dimensions. This is due to a change in how split General Ledger entries are handled for transaction allocations.

If the transaction that a bill item represents does not involve allocations to department or location, there is no change in the fields returned for the read response. Additionally, if an allocation rule allocates to only one of these dimensions, then only that field is omitted from the read response. For example, if a rule allocates to location and project, the DEPT field is returned in the read response for a bill, but the LOCATION field is not.

Provide feedback