Journal Entries logo

Journal Entries

Organization
vm0-ai
journal-entries

Create or review journal entries, accruals, amortization, depreciation, payroll, revenue, and adjustments.

Overview

Publishervm0-ai
Repositoryvm0-skills
Skill namejournal-entries
Stars
76
Forks
18
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vm0-ai on GitHub. Read the source before you install it.

Installation

Install the Journal Entries AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vm0-ai/vm0-skills.git /tmp/vm0-skills
mkdir -p .claude/skills
cp -r /tmp/vm0-skills/journal-entries .claude/skills/journal-entries
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Journal Entries in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Journal Entries on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Journal Entries is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Core Entry Patterns by Accounting Cycle

Vendor & Expense Accruals

Record obligations for goods received or services consumed when no invoice has arrived by the reporting cut-off.

Entry template:

  • DR: Appropriate expense (or asset if capitalizable)
  • CR: Accrued liabilities

Estimation sources:

  • Purchase orders showing confirmed delivery
  • Service agreements with work performed but unbilled
  • Standing vendor arrangements (utilities, professional fees, SaaS)
  • Staff reimbursement claims awaiting processing

Operational guidance:

  • Configure for automatic reversal at the start of the subsequent period
  • Apply the same estimation technique from period to period for comparability
  • Record the basis of each estimate (contract value, PO total, trailing average)
  • Compare prior-period estimates to eventual actuals and refine methodology

Tangible & Intangible Asset Charges

Systematically allocate the cost of long-lived assets over their service lives.

Entry template:

  • DR: Depreciation or amortization expense (allocated to cost center)
  • CR: Contra-asset (accumulated depreciation or amortization)

Allocation approaches:

  • Even-line: (Acquisition cost minus residual) divided by expected life — the default for most financial reporting
  • Accelerated: Apply a declining percentage to the remaining book value each period
  • Activity-based: Charge proportional to actual output versus total expected output

Operational guidance:

  • Source the entry from the fixed-asset or intangible-asset subledger
  • Confirm newly capitalized items carry the correct useful life and method
  • Check for retired or impaired assets requiring a write-off entry
  • Maintain parallel tracking for book versus tax depreciation where they diverge

Prepaid Cost Amortization

Release advance payments to expense as the underlying benefit is consumed.

Entry template:

  • DR: Relevant expense category (insurance, licenses, rent, maintenance)
  • CR: Prepaid asset

Frequently encountered prepaids:

  • Annual insurance policies
  • Multi-period software or platform subscriptions
  • Advance rent payments
  • Service and maintenance agreements
  • Deposits for conferences or events

Operational guidance:

  • Maintain an amortization register showing coverage dates and monthly charge amounts
  • Expense immaterial prepayments immediately rather than building a schedule
  • Accelerate remaining amortization when a contract is cancelled or terminated early
  • Add new prepaid items to the register promptly upon payment

Compensation Accruals

Capture all people costs attributable to the reporting period.

Entry templates:

Wages for partial pay-period overlap:

  • DR: Wage expense (by department)
  • CR: Accrued compensation

Incentive compensation:

  • DR: Bonus expense (by department)
  • CR: Accrued bonuses

Employer benefit obligations:

  • DR: Benefits expense
  • CR: Accrued benefits

Employer payroll taxes:

  • DR: Payroll tax expense
  • CR: Accrued payroll taxes

Operational guidance:

  • Pro-rate salary accruals based on business days falling inside the period versus the total pay cycle
  • Incentive accruals should mirror plan design: target payout, performance multipliers, and expected distribution timing
  • Include employer-borne costs — social security, unemployment insurance, health plans, retirement matching
  • Accrue for earned but unused paid time off where required by law or company policy

Contract Revenue Recognition

Record revenue consistent with the transfer of promised goods or services to the customer.

Entry templates:

Release of advance billings:

  • DR: Contract liability (deferred revenue)
  • CR: Revenue

Recognize with simultaneous receivable:

  • DR: Trade receivables
  • CR: Revenue

