revenue-concentration-audit

Analyzes revenue by customer and flags single clients exceeding 20% of total revenue.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finance teams need to detect customer concentration risk for governance and board reporting, but manually aggregating invoices and computing revenue shares per client is slow and error-prone. ## Core Features & Use Cases - Customer Revenue Aggregation: Pulls sales invoices via acct_list_sales_invoices and resolves customer names with acct_list_contacts, then computes each customer's share of total revenue. - Concentration Risk Flagging: Ranks customers by revenue share and marks any single customer above the 20% threshold with a concentration risk flag. - Audit Trail Storage: Saves each period's concentration table to finance/concentration-audit/<YYYY-MM>.json in the gbrain finance source. - Use Case: During a monthly finance review, run the audit for August 2026 to produce a ranked concentration table showing MegaCorp at 20.2% flagged as a risk, ready for inclusion in board materials. ## Quick Start Run a revenue concentration audit for last month and flag any customer exceeding 20% of total revenue.

Frequently Asked Questions about revenue-concentration-audit

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

FAQPage Schema
How do I audit customer revenue concentration for board reporting?

Pull all sales invoices for the period, aggregate revenue by customer, compute each customer's share of total revenue, and rank them descending. Flag any customer above 20% of total revenue as a concentration risk and save the table for the audit record.

What revenue concentration threshold should trigger a risk flag?

The standard threshold is 20% of total revenue from a single customer, a common corporate governance and investor-reporting convention. Do not raise this threshold without board approval, as it understates disclosed risk.

Should subsidiary customers be combined in concentration analysis?

Yes. If multiple customer entities share a single ultimate parent, their revenues must be aggregated before the concentration check. Treating subsidiaries separately understates the true concentration risk.

Why does one month show a customer above 20% concentration?

Short reporting periods with lumpy payments can spike one customer above the threshold. Use a trailing 12-month revenue total alongside the month-to-date figure to assess structural rather than temporary concentration.

When should I not use a revenue concentration audit?

Do not use it for margin analysis by client, which belongs to unit economics analysis, or for AR collections, which belongs to credit control workflows. It only measures revenue share concentration, not profitability or collectability.