Microsoft Business Central to PostgreSQL integration

Connect Microsoft Business Central to PostgreSQL and automatically sync your finance & accounting data. Weld extracts General Ledger, Customers, Vendors, and Items from Microsoft Business Central, loads them into PostgreSQL, and lets you transform the data using SQL or dbt, no custom scripts required.

4.8 on G2
Microsoft Business CentralSource
WeldWeld
PostgreSQLWarehouse
Weld · New sync
Microsoft Business CentralSourceMicrosoft Business CentralConnected
Tables to sync
  • company10 cols
  • customer31 cols
  • account11 cols
  • item19 cols
  • currency9 cols
  • vendor24 cols
  • Extract
  • Load
  • Keep in sync
PostgreSQLDestinationPostgreSQLReady
business_central schema
  • business_central.companySynced
  • business_central.customerSyncing
  • business_central.accountSynced
  • business_central.itemSynced
  • business_central.currencySynced
  • business_central.vendorSynced
Microsoft Business Central tables
92
fields, typed
1,475
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 Microsoft Business Central to PostgreSQL in Weld.
In the app, with the API or an agent.

Weld · New Microsoft Business Central sync
Microsoft Business CentralNew connectionMicrosoft Business CentralAuthorised
Connection namebusiness_central
AuthorizeOpens Microsoft Business Central to grant read access
Use cases

Why sync Microsoft Business Central to PostgreSQL?
Ready for analysis.

Centralizing your Microsoft Business Central data in PostgreSQL lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying Microsoft Business Central data directly in PostgreSQL using SQL or your preferred BI tool.

  • Financial reporting

    Centralize General Ledger, Customers, and Vendors from Microsoft Business Central in PostgreSQL for automated financial dashboards and month-end close analysis.

  • Centralized data warehouse

    Bring Microsoft Business Central data into PostgreSQL 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 Microsoft Business Central to PostgreSQL. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Microsoft Business Central table, keys intact.

Weld syncs the following data objects from Microsoft Business Central into PostgreSQL. The exact tables and fields depend on your Microsoft Business Central configuration and the permissions granted during setup.

Open the schema explorer
All 92 tables
  • company
  • customer
  • account
  • item
  • currency
  • vendor
  • unit_of_measure
  • item_variant
  • shipment_method
  • sales_order_lines
  • sales_invoice_lines
  • purchase_credit_memo_line
  • sales_quote_lines
  • sales_credit_memo
  • purchase_order_lines
  • purchase_invoice_lines
  • sales_credit_memo_lines
  • location
  • sales_invoice
  • sales_order
  • sales_quote
  • purchase_order
  • purchase_credit_memo
  • purchase_invoice
  • customer_payment
  • vendor_payment
  • fixed_asset
  • default_dimension
  • journal
  • dimension_value
  • and 62 more
Weld MCP server

Ask your agent.
It queries PostgreSQL for you.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Microsoft Business Central context, finds the tables it needs and runs the query in PostgreSQL.

Claude CodeOpus 5
>

How many customer rows do we have per tax_area? Use our Microsoft Business Central data in PostgreSQL.

Reading the Microsoft Business Central context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.business_central.customer
raw.business_central.tax_area
+ 90 more Microsoft Business Central tables
●weld·get_reference_schema
⎿customer · 31 columns
joins tax_area on tax_area_id
●weld·run_query
⎿select t.id, count(*) from {{raw.business_central.customer}} c
join {{raw.business_central.tax_area}} t on c.tax_area_id = t.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Microsoft Business Central data in PostgreSQL
>Ask about your Microsoft Business Central data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the Microsoft Business Central API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Microsoft Business Central adds new fields, they're detected and added to the corresponding PostgreSQL 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.
FAQ

Common questions.
About Microsoft Business Central to PostgreSQL.

Start syncing Microsoft Business Central to PostgreSQL.

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

Microsoft Business CentralSource
WeldWeld
PostgreSQLWarehouse