FlowRunner
PricingContact
Theme
Start Free

Dynamics 365 Business Central

ERP

Connect AI agents to Dynamics 365 Business Central. Agents manage customers, vendors, and items, create and post sales invoices and orders, record general journal lines, and sync purchase documents across 45 accounting actions.

45 actions OAuth available
A paid order arrives from the storefront
List Customers filters on email to resolve the buyer against the company
Create Customer registers the buyer when no match exists
Create Sales Invoice drafts the invoice with lines referencing catalog item numbers
The agent compares draft totals, tax groups, and payment terms against the order payload
The controller approves the draft, because posting writes ledger entries that cannot be undone
Post Sales Invoice finalizes the document and creates the G/L, customer, and inventory entries
The posted invoice number and totals report to the finance channel

What This Integration Enables

Dynamics 365 Business Central is a system of record in the strict sense: once a document posts, the ledger entries it creates are permanent. That is not a limitation to automate around, it is the design that makes the ERP trustworthy, and it dictates how automation should work here. FlowRunner agents do everything up to the point of no return at machine speed, and put the point of no return in front of a person. Agents manage customers, vendors, and items, draft and post sales invoices, create sales orders and quotes, sync purchase invoices and purchase orders from procurement tools, and stage general journal lines against the chart of accounts, across 45 actions scoped to the company you designate. - Drafts are cheap and reversible in Business Central, so agents prepare aggressively and post conservatively - OData filtering, paging, and expansion let agents read exactly the records a decision needs - Reference lookups for accounts, payment terms, tax groups, and dimensions keep coding correct at write time - Post Sales Invoice, the irreversible step, sits behind a [human-in-the-loop](/concepts/human-in-the-loop) gate

Without FlowRunner

The ERP is fed by hand Orders, payments, and vendor bills get rekeyed into Business Central days after the fact
Posting anxiety slows everything Because posting is permanent, every entry waits for a senior person to find time to key it themselves
Side systems drift from the ledger The storefront catalog, the CRM customer list, and the item master disagree by a little more every week

With FlowRunner

Documents arrive as drafts, ready to post Agents assemble invoices, orders, and journal lines with the right accounts and dimensions attached
Posting is an approval, not a chore A person reviews the prepared batch and authorizes the irreversible step; the agent does everything around it
Master data syncs continuously Customers, vendors, and items stay aligned with source systems through matched, incremental updates

Use Case Scenarios

Storefront sales that reach the ledger the same day

Orders arrive from [Shopify](/integrations/shopify). For each one the agent resolves the buyer with List Customers, creates the customer if new, and calls Create Sales Invoice with lines referencing the mapped item numbers. Each morning the controller reviews the draft batch in a [Slack](/integrations/slack) digest showing totals, tax groups, and any customer the agent created. On approval, the agent calls Post Sales Invoice per document. Revenue recognition stops trailing the storefront by a week.

Payment receipts staged as journal lines, coded correctly

When [Stripe](/integrations/stripe) settles a payout, the agent reads the payout composition, looks up the right G/L accounts with List Accounts and the reporting dimensions with List Dimensions, and calls Create Journal Line for each component: gross receipts, processor fees, refunds. The lines land unposted in the designated journal, so the accountant reviews the staged batch inside Business Central and posts it there. The agent never touches the ledger directly; it just makes the ledger's inbox perfect.

Procurement documents that match themselves

Purchase requests approved in the spend tool become Create Purchase Order calls, with vendors resolved through List Vendors. When the vendor's invoice arrives by email, the agent extracts the details, finds the matching order with List Purchase Orders, and drafts a Create Purchase Invoice with the order's lines. Clean matches queue for routine approval; quantity or price mismatches route to the buyer with both documents side by side. The AP team reviews exceptions instead of typing everything.

Human-in-Loop Highlight

Post Sales Invoice is the action this connector treats with respect: posting finalizes the document and writes general ledger, customer, and inventory entries that cannot be undone. Reversing a bad post means correcting entries, credit memos, and an audit trail that permanently records the mistake. So no FlowRunner agent posts on its own judgment. The agent drafts the invoice, validates lines and tax groups, and presents the batch: "Fourteen drafts ready. Twelve match orders exactly. Two have customers created today from storefront data. Post all, or hold the two?" The controller answers, and only approved documents cross the line. Everything before the post is fast and fixable; the post itself belongs to a person.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

45 actions

Companies

2
  • List Companies Retrieves all companies in the connected environment. Each company GUID scopes every other operation.
  • Get Company Information Retrieves the company information record: legal name, address, tax registration, currency, and contacts.

Customers

