Accounting PREVIEW
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. The Search box above the grid looks through every page of the chosen timeframe and account, by memo, account code or account name, and the count then shows how many lines match. Clear brings back the full list.
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.
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 and sortable, and shows Showing X–Y of N so you can tell at a glance how many entries the org holds. Search looks through every page by memo or by an account on the entry’s lines.
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.
Each line is a card, so the form fits a phone without scrolling sideways. Type part of an account name or code to pick it. While the entry doesn't balance, the form says by how much in each currency and Post Entry stays off. Posting adds the entry to the books right away, and a date in a closed month is refused.
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. Posted entries can't be deleted, which is what accountants and auditors expect.
To undo a manual entry, open it and click Reverse entry. RSA shows the lines the reversal will post, every debit and credit swapped on the same accounts, currencies and projects, and asks for the reversal date and a reason. Nothing is posted until you click Post reversal. The date can't be before the original entry or in a closed period or reconciled bank month; RSA refuses it rather than moving it to another day. Both entries stay in the books and can no longer be changed, each links to the other, the entry shows the reason and who posted the reversal, and an entry can only be reversed once. If the connection drops while you post, RSA shows an error and a Retry button that sends exactly the same reversal again; if the first attempt had already gone through, Retry opens that reversal instead of posting a second one.
An entry in a closed month can still be reversed into a later open month: the original and its bank reconciliation stay as they are, and RSA reminds you to review the reconciliation when the original had reconciled lines. Only the journal entry is posted: no refund, payment or message is sent.
Switch to RSA
Accounting → Switch to RSA is the one place to bring a company's books over from its old system. It is free on every plan. It replaces the old Wave Import page; old links to that page open Switch to RSA with Wave already chosen.
- Choose your old system. Pick Wave, or another system and type its name, for example QuickBooks Online, Xero or Sage 50.
- Choose how much to bring. Full history brings the general ledger, every transaction. Quick switch brings the trial balance on the cutover day, posted as one opening entry.
- Upload your export. Use a CSV or Excel (.xlsx) file, up to 20 MB and 100,000 rows. Wave's columns are read for you. For any other system, match the columns once: transaction, date, account name or number, debit and credit (or one signed amount), and the date order. RSA remembers your choices for the next file with the same columns.
- Match accounts and check the balances. Accounts are matched only by exact name or number, never guessed, and each one shows its balance on the cutover day. Confirm that these balances match your old system's trial balance before anything is written.
- Preview, then confirm. Every transaction must balance and every date must be readable, or nothing is posted. Bringing in the same file twice writes nothing twice.
A Quick switch file can be as simple as two columns: an account column and a balance column, in either order, under common names such as Account and Balance. A title row, a single column, or a row holding a date or an amount is not taken as the column names. Amounts written with a typographic minus sign or a dash (the longer kinds, not just the keyboard hyphen) are read as negative.
Entries brought from another system show the source Brought from your old system and the same history details as Wave entries.
Undoing an import
Every import is recorded and can be undone. Undo removes every entry that import wrote. It is refused while one of those entries is matched to a bank line, linked to the Wave invoices and bills history, or in a closed month. Accounts matched by an import stay fixed until that import is undone.
The first import sets one cutover day for the company, across every system, including earlier Wave imports. After that, an import with a different cutover, an entry dated after it, or mixing Full history with Quick switch is refused.
Importing history from Wave
Wave imports now go through Switch to RSA (above). The notes below describe how a Wave ledger import works and the Wave history pages that follow it. 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. Each reason names what is affected and the fix: the Wave accounts still to map, or the Wave transactions with errors, which you fix in Wave before exporting the general ledger again. 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.
The cutover date and import records
The import asks for the cutover: the last day your books came from Wave. Only entries dated on or before it are imported; later ones are left out and counted as such, so Wave history never lands beside your own RSA activity. The first recorded import fixes the cutover for the company, and a later import with a different date is refused. Once it is set, RSA also won't accept a Wave entry dated after it.
Each import is recorded as a batch that can't be changed afterwards: the file name and fingerprint, the cutover, how many transactions the file held, how many entries were written, skipped as already imported or left out for being after the cutover, and the debits and credits written. Importing the same file again writes nothing and adds no record. Entries imported before these records existed are left as they are.
A Wave journal entry's page now shows where it came from: its Wave transaction, the import file (name, fingerprint, date and cutover, or a note that it came before import records), the Wave documents it raised or settled, and any bank line matched to it.
Check the switch (migration tie-out)
Accounting → Switch to RSA → Check the switch is a read-only page that shows where your move from your old system stands, and it now covers imports from any system. It lists the company's cutover, every recorded import (earlier Wave imports stay listed) and checks for overlap, for example Wave entries dated after the cutover and your own RSA entries on or before it.
It also ties out your Accounts Receivable and Accounts Payable at the cutover against the invoices and bills still open that day, customer by customer and vendor by vendor. These come from RSA's own documents, the Wave invoices and bills register, and the historical register. A ledger line counts toward a customer or vendor only when it is linked to them through the invoice, bill or payment that posted it, a historical register line, or a Wave document or settlement linked to its journal entry. Lines with no such link appear in their own Not linked row and are never guessed. Before the company's first recorded import, you can pick a day to see the tie-out for it.
Wave invoices and bills (history only)
Accounting → Switch to RSA → Wave invoices and bills rebuilds the invoices and bills behind a ledger you have already imported, so you can see them in a read-only register. Use the same accounting.csv as the ledger import and enter a cutoff date; documents up to and including that date are included. You need View on Historical records to preview, Add on Historical records to save, and View on Journal Entries.
- Choose the file and cutoff date. RSA finds invoices (lines with an invoice number) and bills (lines with a bill number, with the vendor), plus the payments and other settlements the ledger links to them.
- Confirm your accounts. The preview lists every Wave account those journals use. For each one, pick the RSA account you mapped it to; what the journals show is only a hint. A Wave account without a confirmed account can't be checked, and the save is refused. Your confirmation is kept for the company, so later saves are checked against it and can't change it.
- Preview, then save. The preview shows counts and totals by type. Saving adds the documents to the register with Wave's transaction IDs, dates, party, memo, sales tax and the dates Wave added and changed each transaction.
Before anything is saved, RSA checks that the file's ledger is valid (every transaction balanced, real dates) and that each document and settlement matches exactly one imported journal entry: same company, date, debit and credit lines, currency and confirmed accounts. If any journal is missing, duplicated, incomplete or different, the whole save is refused and nothing is written.
- Nothing is posted. No journal entry, invoice, bill, payment, customer or vendor is created or changed. The register does not add closed-period, reconciled-month or protected-journal protection to any journal; those stay on the journals themselves.
- Safe to run again. A rerun adds only what is new, and two saves at the same moment can't both add the same record.
- One document per Wave transaction. If a re-export would read a transaction as a different document (for example a corrected invoice number or vendor spelling) or now raises a different set of documents, RSA refuses it as a conflict rather than saving a second one. Documents raised by one transaction are saved together.
- Several documents in one transaction. Lines are split between the documents only when every line carries one of their numbers and each document's lines add up to its total. Otherwise each document keeps its total but shows no lines or tax figure, and is marked Needs review with the reason. A single document whose lines don't add up to its total is an error and is left out.
- Lines are summaries from the ledger, not the original invoice or bill lines: the ledger may combine quantity, price and sales tax into one amount. Keep the original documents in Historical entry.
- Document state describes what the ledger links show: settled, partly settled, settled for more than the total, or no linked settlement found. It never says paid or unpaid. Ledger movements with no document number are flagged and not linked to any document.
A page for each Wave invoice and bill
In Wave invoices and bills, select a document number to open its own page. It shows the Wave total, the tax, the settlements found in the ledger and the summary lines from Wave. The record carries a GL-derived label, meaning it was rebuilt from the Wave general ledger; it keeps that label even after you attach evidence. A Wave journal entry's page now links to each document it raised or settled.
Attach the original and type its lines
If you have Add on Historical records, you can attach the original invoice or bill on the document's page and type in its lines.
- Attach the original. Upload a PDF, PNG or JPG. The file is scanned, stored privately and fingerprinted. Attaching the same file again doesn't create a duplicate.
- Type its lines. Enter each line as an item, discount, tax, tip or fee. The kind is the one you choose, never guessed from the description: a line described as "Stripe fee" that you enter as an item stays an item.
- Check the totals. The lines must add up to the Wave total, to the cent. When Wave recorded tax, the tax lines must add up to the Wave tax as well. The screen shows any difference, and if the totals don't match, nothing is saved and you are told the difference.
If attaching fails, the form keeps your file and your typed lines and tells you why: the file could not be stored, the virus check is busy (try again in a moment) or refused the file, the save was refused, or there is no connection to RSA. The form clears only once RSA confirms the evidence is attached.
Attaching evidence is a record only: nothing is posted, and the GL-derived record doesn't change. Saved evidence can't be edited or removed afterwards.
Historical entry
Journal Entries → Historical entry lets accounting staff rebuild the invoice history behind journals they have already reviewed, for example when moving from another system. It needs View on both Journal Entries and Invoices to see, Add to record and Edit to correct.
- Choose the journal month and review its entries.
- Record each original invoice with its customer, original number, issue and due dates, amount and source reference, and pick the reviewed Accounts Receivable debit it belongs to. An unpaid balance carried into an opening-balance entry is recorded as an opening unpaid receivable with its original date, without counting the income again.
- Keep the original invoice or proof as a private PDF, PNG or JPG; RSA keeps the file unchanged with its SHA-256 fingerprint.
- Link each payment to the receivable credit and the bank, processor clearing or customer-credit debit of the same reviewed entry. Allocations can't exceed the invoice or the journal lines.
The register is for your books only: it never posts journal entries, creates active invoices or payments, sends emails or reminders, or appears in the customer portal or online payments.
Correcting a historical record
Open Correct this invoice (or settlement) to change its details, cancel it or restore a cancelled one. Give a reason, optionally pick the source files that support it, and click Review correction: RSA shows exactly what will change, and Confirm correction saves that and nothing else. If someone changed the record meanwhile, RSA asks you to review again.
- The record keeps its identity, source reference and original reviewer. Correction history lists every change with its reason, who made it and the files it relied on, separately from who first recorded it.
- An invoice with active payments can't be cancelled or moved to another customer. Cancel or move the payments first, correct the invoice, then restore them.
- Corrections follow closed periods and reconciled bank months for both the old and the new dates; reopening the books is a separate step.
- Cancelling keeps the record and its files, marked Cancelled. The journal entry does not change, so the amount no longer allocated appears under Reconciliation holds until you relink it or record a reviewed journal entry. It is not a refund or write-off.
- A record shows Evidence hold until a correction links its current version to a kept source file.
- A journal entry that a historical record relies on can't be reversed until that link is cancelled.
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.