ar-credit-control

Generates AR aging summaries, dunning queues, and credit limit recommendations from accounting data.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill ar-credit-control-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ar-credit-control
Source: https://github.com/tapway/shogun-os/tree/main/skills/finance/ar-credit-control
Command: npx skills add https://github.com/tapway/shogun-os --skill ar-credit-control-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Overdue customer invoices and unmanaged credit limits create cash-flow risk, and manually tracking aging buckets and follow-ups is slow and error-prone. This Skill automates the AR sweep so finance teams get a prioritized collections queue without spreadsheet work. ## Core Features & Use Cases - AR Aging Sweep: Pulls the receivables aging report via acct_get_aging_report and buckets invoices into 0-30, 31-60, 61-90, and 90+ day tiers. - Dunning Queue Generation: Assigns each overdue invoice a Reminder, Escalation, or Legal tier and drafts follow-up messages from gbrain finance templates. - Credit Limit Review: Compares proposed credit limits against 12 months of payment history and returns an approve, reduce, or hold recommendation with rationale. - Use Case: Run a weekly AR sweep over 45 overdue invoices totaling RM128,500 and receive a dunning queue sorted by days overdue with ready-to-send messages per tier. ## Quick Start Ask the finance-manager agent to run the weekly AR aging sweep and produce the dunning queue with draft follow-up messages for every overdue invoice.

Frequently Asked Questions about ar-credit-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an AR aging report and dunning queue?

Run the AR aging sweep workflow, which calls acct_get_aging_report for receivables, buckets invoices into 0-30, 31-60, 61-90, and 90+ day tiers, then assigns each overdue invoice a Reminder, Escalation, or Legal dunning tier sorted by days overdue.

How to review customer credit limits before approving new orders?

The credit limit review workflow pulls customer profiles via acct_list_contacts and 12 months of sales history via acct_list_sales_invoices, then compares the proposed limit against payment history and aging risk to recommend approve, reduce, or hold with rationale.

What tools does AR collections automation require?

It requires the existing acct_* MCP contract tools (acct_list_sales_invoices, acct_get_aging_report, acct_list_contacts), the finance-manager owning profile, and a gbrain finance source containing credit-limit policy and dunning message templates.

Why do aging buckets differ between reports?

Aging bucket drift happens when invoice date is used instead of the contractual due date as day-0. Always age invoices from the due date, and flag partial-payment residuals by outstanding balance rather than original invoice amount.

When should I not use AR credit control for invoice processing?

Do not use it for supplier invoice processing, which belongs to ap-vendor-management, or for bank and gateway settlement, which belongs to bank-payment-reconciliation. It also does not enforce credit limits at order entry; that handoff must be documented separately.