Flagging lets users highlight transactions that need further review, so potential issues are caught before they affect reporting. It streamlines communication between teams, keeps financial records accurate, and tracks flagged items through each stage of the workflow. A flagged transaction is an entry marked as needing additional review or information.
This overview introduces the feature. For step-by-step instructions, see the articles How to Add and Manage a Flagged Transactions and Understanding the Communications Inbox - Flagged Transactions.
Why Use Flagging
Improved accuracy – Identify and resolve discrepancies before they impact reporting.
Streamlined communication – Highlight items that need attention so users, clients, and agents can act quickly.
Reduced errors – Catch missing or incorrect information early, before it propagates through the system.
Where You Can Flag
You can flag transactions in several modules, and a flag persists as the transaction moves between stages:
AP Inbox – Flag invoices missing key information such as vendor details or invoice numbers. (The AP Inbox is where incoming vendor invoices land for coding and approval.)
Invoice Approval – Flag discrepancies during approval, such as a mismatch between an invoice and a purchase order.
Payments – Flag issues before processing, such as missing authorizations or incorrect payment terms.
Bank Sync – Flag unmatched transactions found during bank reconciliation for further investigation. (Bank Sync connects Inn-Flow to the bank feed to match transactions against the register – the account's running list of transactions.)
How Flagging Works
1. Locate the transaction in the relevant module (AP Inbox, Payments, Bank Sync).
2. Use the triple-dot menu next to the transaction and select Flag for Review. A popup lets you add notes and the reason for the flag.
3. Monitor the flagged item in the Communications Inbox, where the relevant team reviews and resolves it.