How does ml-connector handle SAP Business One's 30-minute session timeout?

ml-connector maintains and reuses active B1SESSION tokens to minimize latency and API calls. When a token expires (error code -5002), it logs in fresh rather than pre-emptively refreshing. This strategy reduces cold-start overhead while ensuring the connector stays authenticated across polling intervals.

What happens if a transaction already exists in TaxJar and ml-connector tries to post it again?

TaxJar returns HTTP 422 when a transaction duplicate is detected. ml-connector falls back to PUT /transactions/{id} to update the existing record. If the transaction does not exist in TaxJar, PUT returns 404 and ml-connector falls back to POST to create it. This idempotency pattern allows retries without data loss or duplicate records.

How are customer tax exemptions handled across SAP Business One and TaxJar?

ml-connector reads the exemption status and exemption type from SAP Business One's BusinessPartners master data and maps those to TaxJar's /customers endpoint. TaxJar gives precedence to customer-level exemptions, which override line-item exemptions, so the mapping respects both systems' hierarchies for accurate tax-exempt reporting.

SAP Business OneTaxJar

SAP Business One and TaxJar integration

SAP Business One manages your financials, sales orders, and inventory on-premise. TaxJar calculates sales tax liability and automates state tax filing. Connecting the two keeps your transaction records in TaxJar aligned with what you invoice in SAP Business One, so your tax calculations are always current and your compliance filings are accurate. Sales orders, invoice amounts, shipping addresses, and line-item detail flow from SAP Business One into TaxJar automatically, eliminating manual entry and reconciliation.

How SAP Business One works

SAP Business One exposes sales invoices, purchase invoices, customers (BusinessPartners), items, and transaction line details through OData v4 REST at a customer-specific on-premise Service Layer URL (e.g. https://<customer-server>:50001/b1s/v2/). Authentication is session-token-based via POST /Login returning a B1SESSION cookie that expires after 30 minutes of inactivity. SAP Business One supports webhooks for Create/Update/Delete events (v10.0 FP 2602 and later) if the Webhook Messenger Service is enabled, but webhooks require SAP administrator setup. Polling with OData $filter on UpdateDate is the default integration pattern, and users must ensure the Service Layer port is accessible from the connector.

How TaxJar works

TaxJar is a cloud REST API at https://api.taxjar.com/v2/ that accepts JSON transaction payloads and returns calculated tax liability. Authentication is token-based via the Authorization header (Bearer or Token format). TaxJar exposes endpoints for real-time tax calculations (POST /taxes), transaction reporting (POST /transactions/orders and PUT for updates), refund reporting (POST /transactions/refunds), and lookups such as tax rates by zip code and nexus region management. TaxJar does not support webhooks or push events; all integration is polling or merchant-initiated POST. The sandbox environment is stateless and validates request format only.

What moves between them

Sales invoices and line items flow from SAP Business One into TaxJar. After invoicing or at a scheduled interval, ml-connector reads Invoices from SAP Business One using OData polling with the UpdateDate filter, extracts customer address, item quantities, and line totals, and posts each transaction to TaxJar's /transactions/orders endpoint. TaxJar calculates the tax liability per state and returns the result. Refunds are posted to /transactions/refunds. Tax rate lookups for specific customer addresses can be fetched via /rates/:zip on demand. The direction is SAP Business One to TaxJar; tax calculations stay in TaxJar and are referenced back in SAP Business One reporting or export.

How ml-connector handles it

ml-connector manages SAP Business One session tokens, which expire after 30 minutes without activity. It reuses live sessions when possible and initiates a fresh login only when a token times out (error code -5002), rather than authenticating on every request, to minimize cold-start latency and comply with SAP Business One rate-limiting expectations. On the TaxJar side, ml-connector stores the API token encrypted and presents it on every request via the Authorization Bearer header. SAP Business One does not provide published idempotency keys, so ml-connector checks the transaction's DocNum against previously synced records to prevent duplicates on retry. TaxJar's idempotency workaround for transactions is: POST /transactions/orders; if the response is 422 (transaction exists), fall back to PUT with the existing transaction ID; if PUT returns 404, fall back to POST. Address validation is performed against TaxJar's /addresses/validate endpoint before posting a transaction, to ensure nexus is correctly tracked. Customer exemption status is read from SAP Business One's BusinessPartners and mapped to TaxJar's /customers endpoint. Every record carries a full audit trail, and failed transactions can be replayed once the underlying data error is corrected.

A real-world example

A regional B2B goods distributor runs SAP Business One on-premise to manage inventory and invoicing across three states. The finance team previously exported sales invoices to a spreadsheet each week, manually entered them into TaxJar for tax calculation, and reconciled differences between SAP Business One and state filing records. With SAP Business One connected to TaxJar, each invoice syncs automatically the moment it posts in SAP Business One. TaxJar calculates the correct tax per destination state, tracks nexus changes as the customer grows into new jurisdictions, and the compliance team submits filings with confidence that every transaction is captured and correctly reported.

What you can do

Sync sales invoices and line items from SAP Business One to TaxJar in real-time or on a polling schedule you control.
Validate customer shipping addresses against TaxJar's nexus database before posting transactions.
Map customer exemption status from SAP Business One to TaxJar's exemption management for accurate tax-exempt reporting.
Handle SAP Business One's session token authentication, refresh on timeout, and reuse of live connections to avoid cold-start latency.
Post refunds to TaxJar, manage transaction updates via idempotency workarounds, and maintain a full audit trail on every sync.

Questions

How does ml-connector handle SAP Business One's 30-minute session timeout?: ml-connector maintains and reuses active B1SESSION tokens to minimize latency and API calls. When a token expires (error code -5002), it logs in fresh rather than pre-emptively refreshing. This strategy reduces cold-start overhead while ensuring the connector stays authenticated across polling intervals.
What happens if a transaction already exists in TaxJar and ml-connector tries to post it again?: TaxJar returns HTTP 422 when a transaction duplicate is detected. ml-connector falls back to PUT /transactions/{id} to update the existing record. If the transaction does not exist in TaxJar, PUT returns 404 and ml-connector falls back to POST to create it. This idempotency pattern allows retries without data loss or duplicate records.
How are customer tax exemptions handled across SAP Business One and TaxJar?: ml-connector reads the exemption status and exemption type from SAP Business One's BusinessPartners master data and maps those to TaxJar's /customers endpoint. TaxJar gives precedence to customer-level exemptions, which override line-item exemptions, so the mapping respects both systems' hierarchies for accurate tax-exempt reporting.

Connect SAP Business One and TaxJar

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started