2025 Release 2 2025-04-14

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:

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>

If you retrieve the audit history for a draft transaction that has not been assigned a document number, the response contains the record number in the OBJECTKEY field. If you retrieve the audit history for a transaction that has already been assigned a document number, the response contains the document number in the OBJECTKEY field. 

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:

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

2025 Release 1 2025-01-19

This release went live on February 7, 2025.

Accounts Payable

The following changes are being introduced for the VENDOR and VENDORVISIBILITY objects. To learn more about the functions that are changing, see Vendors in the XML API Reference.

VENDOR read function

VENDOR lookup function

The data returned for the OBJECTRESTRICTION field has changed:

VENDORVISIBILITY read function

Starting in the 2025 R1 release:

Accounts Receivable

Customer bank account to be deprecated

As part of the initiative to minimize the auditing burden that comes with handling sensitive data, the legacy customer bank account object will be deprecated and unavailable for use starting in 2025 Release 4.

Anyone using the legacy customer bank account object should plan for its deprecation. The object and all its supported operations, documented in the Customer Bank Accounts API reference content, will no longer be available after November 7, 2025.

Customer and customer visibility objects

The following changes are being introduced for the CUSTOMER and CUSTOMERVISIBILITY objects. To learn more about the functions that are changing, see Customers in the XML API Reference.

CUSTOMER read function

CUSTOMER lookup function

The data returned for the OBJECTRESTRICTION field has changed:

CUSTOMERVISIBILITY lookup function

Starting in the 2025 R1 release:

CUSTOMERVISIBILITY read function

Starting in the 2025 R1 release:

Cash Management

New fund transfers fields - Early adopter enhanced currency support

For global companies configured to use enhanced currency support, which is available for early adopters in the 2025 R1 release, the following new fields are returned in results for FUNDSTRANSFER lookup and read functions. Note that the new Enable Multi-Currency Funds Transfer feature flag must be enabled to use enhanced currency support.

For more information about the FUNDSTRANSFER object, see Fund Transfers in the API Reference.

Purchasing

Use custom fields for compliance objects

Custom fields give you a way to capture business-specific data. Compliance types provide a way to specify which custom fields are applicable to the type of compliance record used. Now when you query on the COMPLIANCETYPE object, you can see a COMPLIANCERECORDCUSTOMFIELDS field. For example:

<query>
    <object>COMPLIANCETYPE</object>
    <select>
        <field>RECORDNO</field>
        <field>COMPLIANCETYPEID</field>
        <field>NAME</field>
        <field>STATUS</field>
        <field>COMPLIANCERECORDCUSTOMFIELDS</field>
    </select>
    <filter>
        <equalto>
            <field>STATUS</field>
            <value>active</value>
        </equalto>
    </filter>
</query>

The COMPLIANCERECORD object remains unchanged. Note that custom fields must be added to compliance records through the user interface before being used by compliance types. From the main menu in your company, go to Platform Services or Customization Services > All > Custom Fields to add custom fields to compliance records. Expected behaviors, such as errors returned when required custom fields are not included, apply. In addition:

For more information, see Vendor Compliance Types.

Construction

Specify entities as limited

The ENTITY object has a new ISLIMITEDENTITY Boolean field. The field is included in read and query responses. The default value is false.

Web Services

RECORDTYPE capitalization change

The capitalization of the RECORDTYPE value for some record types has been changed slightly. For example, the previous value of AR Advance is now returned as AR advance. This is the list of new record type values:

Permission enhancement for AUDITHISTORY and ADVAUDITHISTORY

Permission requirements for the use of the AUDITHISTORY and ADVAUDITHISTORY objects in the API have been changed to match the requirements of the equivalent Audit Trail and Advanced Audit Trail features in the application. The user associated with the API session must have View permission for custom reports. That permission can be enabled under the Platform Services subscription.

Audit-related requests when the user does not have the right permission will return this error:

Unable to view audit history. You do not have permission to view audit history

2024 Release 4 2024-10-14

This release went live on November 8, 2024.

Platform Services

Labels for custom objects and custom fields support different locales

To define a custom field using XML, you use <label>. Now you can use a new tag, <customLabels>, to add labels for different locales. Nest <customLabels> under the custom object or custom field for which to define locales. Then, define a <customLabel> using the <locale> and <text> tags. In this example, <customLabels> is used to define two locales: US English and French.

    <customField> 
        <customFieldId>CF_ID_1</customFieldId>
        <type>checkbox</type>
        <ownerObject>vendor</ownerObject>
		<customLabels>
			<customLabel>	
				<locale>en-US.UTF-8</locale>
				<text>Preacquisition vendor</text>
			</customLabel>
			<customLabel> 
				<locale>fr-FR.UTF-8</locale>
				<text>vendeur de préacquisition</text>
	    	</customLabel>
		</customLabels>	
        ...

If you include both <label> and <customLabels>, then <label> defines the company’s locale.

For more information, see Customization Packages.

Accounts Receivable

Customer charge card to be deprecated

