Finance & Compliance
Late Payment Follow Up
Late Payment Follow Up turns invoicing & receivables material into an operator-ready artifact with a concrete late receivable-aging classification, payment payment-risk and dispute framing, and follow collections-safe communication step. It is built for teams that need a usable draft artifact, not a broad summary with a familiar title. The skill asks for invoice, payment, dispute, or aging data, customer history and commercial terms, and collection tone and escalation limits up front, then organizes the output around late, payment, follow, invoicing, and receivables. It is delivered with adapters for Claude Code, Codex, OpenClaw, and Antigravity so teams can use the same workflow across their preferred agent environment. Late Payment Follow Up is scoped to the Invoicing & Receivables workflow and is distinct from adjacent catalog skills by producing this specific deliverable rather than a broad summary.
One-Time Purchase
$19.99
Late Payment Follow Up — Sample Brief
Headline
Builds a receivables action artifact for late payment follow up work, turning invoice, payment, dispute, or aging data, customer history and commercial terms, and collection tone and escalation limits into late receivable-aging classification, payment payment-risk and dispute framing, and follow collections-safe communication step. For Apex Plumbing & HVAC, the example focuses on a concrete operator-ready artifact: the evidence to use, the fields a reviewer can inspect, and the owner decision needed before the work leaves draft state.
Evidence Packet
| Input | Example | Status |
|---|---|---|
| invoice, payment, dispute, or aging data | Apex Plumbing & HVAC notes and excerpts | Provided |
| customer history and commercial terms | Three representative examples from the current workflow | Reviewed |
| collection tone and escalation limits | Approval threshold and final reviewer | Confirm |
| finance owner and desired payment action | Invoicing & Receivables owner and downstream audience | Ready |
Review Focus
| Lens | What this skill must inspect | Why it matters |
|---|---|---|
| Late | Evidence specific to late payment follow up late / payment / follow | Keeps the artifact tied to the actual source packet |
| Payment | The boundary between Late Payment Follow Up and adjacent Invoicing & Receivables skills | Keeps this skill from absorbing neighboring workflows |
| Follow | The final reviewer decision, rejection reason, or edit path | Gives the next owner a clear approval or edit path |
Acceptance Checks
| Check | Required evidence | Review action |
|---|---|---|
| Late depth | Track invoice date, due date, aging bucket, payment history, dispute reason, and escalation limit. | Keep, revise, or ask a targeted follow-up |
| Payment boundary | Keep collection tone separate from finance-policy decisions. | Confirm this is not a renamed adjacent bundle skill |
| Follow handoff | Name the next finance owner action and the evidence needed before escalation. | Assign the owner decision before final use |
Late Payment Follow Up Work Map
Late Payment Follow Up focus areas
Draft Operator Ready Artifact
| Late signal | Late Receivable Aging Classification | Payment Payment Risk And Dispute Framing | Follow Collections Safe Communication Step | Payment decision |
|---|---|---|---|---|
| Metric | Late variance uses actual, baseline, and period | payment payment-risk and dispute framing | follow collections-safe communication step | Finance check |
| Driver | late receivable-aging classification | Payment assumption is tagged as sourced or missing | Invoice, due date, payment history, or dispute basis is missing. | Revise |
| Decision | Track invoice date, due date, aging bucket, payment history, dispute reason, and escalation limit. | Keep collection tone separate from finance-policy decisions. | Follow implication is framed for the reviewer | Ready |
Use now
Late Payment Follow Up
Best when invoicing & receivables work needs a concrete operator-ready artifact.
Hold back
Missing evidence
Best deferred when a key input would change the artifact.
Reviewer note
This financial workflow needs qualified review before anyone treats the output as a decision record. The final answer should label unknowns plainly and avoid inventing metrics, policies, quotes, or commitments.
This sample illustrates the skill's output format. The example is fictional and assists with financial workflows but is not a substitute for professional financial review. Decisions of consequence should be reviewed by appropriate counsel or a qualified professional reviewer.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Invoicing & Receivables
Bundle price: $55. Compare this skill with the full workflow bundle or Pro access.
Best for
Late Payment Follow Up is best for buyers who need repeatable late, payment, follow work packaged as a structured, review-ready deliverable.
Not ideal for
Late Payment Follow Up is not a fully autonomous service, managed integration, or substitute for required human review in high-stakes workflows.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short copy-and-configure setup in your preferred agent workspace. No custom integration is required for the skill file itself.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.