Trex can close the books
because Trex is the books.
Many finance “copilots” are chatbots wrapped around an integration. Trex has the same database access, the same RBAC, and the same audit trail as your accountant.
What Trex actually does.
Understand
Recommend
Answer
Explain
Summarise
Watch it work.
Scripted examples of the flow you’d see in the product. Names and numbers are illustrative.
Model orchestration, automated.
Override per session.
- ▸Cost-aware routing. Cheap models for INTENT_PARSE, stronger models for REPLY_SYNTHESIS. You don’t pay Claude Opus rates to summarise an invoice.
- ▸Per-session override. Force a specific provider for sensitive sessions (e.g. financial close on Claude only).
- ▸Fallback chain. If primary fails JSON validation, we try secondary providers. Your accountant doesn’t see the retry.
- ▸Your data stays yours. Requests go to Anthropic and Mistral under their no-train terms. We route, we don’t train.
The most useful thing about an in-ledger agent is that we know exactly where it can act. Here’s the rule sheet — as the agent sees it.
Post anything to your books without your approval. Every Trex action is a proposal. You approve it, or it doesn’t happen.
Touch a hard-closed period. Blocked. Period reopen requires admin and audit entry.
Create a vendor and pay them in one session. Vendor creation is a separate approval gate. By design.
Send anything outside your tenant. Tenant-isolated. Trex cannot read data outside your schema.
Change the COA structure. Restricted to admin roles. Trex can suggest, not commit.
Train on your data. Pass-through to LLM providers under their no-train terms. We do not fine-tune on customer data.
Watch Trex on your own books.
Bring a Tally XML export. We’ll spin up a tenant, import the data, and walk Trex through your month.