AGENT SKILL

ar-aging-and-cash-application

Build an accounts receivable aging report and apply incoming cash to invoices. Covers aging buckets, due dates from payment terms, allocation order, early-payment (settlement) discounts, partial payments, credit memos, unapplied cash, disputes and collection stages. Use for AR aging, collections prioritisation, or cash application tasks.

License 许可
Apache-2.0
所属仓库
getedgehq/skills
最近更新
2026-11-12
Stars
★ 5
Forks
0

01 前言 Front Matter

name
ar-aging-and-cash-application
description
Build an accounts receivable aging report and apply incoming cash to invoices. Covers aging buckets, due dates from payment terms, allocation order, early-payment (settlement) discounts, partial payments, credit memos, unapplied cash, disputes and collection stages. Use for AR aging, collections prioritisation, or cash application tasks.

02 资源文件 3

03 SKILL.md 正文

AR aging and cash application

Goal: as of a reporting date, determine what each customer still owes, how overdue it is, and what to do about it. Correctness depends on the order of operations and on rules that are usually implied, so enumerate them first.

1. Read all sources before computing

Read every policy document, terms file and notes in full. Tables of history (terms that changed over time, disputes, write-offs) are rules too, not decoration. Hints in a collections policy about discounts or exclusions are binding. If a rule has an obvious generic meaning (below), apply it even if only mentioned once.

2. Due dates and terms

  • Due date = invoice date + terms days (Net N), or end of month + N for EOM terms. Use the terms that were in force on the invoice date, not the current terms, when a terms history exists.
  • "Days past due" = reporting date - due date. Not yet due (<= 0) goes in the current bucket. Be explicit whether the due date itself counts as past due (normally not).
  • Standard buckets: current, 1-30, 31-60, 61-90, 90+ days past due. Use the spec's bucket edges; boundaries are inclusive on the upper side of each bucket.
  • Only invoices dated on or before the reporting date count; payments after it are ignored (as-of semantics).

3. Payments, credits and allocation

  • A payment that references an invoice is applied to that invoice first. A reference may be messy (case, spacing, prefix); normalise before matching and never apply to a non-existent invoice.
  • Unreferenced cash is applied in a fixed order. Default: oldest due date first (FIFO by due date), ties by invoice date then id. Use the spec's order if stated. Allocate across invoices until the cash is exhausted; the last one may be partially paid.
  • Partial payments reduce the open balance; the remainder keeps the ORIGINAL due date and ages from it.
  • Cash left after all open invoices are settled is unapplied cash. It is a credit to the customer, not a negative bucket; report it separately.
  • Credit memos reduce the amount owed. A memo tied to an invoice reduces that invoice; an unattached memo is a customer credit that offsets the total balance. Keep customer credits (unapplied cash plus unapplied memos) distinct from past-due buckets, and make net exposure = open invoices - credits only if the spec defines it so.
  • Chargebacks, refunds and reversals reopen or create balance; reversals of a payment must be undone before allocation.

4. Discounts and settlement terms

  • Terms of the form "x/y Net z" mean: x% discount if paid within y days of the invoice date, otherwise the full amount is due in z days. Count days from the invoice date, inclusive of the last discount day.
  • A payment inside the discount window that equals the discounted amount (net of the discount, within rounding) settles the invoice in full; the withheld discount is not an open balance. Apply the discount test before treating the shortfall as a partial payment.
  • Payments just short of the full amount because of rounding or bank fees leave small residuals; treat residuals under the spec's materiality limit as zero.
  • Late payments forfeit the discount.

5. Disputes and collections stages

  • Disputed invoices stay in the aging buckets (they are still owed) but are normally excluded from collections-reminder/escalation actions. Apply the exclusion only to the action, not to the balance, unless told otherwise.
  • Collections stage is driven by days past due of the oldest unpaid undisputed item, per spec thresholds. Compute the stage from what remains AFTER cash application.

6. Money and rounding

  • Work in integer cents (or Decimal). Round discounts and percentages once, half up, at the point the spec defines. Never accumulate floats.
  • Totals must tie: sum of buckets = total open; open + credits relationships stated in the spec must hold exactly.

7. Order of operations (most common bug source)

  1. Parse and normalise invoices, payments, memos, terms (with history).
  2. Drop anything after the reporting date.
  3. Apply referenced payments (with discount test), then credit memos.
  4. Apply unreferenced cash in the allocation order.
  5. Zero out immaterial residuals.
  6. Age what remains, bucket it, compute credits and stage.
  7. Format output exactly as specified (key names, ordering, units).

8. Self-checks

  • Pick customers with a partial payment, a discount payment, a dispute, unapplied cash and changed terms and recompute by hand.
  • No invoice has a negative open amount; no payment is applied twice; total cash in = applied + unapplied.
  • Count of customers and sort order match the spec.

04 同仓库更多 Skills

getedgehq
getedgehq/skills

zero-downtime-cloud-move

Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.

★ 5
getedgehq
getedgehq/skills

zayats-ceo-branding

Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.

★ 5
getedgehq
getedgehq/skills

yc-app-roast

YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.

★ 5
getedgehq
getedgehq/skills

yc-app-review

YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.

★ 5
getedgehq
getedgehq/skills

x-growth-playbook

X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.

★ 5
getedgehq
getedgehq/skills

workplan

Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.

★ 5