This app is currently under development.

The chart of accounts is populated with a default set of accounts based on initial region.

Bank accounts can be created manually, or via import by OFX or Open Banking. Depending on the account type it will be given 1010 transaction account code, or 1020 savings account code, with the code incremented by one for each new bank account.

The account type (asset, liability, equity, income, other income, cost of goods, expense, other expense) conforms to standard accounting practice.

If an account has a associated tax code, tax will be calculated and subtracted from the bank transaction amount when that bank transaction is categorised. In that case, categorisation creates two contra transactions for the bank transaction: a net of tax item for the selected expense code, and a tax collected or paid transaction for the tax amount, depending on whether the destination account is a revenue account or expense account.

Transactions
This includes three basic types of transactions:
- imported bank transactions, with a type of DEBIT or CREDIT and source id being the transaction id from the source.
- contra transactions created by categorising bank transactions that have no payee id set. There can be one or two contra transactions for each bank transaction depending on if the categorisation account has a tax code or not.
Contra transactions are identified with a contra id field set to the transaction id of the corresponding bank transaction, and the same payee id of the categorised bank transaction.
- journal transactions are balanced sets of transactions that can be imported from applications such as invoicing or payroll, or created within the admin application. Journal transactions generally have no payee id, but the payee name set to the associated account name, a type of 'JRN' and a source id set to the id or the related journal table record.

Categorisation
Bank transactions are assigned a payee id automatically when they are imported by matching the transaction payee name with a saved payee name in the payee table. Matching on payee name will generate the one or two contra transactions, depending if the destination account has a tax code.

Both the bank transaction and contra transaction have the same payee id set, the bank transaction has a null contra id, and the contra transaction(s) have the contra id set to the id of the corresponding bank transaction.

Journals
A record of each journal imported from external applications or entered in admin is saved in the journal table. When that record is created, corresponding journal transactions are created in the transactions table, one transaction per journal line. No tax transactions are created from journals, regardless of the destination account for the journal line.

As an aid to entering journals in admin, a set of journal templates are provided to indicate how debits and credits should be entered for a variety of specific purposes: opening balances for bank accounts, customer or supplier invoices and GST/VAT reconciliation.

Payees
A payee record is created when bank transactions are categorised and linked to specific ledger accounts. If a future bank transaction is imported with the same payee, it is categorised automatically. Payees can be edited and a pattern set so the payee can be matched with a sub-string of the bank transaction payee. e.g. a pattern of woolworth will match with any bank transaction that has woolworth in any part of the payee name.

If a payee is deleted, any bank transaction with that payee is uncategorised, and re-matched against all remaining payees to be automatically categorised.

CSV transaction imports
If bank transactions are not available in OFX file format or via Open Banking, they can be imported by CSV format file. In that case, a CSV template has to be created that specifies which column in the CSV file contains what transaction field. A template has to identify a date, payee and amount at a minimum.