ERP

Wave

< Back to All Connectors
Connect your AI to Wave
Small-business owners, bookkeepers and accountants, and finance and operations managers run invoicing and bookkeeping through Wave, but the answers they need sit across invoices, payments, estimates and customers that each live on their own screen. AI can pull those together in seconds, but only if access stays read-only and limited to the Wave companies the user is permitted to see, and customer payment details and contact data are shown no further than the question needs.

‍

Start a Trial
Get a Live Demo

Why it matters

Capabilities that matter most for Wave

01

Eleven Wave lists, read in plain words

Customers, vendors, invoices, invoice lines, invoice payments, estimates, estimate lines, estimate deposits, products, product default taxes and accounts are each available to your AI client as a read-only tool.
02

Ready-made bookkeeping reviews

App store prompts cover overdue invoices, open estimates, payment reconciliation, sales by product and chart of accounts, product and contact clean-up, each limited to reading.
03

Wave checked against the systems around it

Prompts compare Wave with Stripe, Shopify, WooCommerce, BigCommerce, Chargebee, Mailchimp, Constant Contact, Avalara AvaTax, Ramp and 2Checkout, so missing customers, orders and payments surface without a spreadsheet.
03

Scoped to the companies you can see

Questions run against the Wave company the user is permitted to use, and the AI is told to show only the customer contact and payment details the question needs.

Use cases

Example AI Use Cases for Wave

Filters

scenario

-

Chart-of-accounts clutter builds up over years. Finding duplicate names, unused accounts and mis-typed ones in Wave means scrolling the whole list and judging each account by eye. An account with an odd balance sign or a clashing account number is easy to miss until a report looks wrong.

What popdock provides

--

Name the company if you have more than one, and optionally an account type to focus on. It reads the active accounts in Wave and checks for duplicate or near-duplicate names, zero-balance accounts that look unused, balances that disagree with the normal balance type, missing or shared account numbers and subtypes that do not fit the name. Findings are grouped by check, each with a suggested action and counts. Nothing is changed or archived; suggestions are text only.

Business outcome

---

A clear list of accounts to merge, rename or review, produced from a read-only pass that changes nothing in Wave.
See Full Use Case

scenario

-

Duplicate and incomplete contacts in Wave cause invoices to go to the wrong place and leave gaps that block collections. Spotting near-duplicate names, missing emails or missing countries means paging through the customer and vendor lists by eye.

What popdock provides

--

Say whether to audit customers, vendors or both, and name the company if you have more than one. It reads the active records in Wave and flags missing or shared emails, near-duplicate names, and missing country, city or currency. For customers it also flags accounts with an outstanding balance and no email, since those cannot be chased. For duplicates it shows the pair side by side and says which looks like the keeper. It only reads, never suggests deleting a customer who owes money, and shows only the name and the failing field.

Business outcome

---

Contact data problems are found and ranked in one read-only pass, so invoices and reminders reach the right people.
See Full Use Case

scenario

-

Missing prices, income accounts or default taxes on products in Wave only show up when an invoice comes out wrong. Checking the catalog by hand means opening product after product and cross-checking each against its tax settings.

What popdock provides

--

Optionally give part of a product name and the company. It reads the active products in Wave and their default sales taxes, then flags sold products with no price or no income account, bought products with no expense account, sold products with no default sales tax, duplicate names and products neither sold nor bought. You get a table per issue with counts, and differing tax rates between similar products are mentioned. Tax gaps are labelled as checks, not errors, and nothing in the catalog is changed.

Business outcome

---

Catalog gaps are found before they reach an invoice, from a read-only review that leaves the catalog untouched.
See Full Use Case

scenario

-

Customers who are overdue in Wave can still be on the Mailchimp mailing list, so someone in collections gets a promotional email by accident. Nobody cross-checks the two, because it means taking each overdue customer's email and searching for it in Mailchimp one by one.

What popdock provides

--

Give a minimum overdue amount, and optionally how many customers to check. It lists the Wave customers with overdue balances, then looks each one up in Mailchimp by email and records their status in every audience. You get a table sorted by overdue amount, with the subscribed customers listed separately as the ones to consider holding back from promotions. Customers with no email are skipped and counted, customers not found are marked as not in Mailchimp, and nothing is changed in either system.

Business outcome

---

Overdue customers who are still subscribed are found before the next campaign goes out, with no changes made in Wave or Mailchimp.
See Full Use Case

scenario

-

Owners cannot easily see whether customers who owe money sit in places where the business has registered tax nexus. Answering means exporting customer addresses from Wave, pulling the nexus list from Avalara AvaTax and matching region names to codes by hand.

What popdock provides

--

Give a minimum outstanding balance. It reads active Wave customers who owe at least that amount, then reads the current nexus from Avalara AvaTax and ignores any that have ended. It matches each customer's country and region to a nexus place, handling names against codes and noting any it had to guess. You get customers in places with no nexus grouped by country and region with total balances, the regions that do have nexus, and the biggest gaps. Customers with no region are listed as unknown. It is a data comparison, not tax advice, and nothing is changed.

Business outcome

---

Owners see which balances sit outside registered nexus places in one read-only comparison, ready to take to their tax adviser.
See Full Use Case

scenario

-

Before year-end, bookkeepers hand-check which paid vendors lack a taxpayer id in the tax system. That means taking each vendor from Wave and searching for it in Avalara AvaTax by email, name or code, so gaps are found too late.

What popdock provides

--

Optionally give part of a vendor name. It reads the active vendors in Wave, then looks each one up in Avalara AvaTax by email, then name, then vendor code, and checks whether a taxpayer id is on file. You get a table grouped as ready, in AvaTax with no taxpayer id and not in AvaTax, with counts and the most urgent vendors first (those with a recent transaction). A name match with a different email is listed as a possible match. It never prints a taxpayer id value, and no vendor is created or changed.

Business outcome

---

Vendors missing a taxpayer id are found early and ranked by urgency, without exposing any ids or changing a record.
See Full Use Case

scenario

-

Checking whether a customer is in good standing means finding them in Stripe, finding them again in Wave, and comparing contact details and amounts owed by eye. It is easy to compare the wrong record, or to compare balances in different currencies.

What popdock provides

--

