1. Overview

This guide explains how Signals help operators identify financial activity that may require review, follow-up, or operational action.

You’ll learn how Signals are prioritized, what types of issues Finz can detect, how to investigate Signal details, and how operators use Signals to stay ahead of operational and financial risk throughout the month.

Signals help reduce manual finance work by surfacing important activity across transactions, invoices, payables, cash flow, and reporting workflows — before issues impact operations or month-end close.

2. What Signals are

Signals are AI-generated workflows that surface financial activity requiring review or action.

Instead of manually searching through transactions, invoices, and reports, Finz continuously monitors your connected systems and highlights operational issues that may impact cash flow, margin, or reporting accuracy.

Signals help operators stay ahead of problems before month-end close.

3. What Signals can detect

Finz may generate Signals for:

• overdue receivables

• aging payables

• unusual spending activity

• missing invoice follow-up

• uncategorized transactions

• margin compression

• cash flow pressure

• reconciliation mismatches

Each Signal includes supporting context so teams can quickly understand what happened and what may need attention.

4. Understanding Signal priority

Signals are prioritized based on operational impact and urgency.

High

Issues that may immediately affect:

• cash flow

• vendor relationships

• reporting accuracy

• operational liquidity

Medium

Issues that should be reviewed soon but may not require immediate action.

Low

Informational workflows and lower-risk operational reviews.

5. Signal details panel

Opening a Signal displays additional operational context, including:

• affected invoices or transactions

• estimated financial impact

• supporting records

• projected operational outcome

• related source activity

This allows operators to investigate and resolve issues without switching between systems.

6. Common Signal examples

Expected receipts are missing follow-up

Invoices remain open past their expected receipt window and may require follow-up.

Payments detected but invoice still open

Finz detected payment activity, but the invoice status may not be updated correctly.

Overdue payables need immediate action

Bills or vendor payments are overdue and may impact vendor operations or cash planning.

Working capital is tight this week

Projected cash flow indicates potential short-term liquidity pressure.

7. Recommended weekly workflow

Most operators review Signals weekly to:

• Identify operational risks early

• Resolve overdue or mismatched activity

• Review financial exceptions

• Keep reporting and forecasts accurate

• Reduce manual finance work