Agent context
Netvisor models
4 SQL models that turn the raw Netvisor tables into the reports people ask about. Deploy them in Weld and your agent queries the definitions behind every number.
How the set is built
- 2Raw tables
- 3Staging
- 5Core
- 4Analytics
Staging cleans each raw table once, core holds the logic, and analytics is the table dashboards and agents read.
- General ledgerThe general ledger (pääkirja): every line of every valid voucher, with its account's report line. Recreates the transaction list behind Netvisor's ledger reports.grain: one row per voucher line (voucher_key x line_index) · 1 raw table
- Payables agingAccounts payable aging (ostoreskontra, avoimet ostolaskut): every purchase invoice with an unpaid amount, bucketed by days past due as of today.grain: one row per open purchase invoice · 1 raw table
- Profit and loss by monthIncome statement by month (tuloslaskelma kuukausittain), at account level with the report line alongside so it can be rolled up in BI.grain: one row per month x account, income statement accounts only (3000-9999 in the default ranges of staging.netvisor.finnish_account_groups) · 1 raw table
- Trial balance by monthTrial balance per month (saldoluettelo): for every account and month, the opening balance, the month's debits and credits, and the closing balance.grain: one row per month x account, from the first month with a synced voucher to the current month (or the latest future-dated month), including months in which an account had no postings · 1 raw table
- Weld or dbt
- The same SQL in both dialects. Sync the folder with GitHub Sync, or copy the dbt models into your project.
- Check before you rely on it
- Reconcile a month against Netvisor's own reports first. Each model's notes say what the synced data can and can't support.
Connect Netvisor.
Your agents start with context.
Sync Netvisor to your warehouse, deploy these models, and query them from Claude, Cursor or ChatGPT over MCP. Free for 14 days, no credit card.