Give the customer's email, and the company if you have more than one Wave business. It finds the customer in Stripe by email and totals their open invoices, then finds the same email in Wave and reads their outstanding and overdue amounts. You get a side-by-side table of name, phone, currency, amount owed and overdue or delinquent flag with a match or mismatch for each, and the differences that need a person. It stops if several customers match or one side is missing, compares amounts only in the same currency, and changes nothing.

Business outcome

---

You know in minutes whether a customer is in good standing in both systems, with every difference listed and nothing changed.
See Full Use Case

scenario

-

Checking whether a customer's details match in the shop and the books means opening BigCommerce, then Wave, and comparing name, phone and company by eye. Mismatches go unnoticed until an invoice or an order goes to the wrong person.

What popdock provides

--

Give the customer's email, and the company if you have more than one Wave business. It finds the customer in BigCommerce by email, then the same customer in Wave, and compares name, phone and company details, ignoring case, spacing and phone punctuation. You get a table of each field with the BigCommerce value, the Wave value and match or differ, plus the amount outstanding and overdue in Wave and the BigCommerce customer id. It stops and lists the matches if there are several, reports a one-sided record, and changes nothing in either system.

Business outcome

---

Mismatched customer details between the shop and the books are found in one question, with no changes made to either record.
See Full Use Case

scenario

-

Plans and prices live in Chargebee while Wave keeps its own product list, and the two drift apart over time. Comparing them means exporting both, lining up names and checking prices by hand, and the differences show up as invoices with the wrong item names or prices.

What popdock provides

--

Optionally give part of a name to focus on. It reads the active item prices in Chargebee and the active products in Wave, matches them by name ignoring case and extra spaces, and reports items with the same name and price, the same name but a different price, items only in Chargebee and items only in Wave. If every difference is a factor of 100 it says Chargebee may store prices in minor units. It never compares prices in different currencies, lists several Wave products with the same name together, and does not change either catalog.

Business outcome

---

Price and naming drift between Chargebee and Wave is found before it reaches an invoice, from a read-only comparison.
See Full Use Case

scenario

-

Quotes sent from Chargebee and estimates sent from Wave often describe the same deals. Sales cannot tell which customer has been quoted twice, or has an offer in only one system, without lining up two exports by customer name and total.

What popdock provides

--

Give a start date (it defaults to 90 days ago) and optionally one customer. It reads the Chargebee quotes and looks up each customer's name and email, then reads the Wave estimates for the same period. It matches them on customer and an equal total, and reports matched pairs with both statuses, status conflicts such as accepted in one and open in the other, quotes only in Chargebee, estimates only in Wave and likely duplicates. Near-matches are listed as possible and never merged. It only reads and creates or changes no quotes or estimates.

Business outcome

---

Duplicate offers, one-sided quotes and status conflicts across Chargebee and Wave are found in one read-only comparison.
See Full Use Case

scenario

-

When the spend system's accounting codes drift from the books chart of accounts, spend gets coded to the wrong or missing accounts and nobody notices until close. Checking means exporting Ramp GL accounts and Wave accounts and matching them by code, then by name, by hand.

What popdock provides

--

Optionally give part of an account name and the Wave company. It reads the GL accounts in Ramp and the active accounts in Wave, matches Ramp codes to Wave account numbers first and then names, and marks a conflict when the code matches but the name differs or the reverse. You get matched accounts, conflicts side by side, Ramp accounts with no Wave account, Wave accounts with no Ramp account and counts, noting if a read hit the record cap. Equity accounts are not listed as missing, it stops if Ramp has no GL accounts, and nothing is changed.

Business outcome

---

Mismatched and missing accounts between Ramp and Wave are found before close, so spend is coded to the right place.
See Full Use Case

scenario

-

Keeping the shop catalog and the books product list in step is a manual comparison. Missing items and price differences between BigCommerce and Wave linger because lining up two long lists by name and sku takes time nobody has.

What popdock provides

--

Optionally give part of a product name and the Wave company. It reads the active products in Wave and the BigCommerce catalog, and checks the BigCommerce store currency so prices are only compared when the currencies can be confirmed as the same. It matches by name ignoring case and extra spaces, and also when a Wave name contains a BigCommerce sku exactly. You get products only in Wave, only in BigCommerce and matched with different prices, with counts. If results are truncated it says the comparison is partial, and it changes nothing in either system.

Business outcome

---

Gaps and price differences between the shop and the books are found in one pass, with no changes made to either catalog.
See Full Use Case

scenario

-

Checking that the vendors in the books are also set up in the spend system means comparing two vendor lists by hand. Duplicates, missing vendors and mismatched contact emails linger because names rarely match exactly between Wave and Ramp.

What popdock provides

--

Optionally give part of a vendor name and the Wave company. It reads the active vendors in Wave and the vendors in Ramp, matches by name after ignoring case, punctuation and endings like Inc or LLC, and checks the Ramp contact email for matched pairs. You get vendors in both systems with email match and Ramp spend for the last 365 days, vendors only in Wave and vendors only in Ramp, with counts. Near-matches are listed as possible instead of decided, spend is never added across currencies, a record cap is flagged and nothing is changed.

Business outcome

---

Vendor gaps and duplicates between Wave and Ramp are listed in one read-only pass, with near-matches left for you to decide.
See Full Use Case

scenario

-

The shop catalog in WooCommerce and the invoicing product list in Wave drift apart, and nobody notices until an invoice uses the wrong price. Comparing them means exporting both lists and lining up names and prices by hand.

What popdock provides

--

Optionally give part of a product name and the Wave company. It reads the active products in Wave and the products in WooCommerce, matches them by exact name ignoring case and extra spaces, and compares the Wave unit price with the WooCommerce regular price. You get products only in WooCommerce, only in Wave and with different prices, with the gap and counts, and a note if either read hit its limit. Draft WooCommerce products are skipped and counted, there is no fuzzy matching, and nothing is changed in either system.

Business outcome

---

Catalog gaps and price differences between WooCommerce and Wave are found before they reach an invoice, from a read-only comparison.
See Full Use Case

scenario

-

Before calling someone who clicked a campaign link, you want to know whether they owe you money. That means exporting the clicks from Constant Contact, then looking up each person in Wave to see balances and unpaid invoices. Skip it and a warm lead gets a sales pitch while an overdue invoice sits unmentioned.

What popdock provides

--

