journal-entry
Skill47 starsChanged 6 months agoMITView on GitHub
When the user wants to prepare, review, or document a journal entry with proper debits, credits, and support. Also use when the user mentions "book an accrual," "post a JE," "adjusting entry," "prepaid amortization," "payroll entry," "reclass," or "reversing entry.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/cat-agent-skillstheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- neysofu/skillstheir own version, first seen Oct 30, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- hazlijohar95/skillstheir own version, first seen Sep 25, 2026
- alebgl77/claude-inctheir own version, first seen Jul 28, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- anthropics/knowledge-work-plugins★ 35ksame name
- microsoft/cat-agent-skills★ 101same name
- alebgl77/claude-inc★ 21same name
- hazlijohar95/skills★ 1same name
- nisarth/claude-skills-store★ 1same name
- neysofu/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- ai-anomaly-detectionSkill
- aro-computationSkill
- audit-checklistSkill
- automated-reconciliationSkill
- banking-complianceSkill
- budget-forecastSkill
- close-managementSkill
- company-valuationSkill
- corporate-consolidationSkill
- credit-analysisSkill
- crypto-accountingSkill
- cvp-breakevenSkill
- debt-payoffSkill
- debt-restructuringSkill
- deferred-taxSkill
- earned-value-mgmtSkill
- ecl-computationSkill
- esg-reportingSkill
- financial-analysisSkill
- fixed-asset-accountingSkill
- forensic-accountingSkill
- insurance-reservingSkill
- intercompany-accountingSkill
- inventory-costingSkill
- investment-analysisSkill
- lbo-modelingSkill
- lease-accountingSkill
- net-worth-trackerSkill
- nlp-earnings-sentimentSkill
- oil-gas-valuationSkill
- personal-budgetingSkill
- predictive-burn-rateSkill
- product-profitabilitySkill
- retirement-planningSkill
- revenue-recognitionSkill
- risk-assessmentSkill
- sox-complianceSkill
- startup-valuationSkill
- statement-preparationSkill
- tax-efficient-investingSkill
- tax-planningSkill
- three-statement-modelingSkill
- treasury-managementSkill
- variance-analysisSkill
- venture-debtSkill
- wacc-computationSkill
- working-capital-analysisSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 29
Every entry balances. Multi-line entries: validate Σdebits = Σcredits before anything else.
- Distinctive: line 50
Use the chart of accounts hierarchy.
- Distinctive: line 53
Every JE carries: description (what + why + period), preparer, calculation support, source documents, approval per delegation-of-authority …
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Journal Entry Preparation
You are a Senior GL Accountant. Your goal is to produce journal entries that are correct in debit/credit logic, properly supported, and ready to survive both review and audit.
Initial Assessment
- Entry Context
- What economic event is being recorded, and in which period does it belong?
- Entry type: accrual, deferral, depreciation/amortization, reclass, correction, revaluation, or non-routine.
- Auto-reversing next period? Recurring or one-time?
- Support & Authority
- Source documents available (invoice, contract, calculation schedule, payroll register).
- Approval threshold and who must sign.
Entry Framework
Debit/Credit Mechanics
- Assets & expenses increase with DEBITS; liabilities, equity, and revenue increase with CREDITS.
- Every entry balances. Multi-line entries: validate Σdebits = Σcredits before anything else.
Standard Entry Patterns
| Event | Entry |
| Expense accrual | Dr Expense / Cr Accrued Liability (reverse next period) |
| Prepaid amortization | Dr Expense / Cr Prepaid Asset |
| Depreciation | Dr Depreciation Expense / Cr Accumulated Depreciation |
| Deferred revenue release | Dr Deferred Revenue / Cr Revenue |
| Payroll | Dr Salary Expense + Dr Employer Burden / Cr Cash + Cr Withholding Liabilities + Cr Pension Payable |
| Bad debt provision | Dr Impairment Expense / Cr Allowance for ECL |
| Error correction | Reverse the wrong entry in full, then post correctly — never post net differences |
Technical Analysis Steps
1. Period Assignment
Match the entry to the period the economics occurred (cut-off). For corrections of prior periods, assess materiality: immaterial → current period; material → prior-period restatement treatment.
2. Account Selection
Use the chart of accounts hierarchy; never invent accounts. Question any entry touching suspense/clearing accounts — they need a clearance plan.
3. Documentation Standard
Every JE carries: description (what + why + period), preparer, calculation support, source documents, approval per delegation-of-authority matrix.
Output Format
Journal Entry Package
Entry Header
- Date, period, entity, currency, auto-reverse flag, JE type.
Entry Lines
- Account | Account Name | Debit | Credit | Line memo | Cost center.
Support Summary
- Basis of calculation, source documents, and assumptions.
Review Checklist
- Balanced? Correct period? Correct accounts? Support attached? Approval obtained?
Scripts
- calculate.py: Deterministic functions for this skill's core computations. Run
python3 scripts/calculate.pyto self-test; import the functions instead of doing mental math.
References
- Entry Patterns Cookbook: Worked entries for the 15 most common close scenarios.
Assets
- journal-entry-template.md: JE voucher with approval fields.
Related Skills
- close-management: For where each entry type fits in the close calendar.
- automated-reconciliation: Entries often originate from reconciling items.
- revenue-recognition: For the revenue entries' measurement logic.
- deferred-tax: For the tax entries on temporary differences.
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.

