11.3 Aging Definitions, Collections Workspace & Customer Pools
Key Takeaways
- Aging Period Definitions establish the analytical time buckets (e.g., Current, 30, 60, 90, 120+ days) and interval direction (Backward for historical delinquency tracking vs. Forward for cash flow forecasting).
- The Customer Aging Snapshot (Credit and collections > Periodic tasks > Age customer balances) pre-calculates and caches customer aged balances to provide high-performance querying in the Collections workspace across single or multiple legal entities.
- The Collections Workspace serves as the centralized command center for collectors, providing instant visibility into delinquent balances, customer pools, open collection activities, and dispute tracking.
- Customer Pools utilize query-based (SysQuery) segmentation criteria to dynamically divide customer portfolios by delinquency status, balance thresholds, collector assignment, or geographic region.
- Dispute Management allows collection agents to mark specific open invoice lines as 'In Dispute', assign Dispute Reason Codes, track disputed amounts separately, and temporarily suppress automated collection escalations.
Last updated: August 2026
11.3 Aging Definitions, Collections Workspace & Customer Pools
Quick Summary: Efficient collection of outstanding receivables is critical to maintaining enterprise liquidity and working capital. In Microsoft Dynamics 365 Finance, the collections framework combines Aging Period Definitions (configurable time buckets with backward or forward interval directions), high-performance Aging Snapshots (pre-calculated multi-company balance caches), dynamic Customer Pools (query-driven portfolio segmentation), and the Collections Workspace (the operational hub for collectors). Furthermore, built-in Dispute Management and Collection Activities enable collectors to log promises-to-pay, schedule follow-ups, and isolate disputed invoices from statutory escalation ladders.
1. Aging Period Definitions: Configuration & Directional Logic
Aging Period Definitions define the discrete chronological time horizons used to categorize open customer balances across reports, balance snapshots, and workspace grids.
Navigation
- Path:
Credit and collections > Setup > Aging period definitions(also accessible viaAccounts receivable > Setup > Collections > Aging period definitions)
+---------------------------------------------------------------------------------------------------------+
| Aging Period Definition Configuration Setup |
+---------------------------------------------------------------------------------------------------------+
| Aging Definition ID: [ STANDARD_30_60_90 ] Description: Standard 30-Day Aging Buckets |
| Interval Direction: [ Backward ] Printing Direction: [ Normal ] |
+---------------------------------------------------------------------------------------------------------+
| PERIOD INTERVALS GRID: |
| Period Code | Description | Unit | Interval | Start Date / Offset | Calculation Logic |
| ------------- | ---------------------- | ---- | :------: | ----------------------- | ------------------- |
| `CURRENT` | Current / Not Yet Due | Days | 0 | 0 (Due Date $\ge$ Today) | Current open balance|
| `PAST_30` | 1 – 30 Days Overdue | Days | 30 | -1 to -30 Days | 1-30 days past due |
| `PAST_60` | 31 – 60 Days Overdue | Days | 30 | -31 to -60 Days | 31-60 days past due |
| `PAST_90` | 61 – 90 Days Overdue | Days | 30 | -61 to -90 Days | 61-90 days past due |
| `PAST_120+` | Over 90 / 120+ Days | Days | 999 | -91 Days and Older | Critical bad debt |
+---------------------------------------------------------------------------------------------------------+
Interval Direction Comparison: Backward vs. Forward
The Interval setting dictates how the aging engine projects time relative to the selected aging cutoff date:
| Direction | Projection Horizon | Primary Use Case & Business Objective | Exam Distinction |
|---|---|---|---|
| Backward | Projects into the past (historical overdue days: 0 to -30, -31 to -60, etc.). | Collections & Delinquency Management: Evaluates how many days an unpaid invoice has remained overdue past its due date. Essential for bad debt provisioning and credit risk. | Default for Collections Workspace & MB-310 collection questions. |
| Forward | Projects into the future (upcoming maturities: +1 to +30, +31 to +60 days). | Cash Flow Inflow Forecasting: Evaluates when expected cash receipts will mature in future periods. Used by Treasury teams to project short-term cash liquidity. | Used when analyzing upcoming receivable maturities. |
Printing Direction: Normal vs. Descending
- Normal: Prints aging columns chronologically from left to right starting with current/youngest balances (
Current$\rightarrow$30$\rightarrow$60$\rightarrow$90+). - Descending: Inverts the column display order, placing the most severely delinquent balances on the far left (
90+$\rightarrow$60$\rightarrow$30$\rightarrow$Current).
2. Customer Aging Snapshot Generation
Real-time calculation of aged balances across tens of thousands of customer subledger transactions would severely degrade database performance. Dynamics 365 Finance eliminates this latency by utilizing Customer Aging Snapshots.
Navigation
- Path:
Credit and collections > Periodic tasks > Age customer balances
+---------------------------------------------------------------------------------------------+
| Age Customer Balances Parameters Form |
+---------------------------------------------------------------------------------------------+
| Parameters: |
| - Aging period definition: ........... [ STANDARD_30_60_90 ] |
| - Pool ID: ........................... [ (Optional: Filter by Specific Pool) ] |
| - Criteria (Aging Date Origin): ...... [ Due date ] (Options: Transaction / Document date) |
| - Aging as of date: .................. [ 08/31/2026 ] |
| - Update collection status: .......... [ Yes ] |
| - Company selection: ................. [ All ] (Options: Current / Selected / All) |
+---------------------------------------------------------------------------------------------+
| Batch Processing Tab: |
| - Batch processing: .................. [ Yes ] |
| - Recurrence: ........................ [ Daily at 01:00:00 AM ] |
+---------------------------------------------------------------------------------------------+
Key Snapshot Generation Parameters
- Criteria (Date Calculation Basis):
- Due date (Standard): Ages transactions based on when payment was legally due (
CustTrans.DueDate). Invoices not yet past their due date fall into theCurrentbucket. - Transaction date: Ages transactions based on the voucher posting date (
CustTrans.TransDate), ignoring granted payment terms. - Document date: Ages transactions based on the vendor/customer original document date.
- Due date (Standard): Ages transactions based on when payment was legally due (
- Company Selection (Cross-Company Collections): Selecting All generates consolidated snapshot records across all participating legal entities, enabling shared service collections agents to view a customer's global balance without switching legal entity companies in the UI.
- Batch Scheduling Best Practice: Aging snapshots should always be scheduled as an overnight recurring batch job. When collections agents begin their workday, the Collections workspace immediately displays refreshed aged balances without waiting for runtime processing.
3. The Collections Workspace: Functional Hub for Collectors
Navigation
- Path:
Credit and collections > Collections
+---------------------------------------------------------------------------------------------------------+
| D365 Finance Collections Workspace Layout |
+---------------------------------------------------------------------------------------------------------+
| SUMMARY TILES (KPIs): |
| [ 42 Overdue Customers ] [ $1.24M Past Due Balance ] [ 15 Disputed Invoices ] [ 8 Open Activities]|
+---------------------------------------------------------------------------------------------------------+
| FILTER PANE: |
| Customer Pool: [ MIDWEST_COMMERCIAL ] Aging Definition: [ STANDARD_30_60_90 ] |
+---------------------------------------------------------------------------------------------------------+
| CUSTOMER AGING GRID: |
| Customer ID | Customer Name | Legal Entity | Total Balance | Current | 30 Days | 60 Days | 90+ Days|
| ----------- | ------------------- | :----------: | :-----------: | :-------: | :------: | :-----: | :-----: |
| `US-0101` | Northwind Traders | USMF | $145,000.00 | $50,000 | $40,000 | $35,000 | $20,000 |
| `US-0108` | Litware Corp | USMF | $82,400.00 | $12,400 | $20,000 | $50,000 | $0 |
| `DE-0205` | Bavarian Motor Tech | DEMF | $210,000.00 | $0 | $60,000 | $50,000 | $100,000|
+---------------------------------------------------------------------------------------------------------+
| ACTION PANE CONTROLS (SELECTED CUSTOMER): |
| [ Manage Customer ] [ Transactions ] [ Write-Off ] [ Collection Letter ] [ Interest Note ] [ Activities]|
+---------------------------------------------------------------------------------------------------------+
Core Collections Workspace Operations
- Customer Detail Pane: Provides instant drill-down into customer master data, contact details, payment terms, credit limits, and credit management hold status.
- Transaction View: Displays all open subledger vouchers for the selected customer. From this grid, collectors can:
- Change transaction collection status (
Open,Promise to pay,Disputed,Resolved). - Mark individual invoice lines as In Dispute.
- Initiate single-invoice or full-balance Write-offs.
- View historical collection letter codes and interest notes.
- Change transaction collection status (
- Action Items & Activity Logging: Allows collectors to log customer phone conversations, record promise-to-pay commitments with dollar amounts and target dates, and assign follow-up tasks to colleagues.
4. Customer Pools: Dynamic Portfolio Segmentation
Customer Pools are query-based filters that segment the customer master database into manageable work queues for collection teams.
Navigation
- Path:
Credit and collections > Setup > Customer pools
+---------------------------------------------------------------------------------------------+
| Customer Pool Setup & Query Criteria |
+---------------------------------------------------------------------------------------------+
| Pool ID: [ MIDWEST_DELINQUENT ] Pool Type: [ Aging ] |
| Description: Midwest Overdue > $25,000 Aging Definition: [ STANDARD_30_60_90 ] |
+---------------------------------------------------------------------------------------------+
| DYNAMIC QUERY CRITERIA (SysQuery AOT Filter): |
| Table | Field | Criteria / Value Expression |
| ----------------- | ------------------------- | ------------------------------------------- |
| Customers | Customer group | `20` (Commercial Domestic) |
| Customers | State / Province | `IL, IN, WI, MI, OH` |
| CustAgingSnapshot | Balance04 (60+ Days Over) | `> 25000` |
| Customers | Blocked | `No` |
+---------------------------------------------------------------------------------------------+
Pool Types & Operational Applications
- Aging Pools: Used in the Collections workspace to filter the customer grid so collection agents only see customers matching their specific assigned portfolio.
- Collection Letter Pools: Restricts periodic batch generation of collection letters to a subset of customers (e.g., excluding VIP accounts or government contracts).
- Interest Pools: Restricts automated periodic interest calculation runs to specific customer groups or regions.
Linking Pools to Collections Agents
To establish personal work queues:
- Define Collections Agents at
Credit and collections > Setup > Collections agents(maps a D365 User ID to an employee worker record). - Assign a default Customer Pool to the Collections Agent record.
- When the collector opens the Collections Workspace, the system automatically applies their default customer pool, displaying only their delinquent accounts.
5. Collection Activities & Case Management
Dynamics 365 Finance provides structured CRM-style tracking for collection interactions directly inside the finance subledger:
+---------------------------------------------------------------------------------------------+
| Collection Activity Lifecycle |
+---------------------------------------------------------------------------------------------+
| |
| [ Customer Contact / Call ] |
| | |
| v |
| +--------------------------------------------------------------------+ |
| | CREATE COLLECTION ACTIVITY | |
| | - Type: [ Action Item / Task / Appointment ] | |
| | - Status: [ Open / In Progress / Completed ] | |
| | - Priority: [ High / Normal ] | |
| | - Assigned To: [ Collector User ID ] | |
| | - Due Date: [ Follow-up Deadline ] | |
| +--------------------------------------------------------------------+ |
| | |
| +-----------------------------------+ |
| | | |
| v v |
| [ Promise to Pay Recorded ] [ Customer Disputes Invoice ] |
| - Promised Amount: $25,000.00 - Dispute Reason: `PRICE_MISMATCH` |
| - Promised Pay Date: 09/15/2026 - Disputed Amount: $8,500.00 |
| - Links to Specific Open Invoices - Status Set to 'In Dispute' |
+---------------------------------------------------------------------------------------------+
Activity Types
- Action: High-level interaction log (e.g., recorded telephone call, email correspondence, or mailed formal demand).
- Task: Actionable to-do item with a target completion date (e.g., "Verify proof of delivery with shipping department by Friday").
- Appointment: Scheduled calendar meeting with customer finance personnel or legal counsel.
6. Dispute Management & Dispute Reason Codes
When a customer refuses to pay an invoice due to billing errors, damaged freight, or missing paperwork, collection agents record a formal Dispute.
Navigation
- Dispute Reason Codes Setup:
Credit and collections > Setup > Dispute reasons - Logging a Dispute:
Credit and collections > Collections > (Select Customer) > Transactions > Dispute tab
+---------------------------------------------------------------------------------------------+
| Invoice Dispute Transaction Record |
+---------------------------------------------------------------------------------------------+
| Invoice: [ CIV-008921 ] Invoice Date: 07/15/2026 Invoice Total: $45,000.00 |
+---------------------------------------------------------------------------------------------+
| DISPUTE DETAILS: |
| - Dispute Status: .................... [ In Dispute ] |
| - Dispute Reason Code: ............... [ `DMG_FREIGHT` ] (Damaged Goods During Transit) |
| - Dispute Date: ...................... [ 08/20/2026 ] |
| - Disputed Amount: ................... [ $12,500.00 ] (Partial Line 2 Damaged) |
| - Undisputed Balance: ................ [ $32,500.00 ] |
| - Follow-up Date: .................... [ 09/05/2026 ] |
+---------------------------------------------------------------------------------------------+
Operational and Accounting Impact of In-Dispute Status
- Isolation on Aging Reports: The disputed portion ($12,500) is segregated on analytical aging reports, allowing credit managers to distinguish between legitimate uncollected debt and contested billing errors.
- Suppression of Collection Letters: During periodic collection letter generation, selecting the Exclude transactions in dispute toggle prevents aggressive dunning letters from being sent to customers while claims are actively being investigated.
- Exclusion from Interest Notes: Interest calculation routines can be configured to waive late interest accruals on open balances marked as disputed.
- Dispute Resolution Paths:
- Dispute Resolved (Customer Pays): Dispute status changed to Resolved; standard collections resume.
- Dispute Legitimate (Credit Issued): AR clerk issues a Credit Memo or Free Text Credit Note against the invoice, settling the disputed balance.
7. Exam Traps & Real-World Best Practices
[!WARNING] Exam Trap: Stale Aging Snapshots A common MB-310 question describes a collector logging into the Collections workspace and observing that customer payments posted earlier in the morning are not reflected in the aging grid. The exam expects you to identify that the Customer Aging Snapshot has not been refreshed. The Collections workspace reads from the snapshot cache table (
CustAgingSnapshot), not liveCustTrans. The collector must either click Update aging for the individual customer or run the Age customer balances periodic batch job.
[!IMPORTANT] Consultant Pro-Tip: Multi-Company Collections Setup To allow a shared services collections team to view customer balances across all corporate legal entities simultaneously in the Collections workspace, ensure that:
- The Age customer balances periodic job is executed with Company selection = All.
- The Collections Agent is assigned appropriate security privileges and organizational hierarchy access across all subsidiary entities.
Loading diagram...
Test Your Knowledge
A financial analyst is configuring Aging Period Definitions in Dynamics 365 Finance. The treasury department requires an aging report to forecast upcoming cash receipts over the next 30, 60, and 90 days into the future. The credit department requires an aging report to evaluate past-due accounts that are 30, 60, and 90 days overdue. What Interval configuration should be selected for each aging definition?
A
B
C
D
Test Your Knowledge
A collections agent logs into the Collections workspace at 9:00 AM and notices that a customer who paid a $50,000 overdue invoice at 8:00 AM still appears in the 60-day overdue bucket with the full unpaid balance. The agent verifies that the cash receipt journal was successfully posted at 8:00 AM. What is the reason for this behavior?
A
B
C
D
Test Your Knowledge
A customer receives an invoice for $20,000 that includes 10 units of an item. The customer reports that 2 units arrived damaged (valued at $4,000) and refuses to pay for the damaged portion while agreeing to pay the remaining $16,000. The collections team must ensure that automated collection letters are not generated for the $4,000 damaged portion while the claim is investigated. What should the collections specialist do?
A
B
C
D