journal-entry-prep

anthropics/knowledge-work-plugins · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill journal-entry-prep
0 commentsdiscussion
summary

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.

skill.md

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:

  1. Entry description/memo: Clear, specific description of what the entry records and why
  2. Calculation support: How amounts were derived (formula, schedule, source data reference)
  3. Source documents: Reference to the underlying transactions or events (PO numbers, invoice numbers, contract references, payroll register)
  4. Period: The accounting period the entry applies to
  5. Preparer identification: Who prepared the entry and when
  6. Approval: Evidence of review and approval per the authorization matrix
  7. 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

  1. Unbalanced entries: Debits do not equal credits (system should prevent, but check manual entries)
  2. Wrong period: Entry posted to an incorrect or already-closed period
  3. Wrong sign: Debit entered as credit or vice versa
  4. Duplicate entries: Same transaction recorded twice (check for duplicates before posting)
  5. Wrong account: Entry posted to incorrect GL account (especially similar account codes)
  6. Missing reversal: Accrual entry not set to auto-reverse, causing double-counting
  7. Stale accruals: Recurring accruals not updated for changed circumstances
  8. Round-number estimates: Suspiciously round amounts that may not reflect actual calculations
  9. Incorrect FX rates: Foreign currency entries using wrong exchange rate or date
  10. Missing intercompany elimination: Entries between entities without corresponding elimination
  11. Capitalization errors: Expenses that should be capitalized, or capitalized items that should be expensed
  12. Cut-off errors: Transactions recorded in the wrong period based on delivery or service date
how to use journal-entry-prep

How to use journal-entry-prep on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add journal-entry-prep
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill journal-entry-prep

The skills CLI fetches journal-entry-prep from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/journal-entry-prep

Reload or restart Cursor to activate journal-entry-prep. Access the skill through slash commands (e.g., /journal-entry-prep) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.872 reviews
  • Carlos Li· Dec 20, 2024

    We added journal-entry-prep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Nia Khan· Dec 4, 2024

    journal-entry-prep has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kiara Singh· Dec 4, 2024

    journal-entry-prep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Carlos Rahman· Nov 23, 2024

    journal-entry-prep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Luis Choi· Nov 23, 2024

    journal-entry-prep has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Nia Abebe· Nov 11, 2024

    Solid pick for teams standardizing on skills: journal-entry-prep is focused, and the summary matches what you get after install.

  • Carlos Zhang· Oct 14, 2024

    We added journal-entry-prep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kaira Singh· Oct 14, 2024

    Solid pick for teams standardizing on skills: journal-entry-prep is focused, and the summary matches what you get after install.

  • Nia Yang· Oct 2, 2024

    journal-entry-prep has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kabir Martinez· Sep 21, 2024

    Keeps context tight: journal-entry-prep is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 72

1 / 8