Finance
Collections Forecast
Build a receivables collection scenario from evidenced payment assumptions.
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
Build a receivables collection scenario from evidenced payment assumptions.
What it covers
Inputs
Open AR, forecast horizon, currency, payment assumptions.
Result
Time-bucketed collection scenarios, invoice drivers, assumptions and unallocated uncertainty.
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 Collections Forecast 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 Collections Forecast: 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.