Give a Constant Contact campaign and a Wave company, and it reads who clicked and which links, grouped by email. Each email is looked up in Wave for the customer's outstanding and overdue balance, and unpaid invoices are listed with number, due date and amount. Contacts with no Wave customer are shown separately, a name that matches more than one customer is listed rather than guessed, and currencies are never mixed in totals. It only reads, so nothing changes in either system.

Business outcome

---

Sales follows up warm clickers knowing who has unpaid invoices, so each call starts with the right conversation and no surprises.
See Full Use Case

scenario

-

A customer pays a Stripe invoice, but the matching invoice in Wave can stay open because nobody recorded the payment. Finding those means exporting paid Stripe invoices and looking each one up in Wave by invoice number or by customer and amount, and the gap is often noticed only when the books are reviewed.

What popdock provides

--

Give a start date and a Wave company, and it reads the Stripe invoices paid since then. Each is found in Wave by invoice number, or by customer name and amount when the number does not match, and those Wave still shows as owing are listed with both amounts and the gap. Stripe invoices with no Wave invoice are labelled separately, with the unrecorded total per currency. A name that fits more than one invoice is listed rather than guessed, currency mismatches are flagged, and nothing is changed in either system.

Business outcome

---

Paid Stripe invoices still open in Wave are found and totalled per currency before the books are reviewed, with nothing changed.
See Full Use Case

scenario

-

To thank recent customers or offer them an upsell, you need to know who just paid and whether they are on your mailing list. That means pulling payments from Wave, finding each customer's email, then checking their status in Mailchimp, and it is easy to mail someone who unsubscribed.

What popdock provides

--

Give a start date, or use the last 30 days, and it reads the Wave invoice payments since then, grouped and totalled by customer. Each customer is resolved to exactly one Wave record to get their email, then checked in Mailchimp for subscription status and open rate. The report ranks customers by total paid and separates subscribed candidates, unsubscribed or cleaned contacts to leave alone, people not in Mailchimp and customers it could not resolve. It only reads, so nothing changes in either system.

Business outcome

---

Sales and marketing know who paid recently and is safe to mail, with do-not-mail contacts kept apart and nothing changed.
See Full Use Case

scenario

-

Store sales have to reach the books, either keyed in or synced, and the only way to find the orders that were missed is to compare the Shopify order list with the Wave invoices line by line. Cancelled and unpaid orders muddy the comparison, so real gaps hide among the noise.

What popdock provides

--

Give a date range, or use the last 30 days, and a Wave company, and it reads the Shopify orders and the Wave invoices for the period. Orders are matched to invoices by purchase order number, with a second pass on customer and total that is marked possible match only. The report gives counts, the unmatched orders by value, cancelled and unpaid orders under their own headings and the unmatched total. It warns when a read hits 500 rows and never creates an invoice, so nothing is changed.

Business outcome

---

Shopify orders that never reached Wave are found and totalled, with cancelled and unpaid orders kept apart and no invoices created.
See Full Use Case

scenario

-

Keeping the mailing audience in step with your customers means comparing the Wave customer list with the Mailchimp audience row by row. It is slow, and customers get missed, so some never hear from you while others are left out because they unsubscribed and nobody can tell which is which.

What popdock provides

--

Name a Mailchimp audience, and it confirms exactly one audience matches before going further. It then reads active Wave customers, up to the number you set (50 by default), and checks each email in that audience, ignoring case. The report lists customers missing, customers present but unsubscribed or cleaned, and customers with no email, with counts and the audience size. It never suggests re-adding anyone who unsubscribed, warns when the list may be truncated and only reads.

Business outcome

---

Marketing sees which Wave customers are missing from an audience, with opted-out people left alone and nothing changed in either system.
See Full Use Case

scenario

-

Customers added in Wave are not copied into Avalara AvaTax automatically, so sales to them may be taxed without a customer record. Finding the gaps means looking up each Wave customer in AvaTax by email, then by name, then by code, and judging near matches by eye.

What popdock provides

--

Optionally give part of a name and a limit (all active customers, up to 100, by default). It reads the Wave customers, then looks each one up in Avalara AvaTax by email, then by name, then by customer code. The report shows customers found in both, noting where region or country differ, and customers missing from AvaTax with email, region and outstanding amount, largest first. A name match with a different email is listed as a possible match, not counted as found. It only reads, so no customer is created or changed.

Business outcome

---

Finance sees which Wave customers have no AvaTax record, largest balance first, so gaps are fixed before sales are taxed without one.
See Full Use Case

scenario

-

A business can owe you money and be paid by you at the same time, but with Wave and Ramp separate, nobody sees both sides. Spotting the overlap means taking each Wave customer with a balance and searching Ramp for a vendor with the same name.

What popdock provides

--

Optionally give a Wave company and a minimum outstanding amount (1 by default). It reads Wave customers with a balance, then looks each name up in Ramp as a vendor, trying a contains search if there is no exact match. It checks at most 40 names, largest balance first, and says how many it skipped. The report shows owed and overdue amounts beside Ramp spend over the last 365 days, marks name-contains matches as possible, never compares across currencies and does not suggest netting. It only reads.

Business outcome

---

Leaders see which customers are also vendors, with what they owe against what you spend, and nothing is changed or netted.
See Full Use Case

scenario

-

Shop customers who never made it into the books are hard to spot, because it means comparing the BigCommerce customer list with the Wave customer list by hand. Invoices then get raised late, or not at all, for people who never reached Wave.

What popdock provides

--

Give a start date for new BigCommerce customers and optionally a Wave company. It reads the customers created since then, up to 200, and looks each email up in Wave. Customers with no match are listed with BigCommerce id, name, email and date created, followed by counts checked, matched and missing. It checks at most 40, the newest first, and says how many it did not check. Customers without an email are listed separately, truncation is called out and nothing is created in Wave.

Business outcome

---

Shop customers missing from Wave are found by email, with unchecked and email-less customers called out and nothing created.
See Full Use Case

scenario

-

Products sold in Wave may have no item or tax code in Avalara AvaTax, and nobody notices until tax comes out wrong. Checking means taking each product, finding its AvaTax item, then looking up the tax code to see whether it is set and still active.

What popdock provides

--

Optionally give part of a product name. It reads the Wave products that are sold and not archived, then finds each one's Avalara AvaTax item by item code, falling back to the description. For each distinct tax code it fetches the description and whether it is active. The report shows each product as mapped, item without tax code, tax code inactive or no AvaTax item, with counts and the highest unit price first to fix. Description only matches are marked possible, and nothing is added or changed.

