Business Central

Documentation Index

Fetch the complete documentation index at: https://usepike.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Pike is a professional services automation (PSA) platform: delivery, time, resources, and project economics live here. Microsoft Dynamics 365 Business Central is your ERP: quotes, sales orders, inventory, and posted finance often start there. A strong BC ↔ PSA integration does not duplicate the ERP—it hands off confirmed commercial work into delivery, keeps identifiers aligned for audit and support, and syncs the finance entities you already use in Pike for reporting and operations. The Business Central integration is designed around that pattern: what is sold and committed in Business Central becomes structured delivery work in Pike, with ongoing sync for customers, catalog data, and invoices so both systems stay coherent.

​

1. Connecting Business Central with Pike

1. Go to Workspace settings → Integrations → Business Central
2. Click Add integration
3. Complete the steps in the flow to connect and authorise your Business Central environment (tenant and company) for Pike

​

2. Importing Business Central data into Pike

​

Sync schedule

You control how often data is pulled from Business Central:

• Manual: Use Import data on the integration page (or Refresh on individual records) whenever you want an immediate update.
• Automatic: Set the schedule in the Business Central integration settings. By default, sync runs once every 24 hours. You can adjust that interval in settings where your workspace allows.
• Higher frequency: If you need sync more often than the defaults support, contact Pike support—we can increase frequency on request.

Direction and rules mirror how we document other accounting integrations (for example QuickBooks): Pike shows what is linked, Refresh pulls the latest from the source system, and last synced timestamps help you see freshness.

​

Customers

• Customers are synced from Business Central to Pike.
• Typical mapping includes Business Central customer name and customer number (and related contact or address fields where configured) into Pike’s customer record.
• Synced customers are identifiable in Pike (for example via integration tagging) with last synced and Refresh on the customer, consistent with QuickBooks-style behaviour.

​

Items and products

• Items (and where relevant resources used as sellable lines) from Business Central align with products in Pike for quoting, invoicing, and line-level reporting.
• When synchronising product catalog data, treat Business Central as the definition source for item numbers, descriptions, and default posting behaviour unless your workspace rules say otherwise.
• Product visibility and manual refresh follow the same patterns as other integrations: Finance-related settings and product lists show sync state and Refresh where supported.

​

Invoices and credit memos

• Posted sales documents from Business Central (for example posted sales invoices and posted sales credit memos) can be represented in Pike so you see customer, amounts, dates, and line context alongside projects and customers.
• Field mapping follows the same spirit as QuickBooks: customer and product links are maintained when those entities are synced; tax and currency behaviour respects what Business Central has posted.
• Once a document is fully owned by the accounting side, edits to financial detail generally happen in Business Central; Pike focuses on visibility, allocation to projects, and operational reporting—aligned with QuickBooks notes on source of truth.

​

Vendor documents (where enabled)

• Where your workspace uses purchase or vendor flows, bills or purchase documents from Business Central can surface in Pike similarly to Bills in the QuickBooks integration: supplier, amounts, dates, and line descriptions—with the same idea that line detail may be summarised for display while totals stay accurate.

​

3. Sales orders → projects (order number → project number)

The core handoff is sales order to project:

• Each sales order in Business Central becomes a project in Pike.
• The sales order number—the document No. on the sales order in Business Central—maps to the project number in Pike.

That gives you a single, stable line of reference from SO-… (or your number series) through delivery: time, tasks, and financial views in Pike stay tied to the same identifier operations and finance already use in BC.

​

4. ERP + PSA: what this integration is for

A typical Business Central ↔ PSA setup looks like this: The integration does not replace BC for GL posting or inventory. It does:

• Create and maintain projects from sales orders with matching numbers for traceability.
• Keep customers and sellable items aligned so invoices and project work reference the same entities.
• Expose posted invoice (and bill) data in Pike for dashboards and customer/project context.

That is the same class of capability enterprises expect when they connect an ERP to any PSA: one commercial truth in the ERP, one delivery truth in the PSA, and explicit mapping between them.

​

5. Synced entity management

For entities that are connected to Business Central, Pike surfaces:

• A Refresh action to pull the latest data from Business Central
• Last synced date and time

​

Source of truth

As with QuickBooks, once an entity is governed by the integration:

• Catalog and customer master data should be updated in Business Central when that system is your system of record.
• Posted financial documents are driven by what is posted in Business Central; Pike reflects them for visibility and assignment (for example linking spend or revenue to the right project).

Exception (delivery in Pike): Even when finance details are controlled in Business Central, you can still assign or reassign projects in Pike where the product allows—so delivery structure stays useful for reporting without fighting the ERP.