Collect or bill before delivery:

  • DR: Cash or trade receivables
  • CR: Contract liability (deferred revenue)

Operational guidance:

  • Apply the ASC 606 five-step model: (1) identify the contract, (2) identify performance obligations, (3) determine the transaction price, (4) allocate price across obligations, (5) recognize upon satisfaction
  • Maintain contract-level schedules that map obligations to delivery milestones
  • Handle variable consideration (discounts, rebates, penalties) using the expected-value or most-likely-amount method
  • Retain documentation sufficient to support external audit review

Documentation Standards

Each posted entry must include:

  1. Narrative memo: A plain-language explanation of what economic event the entry captures and the reason it is required
  2. Quantitative support: The formula, schedule, or data extract that produces the recorded amounts
  3. Source references: Identifiers linking to underlying evidence — PO numbers, invoice references, contract IDs, payroll registers
  4. Applicable period: The fiscal period to which the entry relates
  5. Preparer identity: Name and timestamp of the individual who built the entry
  6. Authorization evidence: Sign-off from the appropriate approver per the delegation matrix
  7. Reversal flag: Indication of whether the entry will auto-reverse, and the reversal date

Authorization Framework

Delegation Matrix

Entry ClassificationDollar RangeRequired Approver
Recurring / template-basedAll amountsAccounting manager
Ad hoc or non-standardUnder $50KAccounting manager
Ad hoc or non-standard$50K -- $250KController
Ad hoc or non-standardOver $250KCFO or VP of Finance
Consolidation / top-sideAll amountsController or higher
Prior-period correctionsAll amountsController or higher

Calibrate dollar bands to the organization's own materiality and governance requirements.

Approval Verification Steps

The approver should confirm each of the following before signing off:

  • Debits and credits are equal (the entry balances)
  • The target period is open and correct
  • General ledger account codes are valid and fit the transaction's nature
  • Dollar amounts tie to the supporting calculation without error
  • The memo is clear enough that a third party could understand the purpose
  • Cost center, department, and project tags are accurate
  • The accounting treatment matches established policy and prior-period practice
  • Accrual entries are flagged for reversal
  • All referenced support documents are attached or linked
  • The entry falls within the preparer's authorized scope
  • No duplicate of a previously posted entry exists
  • Any unusually large or round-dollar figures carry explicit justification

Frequent Mistakes and Prevention

  1. Imbalanced entries: Total debits do not equal total credits — system controls should block this, but verify on manual uploads
  2. Incorrect period: Entry lands in a closed or wrong fiscal month
  3. Inverted signs: Debit and credit legs are swapped
  4. Duplicate posting: The same economic event is captured twice — search for duplicates before submitting
  5. Misrouted account: Amounts post to a similarly numbered but incorrect GL code
  6. Unreversed accruals: A prior-period accrual remains on the books, overstating the current balance
  7. Outdated recurring estimates: Template entries roll forward without reflecting changed business conditions
  8. Suspiciously round figures: Amounts ending in multiple zeros that may not derive from actual calculations
  9. Wrong exchange rate: Foreign-currency entries converted at an outdated or incorrect FX rate
  10. Orphaned intercompany legs: One side of an intercompany transaction posted without the offsetting entity's entry
  11. Capitalization misjudgment: Expenses incorrectly capitalized, or capital items expensed in error
  12. Cut-off violations: Transactions recorded based on invoice date rather than the date goods transferred or services were rendered

Frequently asked questions

What does the Journal Entries AI skill do?

Create or review journal entries, accruals, amortization, depreciation, payroll, revenue, and adjustments.

Why use Journal Entries on TypingMind?

Because you install it once and use it with any model. Journal Entries is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Journal Entries in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vm0-ai/vm0-skills/tree/main/journal-entries. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Journal Entries?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Journal Entries?

As many as you like. As long as a model supports skills, you can use Journal Entries with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Journal Entries AI skill free?

It is published on GitHub by vm0-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