SAP Business One Bank Feeds
Setting up a SAP Business One Bank Feeds Workflow with Rutter
Early access
SAP Business One Bank Feeds is in development and is not yet generally available. The SAP-side setup described below is final and can be completed now. The Rutter API behavior described under Implementation Steps is the planned design and may change before release. Contact your Rutter Customer Success manager for availability.
Introduction
Rutter API enables you to support bank feeds for your customers' SAP Business One companies. This allows you to send bank or card transaction data into SAP Business One as external bank statement lines, so the customer can reconcile them against their books.
- Connect to your customer's SAP Business One company.
- Discover the house bank accounts that you want to feed transactions into.
- Continuously sync transaction data into those bank accounts to enable reconciliation.
How SAP Business One Bank Feeds differ from Intuit, Sage, and Plaid
SAP Business One does not require a separate financial-institution partnership, a bank feeds add-on, or a dedicated bank feeds connection. Transactions are written as external bank statement lines through SAP Business One's standard Service Layer API, using the same connection you use for the rest of SAP Business One. There is no Rutter-side account registration step. You send transactions to house bank accounts that already exist in the customer's company.
Supported versions
SAP Business One 10.0 on SAP HANA, with Service Layer. Bank statement lines work for every localization.
Platform Setup
Data Sync Configuration
Make sure to include these Rutter Objects in your Data Sync Configuration through the Rutter dashboard.
- Bank Feed Account
- Bank Feed Transaction
Connect to SAP Business One
Embed Rutter Link into your application and walk through an end to end business authentication flow in order to create a new Connection. The customer provides their Service Layer URL, company database, and a SAP Business One user name and password. This Connection represents the business's SAP Business One company and contains an access_token used to read and write data for that company.
Make your first connection in minutes
Follow our guide to get up and running
Configure the SAP Business One Company
Bank feeds need little configuration beyond what the accounting connection already requires.
Make Service Layer reachable. Rutter connects through SAP Business One Service Layer (port
50000by default). The customer's IT team or SAP partner must make it reachable from Rutter. This is the same requirement as the rest of the SAP Business One integration.Set up house bank accounts. Each account you feed must exist as a house bank account (Administration → Setup → Banking → House Bank Accounts) and be linked to a G/L cash account. Rutter writes statement lines to that G/L account.
Authorize the integration user. The SAP Business One user on the Rutter connection needs authorization for Banking → Bank Statements and Reconciliations, including external bank statements.
Important Post-Setup Step
Once the customer has completed the steps above, contact your Rutter Customer Success manager to confirm the bank feed objects are enabled for your organization.
Implementation Steps
The steps below describe the planned API behavior.
Step 1: Discover Bank Feed Accounts
Bank accounts are created and maintained inside SAP Business One, not through Rutter. Use Rutter's GET /bank_feeds/accounts API endpoint to list the house bank accounts in the customer's company. Each account includes its bank, account number and linked G/L account.
POST /bank_feeds/accounts is not supported for SAP Business One
Because transactions are written to existing house bank accounts, the Create a Bank Feed Account endpoint is not available for SAP Business One and returns ENDPOINT_NOT_AVAILABLE_FOR_PLATFORM. Use GET /bank_feeds/accounts to find the account you want, then reference its Rutter id when syncing transactions.
Step 2: Sync Bank Feed Transactions
Use Rutter's POST /bank_feeds/transactions API endpoint to send transactions to the bank account. Each transaction becomes one external bank statement line on the account's G/L account.
1{
2 "bank_feed_transactions": {
3 "bank_feed_account_id": "00000000-0000-0000-0000-000000000000",
4 "current_balance": 1234.56,
5 "transactions": [
6 {
7 "transaction_id": "ACRAF23DB3C4",
8 "posted_at": "2026-11-16T02:34:56.000Z",
9 "amount": -300,
10 "description": "Office supplies",
11 "transaction_type": "debit",
12 "debit_credit_memo": "DEBIT",
13 "payee": "Office Depot"
14 }
15 ]
16 }
17 }
- If the request succeeds, the lines are created in SAP Business One and appear in the external bank statement for that account.
- If
response_mode=asyncis specified in the request, the response includes a job ID, which can be used to check the status of the POST request using the Fetch a Job API.
How transactions are written to SAP Business One
- Transaction ID. Each line carries your
transaction_idas its external reference, so the customer can trace a line back to your system. - Description and memo.
descriptionis written to the line's memo. - Statement number. Rutter groups the lines from each request under a statement number for the account.
Transaction Syncing Rules
- You must provide at least one transaction per sync request.
- Only posted transactions should be submitted.
- Each transaction must have a unique identifier (
transaction_id). The identifier for a transaction must never change, and the same identifier should not occur more than once for a Bank Feed Account. - The
debit_credit_memofield is required. - Transactions must be in the bank account's currency.
Idempotency and Retries
SAP Business One does not reject duplicate statement lines on its own: writing the same transaction twice creates two lines. Each line carries your transaction_id as its external reference, so duplicates can be found and removed in SAP Business One. How Rutter will prevent duplicates on retries is still being designed. Until it is, avoid re-sending a request that may already have succeeded; use response_mode=async and check the job's result instead.
Reconciliation with SAP Business One
The customer reconciles the imported lines in SAP Business One under Banking → Bank Statements and Reconciliations, by matching the external bank statement lines against the G/L account's journal activity.
Current Limitations
- Reconciliation is done by the customer in SAP Business One. Rutter imports the statement lines but does not match them to journal entries.
- No duplicate protection from SAP Business One: see Idempotency and Retries above.
- Bank Statement Processing module: SAP Business One's separate Bank Statement Processing module (available only in some European localizations) is not used. Lines are written as external bank statements, which work in every localization.
If your use case requires any of these, reach out to your Rutter Customer Success manager.