CreateDunningLevelCommandRequestInput
Adds a dunning level at the end of a scope. It gets the number one higher than the highest number in the scope. Creating the first level of a scope makes this scope apply to its invoices from now on instead of a less specific one. Levels belong to a scope: a company and a customer group, each of which can be ‘all’. For an invoice that has not been dunned yet, the most specific scope that has levels is used, in this order: the company and the customer group of the invoice, the company and all customer groups, all companies and the customer group, all companies and all customer groups. Later notices stay in the scope of the first one. - Request
CreateDunningLevelCommandRequestInputFields
The company the level applies to. Omitted means all companies.
The customer group the level applies to. Omitted means all customer groups.
The name of the level, 1 to 255 characters.
The days the customer gets to pay after the dunning date, 1 to 9999.
The days after the payment due date before a notice at this level can be issued, 0 to 9999. Defaults to 0.
The fee charged with a notice at this level, 0 or more, at most two decimal places. Defaults to 0.
The yearly interest rate in percent, 0 to 100. Defaults to 0.
Client-supplied idempotency key. When provided, a repeated request with the same key and payload replays the original result instead of re-executing the mutation.
Was this page helpful?