5
  • List Customers Retrieves customers with OData filtering, sorting, field selection, and paging. The resolution step behind every sales flow.
  • Get Customer Retrieves a single customer by GUID, optionally expanding default dimensions or financial details.
  • Create Customer Creates a customer with sensible defaults from company configuration. Only displayName is strictly required.
  • Update Customer Updates writable properties of a customer; only provided fields change.
  • Delete Customer Permanently deletes a customer by GUID. Fails if posted transactions or open documents prevent deletion.

Vendors

5
  • List Vendors Retrieves vendors with OData filtering, sorting, and paging.
  • Get Vendor Retrieves a single vendor by GUID with optional expansions.
  • Create Vendor Creates a vendor; only displayName is strictly required.
  • Update Vendor Updates writable properties of a vendor; only provided fields change.
  • Delete Vendor Permanently deletes a vendor by GUID. Fails if posted transactions or open documents prevent deletion.

Items

5
  • List Items Retrieves items (products and services) with OData filtering, sorting, and paging.
  • Get Item Retrieves a single item by GUID, optionally expanding the picture or default dimensions.
  • Create Item Creates an item typed as Inventory, Service, or Non-Inventory, with unit of measure and tax group linked by ID.
  • Update Item Updates writable properties of an item; only provided fields change.
  • Delete Item Permanently deletes an item by GUID. Fails if posted transactions or inventory prevent deletion.

Sales Invoices

6
  • List Sales Invoices Retrieves sales invoices with filtering, paging, and optional expansion of lines and customer. Drafts are editable; posted invoices are read-only.
  • Get Sales Invoice Retrieves a single invoice by GUID with lines and customer expanded by default.
  • Create Sales Invoice Creates a draft invoice for a customer, with lines referencing items, accounts, or resources by number.
  • Update Sales Invoice Updates header properties of a draft invoice. Posted invoices cannot be edited.
  • Delete Sales Invoice Deletes a draft invoice. Posted invoices cannot be deleted.
  • Post Sales Invoice Posts a draft invoice, creating the G/L, customer, and inventory entries. Posting cannot be undone; this page's human gate exists for it.

Sales Orders

5
  • List Sales Orders Retrieves sales orders with filtering, paging, and optional line expansion.
  • Get Sales Order Retrieves a single order by GUID with lines and customer expanded by default.
  • Create Sales Order Creates a sales order for a customer, optionally with line items.
  • Update Sales Order Updates header properties of a sales order; only provided fields change.
  • Delete Sales Order Deletes a sales order. Fails if posted shipments or invoices prevent deletion.

Sales Quotes

4
  • List Sales Quotes Retrieves sales quotes with filtering, paging, and optional line expansion.
  • Get Sales Quote Retrieves a single quote by GUID with lines and customer expanded by default.
  • Create Sales Quote Creates a sales quote that can later be converted to an order or invoice in Business Central.
  • Delete Sales Quote Deletes a sales quote by GUID.

Purchase Invoices

3
  • List Purchase Invoices Retrieves purchase invoices (vendor bills) with filtering, paging, and optional line expansion.
  • Get Purchase Invoice Retrieves a single purchase invoice by GUID with lines and vendor expanded by default.
  • Create Purchase Invoice Creates a draft purchase invoice for a vendor, with lines referencing items, accounts, or resources by number.

Purchase Orders

3
  • List Purchase Orders Retrieves purchase orders with filtering, paging, and optional line expansion.
  • Get Purchase Order Retrieves a single purchase order by GUID with lines and vendor expanded by default.
  • Create Purchase Order Creates a purchase order for a vendor, optionally with line items.

General Ledger

4
  • List Accounts Retrieves the chart of accounts with number, name, category, and posting or heading status.
  • List Journals Retrieves the general journal batches defined in a company.
  • List Journal Lines Retrieves the unposted debit and credit lines in a specific journal.
  • Create Journal Line Creates an unposted journal line against a G/L account, with amount, posting date, and optional balancing account. Staged, never posted, by the agent.

Reference Data

3
  • List Payment Terms Retrieves payment terms with due date calculations and discount settings.
  • List Tax Groups Retrieves the tax groups that classify items and resources for tax calculation.
  • List Dimensions Retrieves analysis dimensions such as Department or Project, optionally with their values, for transaction categorization.

Frequently Asked Questions

What can FlowRunner do with Dynamics 365 Business Central?

FlowRunner agents can run List Companies, Get Company Information, and List Customers in Dynamics 365 Business Central, plus 42 more actions.

Does connecting Dynamics 365 Business Central to FlowRunner require OAuth?

Yes. Dynamics 365 Business Central connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Dynamics 365 Business Central trigger a FlowRunner workflow automatically?

Dynamics 365 Business Central doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Dynamics 365 Business Central

$100 in credits. No card required. Connect in minutes.