Accounting

Transactions

Accounting → Transactions lists journal lines across all accounts, newest first. Each row displays the date, description, account, whether the line is a debit or credit, and the amount. This is a read-only ledger view — to create or edit entries, use Journal Entries.

The list is paged: it shows Showing X–Y of N with Previous and Next controls, so the full count is always visible and older lines stay reachable. Sort by any column heading, and narrow the rows with the filter box above the grid.

Use this screen as a quick audit trail to verify that a specific charge or payment was posted correctly.

Chart of Accounts

Accounting → Chart of Accounts lists every account in your organization in a single sortable, filterable grid. Every account has one of five types:

Asset — things your business owns: bank accounts, accounts receivable, equipment.
Liability — amounts your business owes: accounts payable, loans, payroll tax liability.
Equity — the owners' stake: retained earnings, owner contributions.
Revenue — income earned: sales, service fees, interest income.
Expense — costs incurred: rent, salaries, utilities, cost of goods sold.

Each account has a numeric code (used for ordering and display), a name, and a type. To add an account, click Add Account, fill in the code and name, and choose a type.

Account codes are free-form. A common convention is 1xxx = Assets, 2xxx = Liabilities, 3xxx = Equity, 4xxx = Revenue, 5xxx–6xxx = Expenses.

Journal Entries

Accounting → Journal Entries is where you record manual accounting entries. Every entry must balance: the sum of all debit lines must equal the sum of all credit lines.

Like Transactions, this list is paged, sortable, and filterable, and shows Showing X–Y of N so you can tell at a glance how many entries the org holds.

To create a journal entry:

Click New Journal Entry.
Set the date and optional memo (appears in transaction history and reports).
Add at least two lines. For each line, choose an account, set the type to Debit or Credit, and enter the amount.
Click Save. RSA will warn you if the entry does not balance.

Common examples:

Record a loan received — Debit Cash (Asset), Credit Loan Payable (Liability).
Record depreciation — Debit Depreciation Expense, Credit Accumulated Depreciation.
Record an owner draw — Debit Owner's Draw (Equity), Credit Cash.

Click any entry, whether manual or system-generated, to open its detail page — it shows every line's account, debit/credit amount, and a per-currency balance check. Manual entries can be deleted from here; system-generated ones cannot.

Journal entries created automatically by payroll, invoice approvals and payments, bill approvals and payments, and bank reconciliation are labelled with their source and cannot be deleted.

Importing history from Wave

Accounting → Wave import brings an existing Wave general ledger into RSA, so your history comes with you instead of starting from an empty set of books. A paid Wave plan isn't needed — the Wave Connect add-on for Google Sheets exports the same data as CSV on the free tier.

Export accounting.csv from Wave, then work through four steps:

Upload — select the exported accounting.csv.
Map accounts — match each Wave account to one in your chart of accounts. RSA suggests matches only where the names line up exactly; anything it can't place with certainty is left for you to map by hand rather than guessed at, since posting to the wrong account is far more work to unpick than mapping a few by hand.
Preview — see exactly what would be written, before anything is.
Confirm — write the entries.

Confirm stays blocked while any account is unmapped or any validation error stands, and the preview lists the specific reasons rather than just showing an empty plan. This is deliberate: a partly-imported ledger is worse than none, because the books are then wrong in a way that is hard to see.

When the import finishes, the result screen reports a reconciliation — expected versus actual debits, credits, and entry counts — not just a number of rows written. Matching row counts prove nothing; matching money does. If the figures don't reconcile, the screen says so plainly: treat the import as unfinished and investigate before carrying on.

The import is safe to run again. Every imported entry is tagged with the Wave transaction it came from, so a second run writes only what is missing — which is what makes an interrupted import recoverable. Transactions that are already in are counted and greyed out in the preview, so you can see what a re-run would and wouldn't do before you commit to it.

Wave's general ledger already contains the entries its own invoices and bills generated, so RSA imports the ledger as it stands and does not re-post journal entries from those documents. Otherwise every transaction would be booked twice.

Recurring entries

Journal Entries don't have a built-in recurring schedule — each one is entered manually. For amounts that repeat on a fixed schedule, use Recurring Invoices for invoice-related revenue or Recurring Expenses for bills and expenses; RSA posts those automatically on the configured schedule. For recurring entries that aren't tied to an invoice or expense (e.g. monthly depreciation), you'll need to create the journal entry manually each period.