journal-entry-review
Skill2 starsChanged 3 months agoAGPL-3.0View on GitHub
Reviews a population of journal entries for risk, propriety and anomalies through a control and audit lens: screens every entry against timing, account-combination, amount and people-and-process indicators measured against the entity's history, risk-scores the flags and leads with patterns such as recurring period-end adjustments and reserves that move with earnings. Reads the entries through a connected Mosofin workspace when the user agrees, or works from uploaded journal or GL exports. Reports the approval-based indicators as not run where approval data is not available, and treats every flag as a question, never a finding of fraud. Use when the user asks to review journal entries, run JE testing, find unusual journal entries, test JEs for fraud indicators or assess journal entry controls. Do not use for building entries (use journal-entry-builder) or for a full forensic investigation. Read-only: produces a risk-scored review workpaper, follow-up items 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
- 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
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.

