Fortnox to Microsoft SQL Server integration
Connect Fortnox to Microsoft SQL Server and automatically sync your finance & accounting data. Weld extracts data from Fortnox, loads it into Microsoft SQL Server, and lets you transform the data using SQL or dbt, no custom scripts required.
Source
WarehouseSourceFortnoxConnected- invoices100 cols
- employees74 cols
- customers70 cols
- articles47 cols
- suppliers43 cols
- supplier_invoices39 cols
- Extract
- Load
- Keep in sync
DestinationMicrosoft SQL ServerReady- fortnox.invoicesSynced
- fortnox.employeesSyncing
- fortnox.customersSynced
- fortnox.articlesSynced
- fortnox.suppliersSynced
- fortnox.supplier_invoicesSynced
- Fortnox tables
- 23
- fields, typed
- 533
- agent context included
- MCP
Trusted by data and AI teams
How to set up Fortnox to Microsoft SQL Server in Weld.
In the app, with the API or an agent.
New connectionFortnoxAuthorisedWhy sync Fortnox to Microsoft SQL Server?
Ready for analysis.
Centralizing your Fortnox data in Microsoft SQL Server lets you join it with other data sources for cross-platform analytics and deeper insights.
Build reliable dashboards and reports by querying Fortnox data directly in Microsoft SQL Server using SQL or your preferred BI tool.
Financial reporting
Centralize financial data from Fortnox in Microsoft SQL Server for automated financial dashboards and month-end close analysis.
Centralized data warehouse
Bring Fortnox data into Microsoft SQL Server alongside other sources to create a single source of truth for your organization.
Automated reporting
Replace manual exports and spreadsheet-based reporting with automated pipelines from Fortnox to Microsoft SQL Server. Connect BI tools like Looker, Metabase, or Power BI.
What data can you sync?
Every Fortnox table, keys intact.
Weld syncs the objects the Fortnox connector exposes into Microsoft SQL Server, and you choose which tables and fields to include. The connector's docs list what is available.
- invoices
- employees
- customers
- articles
- suppliers
- supplier_invoices
- invoices_invoice_rows
- supplier_invoice_rows
- accounts
- voucher_rows
- vouchers
- currencies
- employee_children
- financial_years
- voucher_series
- cost_centers
- employees_dated_schedules
- expenses
- terms_of_deliveries
- units
- way_of_deliveries
- terms_of_payments
- tax_reductions
Ask your agent.
It queries Microsoft SQL Server for you.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Fortnox context, finds the tables it needs and runs the query in Microsoft SQL Server.
How many invoices rows do we have in Microsoft SQL Server?
Reading the Fortnox context first, so the query uses the right tables and keys.
Technical considerations.
What to expect.
- Incremental syncing
- Weld uses incremental syncing where supported by the Fortnox API, loading only new and updated records to minimize data transfer and warehouse costs.
- Schema handling
- Weld automatically manages schema changes. If Fortnox adds new fields, they're detected and added to the corresponding Microsoft SQL Server tables.
- Data freshness
- Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
- Security
- All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
Keep reading.
Guides, docs and schema.
Fortnox setup guide
How to connect Fortnox to Weld, step by step.
DocumentationMicrosoft SQL Server setup guide
How to connect Microsoft SQL Server to Weld, step by step.
SchemaFortnox schema explorer
Browse all 23 tables and 533 fields.
ConnectorFortnox connector
Everything Weld does with Fortnox.
Common questions.
About Fortnox to Microsoft SQL Server.
Start syncing Fortnox to Microsoft SQL Server.
Set up your Fortnox data pipeline in minutes. No credit card required. Free for 14 days.
SourceWarehouse
