How collections is usually set up in finance and ERP systems

In most finance systems, collections lives inside the accounts receivable module. Customer master records hold payment terms and the rules that decide when an account counts as delinquent. Aging reports feed worklists, dunning runs produce reminder letters, and write-offs post through restricted journal types that need approval.

Where the delinquency policy sits

The written policy for delinquent accounts rarely exists as one object in the system. It is scattered. Payment terms sit on the customer or the invoice. Aging buckets are defined in receivables configuration. Dunning levels, with their letter templates and escalation triggers, live in a separate setup table. Credit limits and credit holds may be managed in yet another place, sometimes in the sales or order management module.

This matters when changing the process. A policy change on paper may need edits in several configuration areas, and those areas are often owned by different teams.

Aging, worklists and dunning

The aging report is the backbone. It sorts open items by how far past due they are, and most systems let collectors filter by region, customer segment or balance size. Many ERP suites add a collections workbench that turns the aging into a prioritised queue for each collector.

Dunning runs on a schedule. The system checks each open item against its dunning level, generates the next letter or email, and stamps the item with the new level. Some setups block dunning automatically when an item is disputed. Others leave that to a manual flag, which is easy to forget.

Specialist collections tools are common as an add-on. They pull open items from the ERP, score customers by risk, and push notes and promises to pay back into the ledger.

Recording contact and negotiation

Correspondence with delinquent customers is usually the weakest part of the setup. Some teams log calls and emails in the collections workbench. Others keep notes in a CRM, a shared mailbox or a spreadsheet. Promises to pay and payment plans may be recorded as structured data, or as free text that no report can read.

Internal discussions about resolution, with sales, customer service or legal, tend to happen outside the system altogether. The outcome only appears later as a credit note or an adjustment.

How payments land against overdue balances

Cash application decides whether collections work actually reduces the balance. Bank files or lockbox data come in, and the system tries to match each receipt to open invoices using remittance details. Unmatched receipts sit in an unapplied or suspense account until someone researches them.

Where penalties, fees or interest are charged, the configuration should set an allocation order. A common pattern applies money to penalties and administrative charges before interest, and to the principal receivable last. Returned payments, such as bounced cheques, need their own transaction type so that the original invoice reopens and the customer record shows the failure.

Adjustments and write-offs

Small balance adjustments are often allowed within a tolerance set in configuration, posted by collectors without further sign-off. Larger write-offs go through an approval workflow tied to authority limits. The write-off posts against an allowance or bad debt expense account, and the receivable is closed.

Good setups keep a reason code on every adjustment. Without it, nobody can later tell a pricing dispute from a genuine credit loss.

Recovery workout and default accounts

When an account moves into recovery, the usual approach is to change its status in the customer master. That status can block new orders, stop routine dunning, and route the account to a specialist queue. Restructured balances may be rebilled as new instalment invoices, with the old items closed.

Accounts placed in default and handed to an outside agency or legal counsel often leave the main system in practice. The ledger keeps the balance, or the written-off amount, while recoveries come back as receipts against a dedicated account. Tracking what the agency has collected, and its fees, frequently happens in spreadsheets.

Balances owed by related entities

Receivables from sister companies or other units of the same organisation are normally kept apart from external collections. They settle through intercompany netting or transfer processes. Monitoring focuses on whether settlements match the original orders and whether both sides agree for reconciliation. Chasing them with external dunning letters causes confusion and should be switched off.

Questions to ask the people who run it

• Which accounts never get a dunning letter, and who decided that?
• Where do notes from customer calls actually end up?
• When a customer promises to pay, how is that tracked, and what happens if the date passes?
• How are disputed items flagged, and does that flag stop reminders?
• Who can post an adjustment without approval, and how often does that limit get worked around?
• What happens to receipts that cannot be matched, and who clears them?
• How does a write-off decision get made in practice, and is the reason recorded anywhere?
• Once an account goes to an outside agency, how does anyone know what has been recovered?
• Which reports do collectors trust, and which ones do they rebuild by hand?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.