Use a check run to process up to 1,000 checks at a time in an offline process. First create a check run, then add payment requests to the check run. A check run's configuration determines how the checks for the payments in a run are processed.
For more information, see Check run overview in the Sage Intacct Help Center.
Returns a collection with a key, ID, and link for each check run. This operation is mostly for use in testing; use the query service to find objects that meet certain criteria and to specify properties that are returned.
OK
Bad Request
{- "ia::result": [
- {
- "key": "4",
- "id": "All Checks For Mar 2025",
- "href": "/objects/accounts-payable/check-run/4"
}, - {
- "key": "2",
- "id": "All Checks For Apr 2025",
- "href": "/objects/accounts-payable/check-run/2"
}, - {
- "key": "3",
- "id": "All Checks For First week of March 2024",
- "href": "/objects/accounts-payable/check-run/3"
}
], - "ia::meta": {
- "totalCount": 3,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}
Creates a new check run.
title | string <= 80 characters Name of the check run. Example: "All Checks For Mar 2025" | ||
sortOrder | Array of strings Default: ["Check","Vendor","Entity"] Sort order for the list of checks included in the check run. Example: ["Check","Vendor","Entity"] | ||
checksPerPage | string Default: "1" Number of checks to be printed per page. Example: "1" | ||
printCheckStubDetail | boolean Default: false Indicates whether to add transaction details, such as bills or expenses paid with the check, to the check stub for your records. Example: true | ||
printVendorStubDetail | boolean Default: false Indicates whether to add transaction details, such as bills or expenses paid with the check, to the check stub for the vendor records. Example: true | ||
checkStock | string Default: "blankCheckStockMicr" Check stock used for printing. With the Example: "blankCheckStockMicr" | ||
object Checking account associated with the check run, which is required when the | |||
| |||
status | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" |
Created
Bad Request
{- "title": "All Checks For Mar 2025",
- "checkStock": "prePrintedCheckStock",
- "checkingAccount": {
- "id": "BDF"
}, - "sortOrder": [
- "Entity",
- "Check",
- "Vendor",
- "Amount",
- "Date",
- "Bank"
], - "checksPerPage": "3",
- "printCheckStubDetail": true,
- "printVendorStubDetail": true,
- "status": "active"
}
{- "ia::result": {
- "id": "6",
- "key": "6",
- "title": "All Checks For Mar 2025",
- "href": "/objects/accounts-payable/check-run/6"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Returns detailed information for a specified check run.
key required | string System-assigned unique key for the check run. Example: 6 |
OK
Bad Request
{- "ia::result": {
- "id": "6",
- "key": "6",
- "title": "First week Jan 2025",
- "checkStock": "prePrintedCheckStock",
- "checkingAccount": {
- "id": "BDF"
}, - "sortOrder": [
- "Entity",
- "Check",
- "Vendor",
- "Amount",
- "Date",
- "Bank"
], - "checksPerPage": "3",
- "printCheckStubDetail": true,
- "printVendorStubDetail": true,
- "status": "active",
- "whenCreated": "2024-12-21",
- "href": "/objects/accounts-payable/check-run/6"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Updates an existing check run by setting field values. Any fields not provided remain unchanged.
key required | string System-assigned unique key for the check run. Example: 6 |
title | string <= 80 characters Name of the check run. Example: "All Checks For Mar 2025" | ||
sortOrder | Array of strings Default: ["Check","Vendor","Entity"] Sort order for the list of checks included in the check run. Example: ["Check","Vendor","Entity"] | ||
checksPerPage | string Default: "1" Number of checks to be printed per page. Example: "1" | ||
printCheckStubDetail | boolean Default: false Indicates whether to add transaction details, such as bills or expenses paid with the check, to the check stub for your records. Example: true | ||
printVendorStubDetail | boolean Default: false Indicates whether to add transaction details, such as bills or expenses paid with the check, to the check stub for the vendor records. Example: true | ||
checkStock | string Default: "blankCheckStockMicr" Check stock used for printing. With the Example: "blankCheckStockMicr" | ||
object Checking account associated with the check run, which is required when the | |||
| |||
status | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" |
OK
Bad Request
{- "printCheckStubDetail": false,
- "printVendorStubDetail": false,
- "status": "active"
}
{- "ia::result": {
- "key": "6",
- "id": "6",
- "title": "All Checks For Mar 2025",
- "href": "/objects/accounts-payable/check-run/6"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Deletes a check run. For more information about when check runs can be deleted, see Delete a check run in the Sage Intacct Help Center.
key required | string System-assigned unique key for the check run. Example: 6 |
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
}
}