Accounts Receivable Workflows: Invoicing to Cash Application

Start here

Overview

AR is part customer experience, part finance discipline. Workflows must balance polite persistence with accurate cash application.

Core concept

Definition

AR automation coordinates invoice generation, delivery, reminder sequences, promise-to-pay capture, and cash application with exception queues for unmatched payments.

Business impact

Why it matters

DSO and write-offs hinge on timely follow-up and clean matching—not only invoicing speed.

Practical model

Framework

Segment customers

Different strategies for SMB vs enterprise; different channels and tone.

Exception-first design

Partial payments, disputes, and currency differences need human paths.

Implementation detail

Detailed breakdown

Integration to GL

Ensure automation does not post out of balance—validate totals and taxes.

In practice

Real-world example

A distributor automated reminders and task creation for overdue tiers—recovering cash without adding headcount.

Avoid these

Common mistakes

Automated dunning without dispute flags—damages relationships.
Weak mapping between portal payments and open invoices.

Engineering layer

Technical patterns

Payment matching

Primary key: `invoice_id` in remittance; fallback fuzzy amount + date window.
Unapplied cash bucket until matched.

Build patterns

Code examples

Apply payment lines

Allocates FIFO to open invoices.

TypeScript

export function allocatePayment(payment, openInvoices) {
  let left = payment.amount;
  const alloc = [];
  for (const inv of openInvoices.sort((a,b)=>a.due-b.due)) {
    if (left <= 0) break;
    const n = Math.min(left, inv.balance);
    alloc.push({ invoiceId: inv.id, amount: n });
    left -= n;
  }
  return alloc;
}

System view

System architecture

YAML

[Bank / PSP webhooks]
        → [Normalization]
        → [Matcher: ref + amount rules]
        → [GL posting]
        → [Dunning if open balance]

Keep learning