A transaction definition includes a subtotals section. You can enter the subtotal details directly in the subtotals table within the transaction definition. Or, if advanced workflow is enabled, you can use subtotal templates to define the subtotals once and then simply refer to them by template name within the transaction definition.
Returns up to 100 object references from the collection with a key, ID, and link for each subtotal template details. This operation is mostly for use in testing; use query to find objects that meet certain criteria and to specify properties that are returned.
OK
Bad Request
{- "ia::result": [
- {
- "key": "28",
- "id": "28",
- "href": "/objects/purchasing/subtotal-template-line/28"
}, - {
- "key": "15",
- "id": "15",
- "href": "/objects/purchasing/subtotal-template-line/15"
}, - {
- "key": "1",
- "id": "1",
- "href": "/objects/purchasing/subtotal-template-line/1"
}
], - "ia::meta": {
- "totalCount": 3,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}
Creates a new subtotal template line object.
description required | string <= 100 characters Provide a description of the subtotal. Each subtotal description must be unique. Example: "HandlingCharge" | ||||
subtotalType required | string Indicates whether the subtotal is discount or charge. Example: "charge" | ||||
valueType required | string The subtotal can be either an amount type or a percent type. Example: "amount" | ||||
txnType required | string or null Indicates whether the subtotal will debit or credit the corresponding GL account and GL offset account. Example: "debit" | ||||
lineNumber | integer <= 8 characters Line number for the subtotal template line. Example: 1 | ||||
defaultValue | string <decimal-precision-10> <= 12 characters Default value for the subtotal, If Example: "10" | ||||
isApportioned | boolean Default: false Indicate whether the discount subtotal will be apportioned across all line items in the transaction. Cannot be enabled if Example: false | ||||
applyToLineNumber | integer or null <= 8 characters Specify the subtotal line number to which the subtotal will apply. Sage Intacct treats the initial subtotal line as line number 0. The first defined subtotal from the transaction definition is line number 1, the second defined subtotal is line number 2, and so on. Example: 1 | ||||
isTax | boolean Default: false Flags the subtotal as a tax. When the transaction posts, the tax will post separately based on the items in the transaction. Set to Example: false | ||||
isAvalaraTax | boolean or null Default: false Set to Example: false | ||||
object Select the GL account to which the subtotal will post. | |||||
| |||||
object Specify the offset GL account to which the subtotal will post. | |||||
| |||||
object The purchasing subtotal template that includes this line detail. | |||||
|
Created
Bad Request
{- "subtotalTemplate": {
- "key": "30"
}, - "description": "HandlingCharge",
- "subtotalType": "charge",
- "valueType": "amount",
- "defaultValue": "20.50",
- "isApportioned": false,
- "glAccount": {
- "id": "1200"
}, - "offsetGLAccount": {
- "id": "1200.01"
}, - "txnType": "debit",
- "applyToLineNumber": 0,
- "isTax": false,
- "isAvalaraTax": false
}
{- "ia::result": {
- "key": "28",
- "id": "28",
- "href": "/objects/purchasing/subtotal-template-line/28"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Returns detailed information for a specified subtotal template line object.
key required | string System-assigned key for the subtotal template line. Example: 28 |
OK
Bad Request
{- "ia::result": {
- "key": "28",
- "id": "28",
- "description": "HandlingCharge",
- "subtotalTemplate": {
- "key": "30",
- "id": "30",
- "href": "/objects/purchasing/subtotal-template/30"
}, - "subtotalType": "charge",
- "lineNumber": 0,
- "valueType": "amount",
- "defaultValue": "20.50",
- "isApportioned": false,
- "glAccount": {
- "key": "36",
- "id": "1200",
- "href": "/objects/general-ledger/account/36"
}, - "offsetGLAccount": {
- "key": "37",
- "id": "1200.01",
- "href": "/objects/general-ledger/account/37"
}, - "txnType": "debit",
- "applyToLineNumber": 0,
- "isTax": false,
- "isAvalaraTax": false,
- "audit": {
- "createdDateTime": "2024-05-15T16:46:11Z",
- "modifiedDateTime": "2024-05-15T16:46:11Z",
- "createdBy": "1",
- "modifiedBy": "1"
}, - "href": "/objects/purchasing/subtotal-template-line/28"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Updates an existing subtotal template line object by setting field values. Any fields not provided remain unchanged.
key required | string System-assigned key for the subtotal template line. Example: 28 |
description | string <= 100 characters Provide a description of the subtotal. Each subtotal description must be unique. Example: "HandlingCharge" | ||||
subtotalType | string Indicates whether the subtotal is discount or charge. Example: "charge" | ||||
lineNumber | integer <= 8 characters Line number for the subtotal template line. Example: 1 | ||||
valueType | string The subtotal can be either an amount type or a percent type. Example: "amount" | ||||
defaultValue | string <decimal-precision-10> <= 12 characters Default value for the subtotal, If Example: "10" | ||||
isApportioned | boolean Default: false Indicate whether the discount subtotal will be apportioned across all line items in the transaction. Cannot be enabled if Example: false | ||||
txnType | string or null Indicates whether the subtotal will debit or credit the corresponding GL account and GL offset account. Example: "debit" | ||||
applyToLineNumber | integer or null <= 8 characters Specify the subtotal line number to which the subtotal will apply. Sage Intacct treats the initial subtotal line as line number 0. The first defined subtotal from the transaction definition is line number 1, the second defined subtotal is line number 2, and so on. Example: 1 | ||||
isTax | boolean Default: false Flags the subtotal as a tax. When the transaction posts, the tax will post separately based on the items in the transaction. Set to Example: false | ||||
isAvalaraTax | boolean or null Default: false Set to Example: false | ||||
object Select the GL account to which the subtotal will post. | |||||
| |||||
object Specify the offset GL account to which the subtotal will post. | |||||
| |||||
object The purchasing subtotal template that includes this line detail. | |||||
|
OK
Bad Request
{- "subtotalType": "charge",
- "defaultValue": "25.00"
}
{- "ia::result": {
- "key": "28",
- "id": "28",
- "href": "/objects/purchasing/subtotal-template-line/28"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Deletes a subtotal template line object.
key required | string System-assigned key for the subtotal template line. Example: 28 |
No Content
Bad Request
{- "ia::result": {
- "ia::error": {
- "code": "invalidRequest",
- "message": "A POST request requires a payload",
- "errorId": "REST-1028",
- "additionalInfo": {
- "messageId": "IA.REQUEST_REQUIRES_A_PAYLOAD",
- "placeholders": {
- "OPERATION": "POST"
}, - "propertySet": { }
}, - "supportId": "Kxi78%7EZuyXBDEGVHD2UmO1phYXDQAAAAo"
}
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 0,
- "totalError": 1
}
}
Queries an object for filtered data.
object | string Object type to query, in the form Example: "purchasing/subtotal-template-line" | ||||||||
fields | Array of strings List of fields to include in the response. Can be any combination of these:
Example: ["key","id","max:vendor.creditLimit"] | ||||||||
Array of equal (object) or not equal (object) or less than (object) or (less than or equal (object)) or greater than (object) or (greater than or equal (object)) or in (object) or not in (object) or between (object) or not between (object) or contains (object) or does not contain (object) or starts with (object) or does not start with (object) or ends with (object) or does not end with (object) Filter conditions to select the objects to return based on their field values. You use operators and conditions to build your filter, such as Example: [{"$eq":{"status":"active"}},{"$gt":{"totalDue":"1000"}},{"$contains":{"name":"Acme"}}] | |||||||||
Array Any of: Field value must be equal to this specified value. For date fields, you can use these macro values that are relative to the current date or the
These are most useful for queries that you want to save and use repeatedly, such as for views or reports. Just change the For example,
| |||||||||
filterExpression | string Default: "and" Logical operators to apply when there are multiple filter conditions. The conditions in the Shortcuts:
Example: "(1 and 2) or 3" | ||||||||
| |||||||||
Array of objects Set the order of the results by specifying field names to sort by and whether they should be in ascending or descending order. Example: [{"totalDue":"asc"},{"lastPaymentMadeDate":"desc"}] | |||||||||
Array
| |||||||||
start | integer First record of the result set to include in the response. Example: 1 | ||||||||
size | integer Number of records to include in the response. Example: 100 |
OK
Bad Request
{- "object": "accounts-payable/vendor",
- "fields": [
- "id",
- "name",
- "status",
- "href"
], - "filters": [
- {
- "$eq": {
- "status": "active"
}
}, - {
- "$eq": {
- "billingType": "openItem"
}
}
], - "filterExpression": "1 and 2",
- "orderBy": [
- {
- "id": "asc"
}
]
}
{- "ia::result": [
- {
- "id": "Vend-00002",
- "name": "Test vendor",
- "status": "active",
- "href": "/objects/accounts-payable/vendor/85"
}, - {
- "id": "VEND-00010",
- "name": "Design Works",
- "status": "active",
- "href": "/objects/accounts-payable/vendor/111"
}
], - "ia::meta": {
- "totalCount": 2,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}