Skip to main content

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.

Nexus CertifiedClaude CodeCodexOpenClawGoogle Antigravity
latepaymentfollowupinvoicing

One-Time Purchase

$19.99

Sample Output

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. In this example, Apex Plumbing & HVAC is reconciling source-of-truth operating metrics before a finance owner approves the recommendation. The output is a concrete operator-ready artifact: source evidence, reviewer checks, and the owner decision that determines whether the work is ready.

Evidence Packet

InputExampleStatus
invoice, payment, dispute, or aging dataApex Plumbing & HVAC is reconciling source-of-truth operating metrics before a finance owner approves the recommendation.Provided
customer history and commercial termsThree representative examples from the current workflowReviewed
collection tone and escalation limitsApproval threshold and final reviewerConfirm
finance owner and desired payment actionInvoicing & Receivables owner and downstream audienceReady

Late Evidence Model

FieldWhat must be capturedReview consequence
Late signalTrack invoice date, due date, aging bucket, payment history, dispute reason, and escalation limit.Treat as draft until late receivable-aging classification is source-backed.
Late Receivable Aging ClassificationKeep collection tone separate from finance-policy decisions.Escalate when invoice, due date, payment history, or dispute basis is missing.
Payment Payment Risk And Dispute FramingName the next finance owner action and the evidence needed before escalation.Reviewer resolves follow collections-safe communication step before final use.

Late Acceptance Checks

CheckRequired evidenceReview action
Late depthTrack invoice date, due date, aging bucket, payment history, dispute reason, and escalation limit.Keep, revise, or ask a targeted follow-up
Payment boundaryKeep collection tone separate from finance-policy decisions.Confirm this is not a renamed adjacent bundle skill
Follow handoffName 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

Extract the details that determine whether the operator-ready artifact is useful.late receivable-aging classification
Separate draftable material from items that need reviewer judgment.payment payment-risk and dispute framing
Package the result so the next owner sees the exact edit or approval needed.follow collections-safe communication step

Draft Operator Ready Artifact

Late signalLate Receivable Aging ClassificationPayment Payment Risk And Dispute FramingFollow Collections Safe Communication StepPayment decision
MetricLate variance uses actual, baseline, and periodpayment payment-risk and dispute framingfollow collections-safe communication stepFinance check
Driverlate receivable-aging classificationPayment assumption is tagged as sourced or missingInvoice, due date, payment history, or dispute basis is missing.Revise
DecisionTrack 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 reviewerReady

Use now

Late Payment Follow Up

Best when invoicing & receivables work needs a concrete operator-ready artifact.

Keeps the artifact tied to supplied materialLate
Names the next edit, approval, or owner decisionPayment

Hold back

Missing evidence

Best deferred when a key input would change the artifact.

Invoice, due date, payment history, or dispute basis is missing.Late
Escalation policy or customer-owner path is unknown.Payment
The draft would overstate collections authority.Follow

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

Finance and AR leads sequencing collections outreach on overdue invoices — escalating tone appropriately as an account ages without burning the relationship. Most useful when several invoices are late and each needs a different touch.

Not ideal for

A single gentle nudge a one-line email handles, or seriously delinquent accounts that need a collections agency or counsel. The sequence is a draft; a finance owner should confirm balances and terms before any escalating message goes out.

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.

Claude CodeCodexOpenClawGoogle Antigravity

Related Skills

FinOps & Compliance
Expense Report
Categorizes expenses for a date range and highlights unusual spend. Useful for quick finance reviews and recurring reporting.
Claude CodeCodexOpenClawGoogle Antigravity
expensesfinancereporting

$19.99

One-time license

View Skill
FinOps & Compliance
Featured
Cost Optimizer
Finds cloud and AI spend optimization opportunities and ranks them by projected savings. Designed for recurring FinOps-style reviews.
Claude CodeCodexOpenClawGoogle Antigravity
finopscost-optimizationcloud

$19.99

One-time license

View Skill
FinOps & Compliance
Compliance Check
Reviews a technology decision for regulatory and policy implications, then outlines obligations, controls, and open questions. Useful for early compliance screening.
Claude CodeCodexOpenClawGoogle Antigravity
complianceregulatory-reviewcontrols

$19.99

One-time license

View Skill

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.

Upgrade to Pro