agentleFS
poorvith-mppoorvith-mp/skills-finance/skills/accounts-payable/SKILL.md

accounts-payable

Skill1 starsChanged 3 months agoMITView on GitHub

Run payables: vendor payments, contractor invoices and recurring bills across fiat, crypto and stablecoin rails. Use when managing incoming vendor bills, payment approvals, or expense reports.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never disburse funds based on an isolated invoice.

    line 16
  2. Distinctive:

    Never pay an invoice directly from an email attachment without verifying the vendor's bank account details against the master vendor file.

    line 38
  3. Distinctive:

    NEVER update vendor banking or routing details based solely on an email request without phone verification via a known number.

    line 50
  4. Distinctive:

    NEVER disburse payment without an itemized invoice detailing services rendered.

    line 51
  5. Distinctive:

    NEVER allow manual paper checks without dual-signature controls for transactions over $10,000.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Accounts Payable

Accounts payable is a working capital and fraud-prevention discipline. Managing payables requires strict three-way matching (purchase order, receiving report, vendor invoice), clear segregation of payment approval duties, and structured disbursement schedules across both traditional banking and modern digital/stablecoin rails.

1. The Three-Way Matching Protocol

Never disburse funds based on an isolated invoice. Validate three core documents before payment approval:

  1. Purchase Order (PO): Validates that the purchase was authorized with approved unit pricing.
  2. Receiving Report / Goods Receipt: Confirms that goods or services were delivered and accepted.
  3. Vendor Invoice: Verifies that billed quantities and rates match the PO and delivery receipt within a tight tolerance (typically <1% variance).

2. Payment Approval Matrix & Segregation of Duties

Prevent unauthorized disbursements through tiered approval thresholds:

  • Level 1 (Tier 1: < $2,500): Department manager approval.
  • Level 2 (Tier 2: $2,500 – $25,000): Department head + Financial Controller approval.
  • Level 3 (Tier 3: > $25,000): Chief Financial Officer (CFO) or CEO co-signature required.
  • Segregation of Duties Rule: The person who enters a vendor into the ERP/accounting system must never have banking disbursement or check-signing authority.

3. Disbursement Rails (Fiat, ACH, Wire, Stablecoins)

  • Domestic ACH: Batch processed bi-weekly (Tuesdays and Thursdays) to optimize cash float while avoiding late fees.
  • Commercial Credit Cards: Used for recurring SaaS subscriptions to capture 1.5%–2.0% cash rebates and leverage 30-day interest-free float.
  • International Wires / Stablecoins (USDC): For cross-border engineering contractors and overseas vendors. Verify wallet addresses via micro-transaction test transfers before executing full invoice disbursements.

4. Vendor Onboarding & Year-End Compliance

  • Collect IRS Form W-9 (US entities) or W-8BEN / W-8BEN-E (foreign contractors) prior to issuing the first payment.
  • Track 1099-NEC non-employee compensation thresholds ($600+ annual cumulative payment).

Critical Rules

  1. Never pay an invoice directly from an email attachment without verifying the vendor's bank account details against the master vendor file.
  2. Reconcile open AP subledger accounts against general ledger account 2000 (Accounts Payable) at every month-end close.
  3. Maintain an audit log of all payment authorizations for at least 7 years.

Verification Checklist

  • Three-way match confirmed between PO, receiving slip, and vendor bill.
  • Tax documentation (W-9 / W-8BEN) verified on file before disbursement.
  • Approval signatures correspond to authorized tier thresholds.
  • Payment schedule optimized for cash flow float without incurring vendor penalties.
  • 1099-eligible disbursements tagged in accounting system.

Anti-Patterns

  • NEVER update vendor banking or routing details based solely on an email request without phone verification via a known number.
  • NEVER disburse payment without an itemized invoice detailing services rendered.
  • NEVER allow manual paper checks without dual-signature controls for transactions over $10,000.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.