LedgerDock is built on a few opinions about how accounting work should move. They are not complicated, but they are non-negotiable.
Most accounting software treats the ledger as the intake point. Import a bank feed and the transactions land directly in the general ledger. Classification happens after the fact, if it happens at all. Evidence is attached later, maybe. Review is optional.
LedgerDock takes the opposite position. The ledger is where work ends up after it has been staged, mapped, reconciled, classified, reviewed, and finalized. Nothing posts to the ledger without passing through this workflow. The ledger is the result of a controlled process, not a dumping ground with a nice font.
Staging is not bureaucracy. It is the space where professional judgment happens. When a bank statement arrives, its rows enter a scratch workbench where they can be mapped to accounts, reconciled against expected totals, classified by rules or AI proposals, and reviewed by an accountant before anything becomes permanent.
This staging layer protects the accountant from having to clean up after an import. It protects the client from having unreviewed transactions in their books. And it protects the firm from having to explain why the trial balance changed three times this week.
AI belongs inside the classification workflow, not above it. LedgerDock uses AI as one layer in a broader resolution cascade: deterministic rules first, then prior decisions, then vendor patterns, then AI proposals. Each layer has a confidence score and a source reason visible to the accountant.
When AI proposes a classification, the accountant reviews it. When the accountant overrides, the system learns. The accountant retains authority. AI is useful, bounded, and visible. It does not pretend to be a synthetic accountant with a suspicious amount of confidence.
A finalized commit should carry its evidence. The bank statement PDF, the receipt photo, the payroll report. These documents attach to the commit before finalization, and once the hash is computed, the relationship is sealed.
This is not a filing feature. It is an integrity feature. When someone asks "why was this $2,340 classified as materials?" the answer is not "I think I remember" — it is a link to the source document, the classification decision, and the accountant who approved it.
Most bookkeeping software is designed for the end state: reports, dashboards, summaries. The work before the reports — the intake, the classification, the reconciliation, the review, the evidence gathering — is treated as someone else's problem.
LedgerDock is operational software. It is built for the work. The pipeline, the staging rows, the review queues, the commit detail, the finalization gate. These are not secondary features bolted onto a ledger. They are the product.
Accountants spend most of their time in the work before the reports. The software should meet them there.