Finance
Invoice Anomaly Flag
Identify invoice exceptions using explicit checks.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Identify invoice exceptions using explicit checks.
What it covers
Inputs
Invoice population, period, applicable purchase/approval policy.
Result
Invoice exception table with rule, comparison evidence, confidence and review action.
What it uses
Finance recordsCalendarEmailDocumentsSlackKeep memoryRead only
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
QuickBooks, Google Workspace, Slack, Keep memory.
Procedure
- Call keep_status and report freshness for: QuickBooks, Google Workspace, Slack, Keep memory. If a required connector for Invoice Anomaly Flag is disconnected or stale, say so up front.
- Before treating empty finance results as 'no invoices', distinguish no access (QuickBooks/finance ACL) from no matches. Never invent balances.
- Resolve inputs for Invoice Anomaly Flag: account, vendor, entity, time_window. Default time window: open AR/AP and current close period (override if caller provides time_window). Ask only for missing critical inputs.