Chart of accounts and GL mappings.
Start with 134 ready-made accounts under the five standard types, and 31 mappings that decide which accounts everyday events like invoices, payments and expenses post to. Nobody picks an account per transaction.
Sending an invoice, taking a payment, approving an expense: each is mapped to an account, and the journal writes itself from that mapping.
The chart and the mappings
The accounts, and what posts to them.
The chart lists every account your books can use. The mappings decide which accounts everyday events post to, automatically, when something happens elsewhere in the company. Switch between them below.
The five types are fixed by double-entry accounting. Sub-types, codes and names are yours.
What the company owns
38 accountsWhat it owes
24 accountsWhat remains for the owners
9 accountsWhat it earned
17 accountsWhat it spent
46 accounts| Code | Account | Sub-type | |
|---|---|---|---|
| Asset | |||
| 1100 | Accounts Receivable | Current asset | System |
| 1200 | Bank, current account | Cash and equivalents | |
| 1400 | Prepaid Expenses | Current asset | |
| 1600 | Office Equipment | Fixed asset | |
| Liability | |||
| 2100 | Accounts Payable | Current liability | System |
| 2200 | Accrued Expenses | Current liability | |
| 2330 | Statutory Payable | Payroll liability | System |
| Revenue | |||
| 4000 | Service Revenue | Operating revenue | System |
| 4100 | Recurring Support Revenue | Operating revenue | |
| Expense | |||
| 5100 | Salaries and Wages | Staff costs | System |
| 5200 | Software Subscriptions | Operating expense | |
| 5400 | Travel and Subsistence | Operating expense | |
System accounts can be renamed but not deleted, because the mappings and the reconciliation both point at them.
Send an invoice, and the accounting is already done.
The difference
How other tools do it.
Other tools keep your operations and your accounting in separate systems. How they bridge the two decides how much of every month goes on making both sides agree.
A connector copies invoices over on a schedule. Details drift out of step, a status change arrives late or not at all, and somebody spends the first week of every month working out which side is right.
You end up with two records of the same client and two versions of revenue. They are matched by name or email, and the match breaks the first time somebody types a company name differently.
Your invoices and your books live in one place. Sending an invoice writes the accounting at the same moment, so there is nothing to copy across and nothing to reconcile.
The five standard types, organised your way.
Every account is an asset, liability, equity, revenue or expense. Under those five, the structure is yours.
- Name your own sub-types under each of the five
- Use your own account codes and your own grouping
- Add accounts as the business needs them
- Rename a built-in account; the automatic postings still find it
- Start with a ready-made chart, not a blank page
Everyday actions do their own bookkeeping.
Send an invoice, take a payment or approve an expense, and a balanced entry is written to the accounts the mapping names.
- Sending an invoice posts it to receivables and revenue
- Recording a payment posts it to bank and receivables
- An approved expense posts to its category and to payables
- A released payroll run posts to wages and statutory payables
- Change a mapping, and every future posting of that event follows it
One invoice, start to finish
A deal won in Sales, booked in Finance.
The account manager never thinks about the ledger, and never needs to. The mapping was set once by somebody who knows accounting, and it has applied to every invoice since.
Debit Accounts Receivable, credit Service Revenue. Set once, by somebody who knows accounting.
Access
Who can do what.
Adding an account is a bookkeeping decision. Changing where an event posts applies to every future transaction, so only Admin can do it.
See the chart and what each account is for.
Post to accounts through everyday work.
Add accounts, and name your own sub-types.
Change a mapping, which changes every future posting.
Admin is the highest role and is not constrained by the permission grid, so it is worth keeping to the smallest group that genuinely needs it.