Weld
Start free

Fourth to Microsoft SQL Server integration

Connect Fourth to Microsoft SQL Server and automatically sync your finance & accounting data. Weld extracts data from Fourth, loads it into Microsoft SQL Server, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for freeView setup guide
4.8 on G2
FourthSource
WeldWeld
Microsoft SQL ServerWarehouse
Weld · New sync
FourthSourceFourthConnected
Tables to sync
  • employee36 cols
  • payroll22 cols
  • employment45 cols
  • shift36 cols
  • shift_forecast36 cols
  • employee_payslip26 cols
  • Extract
  • Load
  • Keep in sync
Microsoft SQL ServerDestinationMicrosoft SQL ServerReady
fourth schema
  • fourth.employeeSynced
  • fourth.payrollSyncing
  • fourth.employmentSynced
  • fourth.shiftSynced
  • fourth.shift_forecastSynced
  • fourth.employee_payslipSynced
Fourth tables
33
fields, typed
565
relationships kept
17
agent context included
MCP

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Fourth to Microsoft SQL Server in Weld.
In the app, with the API or an agent.

Setup guideAPI guideMCP docs
Weld · New Fourth sync
FourthNew connectionFourthAuthorised
Connection namefourth
AuthorizeOpens Fourth to grant read access
Use cases

Why sync Fourth to Microsoft SQL Server?
Ready for analysis.

Centralizing your Fourth 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 Fourth data directly in Microsoft SQL Server using SQL or your preferred BI tool.

  • Financial reporting

    Centralize financial data from Fourth in Microsoft SQL Server for automated financial dashboards and month-end close analysis.

  • Centralized data warehouse

    Bring Fourth 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 Fourth to Microsoft SQL Server. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Fourth table, keys intact.

Weld syncs the objects the Fourth connector exposes into Microsoft SQL Server, and you choose which tables and fields to include. The connector's docs list what is available.

Open the schema explorer
All 33 tables
  • employee
  • payroll
  • employment
  • shift
  • shift_forecast
  • employee_payslip
  • payroll_forecast
  • employee_next_of_kin
  • employee_pay_part
  • employee_address
  • employee_payment_details
  • employee_absence
  • employee_document
  • employee_accrual
  • staff_skill
  • employee_payroll_period
  • employee_passport
  • employee_country_specific
  • contractor_shift
  • fixed_task
  • minimum_staffing
  • budget
  • sales
  • sales_forecast
  • employee_import_log
  • sales_type
  • labour_daily_summary
  • productivity_analysis
  • fixed_cost
  • employee_location
  • and 3 more
Weld MCP server

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 Fourth context, finds the tables it needs and runs the query in Microsoft SQL Server.

Set up the MCP serverClaudeCursorChatGPTGemini
Claude CodeOpus 5
>

How many employee rows do we have per employee? Use our Fourth data in Microsoft SQL Server.

Reading the Fourth context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.fourth.employee
raw.fourth.employee
+ 31 more Fourth tables
●weld·get_reference_schema
⎿employee · 36 columns
joins employee on employee_id
●weld·run_query
⎿select j.id, count(*) from {{raw.fourth.employee}} e
join {{raw.fourth.employee}} j on e.employee_id = j.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Fourth data in Microsoft SQL Server
>Ask about your Fourth data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the Fourth API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Fourth 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.
Resources

Keep reading.
Guides, docs and schema.

Documentation

Fourth setup guide

How to connect Fourth to Weld, step by step.

Documentation

Microsoft SQL Server setup guide

How to connect Microsoft SQL Server to Weld, step by step.

Schema

Fourth schema explorer

Browse all 33 tables and 565 fields.

Connector

Fourth connector

Everything Weld does with Fourth.

FAQ

Common questions.
About Fourth to Microsoft SQL Server.

Start syncing Fourth to Microsoft SQL Server.

Set up your Fourth data pipeline in minutes. No credit card required. Free for 14 days.

FourthSource
WeldWeld
Microsoft SQL ServerWarehouse
Start for freeTalk to us
Related

Related integrations.
More with Fourth and Microsoft SQL Server.

View all