NetSuite Bundle v89

Antire Dunning System

Automated payment collection for NetSuite. Send professional dunning letters, track overdue invoices, and manage debt collection with Norwegian legal compliance built-in.

Get Started View Workflows Troubleshooting

6

Dunning Levels

8

Scripts

7

Custom Records

14

Saved Searches

Quick Navigation

Key Features

Fully Automated

Letters generate and send automatically based on configurable rules. Zero manual intervention for routine operations.

Multi-Level Escalation

6 dunning levels from initial reminder (Betalingspåminnelse) through debt collection (Inkasso).

Multi-Subsidiary

Different procedures per subsidiary with Norwegian legal terminology and regulatory compliance.

Smart Email Routing

Source emails from transactions, customers, or manual override. Supports multiple recipients.

Legal Compliance

Built-in support for Norwegian Inkassoloven requirements including fee limits and notice periods.

Full Audit Trail

Track every letter sent, level change, and payment. Complete dunning history per customer.

Quick Start Guide

Get up and running in 10 minutes

Prerequisites

You need a NetSuite role with access to Custom Records, Script Deployments, and the Antire Dunning center tab.

Verify Dunning is Enabled

Navigate to Setup → Antire Dunning → Configuration. Verify Dunning Enabled is checked.

Review Dunning Procedures

Navigate to Lists → Custom → Antire Dunning Procedure. Verify procedures exist for your subsidiary with correct timing (14 days L1, 28 days L2).

Check Email Templates

Navigate to Templates → Marketing Templates. Verify: Level 1 - Betalingspåminnelse and Level 2 - Inkassovarsel.

Verify Script Deployments

Navigate to Customization → Scripting → Script Deployments. Search "Dunning" - ensure all are Released with daily schedule.

Test the System

Create a test invoice. Check Lists → Custom → Antire Dunning for a new record with Level 0 and status "Awaiting Payment".

You're Ready!

The system now automatically creates dunning records for new invoices and processes them through the workflow based on your configured procedures.

Key Concepts

Essential terminology and system components

What is a Dunning Record?

The central tracking entity linking an invoice to the dunning process. Each unpaid invoice has one active dunning record that tracks its payment status, escalation level, and collection history.

1:1

Invoice Ratio

0-5

Level Range

6

Possible Statuses

Record Type

customrecord_rcs_dunning — Navigate: Lists → Custom → Antire Dunning

What is a Dunning Letter?

The actual communication sent to customers. Letters consolidate all eligible invoices for a customer at a specific dunning level into a single communication.

Email

Method ID: 1

Print

Method ID: 2

Record Type

customrecord_rcs_dunning_letter — Navigate: Lists → Custom → Antire Dunning Letter

What is a Dunning Procedure?

Configuration rules that define when and how dunning letters are generated. Create multiple procedures for different subsidiaries, dunning levels, and business scenarios.

Setting	Description	Example
Days Overdue	Days past due before triggering	14, 28
Dunning Level	Which level this procedure creates	1, 2, 3
Subsidiary	Target subsidiary	Norway AS
Dunning Fee	Fee to apply (max NOK 70)	70.00
Use Transaction Email	Source email from invoice	Yes/No

Dunning Levels & Statuses

Level	ID	Name	Norwegian	Timing
0	1	Initial	—	Invoice created
1	2	First Reminder	Betalingspåminnelse	14 days overdue
2	3	Collection Warning	Inkassovarsel	28 days overdue
3	4	Final Notice	Siste varsel	42 days overdue
4	5	Pre-Collection	Før inkasso	56 days overdue
5	6	Debt Collection	Inkasso	Manual escalation

Status IDs

1

Awaiting Payment

2

1st Notif Sent

3

2nd Notif Sent

4

Sent to Collection

5

Paid in Full

6

3rd Notif Sent

Dunning Level Flow

Visual progression through the collection process

L0

Level 0

Invoice Created

Awaiting Payment

L1

Level 1

Betalingspåminnelse

14 days

L2

Level 2

Inkassovarsel

28 days

L3

Level 3

Final Notice

42 days

L4-5

Inkasso

Debt Collection

Collection

Norwegian Term: Betalingspåminnelse (Payment Reminder)

