ap-aging-and-payment-runs
Skill2 starsChanged 3 months agoAGPL-3.0View on GitHub
Builds an accounts payable aging by vendor and due-date bucket and proposes a prioritised payment run within the cash the user confirms: early-pay discounts with their deadline and annualised return, late-pay penalties, critical vendors first, held and disputed bills kept out, and the unpaid remainder shown. Reads the A/P aging report, or rebuilds it from open bills, payments and credits and ties it to the A/P control balance, through a connected Mosofin workspace when the user agrees, or works from an uploaded open-bill list. Always asks for the cash available and never reads it off a bank balance. Use when the user asks for an AP aging, who they owe and when it is due, a payment run for this week, which bills to pay first, early-pay discounts or who is overdue, or uploads an AP balance or open bill list. Do not use for extracting individual vendor invoices (use invoice-data-extractor). Read-only: produces an aging, a proposed payment run, a discount analysis and a coverage sheet, and posts and pays nothing.
In this repository30 other files it gives its agents.
- accruals-and-deferralsSkill
- ap-accrual-cutoffSkill
- ar-aging-and-collectionsSkill
- balance-sheet-reconciliationsSkill
- bank-reconciliationSkill
- budget-vs-actual-analysisSkill
- cash-applicationSkill
- cash-flow-forecast-13-weekSkill
- closing-entries-and-trial-balanceSkill
- credit-card-reconciliationSkill
- credit-memo-and-refund-handlerSkill
- customer-invoicingSkill
- duplicate-invoice-detectionSkill
- expense-report-processorSkill
- financial-statement-builderSkill
- fixed-asset-register-and-depreciationSkill
- gl-coding-assistantSkill
- inventory-to-gl-reconciliationSkill
- invoice-data-extractorSkill
- journal-entry-builderSkill
- journal-entry-reviewSkill
- merchant-and-payment-processor-recSkill
- month-end-close-checklistSkill
- payroll-clearing-reconciliationSkill
- payroll-journal-entry-builderSkill
- payroll-reconciliationSkill
- prepaid-amortization-scheduleSkill
- recurring-transaction-builderSkill
- three-way-matchSkill
- vendor-statement-reconciliationSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
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
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.

