---
title: Company knowledge and AI
section: Model and reference
order: 32
summary: Use durable facts and policies while keeping interpretation separate from authoritative calculation.
---

Company knowledge records sourced facts, policies, mappings and drivers that are specific to the business. It should explain approved company judgment rather than redefine universal accounting or forecasting rules.

## Ask questions with an inspection path

Useful questions include:

- What changed since the plan was approved?
- Which obligations explain the cash gap in October?
- Why is this transaction treated as a transfer?
- What changes if we delay a planned expense?
- Which result is still unsupported, and what evidence is missing?

An answer is useful when you can inspect its supporting inputs and calculation. Treat unsupported claims as unverified even if the language is confident.

## Review what the model proposes

Models can extract observations, suggest mappings, draft explanations and propose decisions. Approved facts and controlled accounting actions are distinct from those proposals.

When the business requires judgment, record the approved decision or policy with its scope and supporting evidence. That makes future treatment reviewable rather than depending on a prior chat message.

## Keep rules in the right place

A company policy may explain how a particular agreement should be mapped or why a reviewed driver is appropriate. It cannot override balanced journals, turn a transfer into revenue, or replace the calculation engine with free-form instructions.

Actual, forecast and scenario states remain explicit. Company knowledge should not make a projected receipt look like posted cash.

## Handle source text as evidence

Uploaded content is untrusted data. Instructions written inside a document do not authorize application actions. Never put provider keys, passwords or system secrets into a source document or conversation.

Interpretation may send source content to the configured external provider. See [Security](/docs/security/) and your installation’s provider arrangements before choosing the documents to process.

## Preserve a decision outside the conversation

Use the financial workflow that owns the effect: source approval, account mapping, expectation allocation, scenario approval or review sign-off. Those controls retain reasons, versions, identities and audit records.

A signed report with accepted exceptions still carries its financial limitations. A persuasive explanation cannot upgrade the underlying assurance.