Finance & Compliance
Payment Reminder Sequencer
Payment Reminder Sequencer turns invoicing & receivables material into a sequenced communication plan with a concrete payment receivable-aging classification, reminder payment-risk and dispute framing, and sequencer 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 payment, reminder, sequencer, 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. Payment Reminder Sequencer 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
Payment Reminder Sequencer — Sample Brief
Headline
Builds a receivables action artifact for payment reminder sequencer work, turning invoice, payment, dispute, or aging data, customer history and commercial terms, and collection tone and escalation limits into payment receivable-aging classification, reminder payment-risk and dispute framing, and sequencer 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 sequenced communication plan: source evidence, reviewer checks, and the owner decision that determines whether the work is ready.
Evidence Packet
| Input | Example | Status |
|---|---|---|
| invoice, payment, dispute, or aging data | Apex Plumbing & HVAC is reconciling source-of-truth operating metrics before a finance owner approves the recommendation. | 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 |
Payment Evidence Model
| Field | What must be captured | Review consequence |
|---|---|---|
| Payment signal | Track invoice date, due date, aging bucket, payment history, dispute reason, and escalation limit. | Treat as draft until payment receivable-aging classification is source-backed. |
| Payment Receivable Aging Classification | Keep collection tone separate from finance-policy decisions. | Escalate when invoice, due date, payment history, or dispute basis is missing. |
| Reminder Payment Risk And Dispute Framing | Name the next finance owner action and the evidence needed before escalation. | Reviewer resolves sequencer collections-safe communication step before final use. |
Payment Acceptance Checks
| Check | Required evidence | Review action |
|---|---|---|
| Payment depth | Track invoice date, due date, aging bucket, payment history, dispute reason, and escalation limit. | Keep, revise, or ask a targeted follow-up |
| Reminder boundary | Keep collection tone separate from finance-policy decisions. | Confirm this is not a renamed adjacent bundle skill |
| Sequencer handoff | Name the next finance owner action and the evidence needed before escalation. | Assign the owner decision before final use |
Payment Reminder Sequencer Work Map
Payment Reminder Sequencer focus areas
Draft Sequenced Communication Plan
| Payment signal | Payment Receivable Aging Classification | Reminder Payment Risk And Dispute Framing | Sequencer Collections Safe Communication Step | Reminder decision |
|---|---|---|---|---|
| Metric | Payment variance uses actual, baseline, and period | reminder payment-risk and dispute framing | sequencer collections-safe communication step | Finance check |
| Driver | payment receivable-aging classification | Reminder 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. | Sequencer implication is framed for the reviewer | Ready |
Use now
Payment Reminder Sequencer
Best when invoicing & receivables work needs a concrete sequenced communication plan.
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
Finance and AR teams building a polite, escalating reminder sequence around an invoice due date so payment nudges go out on schedule without manual chasing. Most useful when many invoices share a cadence and tone should firm up as dates slip.
Not ideal for
A single one-off reminder, or accounts already in hard collections that need counsel. The sequence is a draft — a finance owner should confirm amounts, due dates, and terms before the reminders are scheduled.
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.