Start free
September 30, 202615 min read

Collect Faster: 90 Day ERP Ready AR Collections for Finance Teams

Finance lead conducting a construction payment follow-up

An effective AR collections process turns unpaid invoices into predictable cash by combining credit checks, structured invoicing, consistent follow-up, and disciplined reconciliation. Done well, it lowers days sales outstanding, resolves disputes faster, and keeps cash flow forecasts reliable. The stages run in sequence: credit screening, invoicing, monitoring, collecting, cash application, and reconciliation.

TL;DR:

  • Proper credit screening based on customer risk profiles reduces the likelihood of disputes and delays in collections.
  • Sending invoices within 24 hours of milestone completion minimizes overdue balances and improves cash flow predictability.
  • A structured dunning sequence with escalating tone and concise messaging increases the chances of timely payment without damaging relationships.
  • Automating collection workflows and tracking compliance helps maintain consistent follow-up and reduces administrative errors.
  • Segmentation of accounts by age, amount, dispute status, and relationship value optimizes collector effort and prioritizes high-impact cases.
Designflow-build
Bring Construction Finance Together
DesignFlow Build combines project management, accounting, and field operations to reduce manual work and improve visibility for construction teams.
Explore DesignFlow Build

Table of Contents

The step-by-step AR collections process from credit to reconciliation

The canonical AR process moves through six connected stages, and skipping or rushing any one of them tends to create the disputes and delays that inflate DSO later.

Credit assessment comes first. Before you extend terms, you check a customer’s payment history, credit references, and financial stability, then set a credit limit and terms (net 30, net 45, or milestone billing for larger contracts) that match the risk. Weak credit screening is the quiet cause behind a lot of collections pain months later.

Invoice creation and delivery come next. Invoices should go out the same day work is completed or milestones are met, with clear line items, purchase order references, and payment instructions. A vague or delayed invoice is one of the most common reasons a payment slips.

Once invoices are live, you record them and start aging. Every invoice lands in your ledger and moves through aging buckets (current, 1 to 30 days past due, 31 to 60, 61 to 90, and 90-plus) so you always know where risk is concentrated.

Then come the routine collection actions: reminders, calls, and documented promises to pay. Every contact, whether an email or a phone call, gets logged with a date, outcome, and next step, because that record becomes your evidence trail if an account escalates.

Cash application and dispute resolution follow. Payments get matched to open invoices, and any discrepancy, like a short pay or disputed line item, gets flagged and routed for resolution before it ages further.

Finally, reconciliation and controls close the loop: AR subledgers tie back to the general ledger, and someone reviews exceptions weekly.

A few practices make the whole chain hold together:

Construction teams juggling progress billing often find that G702/G703 checklists tighten this process further by standardizing what an invoice needs before it goes out.

Collections cadence and dunning sequence templates that actually work

A dunning sequence is the calendar of reminders and escalations that runs automatically once an invoice ages past due, and getting the timing right prevents both under-collection and customer annoyance.

A practical cadence for a net-30 invoice looks like this:

  1. Day 1 past due: a friendly automated reminder email, subject line focused on account status, not payment demand.
  2. Day 7 past due: a second email with a firmer tone and a direct link to the outstanding invoice.
  3. Day 14 past due: a phone call from the collector, followed by an email summary of what was discussed.
  4. Day 21 past due: a formal notice referencing account terms and next steps if payment is not received.
  5. Day 30 to 45 past due: a demand letter, often built around a 10-day payment window, which is a common practice for B2B collections rather than a legal requirement.

Email tone should shift with each step: informational at day 1, direct at day 7, and unambiguous by day 21. Escalate to a phone call once an account crosses 14 days past due, and escalate to a payment plan discussion or demand letter once it crosses 30. A demand letter typically states the amount owed, the original due date, the new deadline, and the consequence of nonpayment, whether that is a referral to collections or legal action.

Pro Tip: Keep every dunning email under 150 words. Long emails get skimmed, and the core ask (pay by this date) gets lost.

Accounts flagged as disputed or with an active promise to pay should pause in the sequence rather than continue receiving escalating notices, since recontacting an account mid-dispute damages the relationship without speeding up payment.

Collections cadence and dunning sequence templates that actually work — overview diagram

Automation and collections process setup for your ERP

