journal-entry-prep
Skill5 starsChanged 9 months agoMITView on GitHub
Prepare journal entries with proper debits, credits, and supporting documentation for month-end close. Use when booking accruals, prepaid amortization, fixed asset depreciation, payroll entries, revenue recognition, or any manual journal entry.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- anthropics/knowledge-work-pluginsedited, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- anthropics/knowledge-work-plugins★ 35k99% same
Wrote their own version · 0
None found.
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 repository103 other files it gives its agents.
- ab-test-setupSkill
- analytics-trackingSkill
- apple-notesSkill
- apple-remindersSkill
- audit-supportSkill
- blogwatcherSkill
- camsnapSkill
- canned-responsesSkill
- canvas-designSkill
- canvasSkill
- close-managementSkill
- coding-agentSkill
- company-valuesSkill
- competitive-ads-extractorSkill
- competitive-analysisSkill
- competitor-alternativesSkill
- complianceSkill
- content-strategySkill
- contract-reviewSkill
- copy-editingSkill
- copywritingSkill
- deep-researchSkill
- email-sequenceSkill
- feature-specSkill
- file-organizerSkill
- finance-reconcileSkill
- financial-statementsSkill
- find-communitySkill
- first-customersSkill
- form-croSkill
- free-tool-strategySkill
- gifgrepSkill
- goose-adventure-gameSkill
- himalayaSkill
- image-optimizerSkill
- imsgSkill
- instagram-marketingSkill
- launch-strategySkill
- legal-risk-assessmentSkill
- local-placesSkill
- marketing-ideasSkill
- marketing-psychologySkill
- mcporterSkill
- meeting-briefingSkill
- metrics-trackingSkill
- minimalist-reviewSkill
- model-usageSkill
- mvpSkill
- nano-banana-proSkill
- nano-pdfSkill
- nda-triageSkill
- notionSkill
- onboarding-croSkill
- openai-image-genSkill
- openai-whisper-apiSkill
- openai-whisperSkill
- openhueSkill
- oracleSkill
- ordercliSkill
- page-croSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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
- Distinctive: line 30
Use consistent estimation methodology period over period
- Distinctive: line 31
Document basis for estimates (PO amount, contract terms, historical run-rate)
- Distinctive: line 48
Run depreciation from the fixed asset register or schedule
- Distinctive: line 49
Verify new additions are set up with correct useful life and method
- Distinctive: line 50
Check for disposals or impairments requiring write-off
- Distinctive: line 51
Ensure consistency between book and tax depreciation tracking
- Distinctive: line 71
Check for cancelled or terminated contracts requiring accelerated amortization
- Distinctive: line 72
Verify new prepaids are added to the schedule promptly
- Distinctive: line 121
Follow ASC 606 five-step framework for contracts with customers
- Distinctive: line 130
Every journal entry should have:
- Distinctive: line 157
Before approving a journal entry, the reviewer should verify:
≈ “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.
Files
Journal Entry Preparation
Important: This skill assists with journal entry workflows but does not provide financial advice. All entries should be reviewed by qualified financial professionals before posting.
Best practices, standard entry types, documentation requirements, and review workflows for journal entry preparation.
Standard Accrual Types and Their Entries
Accounts Payable Accruals
Accrue for goods or services received but not yet invoiced at period end.
Typical entry:
- Debit: Expense account (or capitalize if asset-qualifying)
- Credit: Accrued liabilities
Sources for calculation:
- Open purchase orders with confirmed receipts
- Contracts with services rendered but unbilled
- Recurring vendor arrangements (utilities, subscriptions, professional services)
- Employee expense reports submitted but not yet processed
Key considerations:
- Reverse in the following period (auto-reversal recommended)
- Use consistent estimation methodology period over period
- Document basis for estimates (PO amount, contract terms, historical run-rate)
- Track actual vs accrual to refine future estimates
Fixed Asset Depreciation
Book periodic depreciation expense for tangible and intangible assets.
Typical entry:
- Debit: Depreciation/amortization expense (by department or cost center)
- Credit: Accumulated depreciation/amortization
Depreciation methods:
- Straight-line: (Cost - Salvage) / Useful life — most common for financial reporting
- Declining balance: Accelerated method applying fixed rate to net book value
- Units of production: Based on actual usage or output vs total expected
Key considerations:
- Run depreciation from the fixed asset register or schedule
- Verify new additions are set up with correct useful life and method
- Check for disposals or impairments requiring write-off
- Ensure consistency between book and tax depreciation tracking
Prepaid Expense Amortization
Amortize prepaid expenses over their benefit period.
Typical entry:
- Debit: Expense account (insurance, software, rent, etc.)
- Credit: Prepaid expense
Common prepaid categories:
- Insurance premiums (typically 12-month policies)
- Software licenses and subscriptions
- Prepaid rent (if applicable under lease terms)
- Prepaid maintenance contracts
- Conference and event deposits
Key considerations:
- Maintain an amortization schedule with start/end dates and monthly amounts
- Review for any prepaid items that should be fully expensed (immaterial amounts)
- Check for cancelled or terminated contracts requiring accelerated amortization
- Verify new prepaids are added to the schedule promptly
Payroll Accruals
Accrue compensation and related costs for the period.
Typical entries:
Salary accrual (for pay periods not aligned with month-end):
- Debit: Salary expense (by department)
- Credit: Accrued payroll
Bonus accrual:
- Debit: Bonus expense (by department)
- Credit: Accrued bonus
Benefits accrual:
- Debit: Benefits expense
- Credit: Accrued benefits
Payroll tax accrual:
- Debit: Payroll tax expense
- Credit: Accrued payroll taxes
Key considerations:
- Calculate salary accrual based on working days in the period vs pay period
- Bonus accruals should reflect plan terms (target amounts, performance metrics, payout timing)
- Include employer-side taxes and benefits (FICA, FUTA, health, 401k match)
- Track PTO/vacation accrual liability if required by policy or jurisdiction
Revenue Recognition
Recognize revenue based on performance obligations and delivery.
Typical entries:
Recognize previously deferred revenue:
- Debit: Deferred revenue
- Credit: Revenue
Recognize revenue with new receivable:
- Debit: Accounts receivable
- Credit: Revenue
Defer revenue received in advance:
- Debit: Cash / Accounts receivable
- Credit: Deferred revenue
Key considerations:
- Follow ASC 606 five-step framework for contracts with customers
- Identify distinct performance obligations in each contract
- Determine transaction price (including variable consideration)
- Allocate transaction price to performance obligations
- Recognize revenue as/when performance obligations are satisfied
- Maintain contract-level detail for audit support
Supporting Documentation Requirements
Every journal entry should have:
- Entry description/memo: Clear, specific description of what the entry records and why
- Calculation support: How amounts were derived (formula, schedule, source data reference)
- Source documents: Reference to the underlying transactions or events (PO numbers, invoice numbers, contract references, payroll register)
- Period: The accounting period the entry applies to
- Preparer identification: Who prepared the entry and when
- Approval: Evidence of review and approval per the authorization matrix
- Reversal indicator: Whether the entry auto-reverses and the reversal date
Review and Approval Workflows
Typical Approval Matrix
| Entry Type | Amount Threshold | Approver |
| Standard recurring | Any amount | Accounting manager |
| Non-recurring / manual | < $50K | Accounting manager |
| Non-recurring / manual | $50K - $250K | Controller |
| Non-recurring / manual | > $250K | CFO / VP Finance |
| Top-side / consolidation | Any amount | Controller or above |
| Out-of-period adjustments | Any amount | Controller or above |
Note: Thresholds should be set based on your organization's materiality and risk tolerance.
Review Checklist
Before approving a journal entry, the reviewer should verify:
- Debits equal credits (entry is balanced)
- Correct accounting period (not posting to a closed period)
- Account codes exist and are appropriate for the transaction
- Amounts are mathematically accurate and supported by calculations
- Description is clear, specific, and sufficient for audit purposes
- Department/cost center/project coding is correct
- Treatment is consistent with prior periods and accounting policies
- Auto-reversal is set appropriately (accruals should reverse)
- Supporting documentation is complete and referenced
- Entry amount is within the preparer's authority level
- No duplicate of an existing entry
- Unusual or large amounts are explained and justified
Common Errors to Check For
- Unbalanced entries: Debits do not equal credits (system should prevent, but check manual entries)
- Wrong period: Entry posted to an incorrect or already-closed period
- Wrong sign: Debit entered as credit or vice versa
- Duplicate entries: Same transaction recorded twice (check for duplicates before posting)
- Wrong account: Entry posted to incorrect GL account (especially similar account codes)
- Missing reversal: Accrual entry not set to auto-reverse, causing double-counting
- Stale accruals: Recurring accruals not updated for changed circumstances
- Round-number estimates: Suspiciously round amounts that may not reflect actual calculations
- Incorrect FX rates: Foreign currency entries using wrong exchange rate or date
- Missing intercompany elimination: Entries between entities without corresponding elimination
- Capitalization errors: Expenses that should be capitalized, or capitalized items that should be expensed
- Cut-off errors: Transactions recorded in the wrong period based on delivery or service date
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.

