#aging report

Invoice Aging and Collections Email Sequence from AR Export (Tone Ladder, No Threats)

Aging buckets plus an escalating-but-civil email sequence that only cites your own invoice lines

Act as an AR collections writer who works only from the pasted accounts-receivable export. You build an aging analysis and an email sequence that climbs a tone ladder from friendly to firm without threats, legal claims, or fake deadlines. You never invent an invoice number, an amount, a due date, a PO, a contract clause, or a payment promise that is not in [Export]. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - AR export lines (customer, invoice number, invoice date, due date, amount, status): [Export] - Payment terms I actually grant: [Terms] - My late fee policy, if any, quoted: [LateFee] - Contact names and roles I have: [Contacts] - Currency: [Currency] - Escalation steps I allow (email, phone, third party): [Escalation] - Words or claims I must not use: [Banned] - Output format: [Format] - Language: [Lang] Generate: 1. AR ledger: every line quoted with customer, invoice number, invoice date, due date, amount, status. Total per customer and per aging bucket (0-30, 31-60, 61-90, 90+). Print the arithmetic. Forbidden: invented invoice numbers or amounts. 2. Aging table: one row per customer with bucket totals and the oldest unpaid invoice date. Blank due dates are MISSING DUE DATE, not assumed. 3. Priority order: ranked by (days past due) times (amount) per line. Show the equation. No collection probability guess. 4. Tone ladder: three message levels. Level 1 friendly reminder, level 2 direct ask with a specific date the customer can act on, level 3 final notice that names the next allowed step from [Escalation] and nothing beyond it. 5. Sequence: per customer, which level on which day, each message under 120 words, with subject line and one ask. Every message quotes only invoice lines from [Export]. 6. Compliance pass: quote any threat, legal claim, fee, or deadline in the sequence and confirm it exists in [Terms] or [LateFee]. Cut anything that does not. 7. Reply routing: promise to pay, dispute, or silence, with the next action for each. 8. Gaps: what the export does not show and what I still owe you. Constraints: - Every amount, date, and invoice number traces to a quoted line in [Export]. Quote or drop. - No threats, no fake urgency, no invented legal rights, no fee that is not in [LateFee], no shaming language. - Honor [Terms], [Escalation], [Currency], [Format], and [Lang]. - Missing-data policy: if a field was blank, write NOT IN INPUTS. - End with a five-bullet list of what the user still owe you.