Knowledge · Business Operations

    The Receivable Lifecycle: Issued Invoice to Settlement

    What happens between issuing an invoice and money actually clearing — recognition, aging, promises, payment application, receipt and closure — and where each stage breaks.

    What is the receivable lifecycle?

    The receivable lifecycle runs from the moment an issued invoice creates a balance, through aging, contact and promises, to a payment being received, applied to that balance, receipted, and the balance closing at zero. Settlement is when cash clears, which is later than payment being recorded.

    Key takeaways

    • The lifecycle starts at issue, not at delivery of the work.
    • Recording a payment and cash clearing are two separate events.
    • Application is the step most teams skip: money must land on a specific balance.
    • A receipt proves a payment; it does not prove the balance is zero.
    • Closure should leave the invoice, payments and receipts linked, never deleted.

    The stages, in the order they actually happen

    • Recognition — an issued invoice with terms creates a balance and a due date.
    • Aging — time passes; the balance moves through buckets relative to its due date.
    • Contact — someone reaches the customer and records what was said.
    • Promise — the customer commits to an amount and a date.
    • Payment received — money arrives through some channel.
    • Application — that payment is attached to specific invoices.
    • Receipt — proof of the payment is issued to the customer.
    • Closure — the balance reaches zero, or is credited or written off deliberately.

    Why payment received and settlement are not the same day

    A cheque recorded on Tuesday may clear the following week. A card payment may be captured instantly but settle to your account later. An ACH transfer can be initiated and then returned. If your AR report treats "recorded" as "in the bank", you will make spending decisions against money that has not arrived.

    The practical fix is to keep the two facts separate in your own records and confirm settlement against your bank rather than against your CRM. Reconciling to the bank is an accounting activity and belongs with whoever owns your books.

    Where the lifecycle breaks in service businesses

    • The invoice is issued without terms, so aging has nothing to measure against.
    • A payment arrives by cheque or transfer and nobody records it, so the customer gets chased.
    • A payment is recorded but not applied, so two reports disagree.
    • A promise is made on a phone call and lives only in one person's memory.
    • A dispute pauses the chase informally, and the balance quietly ages past 90 days.

    Where URBLD fits

    URBLD records payments and receipts as separate records linked to the invoice, and derives the outstanding balance from what has been applied. It does not connect to your bank, so settlement confirmation stays with your bank statement and your accountant.

    Principles reinforced

    This page rests on the following foundational ideas.

    FAQ

    Frequently Asked Questions

    Straight answers about how URBLD runs the business end-to-end.

    More in Business Operations

    The daily mechanics: workflows, checklists, scheduling and handoffs.

    Browse Business Operations
    Share this page