finance/skills/journal-entry/SKILL.md
Prepare journal entries with proper debits, credits, and supporting detail
npx skillsauth add grailautomation/claude-plugins journal-entryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Important: This command assists with journal entry workflows but does not provide financial advice. All entries should be reviewed by qualified financial professionals before posting.
Prepare journal entries with proper debits, credits, supporting detail, and review documentation.
/je <type> <period>
type — The journal entry type. One of:
ap-accrual — Accounts payable accruals for goods/services received but not yet invoicedfixed-assets — Depreciation and amortization entries for fixed assets and intangiblesprepaid — Amortization of prepaid expenses (insurance, software, rent, etc.)payroll — Payroll accruals including salaries, benefits, taxes, and bonus accrualsrevenue — Revenue recognition entries including deferred revenue adjustmentsperiod — The accounting period (e.g., 2024-12, 2024-Q4, 2024)If ~~erp or ~~data warehouse is connected:
If no data source is connected:
Connect ~~erp or ~~data warehouse to pull GL data automatically. You can also paste trial balance data or upload a spreadsheet.
Prompt the user to provide:
Based on the JE type:
AP Accrual:
Fixed Assets:
Prepaid:
Payroll:
Revenue:
Present the entry in standard format:
Journal Entry: [Type] — [Period]
Prepared by: [User]
Date: [Period end date]
| Line | Account Code | Account Name | Debit | Credit | Department | Memo |
|------|-------------|--------------|-------|--------|------------|------|
| 1 | XXXX | [Name] | X,XXX | | [Dept] | [Detail] |
| 2 | XXXX | [Name] | | X,XXX | [Dept] | [Detail] |
| | | **Total** | X,XXX | X,XXX | | |
Supporting Detail:
- [Calculation basis and assumptions]
- [Reference to supporting schedule or documentation]
Reversal: [Yes/No — if yes, specify reversal date]
Before finalizing, verify:
Provide:
development
Parse and analyze Workato recipe JSON exports. Use when the user asks about a Workato recipe's logic, data flow, field mappings, error handling, or control flow. Also use when the user references a .recipe.json file or asks to debug a Workato integration.
databases
Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.
tools
Use when the user invokes $spec-kit:tasks or /spec-kit:tasks, or asks to generate dependency-ordered tasks from the plan and repo context.
testing
Use when the user invokes $spec-kit:specify or /spec-kit:specify, or asks to create a brownfield-aware feature specification from a natural language description.