2024 Release 4

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.

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:

  • American Express ACH Payment Service
  • American Express Card Payment Service

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:

  • APPLICATION - Specifies whether the contract is a full contract or dimension-only.
  • ADDITIONALCONTACTNAME - Identifies an additional contact.

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

  • SERVICEPERIODSTARTDATE - Identifies the start date of a billed service period in the billing schedule.
  • SERVICEPERIODENDDATE - Identifies the end date of a billed service period in the billing schedule.

CONTRACTUSAGE

  • SERVICEPERIODSTARTDATE - Identifies the start date of a billed service period based on usage. When used, the service period start date should be the first day of the month of USAGEDATE. For example, if USAGEDATE falls anytime in September, 2024, then SERVICEPERIODSTARTDATE should be 09/01/2024.
  • SERVICEPERIODENDDATE - Identifies the end date of a billed service period based on usage. When used, the service period should be the last day of the month of USAGEDATE. For example, if USAGEDATE falls anytime in September, 2024, then SERVICEPERIODENDDATE should be 09/30/2024.

GENINVOICEPREVIEW

  • SERVICEPERIODSTARTDATE - Identifies the start date of a billed service period in a contract invoice preview. Not used when SERVICEPERIODOVERRIDEOPTION is set to “Do not override”.
  • SERVICEPERIODENDDATE - Identifies the end date of a billed service period in a contract invoice preview. Not used when SERVICEPERIODOVERRIDEOPTION is set to “Do not override”.
  • SERVICEPERIODOVERRIDEOPTION - Indicates whether SERVICEPERIODSTARTDATE and SERVICEPERIODENDDATE in the invoice lines that come from a CONTRACTBILLINGSCHEDULEENTRY or CONTRACTUSAGE record are overridden. Valid options are:
    • Do not override - Indicates that the values in SERVICEPERIODSTARTDATE and SERVICEPERIODENDDATE from CONTRACTBILLINGSCHEDULEENTRY or CONTRACTUSAGE are used to generate the invoice preview.
    • Override empty dates only - When used, include values for SERVICEPERIODSTARTDATE and SERVICEPERIODENDDATE, which override null values used in CONTRACTBILLINGSCHEDULEENTRY or CONTRACTUSAGE.
    • Override all dates - When used, include values for SERVICEPERIODSTARTDATE and SERVICEPERIODENDDATE, which override all values in CONTRACTBILLINGSCHEDULEENTRY or CONTRACTUSAGE.

GENINVOICEPREVIEWLINE

  • SERVICEPERIODSTARTDATE - Identifies the start date of a billed service period in an invoice line based on values in CONTRACTBILLINGSCHEDULEENTRY, CONTRACTUSAGE, or GENINVOICEPREVIEW. Read only.
  • SERVICEPERIODENDDATE - Identifies the end date of a billed service period in an invoice line based on values in CONTRACTBILLINGSCHEDULEENTRY, CONTRACTUSAGE, or GENINVOICEPREVIEW. Read only.

SODOCUMENTENTRY

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

  • SERVICEPERIODSTARTDATE - Identifies the start date of a billed service period in an invoice line.
  • SERVICEPERIODENDDATE - Identifies the end date of a billed service period in an invoice line.

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.

  • SCOPE - Expected scope of the work for the project.
  • INCLUSIONS - Inclusions as part of the project.
  • EXCLUSIONS - Exclusions as part of the project.
  • TERMS - Terms of the project.
  • SCHEDULEDSTARTDATE - Scheduled start date of the project in format mm/dd/yyyy.
  • ACTUALSTARTDATE - Actual start date of the project in format mm/dd/yyyy.
  • SCHEDULEDCOMPLETIONDATE - Scheduled completion date in format mm/dd/yyyy.
  • REVISEDCOMPLETIONDATE - Revised completion date in format mm/dd/yyyy.
  • SUBSTANTIALCOMPLETIONDATE - Substantial completion date in format mm/dd/yyyy.
  • ACTUALCOMPLETIONDATE - Actual completion date in format mm/dd/yyyy.
  • NOTICETOPROCEED - Date of notice to proceed in format mm/dd/yyyy.
  • RESPONSEDUE - Date that the response for the project is due in format mm/dd/yyyy.
  • EXECUTEDON- Date that the project is executed on in format mm/dd/yyyy.
  • SCHEDULEIMPACT - Description of the impact of the project on the schedule.

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:

  • CUSTOMER: RETAINAGEPERCENTAGE
  • VENDOR: RETAINAGEPERCENTAGE
  • SODOCUMENT: RETAINAGEPERCENTAGE, TRX_AMOUNTRETAINED, PREVIOUSRETAINAGEBALANCE, RETCOMPLETEDAMT, RETSTOREDMATERIALS, and ISRETAINAGERELEASE
  • POTRANSACTION: RETAINAGEPERCENTAGE, TRX_AMOUNTRETAINED
  • PODOCUMENTPARAMS: ENABLE_RETAINAGE

For more information, see:

Provide feedback