Business outcome

---

Products with no AvaTax item, no tax code or an inactive code are found, highest price first, before wrong tax shows up on a sale.
See Full Use Case

scenario

-

Month-end matching of shop orders to invoices is usually done in spreadsheets. Orders without invoices, invoices with a different total and invoices with no order slip through, and cancelled orders and mixed currencies make the totals unreliable.

What popdock provides

--

Give a date range and optionally a Wave company. It reads BigCommerce orders and Wave invoices for the range, ignoring cancelled and incomplete orders and saying how many. Orders are matched by purchase order number equal to the order id, then by customer name and equal total, and a name only match is shown as a total mismatch. The report lists orders with no invoice, matched orders with different totals and the difference, and invoices with no order. Currencies are never added or compared, partial results are flagged and nothing is written.

Business outcome

---

Orders without invoices, wrong totals and orphan invoices are found for the period, with no currency mixing and nothing changed.
See Full Use Case

scenario

-

The accounting customer list and the email list rarely agree. Matching them by hand means two exports and a lot of scrolling, which misses people and leaves gaps nobody sees, such as paying customers who are not on the email list at all.

What popdock provides

--

Give a Wave company and optionally how many customers to check (100 by default). It reads active Wave customers, sets aside those with no email, and looks each email up in Constant Contact, ignoring case. The report gives three tables: matched customers with their permission to send, Wave customers missing from Constant Contact with their outstanding amount, and customers with no email, plus counts. If one email returns several contacts they are all listed, truncation is flagged and it only reads, so nothing changes in either system.

Business outcome

---

Marketing sees which Wave customers are missing from Constant Contact, with permission status and balances shown and nothing changed.
See Full Use Case

scenario

-

Checking that every store order has an invoice means lining up two exports by eye. Orders with no invoice or a wrong total slip through, and a loose guess at a match can pair the wrong order with the wrong invoice.

What popdock provides

--

Give a start date and optionally an order status (completed by default) and a Wave company. It reads the WooCommerce orders and the Wave invoices since then. An order matches an invoice when its number appears in the invoice PO number, invoice number or memo. Without one, it accepts a match only when customer name, total and a date within 3 days all agree, labelled weak. The report shows each pair with the difference, then orders with no invoice and invoices with no order. Currencies are never compared, several candidates are listed, and it only reads.

Business outcome

---

Store orders with no invoice or a different total are found, with weak matches labelled and nothing guessed or changed.
See Full Use Case

scenario

-

Month-end matching of 2Checkout orders to Wave payments is done in spreadsheets. Missing payments, duplicates and amount differences slip through, and test orders, refunds and mixed currencies make the totals hard to trust.

What popdock provides

--

Give a period and optionally a currency, and it reads the 2Checkout orders and the Wave invoice payments for those dates, leaving out test orders. Orders are matched to payments by reference number in the memo or confirmation code, or by amount, currency, name and date within 3 days, and each match is labelled. The report shows matched items, orders with no Wave payment, payments with no order and amount mismatches, with counts and totals per currency. Refunded and cancelled orders get their own list, and it only reads.

Business outcome

---

Matched, missing and mismatched payments are found for the period per currency, with refunds and test orders kept apart and nothing changed.
See Full Use Case

scenario

-

Subscription invoices raised in Chargebee are supposed to appear in the Wave books. Finding the ones that are missing, or that differ in amount, means opening both systems for a customer and comparing two exports by hand, and several similar invoices make it easy to pair the wrong ones.

What popdock provides

--

Give a customer by email or Chargebee id, and optionally a date range (the last 90 days by default). It finds the customer in Chargebee, stopping to list them if more than one matches, then reads their Chargebee invoices and the Wave invoices for the same period. Invoices are matched by PO number, or by the same total within 1 day. It reports matched with equal totals, matched with different totals or paid amounts, in Chargebee only and in Wave only, with each difference. Several candidates are listed, currency differences are reported and nothing is written to Wave.

Business outcome

---

Missing and mismatched subscription invoices for a customer are found, with candidates listed instead of guessed and nothing written to Wave.
See Full Use Case

scenario

-

At month end, cash collected through Chargebee has to be recorded as invoice payments in Wave. Someone exports the successful Chargebee transactions, opens the Wave payments and ticks them off by amount and date. A payment that was never recorded, or recorded twice, only comes to light when the bank balance does not agree.

What popdock provides

--

Give a date range (the last 30 days by default) and optionally one Chargebee customer. It reads the successful Chargebee payments, then the Wave invoice payments for the same period with a few days of slack on each side. Each payment is matched on amount and a date within 3 days, and where several fit it prefers the one with the matching customer name. You get the matched payments, the Chargebee payments not recorded in Wave and the Wave payments not in Chargebee, with totals. It only reads, so nothing in Wave is recorded, changed or deleted.

Business outcome

---

Missing and unmatched payments surface before the bank reconciliation, with nothing in Wave changed to get there.
See Full Use Case

scenario

-

Matching Stripe charges to Wave payments means exporting both lists each month and ticking them off by hand. Amounts in Stripe may be in minor units, refunds change the net figure, and a receipt that never reached Wave slips through unnoticed.

What popdock provides

--

Give a start and end date and the Wave business. It reads the succeeded Stripe charges and the Wave invoice payments for those dates, and matches each charge on amount, a date within 3 days and the customer name, also trying the Stripe charge id against the Wave confirmation code. Refunds are taken off to give a net amount. You get matched pairs, Stripe charges with no Wave payment and Wave payments with no Stripe charge, with counts and value per currency. It only reads, never mixes currencies and warns when a read may be truncated.

Business outcome

---

Unrecorded Stripe receipts are found in one pass, with Wave left untouched and currencies kept apart.
See Full Use Case

scenario

-

Billing and bookkeeping keep separate customer lists. Nobody notices a customer who exists in Chargebee but not in Wave, or the other way round, until an invoice or payment cannot be matched. Comparing the lists by hand means two exports and a lot of eyeballing of names and emails.

What popdock provides

--

Optionally give a piece of text to narrow the check, otherwise it reads up to 200 customers from each of Chargebee and Wave. Customers are matched on email first, ignoring case. If there is no email match it tries the company name and then first plus last name, and marks those as name-only matches to verify. You get four lists: matched, name-only matches, in Chargebee only and in Wave only, with any name or email differences on matched pairs. It only reads, warns when a list may be capped, and lists a shared email on two Wave customers as a conflict.

