The familiar interface
The screens bookkeepers already know: vendors, bills, customers, invoices, jobs, and reports, with instant company switching and role-based access. Built first so nobody has to relearn their week.
A vendor invoice lands in a company inbox, gets checked to the cent, and posts as one balanced entry with the original kept. Sample data.
DigiBooks keeps the books for every company you own from one login. Switch companies instantly, capture vendor invoices straight from email, cost every job, and post to a double-entry ledger that never rounds a cent. Familiar where QuickBooks is familiar, stricter where it matters. accounting.
Connect a company inbox and vendor invoices are read, checked for arithmetic, and filed against the right bill with the original PDF kept. Anything uncertain waits for a person instead of guessing.
Each company has its own books, users, and documents. Switching companies resets everything on screen, so nothing is ever posted to the wrong set of books.
Material bills and labor land on the job they belong to, split where needed. Costs that cannot be matched stay visible as unassigned instead of disappearing into an average.
Try the company switcher on four sample businesses. Every figure below is illustrative sample data, not a live ledger.
Operational HVAC service jobs, commercial installations, inventory & technicians
Email intake validated: $4,280.00 • 3 compressors • Assigned to job 2026-88
Field receipt $148.20 recorded by a technician • Attachment retry queued without holding up the books.
General-purpose accounting software assumes one company, one login, and a bookkeeper retyping PDFs. DigiBooks starts from the other end: several companies, shared staff, and documents that should file themselves.
Sharing a vendor name across companies never merges balances or documents. Company scope is enforced in the database, not just on screen. Every ledger entry, report, and document belongs strictly to its authorized entity.
Stop downloading PDFs from email and retyping line items. DigiBooks files incoming invoices, treats vendor statements as reconciliation documents rather than new bills, flags missing attachments, and links every original to its posting.
Keep your payroll provider. DigiBooks is built to bring gross wages and employer taxes into the books and allocate them to jobs, with anything unallocated kept visible. Payroll sync is on the roadmap and clearly labelled until it ships.
Four kinds of business DigiBooks is designed around. Add companies as you grow; each gets its own books, staff permissions, and documents.
Equipment bills, technician field receipts, customer invoices, and job costing for HVAC, plumbing, and similar trades.
Subcontractor invoices, field materials, rental equipment, and payroll mapped to the jobs it was worked on.
Real estate acquisition capitalization, contractor draw disbursements, and project-specific renovation cost tracking.
The parent company that owns the others: software and cloud costs, subscriptions, and its own clean set of books.
DigiBooks runs on TypeScript and PostgreSQL with every posting committed as one balanced, atomic transaction in exact cents. Posted history is never silently edited, periods lock, and every change is in the audit trail.
Complete. The screens staff already know, with company switching and role-based access.
Complete in internal validation. Ledger, bills, invoices, payments, bank reconciliation, and the standard reports.
In build. Invoice extraction with arithmetic checks, duplicate detection, and a review queue for anything uncertain.
Every amount is stored and calculated as whole cents. Reports never balance themselves with a hidden plug entry; a difference is shown, not absorbed.
A posted bill, invoice, or journal is corrected with a traceable reversal, never edited in place. Closed periods stay closed without an authorized reopen.
The interface reserves space for AI assistants that read and propose but never post without approval. Nothing on this page claims one is running yet.
Each stage ships only after independent review against real bookkeeping scenarios. Nothing below is marked done because a demo looked right.
The screens bookkeepers already know: vendors, bills, customers, invoices, jobs, and reports, with instant company switching and role-based access. Built first so nobody has to relearn their week.
An exact-cent double-entry ledger, bills and invoices, recorded payments and credits, deposits and transfers, bank and card reconciliation, and the standard reports plus saved custom views. Posted history is corrected by reversal, never edited.
Connect a company inbox. Vendor invoices are read, checked for arithmetic and duplicates, and posted as bills with the original kept. Statements are matched against what's already booked instead of becoming new payables. Anything uncertain waits for a person.
Migrate from QuickBooks Online with month-by-month validation against the old books. Pull payroll runs into the ledger and onto jobs, keeping your payroll provider. Connect the field-service systems your companies already run.
Opening balances, reconciled source months, backup and restore drills, access reviews, and a named release owner before any company moves its books for good.
AI assistants that read and propose but never post without approval. Collecting payments and payment links. Then opening DigiBooks to other business owners, after it has run our own books for real.