SAP Business One Guide

Setting up the SAP Business One Integration

To access your users' data from SAP Business One, you need to enable the SAP Business One integration in the Platforms Page of the Rutter dashboard.

SAP Business One does not require any additional developer app setup. Rutter connects directly to the SAP Business One Service Layer using the user's own credentials.

User Authentication with SAP Business One

A Rutter Connection is created when your end user authenticates their SAP Business One account via Rutter Link. This in turn allows you to access their account data via the Rutter API.

Rutter Link prompts the user for the following credential fields:

  1. Service Layer base URL — The full URL of the SAP Business One Service Layer endpoint, e.g. https://my-sap-host/b1s/v1/. This is the host running the SAP Business One Service Layer (B1SL).

  2. Company database — The SAP Business One company database name, e.g. SBODEMOGB. This identifies which company database to connect to on the Service Layer host.

  3. Username — The SAP Business One username for the account Rutter will authenticate as.

  4. Password — The password for that SAP Business One user account.

Rutter uses these credentials to authenticate against the SAP Business One Service Layer on behalf of the connected company database.

Tax Rates (US Beta)

GET /accounting/tax_rates supports US sales-tax catalogs from SAP Business One's SalesTaxCodes resource. VAT-regime catalogs (VatGroups), including UK VAT, effective-date history, and equalization, are not supported in this beta. An empty sales-tax catalog does not trigger a VAT fallback. Confirm the connected company's tax regime before relying on this endpoint.

effective_tax_rate uses SAP's tax-code header rate, including compounding. total_tax_rate and the applicable sales/purchase totals use the sum of base component rates, excluding compounding. For example, 5% plus 10% compounded has a 15% additive total and a 15.5% effective rate.

For compound components, Rutter reads the base rate from the corresponding sales-tax authority. SAP's line EffectiveRate may already include tax-on-tax. If a compound base rate is unavailable, the additive totals are null and that unknown base component is omitted; the header effective rate is still returned. Genuine zero rates are preserved. Creation and modification timestamps are unavailable.

This read-only catalog does not enable invoice-line tax selection or tax-code writes.

Creating Vendors

Creating a Vendor creates a SAP Business One Business Partner with type Supplier (cSupplier). Rutter generates a vendor code (CardCode) of at most 15 characters for manual numbering, as verified in the sandbox. Other numbering configurations have not been verified. Once creation completes, use the returned Rutter vendor id as vendor_id when creating a Bill.

The primary contact is created in ContactEmployees and selected through ContactPerson. Billing and shipping addresses are created in BPAddresses; other address types and address3 are not supported.

Payment terms, subsidiaries, additional fields, and custom fields are not supported on vendor creation. Names and other accepted customer values are forwarded without trimming or truncation. State and country codes must match the connected company's SAP configuration.

Currency codes must be configured in the connected company. CAD maps to SAP's standard CAN code; XXX omits the currency and lets SAP use its default. Rutter reserves the supplier's Notes field for create reconciliation so retries recover an existing supplier instead of creating a duplicate. Do not overwrite Notes on suppliers created through Rutter: doing so can prevent recovery and allow a retry to create a duplicate.

Creating Customers

Creating a Customer creates a SAP Business One Business Partner with type Customer. customer_name and contact_name are required; email and phone are optional. Send contact_name: "" when no primary contact is needed.

Rutter assigns a 15-character customer code (CardCode) beginning with C for manual numbering. Automatic numbering series have not been verified. Billing and shipping addresses are supported; state, country, and currency codes must match the connected company's SAP configuration. additional_fields.currency_code: "CAD" maps to SAP's CAN and reads back as CAD; omitted currency or XXX uses SAP's default currency.

Do not overwrite the customer's Notes field: Rutter reserves it to recover existing customers on retries. If a create has an uncertain commit state, inspect SAP before retrying.

Once creation completes, use the returned Rutter customer id as customer_id when creating an invoice.

Previous
Salla
SAP Business One Guide