Business outcome

---

Customers missing from either system are caught before an invoice or payment fails to match, and Wave is left unchanged.
See Full Use Case

scenario

-

The accounting customer list and the store customer list are matched by hand, usually by scrolling two exports side by side. Duplicates, typos and customers who exist in only one system go unnoticed, and a Wave customer with no email cannot be matched at all.

What popdock provides

--

Optionally give an email fragment to narrow the check, and the Wave business if you have more than one. It reads the active Wave customers and the Shopify customers, lower-cases and trims the emails, and matches on them. You get counts for customers in both, only in Wave and only in Shopify, then tables of each gap with outstanding amount, orders and total spent, and name or phone mismatches shown side by side. Wave customers with no email are listed separately. It only reads, and warns when a read may be incomplete.

Business outcome

---

Customers missing or mismatched between the store and the books are listed in one report, with nothing changed in either system.
See Full Use Case

scenario

-

Keeping the store and the books in step means comparing the WooCommerce customer list with the Wave one by hand. Missing customers and mismatched names go unnoticed, and rows with no email cannot be compared at all.

What popdock provides

--

Optionally give an email fragment, and the Wave business if the login has more than one. It reads the Wave customers and the WooCommerce customers, lower-cases and trims the emails and matches on them. You get three lists: in Wave only, in WooCommerce only and matched with differences, where the Wave name is compared with the WooCommerce first and last name. Rows with no email are listed separately and the counts say if a read hit its limit. It only reads, matches on exact keys and never treats a different spelling as a different customer when the email matches.

Business outcome

---

Customers missing or different between the store and the books are listed in one pass, and neither system is changed.
See Full Use Case

scenario

-

At period end, invoices and payments in Wave are matched by hand. Underpayments, overpayments and payments that point to no invoice stay hidden in the totals. Someone has to add up the payments per invoice and compare them with the amount paid and amount due.

What popdock provides

--

Give a range of invoice dates and the Wave business if you have more than one. It reads the invoices and the invoice payments, sums the payments for each invoice number and compares them with the amount paid, the amount due and the total. It finds invoices marked paid that still show an amount due, payments that exceed the invoice total, payments not completed or tied to no invoice in the range, and unpaid invoices with a payment. The report lists each mismatch with a suspected cause, counts per issue type and the total unexplained difference. It only reads, fixes nothing and keeps currencies apart.

Business outcome

---

Underpayments, overpayments and orphan payments are listed with likely causes before period end, with no record changed.
See Full Use Case

scenario

-

Checking that the tax on Wave invoices matches what Avalara AvaTax calculated means comparing two systems invoice by invoice. Totals, subtotals and tax amounts are compared by hand, and a mismatch tends to surface only at filing time.

What popdock provides

--

Give a date range (the last 30 days by default) and optionally one customer. It reads the non-draft Wave invoices, then the AvaTax transactions for the range with a few days of slack, matching on the invoice number and falling back to the subtotal, date and customer. Wave tax and subtotal are compared with AvaTax and any difference over 0.01 is flagged, with the tax line shown for flagged pairs. The report lists status per invoice (match, tax differs, amount differs, not in AvaTax) and totals including the net tax difference. It only reads on both systems and refuses to compare mixed currencies.

Business outcome

---

Tax differences between Wave and AvaTax are found before filing, with nothing created, adjusted or voided in either system.
See Full Use Case

scenario

-

Open quotes sit in Wave unanswered. Nobody lists which estimates are stale, which are still drafts that were never sent, or which already carry a deposit but have not been accepted. The follow-up list is built by scrolling through estimates one customer at a time.

What popdock provides

--

Optionally give how far back to look (90 days by default), how many days make an estimate stale (30 by default) and the Wave business. It reads the estimates and keeps those not accepted, converted or declined, with drafts in a separate group, then checks estimate deposits and matches them by estimate number. You get open estimates by customer with age and deposit, a follow-up list of stale ones and those with a deposit but no acceptance ranked by total, the unsent drafts and the total open pipeline. It only reads and never sends, approves or accepts anything.

Business outcome

---

Stale and deposit-backed estimates get followed up, with a total for the open pipeline and nothing sent from Wave.
See Full Use Case

scenario

-

Before chasing a late payer, the team checks the online store by hand to see whether the customer still buys. That context is usually skipped, so a regular buyer gets a harsh reminder while a customer who has gone quiet is treated gently.

What popdock provides

--

Optionally give a minimum overdue amount (1 by default) and the Wave business. It reads the Wave customers with overdue balances, skipping and listing any with no email, then finds each one in Shopify by email for orders count, total spent and last order. For the ten largest overdue balances that matched, it reads the latest five orders and checks the order risk on any not fully paid. The report groups customers into active buyers to chase gently, no recent activity to chase firmly, and not in Shopify, with overdue totals. It only reads, contacts nobody and never matches on name alone.

Business outcome

---

Collection calls fit the relationship, with store activity beside every overdue balance and no customer contacted.
See Full Use Case

scenario

-

Chasing late payers means exporting invoices, sorting them by hand and guessing who matters most. Days overdue are worked out in a spreadsheet, customers are totalled by eye and big balances can be missed in a long list.

What popdock provides

--

Optionally give an as-of date (today by default), a minimum amount and the Wave business. It reads the past-due invoices, ignoring paid, draft and void ones, works out days overdue for each and sorts them into 1 to 30, 31 to 60, 61 to 90 and 90 plus day buckets. It groups by customer and adds email and overall overdue amount for the five biggest balances. You get a customer table, the bucket totals, a ranked chase-first list with a line of reasoning for each and the grand total. It only reads, sends nothing, keeps currencies separate and warns if results may be truncated.

Business outcome

---

Late payers are ranked by what they owe and how long, so the biggest overdue balances get chased first, with nothing sent.
See Full Use Case

scenario

-

Refunds issued in the store are easy to forget in the accounting system, so revenue stays overstated until someone spots it. Checking means taking each Shopify refund, finding its invoice in Wave and comparing the invoice with the refunded amount.

What popdock provides

--

