> ## Documentation Index > Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # What the suppliers are likely to invoice over the coming months, from the invoices accepted > against past work orders. Two halves, returned side by side and never blended. `planned` is the rounds the active maintenance plans will raise in the horizon, each priced at what that plan has been invoiced on that asset per completed round over the look-back (falling back to the plan's average across its assets). A round the plant has done itself has been invoiced nothing and costs nothing here. `run_rate` is everything with no round behind it — breakdowns and ad-hoc jobs — as the look-back's monthly average carried forward. `unpriced_rounds` counts rounds of plans with no completed round in the look-back, which are in no amount. `estimated_rounds` counts rounds placed by extrapolating a meter rather than by a calendar. One row per group — TOTAL, SITE, VENDOR, ASSET_CATEGORY or ASSET — with `months` holding each month of the horizon in order, so every group has every month. The horizon starts on the first of next month. Largest total first. Amounts are in the organisation's counting currency; invoices with no conversion into it are left out and counted by `api.vendor_spend_forecast_basis`. ## OpenAPI ````yaml /api-reference/openapi.json get /rpc/vendor_spend_forecast openapi: 3.0.0 info: description: '' title: >- The only schema PostgREST exposes. Reads are security_invoker views; writes are SECURITY DEFINER functions. Rebuilt wholesale on every deploy — it holds no data. version: 12.2.3 servers: - url: https://app.assetinfinity.ai/api security: [] tags: - name: Signing in - name: Profile - name: Assets - name: Asset lifecycle - name: Work lifecycle - name: Maintenance - name: Inventory - name: Inventory detail - name: Procurement - name: Contracts - name: Workforce - name: Capacity - name: Dispatch - name: Tools - name: Inspections - name: Verification - name: Reliability - name: Parts demand - name: Sensors and meters - name: Map - name: Floor plans - name: Labels - name: Lost and found - name: Root cause analysis - name: Reports - name: Audit center - name: Activity - name: Notifications - name: Channels - name: Search - name: Copilot - name: Import - name: Files - name: Sync - name: Support - name: Admin - name: Access - name: Lookups - name: Read models - name: Branding - name: Custom fields - name: Form studio - name: Workflows - name: Workflow studio - name: Rules - name: Statuses and transitions - name: Currencies and locales - name: Work configuration - name: Asset configuration - name: Inventory configuration - name: Tool configuration - name: Workforce configuration - name: Vendor and contract configuration - name: Document configuration - name: Inspection configuration - name: Sites, locations and the organisation - name: Platform - name: Amendments - name: Asset clone - name: Asset components - name: Asset register - name: Asset transfer - name: Audit feed - name: Billing - name: Bookings - name: Budgets - name: Bulk jobs - name: Calibration history - name: Capex plans - name: Conversations - name: Costing - name: Currency - name: Dashboards - name: Directory sync - name: Document control - name: Document folders - name: Document tree - name: Documents - name: Energy - name: Extracts - name: Features - name: Feeds - name: File exchange - name: Filing exceptions - name: Finance - name: Inbound mail - name: Keys - name: Knowledge - name: Licence - name: List views - name: Locations - name: Mapping - name: Mcp - name: Mcp oauth - name: Mfa - name: Numbering - name: Permits - name: Readers - name: Reference - name: Reference columns - name: Reference entry - name: Release - name: Scim - name: Security streams - name: Self verification - name: Setup - name: Shutdown - name: Sso - name: Telegram - name: Tenant switch - name: The caller's own work - name: The checklist library - name: Tools on a job, and who has them out - name: Tray - name: Vendor spend forecast - name: Vendors and contracts - name: Visitors - name: Work order execution - name: Work sequencing - name: Workforce detail externalDocs: description: PostgREST Documentation url: https://postgrest.org/en/v12/references/api.html paths: /rpc/vendor_spend_forecast: get: tags: - Vendor spend forecast summary: >- What the suppliers are likely to invoice over the coming months, from the invoices accepted description: >- against past work orders. Two halves, returned side by side and never blended. `planned` is the rounds the active maintenance plans will raise in the horizon, each priced at what that plan has been invoiced on that asset per completed round over the look-back (falling back to the plan's average across its assets). A round the plant has done itself has been invoiced nothing and costs nothing here. `run_rate` is everything with no round behind it — breakdowns and ad-hoc jobs — as the look-back's monthly average carried forward. `unpriced_rounds` counts rounds of plans with no completed round in the look-back, which are in no amount. `estimated_rounds` counts rounds placed by extrapolating a meter rather than by a calendar. One row per group — TOTAL, SITE, VENDOR, ASSET_CATEGORY or ASSET — with `months` holding each month of the horizon in order, so every group has every month. The horizon starts on the first of next month. Largest total first. Amounts are in the organisation's counting currency; invoices with no conversion into it are left out and counted by `api.vendor_spend_forecast_basis`. parameters: - in: query name: p_group_by required: false schema: format: text type: string - in: query name: p_months required: false schema: format: integer type: integer - in: query name: p_lookback_months required: false schema: format: integer type: integer - in: query name: p_site_id required: false schema: format: uuid type: string responses: '200': description: OK ````