2021 Release 1

This release is scheduled to go live beginning on the evening of February 21, 2021.

Web Services

Enhanced asynchronous callbacks for readReport

In the previous release, we introduced a new feature to support asynchronous callbacks when using readReport on original custom reports. With asynchronous callbacks, your readReport request could initiate a secondary process to automatically send the response and the first batch of results to a callback URL.

We’ve expanded this capability so that you can choose to notify the callback URL without including the first batch of results. To do this, set the new showStatusOnly flag to true.

For more information:

General Ledger

Migrate your data now to take advantage of the new budget API and avoid future problems

In 2020-R3, a new GL budget object (GLBUDGETHEADER) was introduced that supports creating a budget with details in the same call. In addition, the create and update functions on the new object provide better performance than the legacy functions on BUDGETHEADER.

If you were using the legacy budget APIs, it is recommended that you update your integrations now to be prepared when the legacy APIs become unavailable, likely 2021-R2:

  • Contact support to plan your data migration—you cannot start using the new APIs without the migration if you were using the legacy APIs previously.
  • Update any API calls to use the new budget objects.

Important: The legacy objects (BUDGETHEADER and GLBUDGET) will be migrated to the new object types (GLBUDGETHEADER and GLBUDGETITEMS) in a future release, planned for 2021-R2. After migration, create, update, and delete, when used on the old object names, will return error messages explaining that you need to use the new objects. You will need to contact support to have your data migrated.

Accounts Payable

Introducing a new electronic payments service for early adopters

This release introduces a more reliable and streamlined electronic payments service for paying US vendors. Talk to your account manager to learn if your company is eligible to participate as an early adopter.

Electronic payments requires a subscription to Outbound Payment Services. Once subscribed and configured, you can use the API to make an electronic payment, designating the provider. Currently, Corporate Spending Innovations (CSI) is the only supported provider.

A new PROVIDERPAYMENTMETHOD read-only object provides access to the names of payment providers and their supported payment methods. You can use the new PROVIDERBANKACCOUNT and PROVIDERVENDOR objects to link bank accounts and vendors to electronic payment providers.

For more information:

Accounts Receivable

Ability to list customer charge card records will no longer be supported

The get_list function for customer charge cards is scheduled for deprecation. This function will become unavailable in a future release, likely, 2021-R2. At this time, the only way to access customer credit card information will be through the Sage Intacct UI.

Important: Check your integrations now and remove this function to avoid problems when this function becomes unavailable in a future release, planned for 2021-R2.

Inventory Control

Available quantities for tracked items

A new object lets you get available quantities for tracked items according to serial number, lot number, bin number, and so forth.

Item cross references

You can enable your customers or vendors to provide their own identifiers for inventory items, which can then be used in transactions.

For example, you might have an inventory item with the ID C-55, but one of your customers might want that item to be identified by I-22. You can create an item cross reference to associate item C-55 with the alias of I-22 for that customer. Now when you create transactions for that customer, you can optionally provide the alias ID as well as the item ID.

For more information:

Contracts and Revenue Management

Clear MEA allocations

You can now use the API to clear MEA allocations and reset the applicable revenue schedules to the amounts that existed prior to the allocations. Clearing an MEA allocation unposts previously posted revenue, so the applicable reporting periods must be open.

You can clear all MEA allocations at once or one at a time, starting with the current one and working back in time.

For more information:

Ship to source for contract lines

You can now choose whether the Ship to contact on a contract line is overridden when the Ship to contact on the contract itself is modified. Set the new SHIPTOSOURCE parameter on the contract line to Contract value to allow this overriding or to User-specified value to preserve the Ship to contact name on the line.

See the SHIPTOSOURCE parameter on the following functions:

Billing frequency for contract lines

Previously, billing frequency was required at the contract level and applied to every contract line.

Starting with this release, billing frequency is optional at the contract level and can be set individually on the line. If not specified on the line, the billing frequency from the contract is used. Billing frequency is required on the contract line when the Flat/fixed amount frequency (BILLINGOPTION) is Include with every invoice.

See the BILLINGFREQUENCY parameter on the following functions:

Order Entry

Revenue recognition schedules API documentation moved to Order Entry

The API documentation for revenue recognition schedules is now under the Order Entry category instead of General Ledger. The Sage Intacct Postman collection also reflects this organization. (The functionality of the APIs has not changed.)

Platform Services

CSP administration

Last release provided more visibility into Content Security Policy (CSP) violations, allowing you to easily find instances of URLs that violated your company’s CSPs.

This release provides more flexibility in how you assign URLs to a company or page’s CSP. Now, when you view a list of CSP violations from the Company Information page or an individual page, you can assign that URL to a CSP directly from the list of violations.

Construction Early Adopter Program

Price conversion for Order Entry transactions

Converting a transaction moves the transaction to the next step in the workflow (for example, from sales order to sales invoice). In previous releases, an Order Entry transaction line could only be converted by quantity—you can now convert a line by price as well. The price you supply is used to to determine when a line is partially or fully converted. Price conversion is only supported for non-inventory items. When specifying price conversion, you must use a quantity of 1 and a unit that is a base unit (unit factor of 1).

For more information, see the conversiontype parameter on these functions:

Production units on PJ estimate entries

New Construction functionality enables you to track production unit estimates as part of a project estimate.

You can provide the number of production units (PRODUCTIONUNITS) when creating or updating a PJ estimate entry. You also need to supply a task ID for the entry, and if that task has a production units description (PRODUCTIONUNITDESC), it is inherited.

When you specify production units, posting to the GL budget becomes optional. In other words, you can omit amount/quantity/unit cost for the entry.

For more information, see the PRODUCTIONUNITS parameter on these functions:

Sage Intacct SDK Updates

SDK for Node.js

Version 2.1.0 of the Sage Intacct SDK for Node.js is available on GitHub and NPM.

This version targets Node.js 12.18.0 (or higher). The following enhancements are included in the SDK since it was last mentioned in these release notes.

Version 2.1.0

  • Large HTTP responses are now handled with fetch

Version 2.0.0

  • ClientConfig now includes sessionTimestamp and sessionTimeout
  • Timesheets now support approve, decline, and update operations
  • ApPaymentRequest has been refactored to ApPayment in order to support the new AP payment model (APPYMT in the XML API).
  • New ApPaymentRequestDecline capability is available
  • Request-promise/native has been replaced by node-fetch

See the getting started example to learn about the SDK. Refer to GitHub and NPM for complete information, including fixes released in these versions.

SDK for PHP

Version 3.0.0 of the Sage Intacct SDK for PHP is available on GitHub.

This version targets PHP 7.3 (or higher), and provides several enhancements, including:

  • Timesheets now support approve, decline, and update operations
  • New lookup, getCompanyPrefs, getDimensions, and getDimensionRelationships functions are available
  • ApPaymentRequest has been refactored to ApPayment in order to support the new AP payment model (APPYMT in the XML API).
  • Refactored FulfillmentStatus for OETransactionLineCreate.

See the getting started example to learn about the SDK. Refer to GitHub for complete information, including fixes released in this version.

Provide feedback