Give a date range (the last 30 days by default) and the Wave business. It reads the Shopify refunds, using the refund lines to work out the amount where a refund has no total. For each refund it looks for the Wave invoice by order name, then reads that invoice's payments and compares the invoice total and amount paid with the order amount net of the refund. The report gives a status per refund: books reflect refund, books still show full payment, no Wave invoice, or unclear, with the full payment group first and totalled. It only reads on both systems and flags currency mismatches as unclear.

Business outcome

---

Refunds the books have missed are listed first and totalled, so revenue is corrected without anything being changed by the check.
See Full Use Case

scenario

-

Refunds issued in Stripe are easy to forget to reflect in the books, which overstates revenue. Checking means taking each refund, finding the customer in Wave and looking through their payments for a reversal of about the right amount.

What popdock provides

--

Give a start and end date and the Wave business. It reads the succeeded Stripe refunds, then for each distinct customer name reads the Wave invoice payments from the start date and looks for a refund, a reversal or a negative amount near the refund value. Each refund is labelled Reflected, Not found or Unclear with its amount and customer, and the Not found refunds are totalled per currency. It only reads and changes nothing in Stripe or Wave. It will not match on amount alone when the customer name differs.

Business outcome

---

Refunds missing from the books are listed and totalled by currency, with no payment edited in Wave.
See Full Use Case

scenario

-

Answering what we spend with a vendor, and whether it is in the books, means opening Ramp and Wave separately. Spend, bills, credits and card transactions live in one system and the vendor record in the other, so you match them by eye and can pick the wrong vendor.

What popdock provides

--

Give a vendor name and, if needed, the Wave business. It finds the vendor in Ramp and stops with a list if more than one matches. It then reads Ramp bills, vendor credits, up to 25 card transactions and vendor contacts, and looks up the vendor in Wave by name, falling back to email. The one-page view shows Ramp spend for the year, 365 days and all time, bills with approval and payment status, credit remaining, recent transactions and the Wave vendor record, with whether contact emails agree. It only reads, notes that merchant-name matching is approximate and never totals different currencies.

Business outcome

---

One view of a vendor across Ramp and Wave answers what you spend and whether the vendor is in the books, with nothing changed.
See Full Use Case

scenario

-

Refunds issued in the store are easy to forget in the books, so revenue is overstated. Checking means taking each WooCommerce refund, finding the Wave payment or invoice for its order and deciding whether the money going back is visible.

What popdock provides

--

Give a start date and the Wave business. It reads the WooCommerce refunds created since that date, then for each refund looks for the Wave invoice payment by order number and falls back to the Wave invoice by purchase order number. It looks at the payment state, amount and type and the invoice status and amount due. The report gives a verdict per refund: appears unrecorded, appears recorded or cannot tell, and it only calls a refund recorded when Wave shows a reduction or reversal. It only reads, makes one Wave lookup per refund and stops after 50 refunds, saying so.

Business outcome

---

Refunds that look unrecorded are listed for follow-up, with no claim made where Wave has no record to check and no changes made.
See Full Use Case

scenario

-

Checking whether a billing customer actually reads your campaigns means finding them in Wave, copying their email into Mailchimp and searching the audience by hand. The two systems often store the address in different letter case, so a real subscriber can look like a stranger and the answer gets guessed.

What popdock provides

--

Give a customer name and, if you like, how many days back to look (90 by default). It finds the customer in Wave and stops if there is no match, several matches or no email on file. It then looks up that email in Mailchimp, matched in lower case, and reports each audience, the subscription status, rating, open and click rates and tags, followed by recent campaign opens and clicks. If the names differ between the two systems it shows both. Nothing is written to either system.

Business outcome

---

You know in one reply whether a billing customer is reachable and engaged in Mailchimp, without searching two systems or guessing at email spellings.
See Full Use Case

scenario

-

Finding out how much a customer buys and what they still owe means opening BigCommerce for the orders, then Wave for the invoices and balance, and totalling both by eye. If the shop sells in more than one currency it is easy to add amounts that should never be added.

What popdock provides

--

Give a customer email, how far back to look (365 days by default) and, if needed, the Wave company. It finds the customer in BigCommerce and stops if there is no match or several, then reads their orders. It finds the same customer in Wave and reads outstanding and overdue amounts and invoices. It reports order count, totals per currency, refunds, the last three orders and the unpaid invoices. Phone numbers and addresses are left out and nothing is changed in either system.

Business outcome

---

You see what a customer has bought and what they owe side by side, with currencies kept apart and no data changed.
See Full Use Case

scenario

-

A billing question from a customer means opening Chargebee for their subscription, invoices and payments, then Wave to see what the books show they owe. You stitch the two together yourself, and a paid invoice in one system can quietly show as unpaid in the other.

What popdock provides

--

Give the customer email and optionally how many invoices to review (10 by default) and the Wave company. It finds the customer in Chargebee and stops if the email matches more than one, then reads their subscription, recent invoices and payments. It finds the customer in Wave and reads balance, invoices and payments. You get a short section per system and a one-line verdict, either that the systems agree or the exact difference. Only amounts and statuses are shown, never card or bank details, and nothing is changed.

Business outcome

---

Support can answer a billing question with one view of both systems and a clear verdict on any difference, without exposing payment details.
See Full Use Case

scenario

-

Proving that a store order reached the books as a paid invoice means reading the order and its payments in Shopify, then hunting through Wave for the matching invoice and payments. Mismatches stay hidden until month end, when someone has to find them under pressure.

What popdock provides

--

Give a Shopify order number and, if you have several Wave companies, the company. It reads the order and stops if the number returns more than one. It totals the successful sales and captures less refunds in Shopify, then finds the Wave invoice by the order reference and reads its payments. If it has to fall back to the customer, it offers only invoices with the same total and labels them unconfirmed. The verdict says whether both sides agree, and amounts in different currencies are shown, not compared. Nothing is changed.

Business outcome

---

You can prove an order was invoiced and paid for the same amount in Wave, or see exactly where it was not.
See Full Use Case

scenario

-

When a customer says they paid, you have to dig through Stripe for the charges, then through Wave for the invoice and the payments recorded against it. The two rarely line up neatly, and a failed or disputed charge can hide inside the pile.

What popdock provides

--

Give a Wave invoice number and, if you have several Wave companies, the company. It reads the invoice and its payments in Wave, then finds the matching Stripe invoice and the charges tied to it. If Stripe has no matching invoice it searches by customer email and date and labels the result as an unlinked search. You get one timeline of the invoice, each Stripe charge and each Wave payment, plus the difference between money received and payments recorded. Failed or disputed charges are flagged and nothing is changed.