Trigger: 14 days past invoice due date

Maximum Fee: NOK 70 (regulated by Inkassoloven)

Email Template: custemailtmpl_dun_template_lvl1

Purpose

Friendly reminder that payment is overdue. This is optional under Norwegian law but recommended as a goodwill gesture.

Norwegian Term: Inkassovarsel (Collection Warning)

Trigger: 28 days past invoice due date

Maximum Fee: NOK 70 (regulated by Inkassoloven)

Email Template: custemailtmpl_dun_template_lvl2

Legal Requirement

Under Inkassoloven §9, a debtor must receive an Inkassovarsel at least 14 days before a claim can be sent to debt collection. This notice is legally required.

Norwegian Term: Inkasso (Debt Collection)

Trigger: Manual escalation or 56+ days overdue

Action: Refer to external collection agency

Important Warning

Once sent to debt collection, this action typically cannot be reversed. Ensure:

Inkassovarsel was sent at least 14 days ago
All documentation is complete
Manager approval obtained

Process Flow Diagrams

Visual representation of system workflows

Complete Dunning Workflow

Main Flow

flowchart TB subgraph TRIGGER["📋 INVOICE CREATED"] A["New Invoice"] --> B{"Dunning\nEnabled?"} B -->|No| X["No Dunning"] B -->|Yes| C{"Procedure\nExists?"} C -->|No| D["Use Default"] C -->|Yes| E["Use Subsidiary Procedure"] end subgraph INIT["📝 DUNNING RECORD"] D --> F["Create Dunning Record"] E --> F F --> G["Level 0\nAwaiting Payment"] end subgraph DAILY["⏰ SCHEDULED PROCESSING"] H["Map/Reduce Script\nruns daily"] --> I["Load Active Procedures"] I --> J["Search Eligible Records\nDays Overdue + Filters"] J --> K{"Found?"} K -->|No| L["Wait for next run"] K -->|Yes| M["Group by Customer\n+ Due Date + Email"] end subgraph LETTER["✉️ CREATE LETTERS"] M --> N["Create Dunning Letter"] N --> O["Advance Level"] O --> P["Link to Letter"] end subgraph SEND["📤 SEND LETTERS"] Q["Send Script"] --> R{"Method?"} R -->|Email| S["Merge Template\nSend Email"] R -->|Print| T["Generate PDF\nSave to Folder"] S --> U["Mark Sent"] T --> U end G --> H P --> Q L -.-> H U -.-> H style TRIGGER fill:#e0f2fe,stroke:#0284c7 style INIT fill:#dcfce7,stroke:#16a34a style DAILY fill:#fef3c7,stroke:#d97706 style LETTER fill:#f3e8ff,stroke:#9333ea style SEND fill:#ffe4e6,stroke:#e11d48

Email Address Resolution Flow

Email Logic

flowchart LR A["Start"] --> B{"Use Transaction\nEmail?"} B -->|No| C["Use Customer\nEmail Field"] B -->|Yes| D["Check Invoice\nEmail Field"] D --> E{"Has Email?"} E -->|No| C E -->|Yes| F{"Use First\nEmail Only?"} F -->|Yes| G["Take First\nEmail Only"] F -->|No| H["Use All\nEmails"] C --> I["Send Letter"] G --> I H --> I style A fill:#f0fdf4,stroke:#16a34a style I fill:#fef2f2,stroke:#dc2626

System Architecture

Technical

flowchart TB subgraph Records["📁 Custom Records"] R1["Antire Dunning"] R2["Antire Dunning Letter"] R3["Antire Dunning Procedure"] R4["Antire Dunning Configuration"] R5["Antire Dunning Level Map"] end subgraph Scripts["⚙️ Scripts"] S1["rc-norway-dunning-ue.js\n(User Event)"] S2["rc-norway-dunning-mr.js\n(Map/Reduce)"] S3["rc-norway-dunning-letter-send-mr.js\n(Map/Reduce)"] end subgraph Libs["📚 Libraries"] L1["rc-norway-lib.js"] L2["rc-norway-def-lib.js"] end S1 --> R1 S2 --> R1 S2 --> R2 S3 --> R2 S1 --> L1 S2 --> L1 S3 --> L1 L1 --> L2 style Records fill:#dbeafe,stroke:#2563eb style Scripts fill:#fef3c7,stroke:#d97706 style Libs fill:#f3e8ff,stroke:#9333ea

