2025 Release 2

This release went live on May 9, 2025.

Note: While Sage Intacct continues to support the XML API, going forward all new objects and features will be released in the REST API. We recommend using the REST API for your client applications. If you have questions or need help, check out the Sage Intacct Developers Club.

Create draft transactions without a document number

These changes apply to Inventory, Order Entry, and Purchasing legacy transactions.

When creating or updating legacy draft transactions in previous releases, the document number was required. This requirement was limiting for certain workflows because a document number cannot be changed after it is set and, by definition, draft transactions may not be well defined and ready for a static document number.

To make legacy draft transactions more flexible, starting with the 2025 R2 release you can:

  • Create draft transactions without specifying a document number.
  • Update a draft transaction using the record number.
  • Update a draft transaction to add a document number.
  • Get and delete transactions using their record number.

For more information about Inventory transactions, see:

For more information about Order Entry transactions, see:

For more information about Purchasing transactions, see:

Retrieve audit history without a document number

These changes apply to Inventory, Order Entry, and Purchasing legacy transactions.

Starting with the 2025 R2 release, you can retrieve the audit history for legacy transactions using the record number for the transaction instead of the document number. This change enables you to retrieve the history for all transactions, including draft transactions that may not yet have a document number assigned.

The following example shows how to retrieve the audit history for a Purchasing transaction using a record number instead of a document number:

<readByQuery>
    <object>AUDITHISTORY</object>
    <fields>*</fields>
    <query>OBJECTTYPE='podocument' and OBJECTKEY = '1165'</query>
    <pagesize>100</pagesize>
</readByQuery>

For more information about audit history, see Query and List Audit History (Legacy).

Purchasing

New HIDEPRICE field in transaction definitions

Starting with the 2025 R2 release, a new optional HIDEPRICE field is available in the Purchasing transaction definition (PODOCUMENTPARAMS) object.

Set this new HIDEPRICE field to true to allow users of the Sage Intacct Purchasing application to hide line item prices in transactions created from the transaction definition.

For more information, see the Accounting Properties in Create Purchasing Transaction Definition and Update Purchasing Transaction Definition in the API Reference.

New fields added for secondary vendor lien waivers

We added three fields to COMPLIANCERECORD to enable the use of lien waivers for secondary vendors:

  • SECONDARYVENDORNAME: The name of the secondary vendor, if one is used. When a secondary vendor is used and a lien waiver is created for compliance purposes, the value of this field defaults to the secondary vendor name that appears on the primary document. Otherwise, this field can be null. You can override the value during an update call.
  • SECONDARYVENDOR: Boolean field that indicates whether a lien waiver is generated for the secondary vendor for compliance purposes. When lien waivers are generated from the primary document, this field is set to true. Additionally, the secondary vendor compliance template is used when the printed document template for the compliance records is printed and emailed. You can override the value during an update call.
  • SECVENDORCOMPLIANCETEMPLATE: A read-only field. Contains values from the COMPLIANCETYPE for the secondary vendor template.

For more information about compliance records, see Vendor Compliance Records.

Provide feedback