Dunning is the process of communicating with customers to collect overdue balances. Dunning levels define the levels of notices that are sent during the collection process. To learn more, see Dunning notices in the Sage Intacct Help Center.
Returns a collection with a key, ID, and link for each dunning level. 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": "2",
- "id": "DL1",
- "href": "/objects/accounts-receivable/dunning-level/2"
}, - {
- "key": "5",
- "id": "Dunning level",
- "href": "/objects/accounts-receivable/dunning-level/5"
}
], - "ia::meta": {
- "totalCount": 2,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}
Creates a new dunning level. Use naming conventions to establish levels for different customer types, company entities, and amount owed ranges. To learn more, see Add dunning levels in the Sage Intacct Help Center.
id required | string Name or other unique identifier for the dunning level. Example: "L1 Dunning level" | ||||||||||||
object The printed document template assigned to the dunning level. | |||||||||||||
| |||||||||||||
object | |||||||||||||
| |||||||||||||
object Sets how dunning notices are sequentially numbered when they're created. | |||||||||||||
| |||||||||||||
object The email template assigned to the dunning level. | |||||||||||||
| |||||||||||||
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
{- "id": "L1 Dunning level",
- "dunningThreshold": {
- "minDays": 0,
- "maxDays": 100,
- "txnCurrency": "USD"
}, - "printTemplate": {
- "id": "L1 PWD Dunning Notice"
}, - "noticeSequence": {
- "id": "AR-Cr"
}
}
{- "ia::result": {
- "key": "4",
- "id": "L1 Dunning level",
- "href": "/objects/accounts-receivable/dunning-level/4"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Returns detailed information for a specified dunning level.
key required | string System-assigned unique key for the dunning level. Example: 4 |
OK
Bad Request
{- "ia::result": {
- "key": "6",
- "id": "DL1",
- "dunningThreshold": {
- "minDays": 0,
- "maxDays": 100,
- "minAmount": "1000",
- "maxAmount": "10000",
- "baseCurrency": "USD",
- "txnCurrency": "USD"
}, - "printTemplate": {
- "key": "2000492",
- "id": "DL1 Dunning Notice"
}, - "emailTemplate": {
- "key": "3",
- "id": "DL1 PWD template",
- "href": "/objects/company-config/email-template/3"
}, - "noticeSequence": {
- "id": "Ar-Rec"
}, - "status": "active",
- "audit": {
- "createdDateTime": "2025-05-21T09:05:50Z",
- "modifiedDateTime": "2025-05-21T09:05:50Z",
- "createdBy": "1",
- "modifiedBy": "1"
}, - "entity": {
- "key": null,
- "id": null,
- "name": null
}, - "href": "/objects/accounts-receivable/dunning-level/6"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Updates an existing dunning level by setting field values. Any fields not provided remain unchanged.
key required | string System-assigned unique key for the dunning level. Example: 4 |
object The printed document template assigned to the dunning level. | |||||||||||||
| |||||||||||||
object | |||||||||||||
| |||||||||||||
object Sets how dunning notices are sequentially numbered when they're created. | |||||||||||||
| |||||||||||||
object The email template assigned to the dunning level. | |||||||||||||
| |||||||||||||
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
{- "minDays": 10
}
{- "ia::result": {
- "key": "4",
- "id": "L2 Dunning level",
- "href": "/objects/accounts-receivable/dunning-level/4"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Deletes a dunning level.
key required | string System-assigned unique key for the dunning level. Example: 4 |
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
}
}