SAP S/4HANA Bank Feeds

Back to Bank Feeds

Setting up a SAP S/4HANA Bank Feeds Workflow with Rutter

Early access

SAP S/4HANA 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 S/4HANA systems. This allows you to send bank or card transaction data into SAP S/4HANA as electronic bank statements, so the customer's finance team can reconcile them against their books.

  1. Connect to your customer's SAP S/4HANA system and complete the one-time SAP configuration.
  2. Discover the bank accounts in SAP S/4HANA that you want to feed transactions into.
  3. Continuously sync transaction data into those bank accounts to enable reconciliation.

How SAP S/4HANA Bank Feeds differ from Intuit, Sage, and Plaid

SAP S/4HANA does not require a separate financial-institution partnership or a dedicated bank feeds connection. Transactions are imported as electronic bank statements through SAP's standard Bank Statement Post web service (BankStatementPost_In), using the same connection you use for the rest of SAP S/4HANA. There is no Rutter-side account registration step. You send transactions to bank accounts that already exist in the customer's SAP system.

Supported editions

  • SAP S/4HANA (on-premise and private cloud): supported. Validated against SAP S/4HANA 2025.
  • SAP S/4HANA Cloud, public edition: the same service is available through communication scenario SAP_COM_0316. It has not yet been validated by Rutter.

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 S/4HANA

Embed Rutter Link into your application and walk through an end to end business authentication flow in order to create a new Connection. This Connection represents the business's SAP S/4HANA system and contains an access_token used to read and write data for that system.

Make your first connection in minutes

Follow our guide to get up and running

Explore Quickstart

Configure the SAP S/4HANA System

Bank feeds need some one-time configuration in the customer's SAP system, done by their SAP Basis or finance administrator.

Start this early

These steps usually involve the customer's SAP Basis team and their finance (FI) configuration team. Share this section with the customer as early as possible.

  1. Create a web service binding for BankStatementPost_In. This is the service Rutter calls to import statements.

    • Open SOA Management (transaction SOAMANAGER) → Web Service Configuration.
    • Search for the service definition BANKSTATEMENTPOST_IN and open it.
    • On the Configurations tab, click Create Service. Enter a service name (for example RUTTER_BANK_STATEMENT) and a binding name (for example RUTTER_BS_BINDING).
    • Under Provider Security, choose SSL (https) and User ID/Password authentication.
    • Click Finish. Share the service name and binding name with Rutter.
    • On SAP S/4HANA Cloud, public edition, create a communication arrangement for scenario SAP_COM_0316 instead.
  2. Activate the bank account API. Rutter reads the list of bank accounts from SAP's released OData service API_BANKACCOUNT_SRV. If it is not already active, add it in Activate and Maintain Services (transaction /IWFND/MAINT_SERVICE) → Add Service, system alias LOCAL.

  3. Set up the bank accounts. Each account you feed must exist as a house bank account in SAP, with its bank key and bank account number. These two values identify the account on every imported statement.

  4. Configure electronic bank statement processing for each account. Assign the bank account to an electronic bank statement transaction type (for example CAMT053 or a BAI type) and maintain the external transaction codes and posting rules for it. This is the standard Make Global Settings for Electronic Bank Statement configuration.

    • Without this step, statements still import into SAP, but the lines are not posted automatically and must be processed by hand.
  5. Authorize the integration user. The SAP user on the Rutter connection must be allowed to call the web service and to create bank statements in the relevant company codes.

Important Post-Setup Step

Once the customer's SAP administrators have 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, not through Rutter. Use Rutter's GET /bank_feeds/accounts API endpoint to list the bank accounts that exist in the customer's SAP system. Each account includes its company code, bank, account number and currency.

POST /bank_feeds/accounts is not supported for SAP S/4HANA

Because statements are imported against existing SAP bank accounts, the Create a Bank Feed Account endpoint is not available for SAP S/4HANA 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 request is imported into SAP as one electronic bank statement for that account.

Example Create Bank Feed Transactions Request Body
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 statement and its lines are created in SAP. The customer can see them in the Manage Bank Statements app (or transaction FEBAN).
  • If response_mode=async is 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

  • Statement number. Rutter assigns each statement a number per bank account. SAP's API limits statement numbers to five digits.
  • Transaction codes. Every statement line carries an external transaction code that the account's transaction type must recognize. By default, Rutter sends ISO 20022 bank transaction codes (for example PMNTRCDTOTHR for money in and PMNTICDTOTHR for money out). If the customer's configuration uses different codes, tell your Rutter Customer Success manager.
  • Dates. SAP applies the statement date to every line in the statement, so send one request per account per posting date.

Transaction Syncing Rules

  1. You must provide at least one transaction per sync request.
  2. Only posted transactions should be submitted.
  3. 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.
  4. The debit_credit_memo field is required.
  5. Transactions must be in the bank account's currency.

Idempotency and Retries

SAP rejects a second statement with the same bank account and statement number. When Rutter retries a request, it reuses the original statement number, so a retry cannot create a duplicate statement.

Reconciliation with SAP S/4HANA

Imported statements appear in SAP's bank statement apps. If the customer has configured posting rules for the account, SAP posts and clears the lines automatically. Lines that cannot be posted automatically can be processed in Reprocess Bank Statement Items (or transaction FEBAN).

Current Limitations

  • Intraday statements are not supported by SAP's bank statement service. Only end-of-day statements are imported.
  • One posting date per statement: SAP uses the statement date for every line, so batches should not span several days.
  • Automatic posting depends on customer configuration: Rutter imports the statement. Whether lines post automatically depends on the electronic bank statement settings in step 4 above.

If your use case requires any of these, reach out to your Rutter Customer Success manager.

SAP S/4HANA Bank Feeds