Business outcome

---

You can show a customer exactly where their payment sits, and spot a failed charge or unrecorded payment, in one timeline.
See Full Use Case

scenario

-

Chasing an overdue invoice by email is guesswork when you cannot tell whether the address bounces or the customer unsubscribed. Finding out means listing overdue invoices in Wave, getting each customer's email, then searching Mailchimp for each one.

What popdock provides

--

Give a minimum amount due (0 by default) and how many days of activity to review (60 by default). It reads up to 25 overdue Wave invoices and finds each customer's email, marking any customer it cannot resolve instead of guessing. It then checks each address in Mailchimp for audience status and counts opens, clicks, bounces and unsubscribes. Every invoice gets a verdict of reachable, silent, bouncing or unsubscribed, with totals of the amount due in each, and a note when the reminder must go another way. Nothing is written to either system.

Business outcome

---

Collections can see which overdue customers email will reach and which need a call or letter, with the amounts owed in each group.
See Full Use Case

scenario

-

Checking one customer means logging into Wave for invoices and balances, then into 2Checkout for subscriptions and orders, and comparing by eye. Overdue balances, live subscriptions and mismatched names or currencies get missed.

What popdock provides

--

Give a customer email and, if needed, the Wave company. It finds the customer in Wave, stopping if several match, and reads the balance, overdue amount and open invoices. It carries the email to 2Checkout and reads the customer, subscriptions and orders. It flags an overdue Wave amount alongside an active subscription, differing currencies and differing names or companies. Matching is on email only, payment details are never shown, and nothing is changed in either system.

Business outcome

---

One account view shows a customer's invoices, subscriptions and orders and the differences between systems, matched by email only.
See Full Use Case

scenario

-

Product names and prices are kept in both Wave and 2Checkout by hand, so the two drift apart. Finding the gaps means exporting both catalogs, lining up names that never match exactly, and checking prices one by one.

What popdock provides

--

Optionally give part of a product name to narrow the check. It reads the products you sell in Wave and the 2Checkout products with their prices, then matches them by name, ignoring case and punctuation. It says clearly that matches are by name, lists uncertain ones as possible matches and compares prices only when the currencies agree. You get four lists: same price, different price, only in Wave and only in 2Checkout. If either side returns nothing it says so, and nothing is changed.

Business outcome

---

You see which products are missing or priced differently between Wave and 2Checkout, without exporting and lining up two catalogs.
See Full Use Case

scenario

-

Seeing what one customer owes and has bought means opening Wave for the balance and invoices, then WooCommerce for orders and refunds, and adding it up by hand. An order with no matching invoice, or amounts in two currencies, is easy to miss.

What popdock provides

--

Give a customer email and, if needed, the Wave company. It finds the customer in Wave and stops if several match, then reads outstanding and overdue amounts and invoices. It finds the customer in WooCommerce and reads their orders and refunds. It reports Wave balances and invoices by status, WooCommerce orders by status, total spent and refunds, plus orders with no matching invoice by order number. Amounts are kept in their own currency, and nothing is changed in either system.

Business outcome

---

You see what a customer has bought, been refunded and still owes in one view, with currencies kept apart.
See Full Use Case

scenario

-

Before a call or a credit decision someone opens a customer in Wave and clicks through invoices, payments and estimates one tab at a time. Totalling what was billed, paid and due, and judging how they pay, takes a while and varies from person to person.

What popdock provides

--

Give a customer name and, if you like, how many days back to cover (365 by default) and the Wave company. It finds the customer and stops to ask if several match. It then reads their invoices, payments and estimates for the period and summarises billed, paid and due totals, unpaid invoices with due dates, payments received, average days to pay where invoices can be matched, and estimates by status. A two-sentence payer assessment closes the report. It only reads, and shows just the email as contact data.

Business outcome

---

You get a one-page account summary with a plain payer assessment before a call or credit decision, without clicking through tabs.
See Full Use Case

scenario

-

Payment reminders sent through marketing email never reach customers who unsubscribed from Constant Contact, and nobody notices they owe money. Finding them means listing Wave customers with balances, then checking each email in Constant Contact one at a time.

What popdock provides

--

Give the Wave company and, if you like, a minimum outstanding balance (1 by default). It lists Wave customers owing at least that amount, then checks each email in Constant Contact for whether they can be sent to. For anyone not subscribed it reads the unsubscribe reason and date. The report shows customer, balance and currency, Constant Contact status and unsubscribe details, and recommends a direct invoice reminder from Wave for the unsubscribed ones. It never suggests marketing email to them, sends nothing and changes nothing.

Business outcome

---

You find customers who owe money but cannot be reached by marketing email, so reminders go directly instead of being lost.
See Full Use Case

scenario

-

Nobody checks whether customers who owe money are still getting promotional email, so a collections call and a sales pitch collide. Finding out means listing overdue customers in Wave, then searching Constant Contact for the campaigns each one received.

What popdock provides

--

Give the Wave company, a minimum overdue amount (1 by default) and a start date (30 days ago by default). It lists Wave customers with overdue balances at or above that amount, then reads the Constant Contact campaigns each customer received since the date and the campaign names. The report shows overdue amount and currency, how many campaigns each received and their names and dates. It flags customers who got campaigns while owing a large balance, and those with no email or Constant Contact record. Currencies are never added together, and nothing is changed.

Business outcome

---

You see which overdue customers still received promotional email, so collections and marketing stop working against each other.
See Full Use Case

scenario

-

Collections teams cannot see which overdue customers still hold live subscriptions, so the chase order is guesswork. Finding out means listing overdue customers in Wave, then searching 2Checkout for each email, subscription by subscription.

What popdock provides

--

Give a minimum overdue amount (0.01 by default) and, if needed, the Wave company. It lists overdue Wave customers and looks up each email in 2Checkout for subscriptions, using the customer record to tell not a customer from no subscriptions. It can show the next renewal price. Results are sorted by overdue amount and grouped as overdue with an active subscription, overdue with subscriptions ended and overdue not in 2Checkout. It matches on email only, never totals across currencies, recommends actions in words only and changes nothing.

Business outcome

---

Collections can start with the overdue customers who still hold live subscriptions, ranked by what they owe, with no changes made to any account.
See Full Use Case

