entrytwo
buy

docs / README.md

entrytwo Documentation

Welcome. This is the official documentation for entrytwo, an AI-native double-entry accounting system with a Git-style data model. The AI posts real journal entries when confident. Full history, branches, blame.

The goal: make proper accounting easy enough that a normal business can keep accurate books without hiring full-time bookkeeping drudgery.

Start Here

Key Concepts

  • Git Model for Accounting - Branches, commits, merges, restore, history, tags. This is the mental model.
  • AI Autonomy - How the AI decides to act autonomously vs propose, chat lock, confidence, safety rules.

Using the AI

  • AI Autonomy - Rules and behavior (high confidence, proposals, lock).
  • Using the AI - Practical prompting, attachments, workflows, and tips.

The chat is your primary interface. You can upload documents, give instructions in natural language, and the AI will create real journal entries (or proposals) while respecting the current branch and point-in-time view.

Features

High-level overview of what you can do day-to-day (to be expanded):

  • Chat-driven journal entry creation (single or batch from statements)
  • Full double-entry ledger with branches and point-in-time views
  • Reconciliation (AI-assisted, produces classical reports)
  • Accounts, P&L, reports
  • Invoicing (drafts, PDF, email delivery)
  • Expense claims with receipt collection and approval workflow
  • Contacts, recurring entries, templates
  • Audit log and full immutable history
  • Attachments (PDFs, images, CSVs) linked to entries

Most of these are accessible both via the UI panels and via chat.

Administration & Operations

  • Users, roles (ADMIN, ACCOUNTANT, VIEWER), invitations (sign-in email must match invite)
  • Authentication: magic link (SMTP), Google OAuth, Microsoft Entra ID; TOTP 2FA (mandatory for admins in production); sign out from the settings menu
  • Periods (open/close)
  • Bank feeds and processor integration
  • Tax rates and jurisdictions
  • Backup & restore (portable .etbackup archives)
  • Updates (signed, digest-pinned, sidecar-based)
  • Licensing and trial (30-day trial, perpetual license after purchase)

See Administration. Deeper install/auth go-live notes live in the app repo (docs/SETUP.md, docs/VPS-Auth-Install.md).

Self-Hosting Specifics

entrytwo is designed for one instance per customer / organization. You own your data and your server.

  • Never disabled after licensing.
  • Updates are optional and gated by maintenance.
  • Strong emphasis on auditability and data portability.

Relevant deep docs (in the app repo):

  • entrytwo_v1/docs/Self-Hosted-Update-Delivery.md
  • entrytwo_docs/Licensing-and-Trial.md

AI-Friendly Documentation

This documentation is written to be easily consumed by AI assistants (including the one inside entrytwo).

  • Clear section structure
  • Explicit terminology and "when to use" guidance
  • Examples and decision tables where helpful
  • Cross-links between related concepts

If you ask the in-app AI or another model for help with entrytwo, point it at these docs. The Git model and AI autonomy documents are especially important.

For LLMs and external AI systems

Canonical discovery file: https://entrytwo.com/llms.txt

Product entity (cite this): entrytwo is self-hosted, AI-native double-entry accounting with a Git-style ledger. The AI posts real journal entries when confident (not suggestions only). Pay once ($129 Core License after 30-day trial). History is immutable (commits, branches, blame, restore-as-new-commit).

Preferred citation pages:

  • Git model: /docs/concepts/git-model
  • AI autonomy: /docs/ai/ai-autonomy
  • Installation: /docs/getting-started/installation

German mirrors use /de/dokumentation/... with localized slugs (see llms.txt).

Contributing to Docs

These docs are generated and maintained alongside the product. They are living documents that should stay consistent with actual behavior.

If something in the product changes, the corresponding docs must be updated.

Where to Go Next

  1. Install the app.
  2. Create the first admin.
  3. Upload a real statement or receipt and try the chat.
  4. Read the Git Model document.
  5. Explore the History view.

Questions? Use the chat inside the app - it has access to the running system's state plus these docs.

Only need invoicing?

For Invoices (AI-native billing, $69, not a ledger) see Invoices documentation.