| Double entry | Nothing stops an unbalanced entry | Enforced | Enforced: an entry must balance before it can be posted |
|---|
| Multiple entities | One file or tab per company; consolidation by copy and paste | Usually one company file open at a time | Any number of businesses under one login, each with its own currency, calendar and chart |
|---|
| Intercompany automation | Re-key every transaction in both files | Rarely built in; often manual or custom scripts | Workflows post the other side automatically, with dry-run tests and loop protection |
|---|
| API and integrations | None, apart from file exports and macros | Varies; often local, limited or a paid add-on | REST API per business, idempotency keys and signed webhooks |
|---|
| Audit trail | File version history, not who posted which entry | Usually available on the local machine or server | Every create, edit, post and reversal logged with user and time; posted entries are corrected by reversal |
|---|
| Year-end closing | Formulas you build and check yourself | Built in | One-click close into retained earnings, automatic opening entry, reopen if needed |
|---|
| Multi-currency | Manual rate lookups and formulas | Common, sometimes only in higher editions | Entries in any active currency with stored rates; reports in the base currency |
|---|
| Collaboration | Shared files with no accounting roles | Single user or office network; remote access needs extra setup | Browser based, email invitations, six roles plus custom roles, two-factor sign-in |
|---|
| Cost model | Little or no software cost, a lot of staff time | License or yearly subscription, often per seat or edition | Pay as you go with credits, free credits to start, no per-seat fee |
|---|