Skip to content
SAP Business One
SAP Business One
Mid-market ERPAvailable via the partner API

Connect SAP Business One with TAC Flow

Sync assets and cost centers and post operating expenses via the Service Layer.

01Overview

Requirements

Requirements

  • SAP Business One 10.0 with the Service Layer enabled
  • A TAC Flow API key with the required scopes
  • A developer or the system implementer at your company

Scopes used

assets:readmaintenance:readfuel:readmeters:read

First: issue an API key from Settings → Integrations — it will be used to read from TAC Flow.

02What syncs

Where your data lands

  • Asset register (equipment & vehicles)From TAC FlowFixed-asset register
  • Approved maintenance costsFrom TAC FlowExpense entries on cost centers
  • Fuel and diesel costsFrom TAC FlowOperating-expense entries
  • Meter readingsFrom TAC FlowUsage-based depreciation
03Setup steps

The setup, start to finish

Executed by your technical team or your system implementer — typical effort is one working day.

  1. 1Issue the API keyFrom TAC Flow Settings → Integrations, issue a key with the required read scopes and save it — it is shown only once.
  2. 2Create a scheduled sync jobIn SAP Business One, create a job that periodically reads the partner API endpoints with incremental sync, per the reference examples.
  3. 3Map the cost centersMap TAC Flow internal asset numbers to your cost centers or assets — once, at setup time.
  4. 4Enable entry postingTurn the maintenance and fuel costs you read into classified entries on your cost centers.
  5. 5Verify and monitorCompare the first batch against TAC Flow reports and watch the usage log in the Integrations screen.
04FAQ

Asked before implementation

Who implements the integration?

Your technical team or your system implementer — this guide plus the technical reference cover everything needed; typical effort is one working day.

Does the external system write into TAC Flow?

No — the partner API is read-only in its current version, which makes the integration inherently safe: no external mistake can corrupt your data.

Ready to integrate?

The full technical reference with runnable examples — your developer starts in minutes.