# Pluvo

> Pluvo is the AI platform for finance teams, connecting your systems and business logic so FP&A, financial modeling, analysis, forecasting, and scenario planning produce answers you can trace and trust.

## Key pages

- [Home](https://pluvo.io): Decision-grade intelligence for finance and strategy teams.
- [Pricing](https://pluvo.io/pricing): Plans for teams connecting systems, controls, and AI capacity.
- [For startups](https://pluvo.io/startups): Startups under $5M in annual revenue get the Plus plan at $1,200/mo — 20% off.
- [Platform](https://pluvo.io/platform): AI finance platform for connected data, business context, agent workflows, reporting, lineage, and governance.
- [Security](https://pluvo.io/security): Security, privacy, access controls, and AI governance.
- [Integrations](https://pluvo.io/integrations): Connect Pluvo to accounting, ERP, warehouse, billing, CRM, payroll, banking, and spend systems.
- [Solutions](https://pluvo.io/solutions): Solutions for monthly close, board reporting, audit support, forecasting, revenue analysis, and finance teams.
- [All comparisons](https://pluvo.io/comparisons): Compare Pluvo with spreadsheets, general AI, legacy FP&A, dashboards, and consultant-led finance workflows.
- [Blog](https://pluvo.io/blog): Product news and finance deep dives.
- [Resources](https://pluvo.io/resources): Guides, templates, and practical resources for AI-native finance teams.
- [Livestreams](https://pluvo.io/livestreams): Live sessions and replays on finance engineering, AI-native planning, reporting, and close.
- [Newsletter](https://pluvo.io/newsletter): Subscribe to Pluvo notes on finance engineering and AI-native finance.
- [Glossary](https://pluvo.io/glossary): Definitions for finance, strategy, data, and AI terms used by modern teams.
- [Finance Engineering](https://pluvo.io/finance-engineering): The discipline of building accurate, governed, auditable AI-native finance systems.
- [Pluvo University](https://pluvo.io/university): Learn finance engineering — courses, tracks, and templates.
- [Customer Stories](https://pluvo.io/customers): How finance and strategy teams use Pluvo.
- [Press & Brand Kit](https://pluvo.io/press): Logos, company facts, and press resources.
- [Partners](https://pluvo.io/partners): Bring Pluvo to your clients and build recurring revenue through the Approved Partner Program.
- [About](https://pluvo.io/about-us): The team and operating principles behind Pluvo.
- [Contact](https://pluvo.io/contact): Talk with the Pluvo team about your finance workflows.
- [AI Finance Agent](https://pluvo.io/platform/agent): Pluvo's AI finance agent connects to your systems, reasons over your business context, and runs reconciliations, variance analysis, and close prep, with every number traced to source.
- [Business Ontology](https://pluvo.io/platform/ontology): Pluvo's ontology models your entities, relationships, and definitions so AI agents and finance teams compute every answer from the same understanding of the business.
- [Data Lineage](https://pluvo.io/platform/lineage): Every number in Pluvo traces back to its source records, definitions, and transformations. Full lineage on every answer, including AI-generated ones.
- [Workflow Automation](https://pluvo.io/platform/workflows): Define close checklists, reconciliations, and reporting workflows once; Pluvo runs them on schedule with review gates, exception routing, and a full audit log.
- [Document Vault](https://pluvo.io/platform/vault): Pluvo's Vault extracts terms from contracts, invoices, and statements, links them to your ledger, and keeps the source attached: documents as governed, queryable data.
- [Controls & Governance](https://pluvo.io/platform/controls): Scoped access, full audit logs, and approval gates for people and AI agents alike: Pluvo Controls make AI in finance meet the governance bar.
- [Reports & Dashboards](https://pluvo.io/platform/reports): Board packs and close reports drafted from live, reconciled data with every figure cited, rebuilt on schedule, and interrogable in place.

## Solutions

- [Monthly Close](https://pluvo.io/solutions/close): Close faster with live reconciliations, flux, and support.
- [Board Reporting](https://pluvo.io/solutions/board-reporting): Board-ready packs with answers behind every number.
- [Audit Support](https://pluvo.io/solutions/audit): Trace every figure to source support and audit evidence.
- [Forecasting & Cash](https://pluvo.io/solutions/forecasting): Model forecasts and cash against live business data.
- [Revenue Analysis](https://pluvo.io/solutions/revenue): Understand revenue drivers, cohorts, and retention.
- [Variance & Flux](https://pluvo.io/solutions/variance): Explain every variance the moment it appears.
- [Consolidation](https://pluvo.io/solutions/consolidation): Roll up entities into one governed source of truth.
- [Spend & Cost Control](https://pluvo.io/solutions/spend): Monitor spend and catch cost anomalies early.
- [Office of the CFO](https://pluvo.io/solutions/cfo): Decision-grade intelligence for the whole office.
- [Strategic Finance](https://pluvo.io/solutions/strategic-finance): Scenario modeling and analysis that keeps up.
- [Accounting & Controllership](https://pluvo.io/solutions/accounting): Governed numbers controllers can trust.

## Comparisons

- [Pluvo vs Excel](https://pluvo.io/comparisons/excel): Excel is where finance models. Pluvo computes the numbers across your connected systems, traces them to source, and produces them the same way every close.
- [Pluvo vs Claude & ChatGPT](https://pluvo.io/comparisons/claude-chatgpt): General AI drafts and explains well. Pluvo computes finance numbers deterministically from connected systems, grounded context, and traceable source data.
- [Pluvo vs Legacy FP&A](https://pluvo.io/comparisons/legacy-fpa): Compare Pluvo with legacy FP&A software for live analysis, source tracing, faster setup, finance reporting, and governed answers from your own systems.
- [Pluvo vs the Dashboard](https://pluvo.io/comparisons/the-dashboard): A dashboard shows what changed. Pluvo tells you why it changed, what it cost, and what to do — root cause and financial impact, traced to source.
- [Pluvo vs the Consultant](https://pluvo.io/comparisons/the-consultant): Compare Pluvo with consultant-led finance workflows and see how governed data, logic, source trails, and context keep recurring analysis repeatable.

## Discovery

Sitemap: https://pluvo.io/sitemap.xml
Robots: https://pluvo.io/robots.txt

- [XML sitemap](https://pluvo.io/sitemap.xml): canonical list of public indexable URLs.
- [Robots policy](https://pluvo.io/robots.txt): crawler access policy. Draft, API, and Studio routes are excluded.

## Blog categories

- [Business](https://pluvo.io/blog/category/business) (6 posts): Pluvo blog category.
- [Finance](https://pluvo.io/blog/category/finance) (110 posts): Pluvo blog category.
- [Tips & Tricks](https://pluvo.io/blog/category/tip-tricks) (1 posts): Pluvo blog category.

## Recent blog posts

- [The CFO Tech Stack in 2027: Context Becomes the Control Point](https://pluvo.io/blog/cfo-tech-stack-2027-context-control-point) (Finance; by Vanessa Galarneau; published 2026-08-09): A practical 2027 CFO stack architecture for systems of record, governed context, AI workflows, controls, dashboards, and human decision rights.
- [Explainable AI in Finance: Accuracy Needs a Proof Trail](https://pluvo.io/blog/explainable-ai-finance-accuracy-proof-trail) (Finance; by Vanessa Galarneau; published 2026-08-08): A financial answer is not decision-grade until a reviewer can retrace its sources, definition, calculation, exceptions, changes, and approval.
- [AI and SOX: Where AI Can Sit in a Controlled Finance Process](https://pluvo.io/blog/ai-sox-compliance-controlled-processes) (Finance; by Vanessa Galarneau; published 2026-08-07): Map AI to SOX-scoped ICFR by control objective, evidence, human authority, exceptions and change governance with a practical controller worksheet.
- [Forecast Accuracy Tracking: A Scorecard for FP&A](https://pluvo.io/blog/forecast-accuracy-tracking-scorecard) (Finance; by Vanessa Galarneau; published 2026-08-06): Track forecast accuracy by version, horizon, line item, and bias with a practical FP&A scorecard that turns every material miss into evidence and action.
- [Model-Agnostic Finance: What Must Survive an LLM Swap](https://pluvo.io/blog/model-agnostic-ai-strategy-finance) (Finance; by Vanessa Galarneau; published 2026-08-05): A finance AI strategy is model-agnostic only when context, calculations, controls, evidence, and decision history survive a tested model replacement.
- [Human-in-the-Loop Finance AI: Where the Review Gates Belong](https://pluvo.io/blog/human-in-the-loop-finance-ai-review-gates) (Finance; by Vanessa Galarneau; published 2026-08-04): Place human review where judgment can prevent a finance error. Use Pluvo's three-gate matrix to define evidence, authority, escalation, and sign-off.
- [AI Pilot Post-Mortem Template for Finance Teams](https://pluvo.io/blog/ai-pilot-post-mortem-template) (Finance; by Vanessa Galarneau; published 2026-08-03): Turn a failed finance AI pilot into an evidence-backed decision with a copyable post-mortem record for causes, controls, owners, and restart gates.
- [Multi-Entity Consolidation With AI: A Control Ledger for the Close](https://pluvo.io/blog/multi-entity-consolidation-automation-ai) (Finance; by Vanessa Galarneau; published 2026-08-02): A practical control framework for automating multi-entity consolidation across currencies, fiscal calendars, chart mappings, and intercompany eliminations.
- [What CFOs Should Stop Hiring For](https://pluvo.io/blog/what-cfos-should-stop-hiring-for) (Finance; by Vanessa Galarneau; published 2026-08-01): Current evidence points to finance task redesign, not wholesale job disappearance. Use a vacancy-level framework to hire judgment and system ownership.
- [The Future of the Finance Function: From Reporting to Reasoning](https://pluvo.io/blog/future-of-finance-function) (Finance; by Vanessa Galarneau; published 2026-07-31): AI can compress finance report production. The harder change is redesigning the function around causal diagnosis, scenarios, controls, and accountable decisions.
- [AI Cash Flow Forecasting: A 13-Week Workflow for QuickBooks and NetSuite](https://pluvo.io/blog/ai-cash-flow-forecasting-quickbooks-netsuite) (Finance; by Vanessa Galarneau; published 2026-07-30): Build a controlled 13-week AI cash forecast from QuickBooks or NetSuite data, with traceable assumptions, weekly error tracking, and human review.
- [10 Questions to Ask AI Vendors About Accuracy](https://pluvo.io/blog/questions-to-ask-ai-vendors-accuracy) (Finance; by Vanessa Galarneau; published 2026-07-29): Use a 10-question answer decoder to test an AI vendor's accuracy claims, evidence, change controls, human authority, and failure handling.
- [When ChatGPT Is Enough for Finance, and When to Upgrade](https://pluvo.io/blog/chatgpt-vs-finance-ai-tools) (Finance; by Vanessa Galarneau; published 2026-07-28): Use a cost-and-control decision rule to choose ChatGPT or purpose-built finance AI, including a verifier-hours break-even calculation.
- [Best AI FP&A Software in 2026: An Architecture-First Buyer's Guide](https://pluvo.io/blog/best-ai-fpa-software-buyers-guide-2026) (Finance; by Vanessa Galarneau; published 2026-07-27): Compare AI FP&A software by working surface, calculation engine, governed context, lineage, permissions, and a 100-point live-demo scorecard.
- [The 7 AI Failure Modes Finance Teams Should Test First](https://pluvo.io/blog/ai-finance-risks-failure-modes) (Finance; by Vanessa Galarneau; published 2026-07-26): Diagnose seven AI finance failure modes by symptom, five-minute test, stop condition, architectural root cause, and accountable human owner.
- [AI Board Reporting: Build a Board Pack That Can Answer Why](https://pluvo.io/blog/ai-board-reporting) (Finance; by Vanessa Galarneau; published 2026-07-25): A governed board-question chain lets AI assemble evidence, decompose drivers, draft commentary, and build scenarios without handing the model authority over the numbers.
- [AI Audit Trails in Finance: Six Questions an AI-Touched Workpaper Should Answer](https://pluvo.io/blog/ai-audit-trail-finance) (Finance; by Vanessa Galarneau; published 2026-07-23): A six-question evidence packet helps finance preserve the source, method, configuration, review, change history, and independent testing path behind AI-touched analysis.
- [AI and the Monthly Close: What You Can Automate in 2026](https://pluvo.io/blog/ai-monthly-close-automation-2026) (Finance; by Vanessa Galarneau; published 2026-07-22): A nine-step monthly-close matrix shows what AI can automate, where it should assist, and which accounting judgments must stay human.
- [What Is a Semantic Layer for Finance Data? Why ERP Data Alone Isn't One](https://pluvo.io/blog/semantic-layer-finance-data) (Finance; by Vanessa Galarneau; published 2026-07-21): A finance semantic layer defines metrics, grain, joins, periods, currency, access, and lineage once so every tool and AI system uses the same meaning.
- [AI Governance Checklist for Finance: 15 Controls Before You Trust a Tool](https://pluvo.io/blog/ai-governance-checklist-finance) (Finance; by Alex Labrèche; published 2026-07-20): Use this 15-point checklist to test whether a finance AI workflow produces reproducible results, traceable evidence, governed access, and reviewable decisions before it moves beyond a demo.
- [Automate Variance Analysis: From 6 Hours to 20 Minutes](https://pluvo.io/blog/automate-variance-analysis-runbook) (Finance; by Vanessa Galarneau; published 2026-07-19): Use this eight-step runbook to automate variance analysis across finance and operating systems without losing lineage, controls, or human judgment.
- [AI Flux Analysis: A 7-Step Workflow for Close](https://pluvo.io/blog/ai-flux-analysis-workflow) (Finance; by Vanessa Galarneau; published 2026-07-18): Run AI flux analysis with finance-owned thresholds, reconciled driver bridges, transaction evidence, residual stop rules, and human sign-off.
- [Is Your Finance Data Ready for AI? A 12-Point Checklist](https://pluvo.io/blog/ai-ready-finance-data-checklist) (Finance; by Vanessa Galarneau; published 2026-07-17): Use this 12-point checklist to test whether finance data is AI-ready across source scope, period logic, mappings, definitions, lineage, access, and ownership.
- [ChatGPT Can Do Financial Analysis. It Cannot Own the Answer.](https://pluvo.io/blog/chatgpt-financial-analysis-control-boundary) (Finance; by Vanessa Galarneau; published 2026-07-16): ChatGPT can analyze spreadsheets and run code. Finance still needs approved definitions, reconciliations, lineage, and a named owner behind every material answer.
- [How to Become a Finance Engineer: Three 90-Day Paths](https://pluvo.io/blog/how-to-become-a-finance-engineer) (Finance; by Vanessa Galarneau; published 2026-07-15): FP&A, accounting, and data professionals can use this 90-day plan to build one controlled finance workflow and a portfolio that proves the work.
- [Why LLMs Hallucinate Financial Numbers: A Two-System Control Pattern](https://pluvo.io/blog/why-llms-hallucinate-financial-numbers) (Finance; by Vanessa Galarneau; published 2026-07-14): LLMs can generate plausible numbers without a controlled calculation. This two-system pattern is designed to keep material figures computed, traceable, and reviewable.
- [Will AI Replace FP&A Analysts? The Honest Answer](https://pluvo.io/blog/will-ai-replace-fpa-analysts) (Finance; by Vanessa Galarneau; published 2026-07-13): AI will automate more FP&A production work, but the evidence points to task change, not wholesale replacement. Here is what stays valuable.
- [FP&A Analyst vs. Finance Engineer: What Actually Changes](https://pluvo.io/blog/fpa-analyst-vs-finance-engineer) (Finance; by Vanessa Galarneau; published 2026-07-13): This operating-model lens compares the same FP&A deliverables: produce each analysis, or also improve the governed system behind the next run.
- [The Finance Engineer Skill Stack: A 60-Point Self-Assessment](https://pluvo.io/blog/finance-engineer-skills-self-assessment) (Finance; by Vanessa Galarneau; published 2026-07-12): Score 20 finance engineer skills across LLM literacy, automation, data fluency, and systems integration, then choose the next workflow to build.
- [AI Finance Agent vs. Copilot: What Can CFOs Trust?](https://pluvo.io/blog/ai-finance-agent-vs-copilot) (Finance; by Vanessa Galarneau; published 2026-07-11): AI copilots help finance teams draft and explore. AI finance agents execute bounded workflows. Learn the controls CFOs need before trusting either.

## Glossary terms

- [13-week cash flow forecast](https://pluvo.io/glossary/13-week-cash-flow-forecast) (aliases 13-week cash flow, thirteen-week cash flow forecast, 13 week cash flow model; topics cash flow, treasury, liquidity, restructuring; by Pluvo Team; published 2026-06-28; updated 2026-06-29): A 13-week cash flow forecast is a rolling weekly direct-method forecast that projects near-term cash receipts, disbursements, and liquidity over roughly one quarter. For 13-week cash flow forecast, the useful boundary is the cash source, timing horizon, owner, liquidity exposure, and decision before options narrow.
- [Account reconciliation](https://pluvo.io/glossary/account-reconciliation) (aliases reconciliation, GL reconciliation, balance sheet reconciliation; topics the close, reconciliation, controllership; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Account reconciliation is the practice of matching an account balance to supporting source data and resolving any differences. For account reconciliation, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Accounting cutoff](https://pluvo.io/glossary/accounting-cutoff) (aliases cutoff, period cutoff, cut-off; topics the close, controllership, audit; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accounting cutoff is the rule that transactions are recorded in the correct period, a frequent source of close and audit errors. For accounting cutoff, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Accounts payable](https://pluvo.io/glossary/accounts-payable) (aliases AP, trade payables, payables; topics AP/AR, cash, controllership; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accounts payable represents amounts a company owes suppliers for goods and services received but not yet paid. For accounts payable, the useful boundary is the source cash view, timing horizon, owner, liquidity exposure, and operating decision before payment timing, runway, or financing options change.
- [Accounts receivable](https://pluvo.io/glossary/accounts-receivable) (aliases AR, trade receivables, receivables; topics AP/AR, cash, controllership; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accounts receivable represents amounts customers owe a company for goods and services delivered but not yet collected. For accounts receivable, the useful boundary is the source cash view, timing horizon, owner, liquidity exposure, and operating decision before payment timing, runway, or financing options change.
- [Accounts receivable aging](https://pluvo.io/glossary/accounts-receivable-aging) (aliases AR aging, accounts receivable aging report, aging schedule, aged receivables, debtor aging; topics accounts receivable, working capital, collections; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accounts receivable aging is a report that groups unpaid customer invoices by how long they have been outstanding, usually in current, 30, 60, 90, and over-90-day buckets. For accounts receivable aging, the useful boundary is the cash source, timing horizon, owner, liquidity exposure, and decision before options narrow.
- [Accounts receivable collections](https://pluvo.io/glossary/accounts-receivable-collections) (aliases collections, AR collections, receivables collection, cash collections, debtor collection; topics accounts receivable, working capital, collections; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accounts receivable collections refers to the process of converting open customer invoices into cash by prioritizing outreach, resolving disputes, and tracking how collection work affects DSO and liquidity. For accounts receivable collections, the useful boundary is the cash source, timing horizon, owner, liquidity exposure, and decision before options narrow.
- [Accrual reversal](https://pluvo.io/glossary/accrual-reversal) (aliases reversing entry, reversing journal entry; topics the close, bookkeeping, accounting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accrual reversal is an entry that backs out a prior-period accrual in the following period so the actual is not double-counted. For accrual reversal, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Accrual vs cash basis accounting](https://pluvo.io/glossary/accrual-vs-cash-basis-accounting) (aliases cash vs accrual accounting, basis of accounting; topics accounting fundamentals, revenue recognition, financial reporting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accrual vs cash basis accounting is the difference between recognizing revenue and expenses when earned or incurred versus when cash moves. For accrual vs cash basis accounting, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Accruals](https://pluvo.io/glossary/accruals) (aliases accrued expenses, accrued liabilities, accrual accounting entries; topics the close, accounting fundamentals, revenue recognition; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accruals are accounting entries that recognize revenue or expenses in the period they are earned or incurred, before cash changes hands. For accruals, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Accrued revenue](https://pluvo.io/glossary/accrued-revenue) (aliases unbilled revenue, accrued income, contract asset; topics revenue recognition, the close, balance sheet; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Accrued revenue is revenue earned but not yet billed or collected, recorded as an asset until invoicing catches up. For accrued revenue, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Adjusted EBITDA](https://pluvo.io/glossary/adjusted-ebitda) (aliases normalized EBITDA, adj. EBITDA; topics profitability, EBITDA, non-GAAP measures, valuation; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Adjusted EBITDA is EBITDA adjusted for one-time, non-cash, or non-recurring items to normalize operating performance across periods or companies. For adjusted EBITDA, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Adjusting journal entry](https://pluvo.io/glossary/adjusting-journal-entry) (aliases AJE, adjusting entry, adjustment entry; topics the close, bookkeeping, accounting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Adjusting journal entry is an entry made at period end to record accruals, deferrals, depreciation, or corrections before reporting. For adjusting journal entry, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Agent memory](https://pluvo.io/glossary/agent-memory) (aliases AI agent memory, long-term memory; topics AI in finance, AI agents, AI infrastructure; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Agent memory is information an AI agent stores or retrieves across steps or sessions so it can maintain context while working toward a goal. For agent memory, the useful boundary is the data, tools, approvals, human review, evaluation standard, and decision the system may influence.
- [Agentic AI](https://pluvo.io/glossary/agentic-ai) (aliases agentic artificial intelligence; topics AI in finance, agentic AI, AI agents; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Agentic AI is artificial intelligence that can plan, choose tools, and take multi-step actions toward a goal with limited human supervision. For agentic AI, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [Agentic finance](https://pluvo.io/glossary/agentic-finance) (aliases agentic AI in finance, autonomous finance, agentic FP&A; topics AI agents, AI in finance, finance automation, AI-native software; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Agentic finance is the practice of using autonomous AI agents to perceive, plan, and execute multi-step finance tasks with limited human intervention. For agentic finance, the useful boundary is the data, tools, approvals, human review, evaluation standard, and decision the system may influence.
- [Agentic workflow](https://pluvo.io/glossary/agentic-workflow) (aliases agent workflow, AI agent workflow; topics AI in finance, agentic AI, finance automation; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Agentic workflow is a multi-step process executed by AI agents that plan, act, and adapt. For agentic workflow, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI accuracy](https://pluvo.io/glossary/ai-accuracy) (aliases model accuracy, AI output accuracy; topics AI in finance, data accuracy, AI reliability; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI accuracy is the degree to which an AI system produces correct, reliable outputs for a defined task, data set, and evaluation standard. For AI accuracy, the useful boundary is the data, tools, approvals, human review, evaluation standard, and decision the system may influence.
- [AI agent](https://pluvo.io/glossary/ai-agent) (aliases intelligent agent, LLM agent; topics AI in finance, AI agents, agentic AI; by Pluvo Team; published 2026-06-28; updated 2026-06-29): An AI agent is a system that can perceive context, choose tools, plan steps, and take actions toward a defined goal. For AI agent, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI copilot](https://pluvo.io/glossary/ai-copilot) (aliases copilot, AI assistant; topics AI in finance, AI agents, natural language interfaces; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI copilot is an assistant that augments a human's work in context. For AI copilot, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI evaluation](https://pluvo.io/glossary/ai-evaluation) (aliases AI evals, LLM evaluation, model evaluation; topics AI in finance, model evaluation, AI reliability; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI evaluation is systematically testing and scoring model or system outputs against benchmarks or ground truth. For AI evaluation, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI finance infrastructure](https://pluvo.io/glossary/ai-finance-infrastructure) (aliases AI infrastructure for finance, finance AI infrastructure; topics AI in finance, data infrastructure, finance engineering, AI-native software; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI finance infrastructure is the foundational AI systems, data connections, and compute layer that support AI-driven finance workflows. For AI finance infrastructure, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI governance](https://pluvo.io/glossary/ai-governance) (aliases AI risk management, AI oversight; topics AI in finance, AI governance, AI trust; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI governance is the policies, controls, and accountability over how AI is used, including cost, risk, and compliance. For AI governance, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI guardrails](https://pluvo.io/glossary/ai-guardrails) (aliases LLM guardrails, model guardrails; topics AI in finance, AI governance, AI security; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI guardrails are constraints, checks, and policies that keep model behavior within safe, intended bounds for a defined finance workflow. For AI guardrails, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI hallucination in finance](https://pluvo.io/glossary/ai-hallucination-in-finance) (aliases financial AI hallucination, hallucinated financial numbers; topics AI in finance, AI trust, data accuracy; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI hallucination in finance is when an AI system outputs a confident but fabricated or incorrect financial figure, why it happens, and the reporting risk it creates. For AI hallucination in finance, the useful boundary is the data, tools, approvals, human review, evaluation standard, and decision the system may influence.
- [AI orchestration](https://pluvo.io/glossary/ai-orchestration) (aliases agent orchestration, LLM orchestration; topics AI in finance, AI orchestration, AI agents; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI orchestration is coordinating multiple models, agents, and tools with routing, shared state, and governance. For AI orchestration, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI transparency](https://pluvo.io/glossary/ai-transparency) (aliases model transparency, algorithmic transparency; topics AI in finance, AI governance, AI trust; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI transparency is disclosing how an AI system works, what data it uses, and its limits. For AI transparency, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [AI-native finance](https://pluvo.io/glossary/ai-native-finance) (aliases AI-first finance, AI-native finance function; topics AI in finance, finance transformation, AI-native software, finance engineering; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI-native finance is finance functions and tools built around AI and automation from the ground up rather than added onto legacy processes. For AI-native finance, the useful boundary is the data, tools, approvals, human review, evaluation standard, and decision the system may influence.
- [AI-native FP&A](https://pluvo.io/glossary/ai-native-fp-a) (aliases AI-native financial planning and analysis, AI-first FP&A; topics FP&A, AI in finance, finance transformation, AI-native software; by Pluvo Team; published 2026-06-28; updated 2026-06-29): AI-native FP&A is the practice of reimagining financial planning and analysis around AI agents and automation rather than manual planning processes. For AI-native FP&A, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [Amortization](https://pluvo.io/glossary/amortization) (aliases amortisation, intangible amortization; topics accounting fundamentals, intangible assets, GAAP; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Amortization is allocating the cost of an intangible asset, or a loan principal, over time as a periodic charge. For amortization, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Annual Contract Value](https://pluvo.io/glossary/annual-contract-value) (aliases ACV, annualized contract value; topics SaaS metrics, bookings & billings, contracts; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Annual contract value is the recurring value of a customer contract normalized to one year, typically excluding one-time fees and usage outside the contract term. For annual contract value, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Annual operating plan](https://pluvo.io/glossary/annual-operating-plan) (aliases AOP, annual budget, operating plan; topics planning, budgeting, FP&A; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Annual operating plan is the detailed one-year financial and operational plan that sets targets and budgets. For annual operating plan, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
- [Annual Recurring Revenue](https://pluvo.io/glossary/annual-recurring-revenue) (aliases ARR; topics SaaS metrics, recurring revenue, ARR; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Annual recurring revenue is the annualized value of committed recurring subscription revenue, excluding one-time fees and non-recurring services. For annual recurring revenue, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, recognition rules, churn, expansion, pricing, or usage behavior.
- [API integration](https://pluvo.io/glossary/api-integration) (aliases API-based integration, application programming interface integration; topics data integration, data infrastructure, finance systems; by Pluvo Team; published 2026-06-28; updated 2026-06-29): API integration is the practice of connecting two or more software systems through their application programming interfaces so they can exchange data or trigger actions automatically. For API integration, a useful definition states connecting two or more software systems through their application programming interfaces so they can exchange data or trigger, who owns it, and which decision it supports.
- [Append-only ledger](https://pluvo.io/glossary/append-only-ledger) (aliases append-only log, write-once ledger; topics audit & governance, data integrity, data infrastructure; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Append-only ledger is a data structure that only permits adding new records, never updating or deleting existing ones, preserving full history. For append-only ledger, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [ARR bridge](https://pluvo.io/glossary/arr-bridge) (aliases MRR bridge, ARR walk, ARR roll-forward, ARR waterfall; topics SaaS metrics, ARR, growth accounting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): ARR bridge is a roll-forward that decomposes the change in ARR from one period to the next into new, expansion, contraction, and churned ARR. For ARR bridge, the important details are the period, source evidence, reviewer, threshold, and control purpose that make the treatment auditable.
- [ARR growth rate](https://pluvo.io/glossary/arr-growth-rate) (aliases MRR growth rate, recurring revenue growth, ARR growth; topics SaaS metrics, growth, ARR; by Pluvo Team; published 2026-06-28; updated 2026-06-29): ARR growth rate is the year-over-year or period-over-period percentage change in ARR, how it is calculated, and its role in efficiency rules like Rule of 40. For ARR growth rate, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [ARR per employee](https://pluvo.io/glossary/arr-per-employee) (aliases revenue per employee, ARR per FTE, ROSE; topics SaaS metrics, operational efficiency, ARR; by Pluvo Team; published 2026-06-28; updated 2026-06-29): ARR per employee is ARR divided by full-time headcount as a measure of operational efficiency, and typical benchmark ranges by stage. For ARR per employee, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, recognition rules, churn, expansion, pricing, or usage behavior.
- [As-of reporting](https://pluvo.io/glossary/as-of-reporting) (aliases as-of date reporting, as-at reporting; topics financial reporting, temporal data, audit & governance; by Pluvo Team; published 2026-06-28; updated 2026-06-29): As-of reporting is the practice of retrieving or presenting data as it existed as of a specified date, on either an effective-date or as-recorded basis. For as-of reporting, the important details are the period, source evidence, reviewer, threshold, and control purpose that make the treatment auditable.
- [ASC 606](https://pluvo.io/glossary/asc-606) (aliases IFRS 15, revenue from contracts with customers, Topic 606; topics accounting standards, revenue recognition, GAAP; by Pluvo Team; published 2026-06-28; updated 2026-06-29): ASC 606 is the FASB/IASB standard governing revenue from contracts with customers and its five-step model. For ASC 606, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Assertion time](https://pluvo.io/glossary/assertion-time) (aliases decision time, knowledge time, belief time; topics temporal data, bitemporal data, data modeling; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Assertion time is a proposed third temporal dimension recording when a fact was asserted or believed, distinct from valid and transaction time. For assertion time, a useful definition states a proposed third temporal dimension recording when a fact was asserted or believed, distinct from valid and transaction, who owns it, and which decision it supports.
- [Audit trail](https://pluvo.io/glossary/audit-trail) (aliases audit log, audit trace; topics audit & governance, compliance, accounting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Audit trail is a chronological, tamper-evident record of every change and action affecting data, enabling reconstruction of how a result was reached. For audit trail, the important details are the period, source evidence, reviewer, threshold, and control purpose that make the treatment auditable.
- [Auditability](https://pluvo.io/glossary/auditability) (aliases audit readiness, auditable systems; topics audit & governance, compliance, data integrity; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Auditability is the degree to which a system's outputs can be independently traced, verified, and explained by an auditor. For auditability, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Autonomous agent](https://pluvo.io/glossary/autonomous-agent) (aliases fully autonomous agent, autonomous AI agent; topics AI in finance, AI agents, agentic AI; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Autonomous agent is an agent that acts toward goals with minimal or no human approval. For autonomous agent, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [Average Revenue Per Account](https://pluvo.io/glossary/average-revenue-per-account) (aliases ARPA, ARPU, ARPC, average revenue per user, average revenue per customer; topics SaaS metrics, unit economics, pricing; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Average revenue per account is the average recurring revenue generated per account or user, how it is calculated, and its role as an input to LTV. For average revenue per account, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Average sales price](https://pluvo.io/glossary/average-sales-price) (aliases ASP, average selling price, average deal size; topics SaaS metrics, sales efficiency, pricing; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Average sales price is the average value of a closed deal, how it differs from ACV, and why it shapes go-to-market motion and CAC payback. For average sales price, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Balance sheet](https://pluvo.io/glossary/balance-sheet) (aliases statement of financial position; topics financial statements, financial reporting, accounting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Balance sheet is the statement showing assets, liabilities, and equity at a point in time. For balance sheet, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Balanced scorecard](https://pluvo.io/glossary/balanced-scorecard) (aliases BSC; topics performance management, strategic finance, KPIs; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Balanced scorecard is a strategy framework tracking performance across financial and non-financial perspectives. For balanced scorecard, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support. For balanced scorecard, the practical standard is making the driver, assumption, and owner visible when actuals change.
- [Bank reconciliation](https://pluvo.io/glossary/bank-reconciliation) (aliases bank rec, cash reconciliation; topics the close, reconciliation, cash; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Bank reconciliation is the practice of reconciling the cash balance per the books to the bank statement and explaining timing differences. For bank reconciliation, the useful boundary is the source cash view, timing horizon, owner, liquidity exposure, and operating decision before payment timing, runway, or financing options change.
- [Beyond Budgeting](https://pluvo.io/glossary/beyond-budgeting) (aliases beyond budgeting model; topics planning, budgeting, FP&A; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Beyond budgeting is a management model that replaces fixed annual budgets with adaptive, decentralized planning. For beyond budgeting, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
- [Billings](https://pluvo.io/glossary/billings) (aliases invoiced revenue, amounts invoiced; topics SaaS metrics, bookings & billings, revenue recognition; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Billings are invoices issued or amounts billed to customers during a period, distinct from bookings, recognized revenue, and cash collections. For billings, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, recognition rules, churn, expansion, pricing, or usage behavior.
- [Bitemporal data](https://pluvo.io/glossary/bitemporal-data) (aliases bitemporal modeling, bitemporality, bitemporal data model; topics data modeling, temporal data, audit & governance, financial data; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Bitemporal data is modeling data along two independent time axes—valid time and transaction time—to capture both what was true and what was known when. For bitemporal data, the important details are the period, source evidence, reviewer, threshold, and control purpose that make the treatment auditable.
- [Blended CAC](https://pluvo.io/glossary/blended-cac) (aliases blended customer acquisition cost, all-in CAC; topics SaaS metrics, unit economics, customer acquisition; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Blended CAC is CAC across all channels including organic, versus paid CAC from paid media only, and when each view is appropriate. For blended CAC, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Blended margin](https://pluvo.io/glossary/blended-margin) (aliases blended gross margin, weighted average margin; topics margins, profitability, unit economics, product mix; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Blended margin is a single margin figure averaged across multiple products, segments, or channels, and why it can mask underlying mix. For blended margin, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, recognition rules, churn, expansion, pricing, or usage behavior.
- [Board reporting package](https://pluvo.io/glossary/board-reporting-package) (aliases board deck, board reporting, board package; topics management reporting, board reporting, FP&A; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Board reporting package is the standardized set of financials and metrics prepared for a board meeting. For board reporting package, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
- [Bookings](https://pluvo.io/glossary/bookings) (aliases new bookings, sales bookings; topics SaaS metrics, bookings & billings, revenue; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Bookings are signed customer commitments recorded during a period, often used as a forward-looking indicator before billings, cash collection, or revenue recognition. For bookings, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Bottom-up forecasting](https://pluvo.io/glossary/bottom-up-forecasting) (aliases bottoms-up forecasting, bottom-up planning; topics forecasting, FP&A, planning; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Bottom-up forecasting is building a forecast from granular unit-, rep-, or transaction-level inputs aggregated upward. For bottom-up forecasting, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
- [Breakeven analysis](https://pluvo.io/glossary/breakeven-analysis) (aliases break-even analysis, break-even point, cost-volume-profit analysis; topics unit economics, profitability, managerial accounting, cost structure; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Breakeven analysis is the practice of calculating the sales volume or revenue at which total contribution margin covers fixed costs and profit is zero. For breakeven analysis, the important details are the period, source evidence, reviewer, threshold, and control purpose that make the treatment auditable.
- [Bridge chart](https://pluvo.io/glossary/bridge-chart) (aliases waterfall chart, bridge analysis, walk chart; topics data visualization, financial analysis, FP&A; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Bridge chart is a chart decomposing the movement between two values into additive and subtractive steps. For bridge chart, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
- [Budget cycle](https://pluvo.io/glossary/budget-cycle) (aliases budgeting cycle, planning cycle; topics budgeting, planning, FP&A; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Budget cycle is the practice of recurring sequence of steps to build, approve, and monitor a budget. For budget cycle, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
- [Budget vs actual](https://pluvo.io/glossary/budget-vs-actual) (aliases BvA, budget to actual, actual vs budget; topics FP&A, variance analysis, management reporting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Budget vs actual is comparing budgeted figures to actual results to surface and act on variances. For budget vs actual, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
- [Burn multiple](https://pluvo.io/glossary/burn-multiple) (aliases net burn multiple; topics SaaS metrics, capital efficiency, growth efficiency; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Burn multiple is net cash burned per dollar of net new ARR added, what the ranges signal by stage, and how it captures growth efficiency. For burn multiple, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Burn rate](https://pluvo.io/glossary/burn-rate) (aliases cash burn rate, monthly burn, cash burn; topics burn, liquidity, startup finance; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Burn rate is the pace at which a company spends cash over a period, usually measured as gross burn or net burn to assess runway and financing needs. For burn rate, the useful boundary is the cash source, timing horizon, owner, liquidity exposure, and decision before options narrow.
- [CAC payback period](https://pluvo.io/glossary/cac-payback-period) (aliases CAC payback, months to recover CAC, payback period; topics SaaS metrics, unit economics, sales efficiency; by Pluvo Team; published 2026-06-28; updated 2026-06-29): CAC payback period is the number of months to recover CAC, the simple versus gross-margin-adjusted formulas, and benchmark ranges by motion and ACV. For CAC payback period, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Canonical metric](https://pluvo.io/glossary/canonical-metric) (aliases governed metric, certified metric; topics data governance, metrics, semantic layer; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Canonical metric is a single governed definition of a business metric that serves as the authoritative way it is calculated everywhere it appears. For canonical metric, a useful definition states a single governed definition of a business metric that serves as the authoritative way it is calculated everywhere, who owns it, and which decision it supports.
- [Capacity planning](https://pluvo.io/glossary/capacity-planning) (aliases resource capacity planning; topics planning, operations, FP&A; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Capacity planning is the practice of matching available resources or capacity to forecasted demand. For capacity planning, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support. For capacity planning, the practical standard is making the driver, assumption, and owner visible when actuals change.
- [Capex vs opex](https://pluvo.io/glossary/capex-vs-opex) (aliases capital vs operating expenditure, capex versus opex; topics accounting fundamentals, fixed assets, financial reporting; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Capex vs opex is the distinction between capitalized expenditures carried on the balance sheet and costs expensed in the period. For capex vs opex, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Capitalization](https://pluvo.io/glossary/capitalization) (aliases capitalize vs expense, cost capitalization, capitalization policy; topics accounting fundamentals, fixed assets, GAAP; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Capitalization is recording a cost as an asset rather than an immediate expense, and the threshold policy that governs it. For capitalization, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Cash conversion cycle](https://pluvo.io/glossary/cash-conversion-cycle) (aliases CCC, cash cycle, net operating cycle; topics working capital, cash flow, liquidity; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Cash conversion cycle measures how many days it takes to turn inventory and receivables into cash after accounting for supplier-payment timing. For cash conversion cycle, the useful boundary is the source cash view, timing horizon, owner, liquidity exposure, and operating decision before payment timing, runway, or financing options change.
- [Cash flow forecasting](https://pluvo.io/glossary/cash-flow-forecasting) (aliases cash flow forecast, cash forecasting, cash projection; topics cash flow, forecasting, treasury, liquidity; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Cash flow forecasting is the process of projecting future cash inflows and outflows over a defined horizon to anticipate liquidity needs. For cash flow forecasting, the useful boundary is the source cash view, timing horizon, owner, liquidity exposure, and operating decision before payment timing, runway, or financing options change.
- [Cash position](https://pluvo.io/glossary/cash-position) (aliases net cash position, current cash position; topics cash flow, treasury, liquidity; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Cash position is the total cash available to a company at a point in time, consolidated across bank accounts, payment processors, and other liquid cash sources. For cash position, the useful boundary is the cash source, timing horizon, owner, liquidity exposure, and decision before options narrow.
- [Cash runway](https://pluvo.io/glossary/cash-runway) (aliases runway, startup runway, financial runway, months of runway; topics burn, liquidity, startup finance, fundraising; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Cash runway is the number of months a company can keep operating before it runs out of cash, usually calculated as cash balance divided by net burn. For cash runway, the useful boundary is the cash source, timing horizon, owner, liquidity exposure, and decision before options narrow.
- [Certified finance engineer](https://pluvo.io/glossary/certified-finance-engineer) (aliases finance engineering certification; topics finance engineering, finance careers, professional certification, AI in finance; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Certified finance engineer refers to a credentialed finance professional who can combine accounting, FP&A, automation, data systems, and AI-enabled workflows in a governed way. For certified finance engineer, the useful boundary is the data, tools, approvals, human review, evaluation standard, and decision the system may influence.
- [Chain-of-thought](https://pluvo.io/glossary/chain-of-thought) (aliases chain-of-thought prompting, CoT, step-by-step reasoning; topics AI in finance, prompting, AI trust; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Chain-of-thought is a model reasoning step by step before answering. For chain-of-thought, the useful boundary is the data it uses, the tools it can call, the approvals it needs, the review standard, and the finance decision it may influence before the output is trusted or automated.
- [Change data capture](https://pluvo.io/glossary/change-data-capture) (aliases CDC, change-data-capture; topics data pipelines, data integration, data infrastructure; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Change data capture is a technique that detects and streams row-level changes from a source database so downstream systems stay in sync without full reloads. For change data capture, a useful definition states a technique that detects and streams row-level changes from a source database so downstream systems stay in sync, who owns it, and which decision it supports.
- [Chart of accounts](https://pluvo.io/glossary/chart-of-accounts) (aliases COA, account structure; topics general ledger, accounting, account structure; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Chart of accounts is the structured, numbered list of every account a company uses to record transactions. For chart of accounts, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Churn rate](https://pluvo.io/glossary/churn-rate) (aliases attrition rate, customer attrition; topics SaaS metrics, churn, retention; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Churn rate is the rate at which customers or revenue are lost over a period, the customer-versus-revenue and gross-versus-net distinctions, and how it is measured. For churn rate, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Churned ARR](https://pluvo.io/glossary/churned-arr) (aliases lost ARR, churn ARR; topics SaaS metrics, ARR, churn; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Churned ARR is the annualized recurring revenue lost to full customer churn in a period, and its place in the ARR bridge. For churned ARR, the useful boundary is whether the movement comes from customers, contracts, billing, cash timing, or recognition rules.
- [Close checklist](https://pluvo.io/glossary/close-checklist) (aliases financial close checklist, month-end checklist; topics the close, controllership, workflow; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Close checklist is the structured list of tasks, owners, and sign-offs that governs the period-end close. For close checklist, the important details are the accounting period, source evidence, reviewer, materiality threshold, and control purpose that make the treatment auditable during close, reporting, and later review.
- [Close cycle time](https://pluvo.io/glossary/close-cycle-time) (aliases days to close, time to close, close duration; topics the close, controllership, performance management; by Pluvo Team; published 2026-06-28; updated 2026-06-29): Close cycle time is the number of business days it takes to finalize the books after period end, a core close KPI. For close cycle time, the important details are the period, source evidence, reviewer, threshold, and control purpose that make the treatment auditable.

## Resources

- No published, indexable resources are currently available.

## Integrations

- [CSV](https://pluvo.io/integrations/csv) (live; data-sources): Finance file source
- [Custom API](https://pluvo.io/integrations/api) (live; data-sources): Internal system source
- [Databricks](https://pluvo.io/integrations/databricks) (live; warehouse): Finance data platform
- [Google Sheets](https://pluvo.io/integrations/google-sheets) (live; data-sources): Finance file source
- [Mercury](https://pluvo.io/integrations/mercury) (live; banking): Business banking source
- [Microsoft Excel](https://pluvo.io/integrations/excel) (live; data-sources): Finance file source
- [NetSuite](https://pluvo.io/integrations/netsuite) (live; erp): Finance ERP platform
- [Plaid](https://pluvo.io/integrations/plaid) (live; banking): Bank connectivity source
- [Postgres](https://pluvo.io/integrations/postgres) (live; warehouse): Finance data platform
- [QuickBooks Online](https://pluvo.io/integrations/quickbooks) (live; accounting): Cloud accounting platform
- [Sage Intacct](https://pluvo.io/integrations/sage-intacct) (live; erp): Finance ERP platform
- [SFTP](https://pluvo.io/integrations/sftp) (live; data-sources): Scheduled file drops
- [Snowflake](https://pluvo.io/integrations/snowflake) (live; warehouse): Finance data platform
- [Stripe](https://pluvo.io/integrations/stripe) (live; billing): Revenue billing platform
- [Workday Adaptive Planning](https://pluvo.io/integrations/adaptive-planning) (live; data-sources): Planning forecast source
- [Xero](https://pluvo.io/integrations/xero) (live; accounting): Cloud accounting platform
- [ADP](https://pluvo.io/integrations/adp) (beta; payroll): Workforce payroll system
- [Bill.com](https://pluvo.io/integrations/bill-com) (beta; expense): Spend management platform
- [Brex](https://pluvo.io/integrations/brex) (beta; expense): Spend management platform
- [Deel](https://pluvo.io/integrations/deel) (beta; payroll): Workforce payroll system
- [Gusto](https://pluvo.io/integrations/gusto) (beta; payroll): Workforce payroll system
- [HubSpot](https://pluvo.io/integrations/hubspot) (beta; crm): Revenue CRM platform
- [Maxio](https://pluvo.io/integrations/maxio) (beta; billing): Revenue billing platform
- [Microsoft Dynamics 365 Business Central](https://pluvo.io/integrations/dynamics-365-business-central) (beta; erp): Finance ERP platform
- [Microsoft Dynamics 365 Finance & Operations](https://pluvo.io/integrations/dynamics-365-finance-operations) (beta; erp): Finance ERP platform
- [Microsoft Dynamics 365 Sales](https://pluvo.io/integrations/dynamics-365-sales) (beta; crm): Revenue CRM platform
- [Ramp](https://pluvo.io/integrations/ramp) (beta; expense): Spend management platform
- [Rippling](https://pluvo.io/integrations/rippling) (beta; payroll): Workforce payroll system
- [Salesforce](https://pluvo.io/integrations/salesforce) (beta; crm): Revenue CRM platform
- [Shopify](https://pluvo.io/integrations/shopify) (beta; ecommerce): Commerce revenue channel
- [Square](https://pluvo.io/integrations/square) (beta; pos): POS revenue system
- [Toast](https://pluvo.io/integrations/toast) (beta; pos): POS revenue system
- [WooCommerce](https://pluvo.io/integrations/woocommerce) (beta; ecommerce): Commerce revenue channel
- [Workday Financials](https://pluvo.io/integrations/workday-financials) (beta; erp): Finance ERP platform
- [Workday HCM](https://pluvo.io/integrations/workday-hcm) (beta; payroll): Workforce payroll system
- [Acumatica](https://pluvo.io/integrations/acumatica) (planned; erp): Finance ERP platform
- [Adobe Commerce](https://pluvo.io/integrations/adobe-commerce) (planned; ecommerce): Commerce revenue channel
- [Adyen](https://pluvo.io/integrations/adyen) (planned; billing): Revenue billing platform
- [Airbase](https://pluvo.io/integrations/airbase) (planned; expense): Spend management platform
- [Amazon Redshift](https://pluvo.io/integrations/redshift) (planned; warehouse): Finance data platform
- [Amazon Seller Central](https://pluvo.io/integrations/amazon-seller-central) (planned; ecommerce): Commerce revenue channel
- [BambooHR](https://pluvo.io/integrations/bamboohr) (planned; payroll): Workforce payroll system
- [BigCommerce](https://pluvo.io/integrations/bigcommerce) (planned; ecommerce): Commerce revenue channel
- [Braintree and PayPal](https://pluvo.io/integrations/braintree-paypal) (planned; billing): Revenue billing platform
- [Brightpearl](https://pluvo.io/integrations/brightpearl) (planned; supply-chain): Inventory operations system
- [Campfire](https://pluvo.io/integrations/campfire) (planned; erp): Modern finance ERP
- [Chargebee](https://pluvo.io/integrations/chargebee) (planned; billing): Revenue billing platform
- [Cin7](https://pluvo.io/integrations/cin7) (planned; supply-chain): Inventory operations system
- [Clari](https://pluvo.io/integrations/clari) (planned; crm): Revenue CRM platform
- [Clear Books](https://pluvo.io/integrations/clear-books) (planned; accounting): Cloud accounting platform
- [Close](https://pluvo.io/integrations/close) (planned; crm): Revenue CRM platform
- [Cloudbeds](https://pluvo.io/integrations/cloudbeds) (planned; pos): POS revenue system
- [Clover](https://pluvo.io/integrations/clover) (planned; pos): POS revenue system
- [Cogsy](https://pluvo.io/integrations/cogsy) (planned; supply-chain): Inventory operations system
- [Copper](https://pluvo.io/integrations/copper) (planned; crm): Revenue CRM platform
- [Coupa](https://pluvo.io/integrations/coupa) (planned; expense): Spend management platform
- [eBay](https://pluvo.io/integrations/ebay) (planned; ecommerce): Commerce revenue channel
- [Epicor](https://pluvo.io/integrations/epicor) (planned; erp): Finance ERP platform
- [Etsy](https://pluvo.io/integrations/etsy) (planned; ecommerce): Commerce revenue channel
- [Expensify](https://pluvo.io/integrations/expensify) (planned; expense): Spend management platform

## Livestreams

- [Finance Engineering 101](https://pluvo.io/livestreams/finance-engineering-101) (onDemand; Finance Engineering; hosted by Vanessa Galarneau; scheduled 2026-07-29): Pluvo CFO Vanessa Galarneau breaks down finance engineering: what it is, why finance teams are adopting it, and how to start turning your team into builders.
- [AI Crash Course](https://pluvo.io/livestreams/ai-crash-course-nyc) (upcoming; In person; hosted by Vanessa Galarneau): An in-person AI crash course in NYC for women in banking and investing, co-hosted by Pluvo’s Vanessa Galarneau with Merge and Rillet.
- [AI for Finance: Building with Claude + Excel, MCP, and more! \(NYC\)](https://pluvo.io/livestreams/ai-for-finance-nyc-tech-week-june-2026) (onDemand; In person; hosted by Pluvo & BMO; scheduled 2026-06-04): An NYC Tech Week working session with Pluvo and BMO on applying AI across forecasting, reporting, and decision support.
- [AI for Finance: Pluvo, Claude + Excel, MCP & more! \(Ottawa\)](https://pluvo.io/livestreams/ai-for-finance-nyc-tech-week-may-2026) (onDemand; In person; hosted by Pluvo; scheduled 2026-05-26): A hands-on NYC Tech Week workshop on putting AI to work in finance with Claude, Excel, and MCP.

## Customer stories

- No published, indexable customer stories are currently available.