Company dunning configuration

You define company-level settings for the dunning cycle in the ReceivableCompany record. These settings include cycle status tracking, IDM template configuration to generate documents and emails, aging period boundaries for the Selection Job, and currency handling for dunning letters. These settings apply to all customers. You must configure these settings before you run the first dunning cycle.

Cycle Tracking Fields

These fields track the progress of the current dunning cycle. The system updates the fields automatically as each job runs.

LastDunningLetterCycleID

A unique identifier for the current dunning cycle. The Selection job increments this identifier each time a new cycle begins. Records in DunningLetterHeader and DunningLetterDetail contain this identifier, which links each record to the dunning cycle.

DunningLetterCycleStatus

The system tracks the current stage of the dunning cycle. Each job advances the status value when the job completes. The system uses the status field to enforce job sequencing. For example, the File Update Job does not run unless the status is 3. See the state table for more information:

Table 1. Cycle status state reference
Value	State Name	Set By	Meaning
Blank / 4	Ready / DunningCycleComplete	File update job	No cycle is in progress, and the company is ready to run a new Selection Job, serving as the starting state for a new company or the final state after a completed cycle.
1	DunningRecordsSelected	Selection Job	DunningLetterHeader and DunningLetterDetail records exist, and the company is ready for the Print Job.
2	PrintedOrCreatedCSVFile	Print Job (with UpdateHistory = No)	Output is generated (printed letters or CSV), but no history records are created. You can rerun the Print Job or set UpdateHistory = Yes to move to status 3.
3	DunningHistoryProduced	Print Job (with UpdateHistory = Yes)	DunningHistory records are created and ReceivableInvoiceDetail fields are updated. The company is ready for the File Update Job, and the Print Job cannot be rerun with UpdateHistory = Yes.
4	DunningCycleComplete	File Update Job	Transient records are deleted and CompanyCustomer/ReceivableInvoiceDetail tracking fields are updated. The cycle is complete and ready for a new run.

IDM Configuration Fields

These fields configure Infor Document Management (IDM) to generate and email Advanced Dunning letters, using template-based document creation to produce professionally formatted letters for electronic delivery.

UseIDM: Acts as the master switch for IDM integration, enabling the Print Job to use IDM templates to generate dunning letter documents (with or instead of standard print output) when set to Yes, and disabling IDM when set to No.
AdvancedDunningLetterTemplate: The IDM template defines the layout, formatting, and data fields of the Advanced Dunning letter generated as a printed or PDF document, and must reference a valid template configured in IDM.
AdvancedDunningLetterIDMEmailTemplate: The IDM email template defines the email body layout for sending Advanced Dunning letters and works with the customer-level EmailAdvancedDunningLetter flag.
AdvancedDunningLetterIDMEmailSubject: The email subject line for Advanced Dunning letters supports text variables that the system replaces at runtime, such as CompanyName for the company name, CustomerName for the customer name, and PrintDate for the print date.

Aging Configuration Fields

These fields define the aging period boundaries used by the Selection Job when the aging filter is enabled, determining how invoices are grouped by age.

AgePeriods: Defines the day-based boundaries for four standard aging periods, creating buckets such as Current, 1–30, 31–60, 61–90, and 91–120+ days, which the Selection Job uses to include or exclude invoices based on their aging bucket.
ExpandedAgingPeriods: Enables expanded aging periods when set to Yes, providing more granular aging buckets; otherwise, the system uses only the four standard aging periods defined in AgePeriods.

Currency Fields

These fields control how the dunning process handles currency for companies operating with multiple currencies.

Currency: The company’s base currency. The system uses it for dunning letter totals and balances unless multi-currency is enabled.
MultiCurrencyProcessing: When Yes, the system handles multiple currencies and creates separate totals per currency. DunningLetterTotals tracks past-due amounts by currency, so each currency's past-due amount is tracked independently. When No, it uses the company’s base currency..