Accounting software features list: 9 core, 7 optional

An accounting software features list has two parts. Nine core features appear in most of the 37 accounting and invoicing products we counted: an income and expense ledger, organisation and fiscal settings, financial reports, an invoice builder, customer records, payments received, document numbering, bank and cash accounts, and a dashboard. Seven optional features depend on your business: bank feeds, multi-currency, payroll, inventory, projects, recurring billing and online payment collection.

Core accounting software features (counted across 37 products)

From the research behind the Accounting & Invoicing Planner: how many of the 37 accounting tools have each feature.

A feature counts only when a source directly showed it shipping. The share is how common a feature is in the sample, not a ruling that your business needs it. The sections further down give a five-minute trial test for each one.

Optional accounting software features (choose by business type)

These are real features, but each is a branch: right for some businesses, unnecessary for others. They are not ranked in this count.

Accounting software features and functions

If you think in jobs rather than screens, the nine core features cover four functions:

A bookkeeping-only business needs the first, third and fourth rows. The second row matters only when you invoice.

Download the requirements checklist

Download the accounting software requirements checklist (.md)

Use the editable checklist to mark each capability Required, Optional or Out of scope, name an owner and record a test result. It covers the nine core features plus decisions about double-entry, bank feeds, currency and access. The frequency counts describe our research sample; they do not automatically make a feature mandatory for your business.

Pick the bookkeeping or invoicing shape first. Then test your chosen system using the sample actions in the checklist. A requirement remains unverified until the observed result and its evidence are recorded. For a custom build, continue with the accounting and invoicing planner or try its discovery questions.

Why a ticked feature grid is not enough

Most feature lists are a grid of ticks, and every product ticks most of the boxes, so the grid cannot separate good software from bad. The difference is in what each feature does. For each core feature below you get the real version, the decorative version, and a test you can run in a trial account in a few minutes.

First, the decision that splits the category

Before any feature list applies, accounting software comes in two shapes, and they are easy to confuse.

Bookkeeping first. The ledger is the product: every pound or dollar in and out, categorised, whether or not an invoice was ever involved. Reports come from the ledger.

Invoicing first. The invoice is the product: bill a client, chase them, mark it paid. The ledger, if there is one, is a by-product of invoices.

The research is clear on which comes first. The most common capability in the count is the income and expense ledger, and the research treats it as something that must work without invoices; the invoice builder is recorded as a branch you choose on top of it. A system built the other way round cannot record the rent, the software subscriptions or the cash sale that never had an invoice, and its reports quietly leave them out.

The nine core features, with a test for each

The order follows the count in the table at the top.

1 · Income and expense ledger: 31 of 37

Decorative version: a list of invoices and a separate list of expenses. Real version: one ledger where every transaction, bank-imported or entered by hand, has a category, whether or not an invoice exists.

The test: record an expense with no invoice (a card payment for software, say), give it a category, and look for it in the profit and loss report. If it does not appear, the reports are built from invoices, not from the books.

2 · Organisation setup and fiscal settings: 30 of 37

Company details, currency, financial year, tax basis, invoice numbering, and the bank and cash accounts you hold.

Decorative version: a settings page that nothing else reads. Real version: settings that change behaviour: the financial year sets the report periods, and the tax basis changes what the reports count.

The test: change the financial year start and open the profit and loss report. The period should follow. If the report still runs January to December, the setting is decoration.

3 · Financial reports: 30 of 37

Profit and loss, cash flow, money owed to you and by you, where the money went.

Decorative version: charts of totals. Real version: reports calculated from the ledger, where every line can be traced to the transactions behind it. A balance sheet is only real if the system keeps double-entry books; a single-entry system that shows one is inventing it.

The test: pick a line on the profit and loss report and add up the transactions behind it by hand. Then ask whether the system is double-entry. If it is not and still offers a balance sheet, check that the balance sheet really balances.

4 · Invoice builder: 29 of 37

A branch, not a default, but the one most people picture first.

Decorative version: a nicely formatted PDF. Real version: line items, tax per line, discounts, a number, a due date, a status, and reminders, with totals calculated the same way every time.

The test: create an invoice with two tax rates and a discount, and check the total by hand. Then change the discount after sending and see what happens to the sent copy. An invoice that silently changes after it has been issued is a problem for your customer and your accountant.

5 · Customers and clients: 28 of 37

Decorative version: a contact list. Real version: a customer record that shows what they have been billed, what they have paid and what they still owe. Only needed when you invoice; a bookkeeping-only system can do without it.

The test: open a customer. Can you see their outstanding balance without running a report?

