- Cash management
- Purchasing and Order Entry
- Accounts Payable
This release is scheduled to go live beginning on the evening of February 18, 2022.
Track federal grant information for your projects
You can now track CFDA (Catalog of Federal Domestic Assistance) grant information for your projects. See the
CFDA and other related parameters for the following project functions:
Credit card reconciliation in bank feeds
In previous releases, only bank accounts were supported when using bank feeds via the API. With this release, credit card accounts are supported as well. You can provide a financial entity (
FINANCIALENTITY) to identify your connected credit card account, then reconcile your account via the API. You can use online bank feeds from Sage Cloud Services, or you can manually create a bank feed that provides your own XML transaction records.
When creating XML transactions for a credit card account, you can specify either
payment as the transaction type. Alternatively, you can specify
deposit for a bank account. For more information, see the
TRANSACTIONTYPE parameter here:
In addition, a read operation on a bank feed object now provides the name of the financial entity (
FINANCIALENTITYNAME), whereas in the past, only the financial entity ID was included. There is also a new parameter that indicates the account type (
Specify primary documents for workflows
In construction, users might need to associate specific documents with any resulting downstream transactions. Likewise, the downstream transactions should link back to the originating document. Now when you create or update a purchasing transaction definition in the API, you can set the
PRIMARYDOC parameter to
true so that the transaction is identified as a primary document. Then, all documents created from the transaction definition, whether automatically or manually, will contain a link to that primary document. Once you enable
PRIMARYDOC for a purchasing transaction definition, you can’t disable the option.
When reading a downstream transaction, your response might include something like the following, where two transaction items point back to a primary doc:
PRIMARYDOC parameter for the following:
Purchasing and Order Entry
Override calculated VAT
When importing or updating Purchasing and Order Entry transactions in VAT-enabled companies, you may need to override the calculated VAT amount to match a tax invoice or for other reasons. There are two ways to use the new
linesubtotals object within order entry and purchasing transactions to override the calculated VAT:
- If you provide a new tax detail ID, the VAT amount for the line subtotal will be calculated using the percentage value set in the tax detail.
- If you provide a new tax detail ID and a new VAT amount, the new amount will be applied to the line subtotal.
linesubtotals object for the following:
- Create Purchasing Transaction (Legacy)
- Update Purchasing Transaction (Legacy)
- Create Order Entry Transaction (Legacy)
- Update Order Entry Transaction (Legacy)
No required fields when creating draft bills
You can now create a draft bill (
ACTION set to
DRAFT) without providing the minimum fields that are required when posting a bill. You must provide values for those fields before a draft bill can be posted. This change only applies to the create APBILL request and not to the legacy
Support for renewal forecast
To support the renewal forecast feature, the system can create CONTRACTDETAIL, CONTRACTBILLINGSCHEDULE, and CONTRACTREVENUESCHEDULE objects with a new
STATE value of
Objects in this state cannot be modified. If you have existing integrations that involve these objects, you might see unexpected data after February 18, 2022.
To ensure that your integrations affect only the data you want, exclude objects in this state, for example:
<query> <object>CONTRACTDETAIL</object> <select> <field>RECORDNO</field> <field>STATE</field> </select> <filter> <notequalto> <field>STATE</field> <value>Renewal forecast</value> </notequalto> </filter> </query>
Get query response in CSV or JSON
returnformat option for
query requests lets you specify the format that will be used in the response, either XML (default), CSV, or JSON. For example, this request would return the list of vendors that are owed more than $100 as plain-text CSV:
<query> <object>VENDOR</object> <select> <field>RECORDNO</field> <field>TOTALDUE</field> </select> <filter> <greaterthan> <field>TOTALDUE</field> <value>100</value> </greaterthan> </filter> <options> <returnformat>csv</returnformat> </options> </query>
See Response data format on the Query page for more information and sample responses.
Disregard temporary read-only fields related to assets
In this release, temporary fields related to assets will appear in responses from several API functions. In particular:
inspectcall on the GLENTRY object returns an
readcall on the GLBATCH object returns
These parameters are not supported in any operations and will be removed in a future release.