payroll-clearing-reconciliation
Skill2 starsChanged 3 months agoAGPL-3.0View on GitHub
Reconciles the payroll control accounts — payroll clearing, payroll suspense, and each withholding, employer-charge, benefit and garnishment liability — at month end: rolls each forward, compares it to its expected balance, ages every balance, tests whether it behaves like its remittance cadence, and finds the stale balances that never clear, including unclaimed pay that may be escheatable. Reads the books through a connected Mosofin workspace when the user agrees, or works from uploaded GL detail, payroll registers and remittance records, treating the register as external unless a payroll platform is connected. Use when the user asks to reconcile payroll clearing or suspense, clear payroll liabilities, or why payroll clearing is not zero. Do not use for the payroll journal itself (use payroll-journal-entry-builder) or a full register-to-GL and bank tie-out (use payroll-reconciliation). Read-only: produces a reconciliation workpaper, proposed cleanup entries and a coverage sheet, and posts nothing.
In this repository30 other files it gives its agents.
- accruals-and-deferralsSkill
- ap-accrual-cutoffSkill
- ap-aging-and-payment-runsSkill
- 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-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
8 rules. About 0 are common, 5 are distinctive, and 3 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.
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.