6 · Payments received and allocation: 28 of 37

Decorative version: a "paid" checkbox on the invoice. Real version: payments recorded against invoices, including part payments, whether the money came through a payment gateway or by bank transfer or cash.

The test: take a part payment on an invoice. The invoice should show the balance due, and the list of money owed to you should move by exactly the amount paid. If the invoice can only be paid or unpaid, the first client who pays in instalments will break your receivables.

7 · Document numbering and PDF templates: 27 of 37

Decorative version: a number that looks sequential. Real version: numbering stored in the system, never issued twice, even when two people create invoices at the same moment.

The test: open two browser tabs and create an invoice in each at the same time. They must get different numbers. Duplicate invoice numbers are the kind of error that is trivial to create and painful to explain.

8 · Bank and cash accounts: 26 of 37

Decorative version: a single balance figure. Real version: each bank and cash account has its own balance, built from its own transactions, which you can reconcile against the statement.

The test: compare the system's balance for one account with the latest bank statement. If they differ and there is no way to see why, you do not have reconciliation, you have a guess. Automatic bank feeds are a branch; the account itself is not.

9 · Dashboard: 25 of 37

Decorative version: metric cards and charts. Real version: every figure opens the records behind it.

The test: click the revenue figure on the dashboard. It should open the transactions that make it up. If it opens nothing, the dashboard is a picture of your finances, not a view of them.

Tests for the optional features

The seven optional features in the second table are not on the core list because each one brings its own data and its own ways to go wrong. If you choose one, test it as hard as the core:

• Bank feeds: import the same statement period twice. The second import should not create duplicate transactions, and every imported line should end up categorised or flagged as waiting.
• Multi-currency: issue an invoice in a foreign currency and record the payment at a different exchange rate. The difference should appear as an exchange gain or loss, not vanish.
• Payroll: run a trial pay run for one employee and check the deductions against your local rules, or with whoever runs payroll for you today. Payroll rules are country-specific, so a feature tick from another market tells you little.
• Inventory: sell more units than you hold. The system should warn, block or record negative stock in a way you can see. Then check that cost of goods sold moved.
• Projects: tag an expense to a project and open that project's profit. It should fall by exactly the expense.
• Recurring billing: schedule a monthly invoice, change the tax rate, and let the next one generate. It should get a fresh number and the current rate.
• Online payment collection: pay a test invoice through the gateway. The invoice should be marked paid, and the gateway fee should be recorded rather than quietly netted off the income.

The most important branch decision is the one above, bookkeeping first or invoicing first. The second most important is whether you need double-entry books. That decision is covered in depth in accounting in Excel, under the wall between single entry and double entry.

The requirements list you can hand someone

1. A ledger that records every transaction with a category, with or without an invoice.
2. Settings that drive behaviour: the financial year sets report periods, the tax basis changes what reports count.
3. Reports calculated from the ledger, every line traceable to its transactions. A balance sheet only if the books are double-entry.
4. [If invoicing] Invoices with line items, tax per line, discounts, numbering, status and reminders. A sent invoice is not silently changed.
5. [If invoicing] Customer records showing billed, paid and outstanding.
6. Payments recorded against invoices, including part payments, whatever the payment method.
7. Invoice and document numbers stored centrally and never issued twice.
8. Each bank and cash account has its own balance and can be reconciled against a statement.
9. Every dashboard figure opens the records behind it.
10. Branches chosen in writing: [bank feeds / multi-currency / recurring billing / payroll / inventory / projects].

Why AI-built accounting software misses these

Ask a coding agent for accounting software and it will build an invoice screen and a dashboard, because that is what accounting software looks like from the outside. The ledger underneath, the reports that trace back to it and the numbering that never repeats are invisible in a screenshot, so they are the parts it improvises.

The accounting build-off shows the pattern: seven builds, by three models. One shipped its profit and loss and balance sheet tabs as "coming soon" placeholders. Another was deliberately narrow: no chart of accounts, no general ledger, no balance sheet, no bank reconciliation. The first was repaired and the second was narrow by design, and both looked like accounting software on the first screen. You can sign into all of them on the accounting software demo page.

---

If you are still keeping the books in a spreadsheet, accounting in Excel shows how far that goes and where it stops, and free accounting software covers what free plans usually hold back. For how an accounting planner scopes a build before any code is written, see the 19 questions an accounting planner asks.

If you are pointing a coding agent at this, the Accounting & Invoicing planner is the specification we hand ours: this inventory, bookkeeping before invoicing, and the numbering and reporting rules written so they cannot be skipped.