2025 R3

This release went live on 2025-08-08.

Welcome to our latest REST API release

Once again, we're happy to announce the addition of more new endpoints. We also continue to improve and make enhancements to the existing objects.

Sage Intacct encourages your feedback, which you can provide using the Feedback tab on the right side of the page.

Updated endpoints

The 25R3 release includes the following updates and enhancements to existing objects:

Expense Tracking

  • employee-expense-line : Four new fields have been added: creditCardTxn , CreditCardTxnLine , electronicReceipt , and electronicReceiptLine . These fields facilitate the linking of the receipts, credit card transactions, and expense reports to each other. In addition, credit card transactions can be split into several expense lines.

Accounts Receivable draft advances

AR advances can now be saved in a draft state. Saving an advance in a draft state allows you to complete and post the advance at a later time. This flexibility is helpful when an advance needs to be recorded, but cannot be completed until additional details are available. Use the state field to create draft advances. For more information, see Advances in the REST API Reference.

Accounts Receivable advances - new advanceNumber field

Starting with the 2025 R3 release, the Accounts Receivable configuration allows you to assign a document sequence to AR advances. When a document sequence is defined for advances in the Accounts Receivable configuration, a new advanceNumber field in AR advance objects shows the unique payment ID for an advance. The new advanceNumber field is included in API responses when you issue a GET request on an AR advance object, improving traceability.

To learn more about setting up a document sequence for AR advances, see About customer advances in the Sage Intacct Help Center.

Cash Management reverse workflows

The reverse workflow has been updated for deposit, funds-transfer, and other-receipt. These can all be reversed after they have been posted, except for other-receipt, which can be reversed after being approved:

New endpoints

This release includes the following new endpoints:

Accounts Payable

Accounts Receivable

Cash management

Common resources

Company configuration

General Ledger

Inventory Control

Order Entry

Purchasing

Tax

Time

Other updates

Supply Chain Management transaction update behavior

Historically, updates to Supply Chain Management (OE/PO/Inv) transactions worked by deleting existing line item records and then re-adding them, treating every update like a new transaction. Starting with the R3 release, Sage Intacct intelligently updates line records for all companies. The benefits of this enhancement are:

  • Existing line records are updated when needed, without the need for a new record number.
  • Unneeded records are removed.
  • Audit trail better reflects changes.

This change in update behavior improves efficiency by reducing unnecessary deletions and recreations. It also makes data management cleaner and minimizes the potential side effects from updates.

If you maintain integrations or custom processes around Supply Chain Management, keep this behavior change in mind. If you have questions or want to provide feedback, go to the Sage Intacct Developers Club.

Deprecated action field in Accounts Payable and Accounts Receivable objects

The action field has been deprecated in the following objects:

  • Accounts Payable: adjustment, bill, advance, payment
  • Accounts Receivable: adjustment, invoice, advance, payment

Because the action field has been deprecated and will be removed in a future API version, use the state field instead when working with these objects. The state field can be modified through workflow operations like Submit and Reverse, but cannot be changed using the PATCH operation.

New bank currency fields for AP and AR payments

Starting in 2025 R4, new bank currency fields will be added to AP and AR payment objects. These new read-only fields are populated when a bank is involved in a bill or invoice payment. For example, for an AP payment:

  • The transaction amount paid by the bank will be stored in a new bankCurrency.txnAmount field.
  • The currency for the bank payment will be stored in a new bankCurrency.currency field.

The new bank currency fields will be added to all AP and AR objects that include transaction amount and currency fields. The new bank currency fields will be added in 2025 R4. Anyone working with AP or AR payments should plan for these changes.

Workspace updates

Workspaces are now called organizations to better reflect the processes involved in creating applications. The steps to create an organization (formerly workspace) and client ID have also been updated. To learn more, refer to REST developer quick start