double-entry-validator

Validate double-entry bookkeeping and US GAAP account code ranges in journal entries.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/OmarMira/Coontabilidad --skill double-entry-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: double-entry-validator
Source: https://github.com/OmarMira/Coontabilidad/tree/main/.agent/skills/double-entry-validator
Command: npx skills add https://github.com/OmarMira/Coontabilidad --skill double-entry-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the persistence of financial transactions that violate fundamental accounting principles, ensuring data accuracy and integrity.

Core Features & Use Cases

  • Double-Entry Validation: Verifies that total debits equal total credits for every transaction.
  • Chart of Accounts Compliance: Checks if account codes fall within the standard US GAAP ranges (1xxx-5xxx).
  • Use Case: Before closing the books for the month, run this Skill to automatically scan all journal entries and flag any that are unbalanced or use invalid account codes, preventing errors in financial reporting.

Quick Start

Validate all accounting entries to ensure they adhere to the double-entry principle.

Frequently Asked Questions about double-entry-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate double-entry bookkeeping transactions before closing the books?

Double-entry validation verifies that total debits equal total credits for every transaction, ensuring data accuracy and integrity. It prevents the persistence of financial transactions that violate fundamental accounting principles before you close your books.

How does chart of accounts compliance checking work for US GAAP account codes?

Chart of accounts compliance checking works by verifying that account codes fall within standard US GAAP ranges (1xxx-5xxx). It utilizes a JSON-based COA definition for range checking to ensure all journal entries use valid account codes.

Can I use this to enforce the fundamental accounting equation for all journal entries?

Yes, you can enforce the fundamental accounting equation for all journal entries. The validator enforces the fundamental accounting equation (Debits = Credits) and verifies account code ranges, ensuring transactional atomicity for every entry.

What's the best way to flag unbalanced journal entries in financial reporting?

The best way to flag unbalanced journal entries is to scan all journal entries automatically before closing the books. This process flags any entries that are unbalanced or use invalid account codes, preventing errors in financial reporting.

Does double-entry validation require a specific format for the chart of accounts?

Double-entry validation requires a JSON-based COA definition for range checking. This format allows the validator to accurately verify that account codes fall within the standard US GAAP ranges (1xxx-5xxx) for all transactions.