# How to use a Righthand with Wave

Prepare a Wave invoice review with business and invoice identities, due dates, status, amounts, and clearly separated send evidence.

By Righthand Team · 2026-10-10

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-wave

## Review invoices within the correct business

Use Righthand with Wave to prepare an invoice exception worksheet for the business owner or bookkeeper. The useful output identifies missing references, uncertain balances, and follow-up questions. It should not create invoices, record payments, or send reminders solely to make the receivables list appear current.

Wave's [API reference](https://developer.waveapps.com/hc/en-us/articles/360019968212-API-Reference) describes business-scoped invoices, statuses, due dates, and reporting filters. Preserve business and invoice identity. Searching a partial invoice number can return several records, so the displayed number should not be the only matching key.

## Choose a concrete read route

Give the business, approved invoice list or date window, report snapshot, currency, and comparison notes. For an illustrative overdue review, the bookkeeper can supply invoice data and approved payment confirmations while retaining control over ledger changes.

Inspect Wave's actual tools in [integrations](/integrations). If invoice reads are unavailable, use an approved export or browser review. Provider capabilities such as invoice sending do not establish native availability or owner authorization in the selected Righthand connection.

## A worked first-run request

> At 10 AM America/Los_Angeles on Monday, review the approved Wave invoice list for the named business as of the supplied date. Produce a private worksheet with business and invoice identity, invoice number, customer reference, due date, status, currency, amount due, and available payment-note match. Keep credits and unusual balances visible. Do not send, create, modify, or mark invoices paid. Deliver to me for bookkeeper review and reconcile the list filters, pages, and currency totals.

This example is illustrative. The bookkeeper supplies the policy for overdue classification and any accounting treatment. A customer email saying “paid” is evidence to investigate, not permission to record a payment.

## Define the expected worksheet

An example entry might say: “Invoice marked partial; outstanding amount present; payment confirmation refers to a similar invoice number; exact match unresolved.” The assistant should preserve both references and ask the bookkeeper to confirm allocation.

Keep invoice status separate from send method or communication evidence when those are supplied. A record marked sent does not prove that a customer received or read an email. A draft invoice can exist without being part of the owner's active collection queue.

## Reconcile fresh evidence before follow-up

On repeat runs, match exact invoice identities and refresh balances. A payment received after the snapshot can resolve a proposed reminder. Do not retain a stale overdue conclusion after updated evidence arrives.

Permissions, partial matching, and incomplete report pages should remain visible. If supported ledger or communication changes are later authorized, independently retrieve the resulting invoice or message evidence. An exported worksheet itself does not alter Wave.

Set authority through [Righthand connection permissions](https://docs.righthand.ai/guides/add-a-connection). Check [pricing](/pricing) for recurring receivables preparation and retain the bookkeeper as the financial decision owner.