scenario

-

Product revenue in Wave needs a manual export and pivot table, so slow sellers and price drift go unnoticed. Draft and void lines can slip into the totals, and a partial export makes the numbers look complete when they are not.

What popdock provides

--

Give a date range and, if you like, part of a product name and the Wave company. It reads the invoice lines in the range, leaving out draft and void invoices, and groups them by product for quantity, subtotal, tax, total and average unit price. It then checks your sold, unarchived products to find those with no sales in the range. The report shows the top 10 products with their share of revenue, unusual price variation within a product, the unassigned total and unsold products. Currencies are reported separately, partial totals are flagged and nothing is changed.

Business outcome

---

You see which products earn the most and which do not sell, without an export or pivot table and with partial data clearly flagged.
See Full Use Case

scenario

-

Collectors cross-check overdue Wave invoices against call logs by hand. Wave and the contact center share no customer id, so the only link is a phone number in different formats, and customers who were never called are easy to miss.

What popdock provides

--

Optionally give a minimum amount due, and how many days of calls to look at, 14 by default. It lists overdue Wave invoices, groups them by customer, and looks up each customer's phone and mobile numbers. It then checks Contivio for calls to or from those numbers, comparing digits only, and records the latest call date, result and summary. You get a table sorted by amount due with customers not contacted first. Numbers with no match are reported as unmatched, and if one number fits several customers it lists the candidates instead of choosing. Nothing is sent or changed.

Business outcome

---

Collectors start with the overdue customers nobody has called, with unmatched numbers shown instead of dropped, and no invoice is touched.
See Full Use Case

scenario

-

Finding out whether a customer paid after being phoned means looking up their payments in the invoicing system and their calls in the phone system, then lining up the dates by hand. The two systems share no customer id, so the only link is a phone number written in different formats.

What popdock provides

--

Give a Wave customer's name and how many days to look back (30 by default). It finds the customer in Wave, stopping if more than one matches, reads their invoice payments, then picks out the Contivio calls whose numbers match the customer's phone or mobile, comparing digits only. You get one timeline, oldest first, mixing calls and payments, with any payment dated within 7 days after a call noted. It is read only, says plainly that this shows timing and not cause, and reports numbers that match nothing instead of dropping them.

Business outcome

---

Finance sees when payments followed collection calls in one timeline, without treating timing as proof that a call caused the payment.
See Full Use Case

scenario

-

A customer agrees on a call to pay an invoice, and someone later keys the payment into Wave from memory or notes. It is easy to pick the wrong invoice or customer, enter more than the balance, or record the same payment twice.

What popdock provides

--

Give a Contivio call, an amount and a Wave invoice number. It reads the call and its summary and asks whether to continue if the summary does not mention a payment. It checks the Wave invoice and customer, compares the customer's phone numbers with the call and stops if the amount is more than the amount due or the balance is already zero. You then see the call, invoice, amount and date, and choose the payment method and account. Nothing is recorded until you say yes, and then it records one payment and reads the invoice again to report the new amount due and status. If the phone numbers do not match, you must confirm explicitly first.

Business outcome

---

Payments agreed on a call land once, on the right invoice, with the new balance confirmed and no overpayment or double entry.
See Full Use Case

scenario

-

Managers want to know whether an agent's calls are going to customers who actually owe money, but the call list is in one system and balances are in another. Linking them means taking each phone number, finding the customer in Wave and checking what they owe, which is rarely done.

What popdock provides

--

Give an agent name and optionally a look-back period, 7 days by default. It reads that agent's Contivio calls, stopping to list the names if the calls come from more than one agent, and picks out the customer number on each call from its direction. It reads the Wave customers with an overdue balance and matches each number to a customer's phone or mobile, comparing digits only because the two systems share no customer id. You get a table of matched calls with customer name, overdue and outstanding amounts, result and talk time, then counts of calls to customers with no overdue balance and of unmatched numbers. If a number fits several customers it lists them. Nothing is changed.

Business outcome

---

Managers see how much of an agent's calling went to customers with overdue balances, with unmatched numbers shown rather than dropped.
See Full Use Case

scenario

-

To find out what was said to a billing customer, an agent searches the call log by hand and guesses which phone numbers belong to which Wave customer. The two systems share no customer id, so the phone number is the only link and it is easy to match the wrong calls.

What popdock provides

--

Give a customer name and a look-back period, and it finds the Wave customer, stopping with a list of names and phone numbers if more than one matches. It matches the customer's phone and mobile numbers to Contivio calls, comparing digits only, and lists each call with direction, queue, agent, result, talk time and AI summary. You also see the customer's balance and overdue amount, the call count and the date of the last contact. Numbers with no match are reported as unmatched, and nothing in Wave or Contivio is changed.

Business outcome

---

Agents see a customer's recent calls and balance together, with unmatched numbers shown and never guessed, so the next conversation starts informed.
See Full Use Case
No items found.

ready, go

Tools for Wave

Start with ready-made MCP tools for the Wave. Each one gives your AI client a single, clearly defined job: get invoices or journal entries, pull a file, or create and update records. Add a tool to your PopdockAI MCP server, choose the fields it returns and who can use it, and it's ready in Claude, ChatGPT or Microsoft Copilot. Nothing is exposed that you haven't switched on.

Tool Types

Name of tool
Description
get-data
wave-get-vendor
Returns vendors from Wave. Wave connector tool; filter by the parameters it offers.
get-data
wave-get-product
Returns products from Wave. Wave connector tool; filter by the parameters it offers.
get-data
wave-get-product-sales-tax
Returns product default taxes from Wave. Wave connector tool; filter by the parameters it offers.
get-data
wave-get-invoice
Returns invoices from Wave. Wave connector tool; filter by the parameters it offers.
get-data
wave-get-invoice-payment
Returns invoice payments from Wave. Wave connector tool; filter by the parameters it offers.
get-data
wave-get-invoice-item
Returns invoice lines from Wave. Wave connector tool; filter by the parameters it offers.
get-data
wave-get-estimate
Returns estimates from Wave. Wave connector tool; filter by the parameters it offers.
get-data
wave-get-estimate-item
Returns estimate lines from Wave. Wave connector tool; filter by the parameters it offers.

Ready to unlock your data?

‍

Start building tools that turn your business systems into AI superpowers

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation