invoice-review-compliance
Invoice review, non-compliance flagging, rejection communication, billing trend analysis, and conversation preparation for in-house legal ops teams managing outside counsel. Review invoices against billing guidelines; flag block billing, prohibited fees, rate violations, staffing violations, late submission. Produce line-item review report and approval note. Draft rejection letter to outside counsel. Build invoice review checklist. Analyse billing trends across multiple invoices and produce a structured conversation guide for the relationship review. Identify systemic patterns and produce form
npx skills add lawve-ai/awesome-legal-skills --skill invoice-review-compliance-scott-margetts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Executes invoice compliance review from line-item flagging through to formal firm communication. Encodes the methodology for reviewing invoices against billing guidelines, categorising violations, producing defensible approval decisions, and escalating systemic non-compliance.
How it works
- Reviews an invoice against provided billing guidelines, flags violations by category (e.g., Block billing, Prohibited fees, Rate violations, Staffing, Late submission).
- Produces a Line-Item Review Report with a table of flagged entries, issue details, and recommended actions, followed by an Invoice Approval Note summarizing the recommended payment decision.
- If needed, drafts a formal rejection letter to the outside counsel and an internal rejection record.
- Builds an invoice review checklist calibrated to the organization’s guidelines.
- Identifies recurring compliance patterns across multiple invoices and prepares a formal non-compliance notice for the firm.
- Uses modes to route tasks: Mode 1 for line-item review, Mode 2 for rejection communication, Mode 3 for review process setup, Mode 4 for pattern analysis, Mode 5 for relationship review triggers.
- Documents are produced as .docx files with header data including Company, Firm, Matter, Invoice number, and date.
When to use it
Triggers include commands such as: 'review this invoice', 'check this against our guidelines', 'flag the billing issues', 'write the rejection letter', 'build an invoice checklist', 'our review process', 'block billing', 'UTBMS', 'LEDES', 'billing non-compliance', 'recurring violations', 'the firm keeps doing this', 'escalate the billing issue'. These map to Mode 1, Mode 2, Mode 3, Mode 4, and Mode 5 respectively.
What it can touch
The skill references and uses external billing guidelines and e-billing system details to assess entries. It may rely on placeholders when data is incomplete and outputs documents (.docx) containing Company Name, Firm Name, Matter Name, and date in headers.
Caveats
Does not draft or create billing guidelines or engagement terms; does not design fee arrangements; does not generate original matter instructions. Uses placeholders if input data is incomplete and flags missing data after producing documents.
# invoice-review-compliance ## Description Invoice review, non-compliance flagging, rejection communication, and billing compliance tracking for in-house legal ops teams managing outside counsel. Review an invoice against billing guidelines, flag violations by category, and produce a line-item review report with an approval note for the payment team. Draft a formal rejection letter to the firm for flagged entries. Build an invoice review checklist calibrated to your billing guidelines. Identify recurring compliance patterns across invoices and produce a formal non-compliance notice for the firm. Trigger on: 'review this invoice', 'check this against our guidelines', 'flag the billing issues', 'write the rejection letter', 'communicate the reductions', 'build an invoice checklist', 'our review process', 'block billing', 'UTBMS', 'LEDES', 'billing non-compliance', 'recurring violations', 'the firm keeps doing this', 'escalate the billing issue'. --- ## What This Skill Does Executes invoice compliance review from line-item flagging through to formal firm communication. Encodes the methodology for reviewing invoices against billing guidelines, categorising violations, producing defensi
- Description
- What This Skill Does
- Pre-flight — Confirm and Fill
- Mode 1: Invoice Line-Item Review
- Input
- How to run this mode
- Line-Item Review Report template
- Invoice Approval Note template
- Violation reference framework — apply inside templates above
- Mode 2: Invoice Rejection Communication
- Invoice Rejection Letter template
- Internal Rejection Record template
- Mode 3: Review Process Setup
- Invoice Review Checklist template
What does the invoice-review-compliance skill do?
Invoice review, non-compliance flagging, rejection communication, billing trend analysis, and conversation preparation for in-house legal ops teams managing outside counsel. Review invoices against billing guidelines; flag block billing, prohibited fees, rate violations, staffing violations, late submission. Produce line-item review report and approval note. Draft rejection letter to outside counsel. Build invoice review checklist. Analyse billing trends across multiple invoices and produce a structured conversation guide for the relationship review. Identify systemic patterns and produce form
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill invoice-review-compliance-scott-margetts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
