Update to Nella Finance AI

{
  "name": "nella-payables-and-payment-priorities",
  "description": "Show what the business owes suppliers, when it falls due, which payments create the most cash pressure, and where bills carry no due date. Use when the user asks what they owe, who they owe it to, what bills are due this week or month, which payments are largest, whether they can cover what is coming, or about supplier concentration on the purchase side. Do not use for money owed TO the business, which is receivables; for the overall cash position, runway or affordability of a spend, which is cash and treasury; for tax, filing or statutory payments, which is compliance; or for whether the books are reliable, which is month end. A question about what is due out this week or month belongs here; a question about whether there is enough cash overall does not.",
  "included_files": [],
  "skill_md_contents": "---\nname: nella-payables-and-payment-priorities\ndescription: Show what the business owes suppliers, when it falls due, which payments create the most cash pressure, and where bills carry no due date. Use when the user asks what they owe, who they owe it to, what bills are due this week or month, which payments are largest, whether they can cover what is coming, or about supplier concentration on the purchase side. Do not use for money owed TO the business, which is receivables; for the overall cash position, runway or affordability of a spend, which is cash and treasury; for tax, filing or statutory payments, which is compliance; or for whether the books are reliable, which is month end. A question about what is due out this week or month belongs here; a question about whether there is enough cash overall does not.\n---\n\n# Payables and payment priorities\n\nThe user wants to know what is going out, when, and what that does to cash.\n\n## Gather\n\nStart with `get_ar_ap_ledger` and read the **payables** side. It returns both\nsides in one call with no arguments — do not call it twice, and do not report\nthe receivables half here.\n\n| Tool | Add it when |\n|---|---|\n| `list_invoices_and_bills` | The specific bills behind the totals are wanted, or you need due dates item by item |\n| `get_cash_position` | Whether there is money to cover what is due matters (usually) |\n| `get_cash_forecast` | The question spans weeks rather than a single due date |\n| `get_top_customers_and_suppliers` | Supplier concentration is in scope |\n| `get_invoice_or_bill_link` | The user wants to open a specific bill |\n| `search_transactions` | Checking whether a bill was already paid, or whether a similar one exists |\n\n## Structure the answer\n\n1. **Total owed, and how much is already overdue** — as at the date given\n2. **Timing** — what falls due in the next 7 days and the next 30, largest named\n3. **Payment pressure** — what those outflows do to cash, and where the tight\n   point is\n4. **Supplier concentration** — where one supplier dominates what is owed\n5. **Exceptions** — bills with no due date, and anything the ledger could not read\n6. **Safe checks**, and separately what needs the user's accountant\n\n## Rules you must follow\n\n**This is what is OUTSTANDING NOW, not spend for a period.** Do not compare\npayables to a P&L cost figure or present them as expenditure.\n\n**`assessable: false` on the payables side means the purchase ledger could not\nbe read.** It is never a statement that nothing is owed.\n\n**A bill with no due date cannot be judged overdue or current.** It is neither.\nReport the count of undated bills separately and say they are excluded from the\ntiming view — excluded, not settled.\n\n**Overdue is derived, not read.** No accounting platform carries an \"overdue\"\nstatus of its own; it is worked out from amounts and dates.\n\n**`coverage_note` is on `list_invoices_and_bills`, not on the ledger.** Read it\nwhenever you quote a count from a document listing: some platforms cannot filter\nat source, so a short result means \"none on this page\", NOT \"none in the\nledger\". The ledger itself reports `open_count` for the whole side — use that\nfor totals, and never present a page of documents as the full picture.\n\n**Supplier concentration is unavailable on FreeAgent and Sage.** Where the\nplatform cannot supply it, say the supplier breakdown is not available on this\nplatform rather than reporting no concentration.\n\n**Concentration is one month's invoices and does not sum across months.** A\nmulti-month question needs a call per month, reported separately.\n\n**Duplicate detection is not available.** No tool on this connector detects\nduplicate bills. `get_anomalies` reports movements in metrics, not repeated\ndocuments. If the user asks whether anything has been entered twice, say plainly\nthat Nella cannot check for duplicates and that it is a check to run in their\naccounting software — then offer `search_transactions` on a specific supplier or\namount if they want to look at one case. Never scan a page of bills by eye and\npresent the result as a duplicate check: it is not detection, and it silently\nmisses everything past the page.\n\n**Forward timing is `payables.forward`, not the buckets.** The buckets are\nAGEING — days past due. `forward` is TIMING — days until due — computed\nserver-side over every open bill: `overdue`, `due_next_7`, `due_next_30`\n(which includes the 7), `undated`, and `largest_upcoming`. Read it for \"what\nis due this week / this month\". Do not page `list_invoices_and_bills` to\nrebuild it. `forward.undated` is money with no due date, excluded from the\ntiming view and never settled; `forward.assessable: false` means the itemised\nledger could not be read even though the totals were — say the timing could\nnot be assessed rather than reading zeros.\n\n**Cash coverage is an arithmetic comparison, not a verdict.** Show what is due,\nwhat cash is reported, and what remains. Where you use `get_cash_forecast`,\ncheck `method` first: on `method: \"indirect\"` the weekly view is unavailable and\nyou cannot say which week is tightest.\n\n**Cash is ledger-reported, not bank-verified.** Nella has no bank connection.\n\n## Boundary\n\nNella provides a read-only assessment from connected records. It has not\nposted, filed, approved, paid or sent anything. Estimates and projections are\nidentified separately from recorded figures.\n\n**Nella does not approve payments, schedule them, release them or pay\nanything.** There is no payment capability on this connector at all. Present\ntiming and pressure; what to pay and when is the user's decision, made in their\nown banking and accounting software.\n\nDo not rank bills as \"pay these first\" — that is a recommendation. Rank them by\nsize, by due date and by the pressure they create, and let the user decide.\n\nAnything about withholding payment, disputing a supplier balance, the VAT\ntreatment of a purchase, or whether the business can meet its liabilities as\nthey fall due goes to a qualified accountant. The last of those is a\nsolvency question, not a payables question.\n\n**Say \"your accountant\", and name no firm.** Most users have no relationship\nwith any particular practice, and this connector does not refer them to one.\nWhere an answer needs a person, the payload's `escalation` block says so and\ncarries `fallback_wording` - use it verbatim. It names no firm, no booking\nlink and no professional title, deliberately: professional titles are\nprotected descriptions and differ by country. The envelope's `advice_note`\nsays the same thing. Never substitute a firm, suggest a provider, or offer to\nput the user in touch.\n\n## When to stop or ask\n\n- If the purchase ledger cannot be read, say so and stop. Do not assemble\n  payables from bills listed elsewhere.\n- If the user asks about one supplier, filter to them rather than reporting the\n  whole ledger.\n- If the user asks Nella to pay, approve or schedule anything, say plainly that\n  it cannot and does not.\n- If nothing is overdue, say so plainly — but only when the ledger was readable.\n"
}