2025 Release 3

This release went live on August 8, 2025.

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 and update draft advances. For more information, see:

New RECORDID field in AR advances

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 RECORDID field in AR advance objects shows the unique payment ID for an advance. The new RECORDID field is included in XML API responses for read, lookup, and query functions, improving traceability.

For more information see About customer advances in the Sage Intacct Help Center.

Customer bank account and 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, these legacy objects will be deprecated and unavailable for use starting in 2025 Release 4:

Anyone using these legacy customer objects should plan for their deprecation. Theses objects and their supported operations will no longer be available after November 7, 2025.

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.

New returned fields and changes to some returned values for foreign currency payments

Starting in 2025 R4, when a bill or invoice is paid using a foreign currency bank, new fields and different values in some existing fields will be returned on query and lookup functions for Accounts Payable and Accounts Receivable payment objects.

All objects that currently return these fields on query and lookup will be affected when a bill or invoice is paid using a foreign currency bank: TRX_TOTALENTERED, TRX_AMOUNT, and CURRENCY.

Anyone paying bills or invoices using a foreign currency bank should plan for these changes.

Header-level payment objects

When a bill or invoice is paid using a foreign currency bank for header-level payment objects like APPYMT and ARPYMT, query and lookup functions return new fields and different values for some existing fields, as follows.

Currently:

  • CURRENCY field - Foreign currency is returned
  • TRX_TOTALENTERED field - Amount paid by bank is returned

After R4:

  • New BANKCURRENCY field - Foreign currency is returned
  • New BANKTRXAMOUNT field - Amount paid by bank is returned
  • CURRENCY field - Base currency is returned
  • TRX_TOTALENTERED field - Transaction amount of bill/invoice is returned

Line-level payment objects

When a bill or invoice is paid using a foreign currency bank for line-level payment objects like APPYMTDETAIL and ARPYMTDETAIL, query and lookup functions return new fields and different values for some existing fields, as follows.

Currently:

  • CURRENCY field - Foreign currency is returned
  • TRX_AMOUNT field - Amount paid by bank is returned

After R4:

  • New BANKCURRENCY field - Foreign currency is returned
  • New BANKTRXAMOUNT field - Amount paid by bank is returned
  • CURRENCY field - Base currency is returned
  • TRX_AMOUNT field - Transaction amount of bill/invoice is returned

You can submit questions about these changes in the Sage Intacct Developers Club.

Custom reports for transaction objects

When reading custom reports for Inventory, Order Entry, and Purchasing transactions in previous releases, the results included a DRILLRECORDNO field for each set of data returned in the report.

Starting with the 2025 R3 release, the DRILLRECORDNO field is no longer included for each set of data returned. Instead, the name of the field returned to identify each set of data is now dependent on the type of transaction, as follows:

  • DRILLSORECORDNO (Order Entry)
  • DRILLPORECORDNO (Purchasing)
  • DRILLINVRECORDNO (Inventory Control)

Get object definition for AP bill and AR invoice

When using the lookup function to get an object definition for AP bill and AR invoice, the results include data about related transactions.

In previous releases, the RELATEDBY field showed that:

  • An APBILL was related to a PODOCUMENT by a value of DESCRIPTION2
  • An ARINVOICE was related to an SODOCUNMENT by a value of DESCRIPTION2

Starting with the 2025 R3 release, the value shown in the RELATEDBY field for both APBILL and ARINVOICE is DOCHDRKEY.

For example, this lookup request:

<lookup>
    <object>ARINVOICE</object>
</lookup>

Shows this relationship data in the results:

<Relationship>
<OBJECTPATH>PODOCUMENT</OBJECTPATH>
<OBJECTNAME>PODOCUMENT</OBJECTNAME>
<LABEL></LABEL>
<RELATIONSHIPTYPE>ONE2ONE</RELATIONSHIPTYPE>
<RELATEDBY>DOCHDRKEY</RELATEDBY>
</Relationship>

Provide feedback