Sage Intacct is in the process of reducing the amount of cardholder data we manage. This initiative is a strategic move to minimize the auditing burden that comes with handling sensitive data. Implementing alternatives to card data storage and processing will streamline our internal operations while ensuring customer information remains secure.

As part of this initiative, the legacy customer charge card object will be deprecated and unavailable for use starting in 2025 Release 1. Anyone using the customer charge card object should plan for its deprecation. The object and all its supported operations, documented in the Customer Charge Cards API reference content, will no longer be available after February 7, 2025.

Now bill to and contact tax IDs available in Invoices

Two new read-only fields now appear in ARINVOICE responses: BILLTO.TAXID and CONTACT.TAXID. This change means that the tax identification information for the bill to and contact objects is available within the invoice itself.

Accounts Payable

Vendor Payments powered by American Express are being retired

On December 31, 2024, the following American Express payment services will no longer be available in Sage Intacct:

Make sure to process all payments by December 20, 2024 to avoid any potential issues. For more payment provider options, visit the Sage Intacct Marketplace.

Update vendor bank file details

Starting with the 2024 R4 release, if you want to update bank file details for a vendor, you must supply the record number of those details in the update request. For example, to successfully update United Kingdom (GB) bank file details, issue a request as shown in the following example:

    <update>
      <VENDOR>
          <RECORDNO>59</RECORDNO>
          <VENDORID>GBVendor</VENDORID>
          <VENDORBANKFILEDETAILS>
              <vendorbankfiledetail>
                <RECORDNO>65</RECORDNO>
                <BSBNUMBER>123-456</BSBNUMBER>
                <BANKACCOUNTNUMBER>53423347</BANKACCOUNTNUMBER>
                <ACCOUNTNAME>sunheel</ACCOUNTNAME>
                <SORTCODE></SORTCODE>
              </vendorbankfiledetail>
          </VENDORBANKFILEDETAILS>
      </VENDOR>
    </update>

For more information, see Update Vendor in the API Reference.

Contracts

New fields added to Contract object

New fields have been added to the CONTRACT object to support the contract dimension, which is available to companies with Order Entry Revenue Management. The contract dimension is used to categorize, track, and analyze Order Entry transactions without a subscription to the Contracts application. To learn more about the contract dimension, see Track Order Entry transactions with the contract dimension in the Sage Intacct Help Center.

The fields added to the CONTRACT object include:

For more information about these new fields,see Create Contract.

New fields added to track service periods

To support the inclusion of service period start date and service period end date in the Contracts workflow, new optional fields have been added to several objects. These updates ensure that service period information is retained throughout the workflow, from the contract phase to invoice generation. These new fields are available to companies with the Contracts and Platform Services subscriptions. To learn more about this update, see “Service periods” in the 2024 R4 Sage Intacct Release Notes.

CONTRACTBILLINGSCHEDULEENTRY

CONTRACTUSAGE

GENINVOICEPREVIEW

GENINVOICEPREVIEWLINE

SODOCUMENTENTRY

In addition to the contract object changes, order entry transactions will now return the new fields:

For more information about these new fields, see:

Construction

New fields added for tracking the scope and schedule of a project

These new fields are available to companies with Construction and Projects subscriptions.

New fields have been added to the PROJECTS object to track project scope and schedule details. Because the details are within the PROJECTS object, details such as scope and terms are always available. To learn more about this update, see “Scope and schedule of a project” in the 2024 R4 Sage Intacct Release Notes.

For more information, see Projects.

Order Entry

Override individual tax line items if you use Advanced tax

Customers who use Advanced Tax can now override individual tax lines; previously, if Advanced Tax was enabled for a company, individual tax lines could not be overridden. The fields to override a tax line are trx_tax and overridedetailid used in linesubtotal. If trx_tax is not provided for the line, the VAT is calculated using the percentage value set in overridedetailid.

For more information, see Order Entry Transactions.

Projects

Retainage now supported with Projects subscription

Retainage is a portion of a contracted price that is intentionally withheld until a project is substantially complete. In previous releases, retainage fields were supported only with a Construction subscription. Starting with this release, XML API retainage fields are supported with either a Purchasing subscription or a Construction subscription. Affected retainage objects and fields include:

For more information, see:

2024 Release 3 2024-07-15

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:

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:

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:

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:

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:

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:

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:

Changes in behavior for payments

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

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:

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:

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

APPYMTDETAIL

APPAYMENTREQUEST

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:

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):

2024 Release 2 2024-04-15

This release went 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.

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.

Value of state field for existing AR payments

With the introduction of draft payments, as discussed in the preceding release note, the state field for existing completed payments will be changed from null (blank) to a value of C in the weeks following the 2024 R2 release.

Get invoices - allocations affect read results

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. When available, the project is retrieved via PROJECTID from the primary document header.

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.

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:

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 discontinued

We want to let you know about a change that’s coming later this year: The smarteventlog object and get_list will be discontinued. 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.

Accounts Payable

Get bills - allocations affect read results

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.