What Transaction Statuses Mean

Learn what statuses like Verified, Awaiting Approval, and Needs Review mean across Ledger workflows.

1. Overview

Transaction statuses help operators understand the current review state of financial activity across the Ledger.

Statuses are designed to improve operational visibility by helping teams quickly identify:

  • reviewed transactions

  • transactions requiring approval

  • items needing operator attention

  • incomplete categorization

  • unresolved vendor mappings

Instead of manually tracking transaction review workflows, statuses help operators prioritize what may still require action.

Transaction statuses may appear across:

  • Ledger

  • Vendor Management

  • AP/AR workflows

  • transaction detail panels

  • review workflows

Related Resources

2. Verified

Verified transactions have already been reviewed or confirmed within the platform.

This may include:

  • confirmed categorization

  • approved vendor mappings

  • reviewed operational activity

  • validated transaction relationships

Verified transactions generally require no further operational review unless new information becomes available.

For example:

A recurring vendor payment that has already been categorized and confirmed may appear as Verified.

Verification helps improve consistency across reporting and operational workflows.

3. Awaiting Approval

Awaiting Approval indicates that a transaction or vendor relationship may still require review before finalization.

This may occur when:

  • a new vendor appears

  • categorization is incomplete

  • mappings require confirmation

  • transaction behavior looks unfamiliar

  • operational review has not yet been completed

Operators commonly review these items to confirm accuracy before they become part of finalized workflows.

For example:

A newly detected vendor may require category confirmation before future transactions can be automatically organized correctly.

Related Resources

4. Needs Review

Needs Review indicates that additional operator attention may be recommended.

This may happen when:

  • transaction details appear incomplete

  • categorization confidence is low

  • vendor relationships are unclear

  • operational activity looks inconsistent

  • transaction mappings may require correction

These workflows help operators maintain cleaner operational finance data across the platform.

5. Why Transaction Statuses Matter

Transaction statuses help operators review financial activity more efficiently.

Instead of manually checking every transaction individually, statuses help prioritize attention toward:

  • unresolved items

  • incomplete workflows

  • new vendor activity

  • categorization issues

  • operational inconsistencies

This helps reduce manual review time while improving reporting consistency across Finz.

6. How Statuses Affect Operational Visibility

Transaction statuses may affect multiple workflows across the platform.

Examples may include:

  • Ledger reporting

  • vendor organization

  • AP/AR visibility

  • Signals

  • AI CFO insights

  • operational forecasting

For example:

  • unresolved categorization may reduce reporting clarity

  • incomplete vendor mappings may affect expense grouping

  • unreviewed transactions may create visibility gaps

Review workflows help improve the accuracy and reliability of operational finance data over time.

Related Resources

7. How Operators Typically Use Statuses

Many operators review transaction statuses regularly to:

  • approve new vendor mappings

  • verify categorization

  • investigate unusual activity

  • resolve incomplete records

  • improve reporting consistency

  • maintain cleaner operational workflows

Over time, recurring review improves operational visibility across the business.

8. Statuses May Change Over Time

Transaction statuses are dynamic and may update as:

  • new financial activity syncs

  • vendors become verified

  • mappings are approved

  • categorization improves

  • operators review transactions

  • operational workflows evolve

For example:

A transaction marked Awaiting Approval may later become Verified after operator review.

This allows Ledger workflows to continuously improve operational accuracy over time.

Related Resources