> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Wave on Vortex IQ

> Monitor Wave payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

Monitor Wave payment health, authorisation and dispute risk, and catch settlement problems before they hit cash flow.

No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue)

| **10**              | **3**            | **Build your own** | **Ready to build yours** | **6**          |
| ------------------- | ---------------- | ------------------ | ------------------------ | -------------- |
| performance signals | automated checks | automated fixes    | workflows                | API operations |

## Monitor performance

10 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher.

| Signal                                              | Outcome         | Alert behaviour         | What it tracks                                                                                                         |
| --------------------------------------------------- | --------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Accounts Receivable Balance (live)**              | Run operations  | Watch only              | Sum of amountDue across all non-PAID, non-DRAFT invoices.                                                              |
| **Ecom Orders Missing Matching Wave Invoice**       | Protect revenue | Merchant rule           | Storefront revenue that never became a Wave invoice/income transaction - invisible to the books and to sales-tax base. |
| **Net Income (month to date)**                      | Run operations  | Watch only              | INCOME-type minus EXPENSE-type money transactions for the current period vs the previous.                              |
| **Overdue AR on Customers with Active Ecom Orders** | Protect revenue | Alert band 1000 / 10000 | Customers who owe overdue money but keep ordering - extend credit knowingly or pause.                                  |
| **Overdue Invoices**                                | Run operations  | Alert band 5 / 15       | Invoices in OVERDUE status. Each is cash stuck past its due date.                                                      |
| **Unreviewed Money Transactions**                   | Run operations  | Merchant rule           | moneyTransactions in UNREVIEWED status. Backlog = books drift from reality + sales-tax filing understated.             |
| **Wave Health Score**                               | Run operations  | Merchant rule           | Composite: AR-aging-low x invoices-not-overdue x transactions-reviewed x order→invoice-reconciled.                     |
| **AR Aging - 60+ Days**                             | Run operations  | Alert band 5 / 15       | Share of AR balance in invoices >60 days past due - the bucket least likely to ever be collected.                      |
| **Days Sales Outstanding (DSO)**                    | Run operations  | Alert band 30 / 60      | Average days from invoice issued to paid - how long cash sits in receivables.                                          |
| **Ecom Customers Absent from Wave**                 | Protect revenue | Alert band 0 / 10       | Sync gap - ecom customers invisible to Wave means invoicing/AR runs against an incomplete customer list.               |

## Audit risks and opportunities

A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable.

| Check                                                              | Severity | Outcome         | Why it matters                                                                                                                                                                                 | Fix status            |
| ------------------------------------------------------------------ | -------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| **AR aging on 60+ day buckets above threshold**                    | high     | Run operations  | More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, | Report only           |
| **ERP-vs-ecom inventory variance > 5% on SKUs with active orders** | high     | Protect revenue | Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or | Report only           |
| **Ecom customers absent from ERP customer master after 7d**        | medium   | Run operations  | Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level repo | Candidate remediation |

### Build your own automated fixes

3 checks report findings on Wave today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change.

## Automate approved work

Vortex IQ is integrated with **0 read** and **6 write** operations across graphqlpublic#accounts, graphqlpublic#business, graphqlpublic#customers, graphqlpublic#invoices, graphqlpublic#moneytransactions, graphqlpublics on Wave. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words.

Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system.

[Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=wave)

<Accordion title="Browse the operations you can build with">
  | Resource                        | Read operations | Write operations |
  | ------------------------------- | --------------- | ---------------- |
  | graphqlpublic#accounts          | 0               | 1                |
  | graphqlpublic#business          | 0               | 1                |
  | graphqlpublic#customers         | 0               | 1                |
  | graphqlpublic#invoices          | 0               | 1                |
  | graphqlpublic#moneytransactions | 0               | 1                |
  | graphqlpublics                  | 0               | 1                |

  Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
</Accordion>

### Ready to build your first Wave workflow

Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

***

*Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*