User Roles

Who does what in the dunning system

Dunning Manager

Primary user responsible for daily dunning operations and customer communication.

Review dunning records daily
Pause/resume dunning for specific customers
Approve escalations to debt collection
Handle customer disputes
Set agreed payment dates
Monitor email delivery

Finance Team

Oversees financial impact and reconciliation of dunning activities.

Monitor overdue invoice aging
Track dunning fee revenue
Reconcile payments received
Review debt collection referrals
Generate AR reports
Audit dunning compliance

System Administrator

Maintains system configuration, scripts, and technical operations.

Configure dunning procedures
Manage email templates
Monitor script deployments
Troubleshoot errors
Manage user permissions
Update PDF templates

Daily Tasks

Morning checklist for Dunning Managers

Morning Checklist

Check Script Execution Logs

Navigate to Customization → Scripting → Script Deployments. Verify no errors in overnight runs.

Review New Dunning Letters

Check Lists → Custom → Antire Dunning Letter for letters created overnight. Verify correct recipients.

Check Held Letters

Filter for "Hold Email = Yes" to review any letters pending manual release.

Review Paused Dunning

Check for records with "Pause Dunning = Yes" that may need to be resumed.

Monitor Debt Collection Queue

Review records flagged "To Be Sent For Debt Collection" before processing.

Common Scenarios

Find the Dunning Record

Search Lists → Custom → Antire Dunning by customer name or invoice number.

Set Agreed Payment Date

Enter the promised date in Agreed Payment Date field.

Pause Dunning

Check Pause Dunning and enter reason: "Payment promised for [date]"

Set Calendar Reminder

Create reminder to follow up if payment not received by agreed date.

Pause Dunning Immediately

Check Pause Dunning with reason: "Under dispute - [brief description]"

Document the Dispute

Add notes to the dunning record with dispute details and customer contact.

Escalate Internally

Notify accounts receivable or sales team to resolve the dispute.

Resume When Resolved

Once resolved, uncheck Pause and allow normal processing to continue.

Pause Dunning

Check Pause Dunning with reason: "Payment plan agreed - [frequency/amount]"

Document Plan Details

Record payment schedule, amounts, and dates in the dunning record notes.

Set Monitoring Schedule

Create reminders to verify each scheduled payment is received.

Resume if Defaulted

If customer misses a payment, uncheck Pause and resume dunning from current level.

Step-by-Step Procedures

How to perform common dunning operations

How to Pause Dunning

Navigate to the Dunning Record

Lists → Custom → Antire Dunning. Search by customer name or invoice number.

Click Edit

Open the record in edit mode.

Check "Pause Dunning"

Find the custrecord_rcs_dun_pause_chbx checkbox and check it.

Enter Pause Reason

Select or enter a reason in custrecord_rcs_dun_pause (required for audit trail).

Save the Record

Click Save. The record will be excluded from all future dunning processing until resumed.

How to Escalate to Debt Collection

Verify Prerequisites

Confirm: Inkassovarsel sent ≥14 days ago, all documentation complete, manager approval obtained.

Open the Dunning Record

Navigate to the dunning record and click Edit.

Check "To Be Sent For Debt Collection"

Check the custrecord_rcs_dun_debt_collection_chbx checkbox.

Save and Process

Save the record. The scheduled script will process the escalation and set the "Sent To Debt Collection" flag.

Legal Warning — Inkassoloven Requirements

Before sending to debt collection, Norwegian law requires:

Inkassovarsel must be sent at least 14 days before debt collection
Maximum dunning fee per notice: NOK 70
All communication must be documented

System Configuration

Global settings and procedure setup

Configuration Record

Navigate: Setup → Antire Dunning → Configuration or Lists → Custom → Antire Dunning Configuration

Setting	Field ID	Description
Dunning Enabled	`custrecord_rcs_is_dunning_enabled`	Master switch to enable/disable all dunning globally
Default Dunning Procedure	`custrecord_rcn_default_dunning_procedure`	Fallback procedure when no subsidiary-specific procedure exists

Dunning Procedure Setup

Navigate: Lists → Custom → Antire Dunning Procedure

Field	Field ID	Description
Name	`name`	Procedure name (e.g., "Norway L1 - 14 Days")
Dunning Level	`custrecord_rcs_dp_level`	Target level (1-5)
Days Overdue	`custrecord_rcs_dp_days_to_send_letter`	Days past due to trigger
Subsidiary	`custrecord_rcs_dp_subsidiary`	Target subsidiary
Saved Search	`custrecord_rcs_dp_saved_search_dun`	Search for eligible records
Letter Template	`custrecord_rcs_dunning_letter_template`	PDF template script ID
Dunning Fee	`custrecord_rcs_dp_dunning_fee`	Fee amount (max NOK 70)
Fee Percent	`custrecord_rcs_dp_dunning_fee_percent`	Percentage-based fee
Send From	`custrecord_rcs_dp_email_sent_from`	Employee to send from
Use Tran Email	`custrecord_rcs_dp_use_tran_email_address`	Source email from transaction
Use First Email	`custrecord_rcs_dp_use_tran_first_email`	Use only first email if multiple
Is L0 Procedure	`custrecord_rcs_dp_l0_procedure`	Mark as Level 0 (initial) procedure
Rule Order	`custrecord_rcs_dp_rule_order`	Processing sequence
Print Folder	`custrecord_rcs_dp_print_id`	Folder for PDF output

Bundle Contents

Complete inventory of NetSuite Bundle v89

7

Custom Records

8

Scripts

6

Libraries

14

Saved Searches

4

Custom Lists

8

Custom Fields

Record Name	Script ID	Purpose
Antire Dunning	`customrecord_rcs_dunning`	Main dunning tracking record
Antire Dunning Letter	`customrecord_rcs_dunning_letter`	Dunning communication records
Antire Dunning Procedure	`customrecord_rcs_dunning_procedure`	Configuration rules
Antire Dunning Configuration	`customrecordrcs_config_record`	Global settings
Antire Dunning Level	`customrecord_rcs_dunning_levels`	Level definitions (5 records)
Antire Dunning Level Map	`customrecord_rcs_dunning_level_map`	Level transition rules (5 records)
Antire Dunning Status	`customrecord_rcs_dunning_status`	Status definitions (6 records)

Entity Fields (Customer)

Field Name	Field ID
Antire Dunning Manager	`custentity_rcs_dunning_manager`
Exclude from Dunning	`custentity_ant_cus_exclude_from_dun`
Antire Dunning Sending Method	`custentity_rcn_cust_dun_send_method`

Transaction Body Fields

Field Name	Field ID
Antire Dunning Fees Checkbox	`custbody_rcs_dunning_fees_inv_checkbox`
Transaction Related Email	`custbody_rcs_dun_tran_rel_email`
Exclude from Dunning	`custbody_ant_tran_exclude_from_dun`
Related Antire Dunning Record	`custbody_rm_related_rcs_dunning_record`
Antire Dunning Fees	`custbody_rcs_dunning_fees_inv_2`

List Name	List ID	Values
Antire Dunning Pause Reason	`customlist_rcs_dunning_pause_reason`	4 records
Antire Dunning Letter List	`customlist_rcs_dl_list`	3 records
Antire Dunning Fees	`customlist_ot_rcs_dunning_fee`	2 records
Antire Dunning Sending Method	`customlist_rcs_dunning_send_meth`	2 records (Email, Print)

Advanced PDF Templates

Template Name	Script ID
Antire Dunning Letter - Master Template	`custtmpl_216_6227880_270`
Antire Dunning Letter Template - Teqva	`custtmpl_615_7083689_942`

Email Templates

Template Name	Script ID	Level
Level 1 - Betalingspåminnelse	`custemailtmpl_dun_template_lvl1`	Level 1
Level 2 - Inkassovarsel	`custemailtmpl_dun_template_lvl2`	Level 2

System Architecture

How the components work together

User Event Layer

Triggers on record create/edit. Creates initial dunning records when invoices are created. Sources email addresses from transactions.

Map/Reduce Layer

Scheduled batch processing. Creates dunning letters, sends emails, generates PDFs. Handles large volumes efficiently.

Library Layer

Shared business logic. Configuration loading, email sending, PDF rendering, level transitions. Used by all scripts.

Processing Flow

1. Invoice Created → User Event creates Dunning Record (Level 0)

2. Daily at 2 AM → Map/Reduce finds eligible records, creates Dunning Letters

3. Daily at 4 AM → Map/Reduce sends letters via email or saves PDFs

4. Cycle Repeats → Records advance through levels based on days overdue

Scripts Reference

All SuiteScripts in the bundle

Map/Reduce Scripts (4)

rc-norway-dunning-mr.jsMap/Reduce

Script ID: customscript_rcn_dunning_letter_mr

Deployment: RCN | Dunning Letter | MR

Schedule: Daily at 2:00 AM

Purpose: Main processing script. Loads dunning procedures, searches for eligible records based on days overdue, groups by customer/due date/email, creates dunning letters, and advances level.

Parameters: custscript_rcn_dunning_letter_subsidiar — Optional subsidiary filter

rc-norway-dunning-letter-send-mr.jsMap/Reduce

Script ID: customscript_rcn_dunning_letter_send_mr

Deployment: RCN | Dunning Letter Send | MR

Schedule: Daily at 4:00 AM

Purpose: Sends generated dunning letters. Finds unsent letters, validates email addresses, merges templates, sends emails or generates PDFs, marks as sent.

Parameters: custscript_rcn_dunning_letter_send_sub — Optional subsidiary filter

rm-mr-create-dunning-records.jsMap/Reduce

Script ID: customscript_rm_mr_create_dunning_record

Deployment: RM | MR | Create Dunning Records

Schedule: On-demand

Purpose: Batch creates dunning records from a saved search of transactions. Used for initial setup or backfill processing.

Parameters: custscript_rm_tran_srch_for_dunning_rec — Saved search ID

rc-norway-dunning-fee-mr.jsMap/Reduce

Script ID: customscript_rcn_add_dunning_fees_mr

Deployment: RCN | Add Dunning Fees | MR

Schedule: Monthly

Purpose: Creates subscription fee items for dunning charges based on configured percentages. Integrates with Zone Advanced Billing (ZAB).

User Event Scripts (4)

rc-norway-dunning-ue.jsUser Event

Script ID: customscript_rcn_dunning_create_invoice

Deployment: RCN | Dunning Creation | UE

Triggers: After Submit on Invoice, Dunning Letter

Purpose: Creates initial dunning record when invoice is created. Links to appropriate dunning procedure based on subsidiary. Also populates dunning level history JSON on letters.

AN-UE-Dunning-Related-Customizations-On-Multiple-Records.jsUser Event

Script ID: customscript_an_ue_dun_rel_rec_cust

Deployments: customdeploy_an_ue_dun_rel_rec_cust_dunl (Dunning Letter), customdeploy_an_ue_dun_rel_rec_cust_dunr (Dunning Record)

Purpose: Sources email addresses from transactions and sets them on dunning-related fields. Handles "Use Transaction Email" and "Use First Email" settings.

AN_UE_Source_Email_Addresses_From_Transaction.jsUser Event

Script ID: customscript_an_ue_src_email_addr_frm_tr

Deployment: AN | UE | Source Email Address From Tran

Purpose: Alternative email sourcing script. Extracts email from transaction JSON data and populates the email field on dunning letters.

rc-norway-sublist-report-field-ue.jsUser Event

Script ID: customscript_rcn_sublist_rprt_flds_ue

Deployment: RCN Sublist Report Fields UE

Purpose: Adds "Refresh report data" button on dunning records. Updates sublist data from related records for display purposes.

Libraries (6)

Library	File ID	Purpose
rc-norway-lib.js	1291753	Core library: email sending, PDF rendering, record updates, searches
rc-norway-def-lib.js	1291752	Definitions: record types, field IDs, status enums, level mappings
rc-norway-auto-email-lib.js	1291755	Automated email functionality
rc-xml-parser-lib.js	1291754	XML parsing for bank file processing
cs-form-builder-lib.js	1291751	Dynamic form building utilities
cs-moment.js	1291750	Date/time formatting (Moment.js)

Field Reference

Complete field reference for main records

Field	Field ID	Type
Invoice	`custrecord_rcs_dun_invoice`	List/Record
Customer	`custrecord_rcs_dun_customer`	List/Record
Dunning Status	`custrecord_rcs_dun_status`	List
Dunning Level	`custrecord_rcs_dunning_level`	List
Dunning Procedure	`custrecord_rcn_dun_rec_dunning_procedure`	List/Record
Invoice Amount	`custrecord_rcs_dun_inv_amount`	Currency
Due Amount	`custrecord_rcs_dun_inv_due_amount`	Currency
Invoice Due Date	`custrecord_rcs_dun_inv_due_date`	Date
Dunning Due Date	`custrecord_rcs_dun_dunning_duedate`	Date
Pause Dunning	`custrecord_rcs_dun_pause_chbx`	Checkbox
Pause Reason	`custrecord_rcs_dun_pause`	List
Agreed Payment Date	`custrecord_rcs_dun_agreed_date`	Date
To Be Sent For Debt Collection	`custrecord_rcs_dun_debt_collection_chbx`	Checkbox
Sent To Debt Collection	`custrecord_rcs_dun_sent_debt_collec_chbx`	Checkbox
Dunning Letter Sent	`custrecord_rcs_dun_dunning_letter_sent`	Checkbox
Dunning Letter Sent Date	`custrecord_rcs_dun_dl_sent_date`	Date
Locked	`custrecord_rcs_dun_locked_checkbox`	Checkbox

Field	Field ID	Type
Customer	`custrecord_rcs_dl_customer`	List/Record
Subsidiary	`custrecord_rcs_dl_subsidiary`	List/Record
Dunning Level	`custrecord_rcs_dl_letter`	List
Dunning Procedure	`custrecord_rcs_dl_dunning_procedure`	List/Record
Email Contact	`custrecord_rcs_dl_email`	Email
Email From Transaction	`custrecord_rcs_dl_email_from_transaction`	Text
Email Template	`custrecord_rcs_dl_email_tamplate`	List/Record
Sending Method	`custrecord_rcs_dl_sending_method`	List
Dunning Fee	`custrecord_rcs_dl_fee`	Currency
Dunning Fee Percent	`custrecord_rcs_dl_dunning_fee_percent`	Percent
Sent	`custrecord_rcs_dl_sent_checkbox`	Checkbox
Sent Date	`custrecord_rcs_dl_sent_date`	Date
Hold Email	`custrecord_rcs_dl_hold_email`	Checkbox
Send Attachments	`custrecord_rcs_dl_send_attachments`	Checkbox
Dunning Hidden JSON	`custrecord_rcs_dl_dunning_hidden_json`	Long Text

Field	Field ID	Type
Name	`name`	Text
Dunning Level	`custrecord_rcs_dp_level`	List
Days Overdue	`custrecord_rcs_dp_days_to_send_letter`	Integer
Subsidiary	`custrecord_rcs_dp_subsidiary`	List/Record
Saved Search	`custrecord_rcs_dp_saved_search_dun`	List/Record
Letter Template	`custrecord_rcs_dunning_letter_template`	Text
Email Template	`custrecord_rcs_dp_email_template`	List/Record
Dunning Fee	`custrecord_rcs_dp_dunning_fee`	Currency
Fee Percent	`custrecord_rcs_dp_dunning_fee_percent`	Percent
Send From Employee	`custrecord_rcs_dp_email_sent_from`	List/Record
Use Transaction Email	`custrecord_rcs_dp_use_tran_email_address`	Checkbox
Use First Email	`custrecord_rcs_dp_use_tran_first_email`	Checkbox
Is L0 Procedure	`custrecord_rcs_dp_l0_procedure`	Checkbox
Rule Order	`custrecord_rcs_dp_rule_order`	Integer

Saved Searches

All saved searches in the bundle

Search Name	Script ID	Category
Antire Dunning Records - All	`customsearch_all_rcs_dunning_records`	Dunning
Antire Dunning - Procedures - All	`customsearch_rcs_dunning_status_remin__2`	Dunning
#Antire Dunning Records - Default Procedure#	`customsearch_rcs_default_procedure_srch`	Dunning
#Antire Dunning (Procedure) - Default Subsidiary	`customsearch_rcs_default_procedure_subs`	Dunning
Antire Dunning Letter Search for Levels - Do not DELETE	`customsearch_dunning_let_search_by_level`	Letter
Antire Dunning Letters - No Dunning	`customsearch_rcs_dunning_letters_2`	Letter
Antire Dunning Letters - All	`customsearch_rcs_dunning_letters`	Letter
Antire Dunning Level Map Next Step	`customsearch443`	Level Map
Antire Dunning Procedure	`customsearch_rcs_dp_overview`	Procedure
Antire Dunning Script Deployments	`customsearch_rcs_dunning_deployment`	Deployment
*\|MR\| Dunning - Transaction Search - Creating Dunning Records	`customsearch_rm_tran_dun_create_mr`	Transaction
#Antire Dunning Related Transactions#	`customsearch_rcs_dunning_open_invoices`	Transaction
*\|MR\| Dunning - Transaction Search - Creating Dunning Records - Teqva	`customsearch_rm_tran_dun_create_mr_2`	Transaction

Important: Do Not Delete Critical Searches

Searches marked with * are referenced by scripts and must not be deleted or modified without understanding the impact. Deleting these will cause script failures.

Troubleshooting

Common issues and solutions

Check these items:

Verify Dunning is Enabled

Navigate to Lists → Custom → Antire Dunning Configuration. Ensure Dunning Enabled is checked.

Check Subsidiary Procedure

Verify a dunning procedure exists for the invoice's subsidiary with Is L0 Procedure checked.

Verify Script Deployment

Navigate to Customization → Scripting → Script Deployments. Search for RCN | Dunning Creation | UE. Ensure status is Released and deployed to Invoice records.

Check Execution Logs

View deployment execution log for errors. Look for "dunningRecord Created" success message.

Check these items:

Verify Letter Has Email Address

Open the dunning letter. Check either Email Contact or Email From Transaction has a value.

Check Hold Email Flag

Ensure Hold Email checkbox is NOT checked.

Verify Related Dunning Records Not Paused

Check that linked dunning records have Pause Dunning unchecked.

Check Send From Employee

Verify the Send From Employee is set on the procedure and the employee has a valid email.

Check Script Deployment

Verify RCN | Dunning Letter Send | MR is Released and scheduled.

Email address priority (highest to lowest):

Email From Transaction — If "Use Transaction Email" is enabled on procedure
First Email Only — If "Use First Email" is also enabled
Customer Email — Default fallback from dunning letter record

Solution

Check the procedure settings for Use Transaction Email and Use First Email. Verify the invoice has the correct email in custbody_rcs_dun_tran_rel_email.

How to diagnose:

Find the Deployment

Navigate to Customization → Scripting → Script Deployments. Search for the script name.

View Execution Log

Click on the deployment, then click the Execution Log tab.

Filter for Errors

Filter by Type = "Error" to see only error entries.

Review Error Details

Click on each error to see the full stack trace and context.

Common error codes:

Error	Cause	Solution
`RCRD_DSNT_EXIST`	Record ID doesn't exist	Verify record hasn't been deleted
`INVALID_FLD_VALUE`	Bad field value	Check field type and valid values
`SSS_MISSING_REQD_ARGUMENT`	Missing required parameter	Review script parameters
`INSUFFICIENT_PERMISSION`	Access denied	Check script execution role

Common PDF issues:

Issue	Solution
Missing VAT number / footer	Use `render.transaction()` instead of `record.load()` for invoice attachments
Template not found	Verify `Letter Template` script ID on procedure matches actual template
Blank PDF	Check template has proper FreeMarker syntax and record data is available
PDF not saving	Verify `Print Folder` on procedure points to valid File Cabinet folder

Frequently Asked Questions

Quick answers to common questions

You have two options:

Per-Invoice: Pause each dunning record individually (temporary)
Customer-Level: Check Exclude from Dunning on the customer record (permanent)

The customer-level exclusion prevents new dunning records from being created for any future invoices.

Yes, but you'll need to manually trigger it:

Open the dunning letter record
Uncheck the Sent checkbox
Clear the Sent Date field
Save the record
The letter will be picked up in the next scheduled send run

The dunning record's Due Amount field is sourced from the invoice and updates automatically when payments are applied. The dunning process continues based on the remaining balance. If paid in full, the status changes to "Paid in Full" and dunning stops.

Under Inkassoloven (Norwegian Debt Collection Act):

Inkassovarsel required: Must send at least 14 days before debt collection
Maximum fee: NOK 70 per dunning notice
Interest rules: Maximum rate set by Norges Bank + margin
Documentation: Must maintain records of all communication

Default schedule:

Dunning Letter Creation (rc-norway-dunning-mr): Daily at 2:00 AM
Dunning Letter Send (rc-norway-dunning-letter-send-mr): Daily at 4:00 AM
Dunning Record Creation: On-demand only
Dunning Fees: Monthly

Schedules can be modified in the script deployment settings.

Yes. The Map/Reduce scripts have a subsidiary parameter:

custscript_rcn_dunning_letter_subsidiar — For letter creation
custscript_rcn_dunning_letter_send_sub — For letter sending

Set these in the script deployment parameters to process only specific subsidiaries.

Glossary

Key terms and definitions

Dunning

The process of systematically communicating with customers to collect overdue payments through escalating notices.

Betalingspåminnelse

Norwegian for "Payment Reminder" — Level 1 notice sent 14 days after invoice due date.

Inkassovarsel

Norwegian for "Collection Warning" — Level 2 notice sent 28 days after due date. Legally required before debt collection.

Inkasso

Norwegian for "Debt Collection" — Referral to external collection agency for recovery of unpaid debts.

Inkassoloven

Norwegian Debt Collection Act — Legislation governing debt collection practices including notice requirements and fee limits.

Dunning Level

Escalation stage in the collection process (0-5), representing increasing urgency and communication intensity.

Dunning Procedure

Configuration record defining rules for when and how dunning letters are generated for a specific subsidiary and level.

Map/Reduce Script

NetSuite script type optimized for processing large data volumes in parallel, used for batch dunning operations.

User Event Script

NetSuite script that runs automatically when records are created, edited, or deleted. Triggers dunning record creation.

Subsidiary

Legal entity within NetSuite representing a company, business unit, or geographic region with separate accounting.

Antire Dunning System

Quick Navigation

Daily Tasks

Pause Dunning

Configure

Fix Issues

Scripts

Key Features

Fully Automated

Multi-Level Escalation

Multi-Subsidiary

Smart Email Routing

Legal Compliance

Full Audit Trail

Quick Start Guide

Prerequisites

Verify Dunning is Enabled

Review Dunning Procedures

Check Email Templates

Verify Script Deployments

Test the System

You're Ready!

Key Concepts

What is a Dunning Record?

Record Type

What is a Dunning Letter?

Email

Print

Record Type

What is a Dunning Procedure?

Dunning Levels & Statuses

Status IDs

Dunning Level Flow

Purpose

Legal Requirement

Important Warning

Process Flow Diagrams

Complete Dunning Workflow

Email Address Resolution Flow

System Architecture

User Roles

Dunning Manager

Finance Team

System Administrator

Daily Tasks

Morning Checklist

Check Script Execution Logs

Review New Dunning Letters

Check Held Letters

Review Paused Dunning

Monitor Debt Collection Queue

Common Scenarios

Find the Dunning Record

Set Agreed Payment Date

Pause Dunning

Set Calendar Reminder

Pause Dunning Immediately

Document the Dispute

Escalate Internally

Resume When Resolved

Pause Dunning

Document Plan Details

Set Monitoring Schedule

Resume if Defaulted

Step-by-Step Procedures

How to Pause Dunning

Navigate to the Dunning Record

Click Edit

Check "Pause Dunning"

Enter Pause Reason

Save the Record

How to Escalate to Debt Collection

Verify Prerequisites

Open the Dunning Record

Check "To Be Sent For Debt Collection"

Save and Process

Legal Warning — Inkassoloven Requirements

System Configuration

Configuration Record

Dunning Procedure Setup