What Balsa does
Understand the product, its users, and the boundary between evidence, judgment, and calculation.
Browse documentation
On this page
Balsa is an evidence-backed financial model that continuously reconciles what happened, what is expected, and what each decision changes. Its recurring question is: How is the business progressing toward its goals, and what should change?
The initial user is a founder managing finance. A CFO should be able to inspect the same inputs, correct the accounting, own the exceptions, and preserve a review without rebuilding the model elsewhere.
The operating loop
- Bring in statements, accounting exports, contracts, invoices, and supporting notes.
- Review extracted facts, source identity, mappings, and proposed accounting.
- Establish starting cash and the coverage of imported activity.
- Set a cash goal and preserve an approved plan.
- Capture expected obligations, reconcile actual payments, and review the remaining forecast.
- Explain changes, compare decisions, and preserve ownership and sign-off.
The first pass is described in Your first financial review. Subsequent imports and decisions run through the same loop.
Three kinds of state
| Layer | What it contains | How to use it |
|---|---|---|
| Evidence | Original files, normalized rows, extracted facts, source references | Inspect what a source actually says |
| Company state | Approved agreements, obligations, assumptions, policies and decisions | Review the business interpretation |
| Financial state | Journals, schedules, balances, statements and forecast calculations | Inspect what follows mathematically |
Language models propose interpretations and explanations. Deterministic code validates journals and calculates reported results. A fluent answer does not replace an approved fact or a supported calculation.
Find your work
These paths belong to your Balsa application, not this documentation site.
| Application page | Purpose |
|---|---|
/ |
Evidence, conversations, accounting and model work |
/progress |
Primary goal, current outlook, guided review, starting cash and weekly cash |
/goals |
Draft and active goals, primary selection, preserved plans and reviews |
/reconciliation |
Expectations, actual allocations, recurring schedules and coverage |
/imports |
Compare imports and approve their financial effects |
/goal-decisions |
Evaluate scenarios, approve decisions and review outcomes |
/reviews |
Accuracy, named cases, exception ownership and sign-off |
Product boundaries
The planning workflow focuses on a company’s reporting currency, month-end cash targets, and cash floors. Dated weekly cash adds timing visibility. The accounting engine has broader entity and currency functionality; that does not mean every planning workflow supports those cases.
Direct provider integrations and an ERP-replacement claim are outside this direction. Files and reviewed exports are valid inputs. Balsa does not require replacing the systems that generated them.
The application is under active development for supervised evaluation. Read Supported scope for the distinction between implemented controls and assurance they cannot provide.