Most ERP systems separate two things that collectors often conflate: the collections process (the hierarchy and rules governing when actions fire) and the collection letter sequence (the actual templates and grace days), and setting up automation correctly means configuring both. According to Microsoft Dynamics documentation, the system runs as of the current date and decides which letter or action to trigger based on the oldest overdue invoice and the configured days in relation to the due date.

A typical setup includes:

The same documentation shows that automation should skip invoices already marked Disputed or Promised to Pay, which keeps collectors focused on accounts that actually need action rather than ones already in progress.

Action type Typical trigger (days from due date) Purpose
Pre-dunning email Before due date Soft reminder, no escalation tone
First collection letter 1 day after due Formal notice, low urgency
Second collection letter 7 days after due Firmer tone, direct payment link
Final collection letter 14 days after due Last automated notice before manual escalation
Create activity 14 to 21 days after due Assigns a task to a human collector

Before turning any sequence live, run it in test mode against a sample of accounts, check that track-step toggles behave as expected (some systems log every step taken per invoice, which matters for audit trails), and confirm the system respects daily run restrictions so customers do not get duplicate notices on the same day. Teams that have used commercial contractor workflow automation to configure similar sequences often catch these errors in the test phase rather than in production.

Prioritization and segmentation for collector workloads

Not every past-due account deserves the same attention, and a simple scorecard helps collectors decide where to spend their time first. The strongest segmentation frameworks weigh invoice age, dollar amount, dispute or promise-to-pay status, and the strategic value of the customer relationship.

A basic collectibility index might weight these factors as follows:

Once scored, the daily workflow splits by segment: high-value, low-risk accounts get a courtesy call before day 14; high-balance, aging accounts get escalated to a senior collector; and disputed accounts get pulled entirely from automated cadence until resolved. Segmentation and collectibility scoring protects customer relationships while still prioritizing cash recovery, which matters most when a handful of large accounts represent most of your outstanding balance.

Escalation triggers should be explicit: a missed promise to pay moves an account up a tier automatically, and three consecutive missed contacts moves it to a senior collector or the demand letter stage.

The Fair Debt Collection Practices Act does not apply to commercial invoices, and that distinction is one collectors get wrong more often than any other. FDCPA and Regulation F govern consumer debt specifically, requiring validation notices and limiting how often and when a collector can contact a consumer. B2B collections operate under a different framework entirely, one built on contract law and the Uniform Commercial Code rather than consumer protection statutes.

That does not mean commercial collectors operate without limits:

Good recordkeeping supports every escalation path that follows. Keep dated logs of every call, email, and letter, retain signed contracts and purchase orders, and document every promise to pay with a specific date and amount. When most late payments trace back to missing documentation rather than an unwillingness to pay, tight paperwork at the front end prevents a dispute at the back end.

Escalation paths: from demand letter to court

When routine cadence fails, you have a decision tree, not a single next step, and choosing the wrong branch wastes time and money.

  1. Send a formal demand letter first, stating the amount owed, the original terms, and a firm deadline, commonly the 10-day window used across B2B collections.
  2. If the demand letter gets no response, consider a commercial collection agency, which typically works on contingency and takes a cut of whatever it recovers, a tradeoff worth it for accounts too small to justify legal fees.
  3. For balances within your jurisdiction’s small claims cap, file there directly. It is faster and cheaper than civil litigation, though it caps the amount you can recover.
  4. For larger balances or complex disputes, civil litigation is the remaining option, though it comes with legal fees, longer timelines, and no guarantee of a collectible judgment even after winning.
  5. Contractors have an additional remedy unavailable to most industries: a mechanic’s lien against the property, or UCC remedies against equipment or inventory pledged as collateral, both of which can pressure payment without a courtroom.

Each step up this ladder costs more and takes longer, so the goal of a strong cadence and clear documentation earlier in the process is to resolve as many accounts as possible before they ever reach a demand letter.

Metrics and reporting: the dashboards your finance leader actually needs

Days sales outstanding is the metric every finance leader tracks, and the countback method, which calculates DSO by counting backward through recent sales until it matches your current AR balance, gives a more accurate read than the simple average-based formula. Reducing DSO directly frees up working capital that would otherwise sit trapped in unpaid invoices, a connection treasury and cash-management guidance consistently points to when discussing collections discipline.

Beyond DSO, a useful dashboard tracks:

Automation feeds these dashboards directly: every action a collector or system takes gets logged, which means the aging report and the PTP rate update in near real time rather than at month-end. That live feed is also what triggers the next collector task, so a missed promise to pay can automatically bump an account into a higher-priority queue instead of waiting for someone to notice.

Implementation checklist and a 90-day rollout plan

Rolling out a stronger AR collections process works best in phases, not all at once.

  1. Weeks 1 to 2: review credit policy, late fee terms, and any attorney-fee clauses in your standard contracts, since these need to be airtight before automation starts sending letters that reference them.
  2. Weeks 3 to 4: configure your collection letter sequence and process hierarchy, run test cycles against sample accounts, and confirm track-step settings log correctly.
  3. Weeks 5 to 6: assign collector roles, define escalation rules by segment, and train the team on documentation standards.
  4. Day 30: baseline your DSO, aging distribution, and PTP rate before full automation goes live.
  5. Day 60 and day 90: review the same metrics again, adjusting cadence timing or segment weighting based on what the data shows.

Pro Tip: Run your new automated sequence in parallel with manual collections for the first two weeks, so you catch configuration errors before they reach a real customer.

Teams handling construction billing often pair this rollout with a revenue recognition review, since inconsistent WIP accounting tends to surface the same documentation gaps that cause collection disputes.

How DesignFlow Build automates and measures AR collections for contractors

DesignFlow Build combines billing, collections automation, cash application, and executive dashboards into one AI-native construction ERP, which means the cadence and segmentation described above run inside the same system that generates your invoices and job costing.

For teams building out an AR collections process, the modules worth configuring first are billing and invoicing, automated reminder sequences, and the cash application workflow, since those three cover the bulk of day-to-day collector time. Automation reduces manual AR tasks across the board, and construction-specific billing formats like progress draws are already built into the system rather than bolted on.

One strategic priority for finance leaders to get right

Automation only works when the policy behind it is consistent. If credit terms, late fees, and escalation rules change account by account depending on who is asking, no dunning sequence will hold up, and collectors will spend more time managing exceptions than collecting cash. Get the policy locked first, train the team on it, and pick one or two accounts as an early automation pilot before rolling out company-wide. Small, visible wins build the trust that gets the rest of the team to actually use the system instead of working around it.

— Keith

Evaluate your AR collections stack before you commit

If you are comparing tools to run this process, look for three things: how well the system talks to your accounting and job costing data, how configurable the automation rules are without a developer, and how long implementation actually takes. Generic ERPs and spreadsheet-plus-QuickBooks setups can handle basic dunning, but they rarely connect collections directly to construction-specific billing formats or field data.

Designflow-build

DesignFlow Build was built specifically for contractors, so collections automation sits next to job costing, certified payroll, and progress billing rather than in a separate tool you have to reconcile by hand. Implementation runs 2 to 4 weeks, and the Pro plan is $100 per office user per month, with Field seats at $25 per user per month, detailed on the pricing page. Review the Construction ERP product page to see how billing and collections fit into the broader platform, and request a demo to see your own invoice data run through it.

Sources

The legal distinctions covered here draw on FDCPA and Regulation F interagency guidance and a practical B2B collections playbook that walks through demand letters and escalation paths. The step-by-step process itself follows treasury and cash-management guidance on invoicing, monitoring, and reconciliation, and the automation configuration details come from Microsoft Dynamics collections documentation. For invoice automation examples in adjacent workflows, see Ksign.

FAQ

Are there risks to AR collections?

Yes. Aggressive or inconsistent collection tactics can damage customer relationships and, in consumer contexts, create legal exposure under Regulation F and the FDCPA. In B2B collections, the main risk is procedural: escalating an account that is actually disputed or has an active promise to pay wastes effort and frustrates a customer who may have simply needed more time.

What happens when accounts receivable are collected?

Once a customer pays, the payment gets matched to the specific open invoice through cash application, and the balance moves off the aging report. The transaction then flows into reconciliation, where the AR subledger is checked against the general ledger to confirm the books match.

Are AR and collections the same thing?

No. Accounts receivable is the broader function covering credit terms, invoicing, and the full lifecycle of what customers owe you, while collections is the specific set of actions (reminders, calls, letters) used to recover overdue balances within that broader process.

What is the 10-day rule for accounts receivable?

The 10-day window refers to a common practice in B2B demand letters, where a business gives a customer 10 days to pay after formal demand before escalating further. It is a widely used practice rather than a legal requirement, and it differs from the 30-day validation period required for consumer debt under Regulation F.