How to Reduce FEBAN Post-processing After Bank Statement Import

SAP FEBAN post-processing can be reduced by improving the rules used during electronic bank statement processing and automating the allocation of incoming customer payments against open receivables.

The distinction between these two stages is important. Standard SAP imports and initially processes the electronic bank statement. Customer clearing then deals with identifying what each incoming payment covers and clearing the relevant invoices.

When SAP cannot determine the correct posting or clearing action from the bank statement information available, the item remains for manual review. Addressing the configuration, payment reference and remittance issues behind these exceptions can significantly reduce the FEBAN workload.

Customer payment allocation can also be automated after the bank statement import. The BEST Customer Clearing module supports this part of the process by loading detailed remittance information into SAP, matching it against open customer items and automatically posting the resulting clearing.

At Unitrade Management Services, 181,086 of 189,035 remittance lines processed through the module had been cleared by March 2026. Read the full case study to learn how UMS achieved a 99.6% clearing rate.

What is FEBAN post-processing in SAP?

FEBAN is used for the post-processing of bank statements that SAP could not post or clear automatically.

When an electronic bank statement is imported, SAP uses the configured account determination, posting rules and interpretation algorithms to decide how each transaction should be handled. Depending on the bank statement information and system configuration, SAP may be able to:

• Identify the relevant customer or supplier
• Find the corresponding open item
• Post the bank transaction
• Clear the payment against the open item
• Direct the amount to the correct general ledger account

Items that cannot be processed automatically require further investigation. In SAP S/4HANA environments, this work may be completed through the Reprocess Bank Statement Items app rather than the traditional FEBAN transaction.

Although the interface may differ, the underlying issue is similar: SAP needs enough reliable information to determine what the incoming bank transaction represents and how it should be posted or cleared.

Why do bank statement items require manual post-processing?

A bank statement can confirm that money has reached the account without providing enough information to allocate it correctly.

Common causes of FEBAN exceptions include:

• Missing or inconsistent invoice references
• Customer account details that cannot be identified
• One payment covering several invoices
• One payment covering multiple customer accounts or company codes
• References being entered differently from the corresponding SAP document
• Deductions, claims or short payments
• Bank charges or payment differences
• Consolidated payments received from customer groups
• Unstructured or separately delivered payment advice
• Posting or interpretation rules that do not cover the transaction

Deductions, short payments and other differences may also need to be handled using the organisation’s configured customer clearing tolerances in SAP.

A customer might pay £250,000 against hundreds of invoices while the bank statement displays only the amount, payer and a short reference. SAP can import the payment, but that bank statement line may not contain enough detail to decide which invoices should be cleared.

The missing allocation detail is often held in a separate remittance advice sent by email, PDF, spreadsheet or another channel. This separation between the payment and its supporting information is one reason the cash application process in SAP can become time-consuming.

How can FEBAN post-processing be reduced in SAP?

Reducing SAP FEBAN post-processing usually requires improvements at more than one point in the process.

Review the existing bank statement configuration

Start by identifying which transaction types repeatedly reach FEBAN.

Posting rules, account symbols, interpretation algorithms and account determination should reflect the bank transaction types the organisation receives. If a common transaction repeatedly requires the same manual correction, the existing configuration may not be handling it effectively.

SAP interpretation algorithms can use information in the note-to-payee field, including document and reference numbers, to identify open items. Search strings and processing rules can also help SAP recognise recurring reference patterns.

Configuration changes should be tested carefully. A broader matching rule may increase automation, but it can also create incorrect postings if the matching criteria are not sufficiently controlled.

Analyse exceptions by reason

FEBAN should not be treated as one general queue. Grouping exceptions by cause makes it easier to determine which problems can be prevented.

Useful categories might include:

• Customer not identified
• Invoice reference not found
• Multiple possible matches
• Payment difference
• Missing remittance
• Incorrect posting rule
• General ledger allocation required

This separates configuration issues from customer payment allocation issues. It also prevents finance teams from trying to solve a missing-remittance problem by continually changing bank statement rules.

Improve the payment references received from customers

Consistent references give SAP a better chance of finding the correct open item.

Where possible, customers should be asked to include an invoice number, account number or other agreed reference with the payment. The same information should appear consistently in SAP and in the bank statement note-to-payee field.

This may improve automatic processing for straightforward one-payment-to-one-invoice transactions. It is less likely to solve large or consolidated payments covering many invoices.

Capture remittance advice in a structured format

Bank statement information and remittance information serve different purposes.

The bank statement confirms that the payment was received. The remittance advice explains how the customer wants that payment allocated.

If remittances remain in email inboxes, PDFs or spreadsheets outside SAP, the receivables team must manually compare them with open items. Bringing the remittance into a structured process provides the detailed references needed for more accurate matching.

Use processing rules for recurring exceptions

In SAP S/4HANA, processing rules can help automate the handling of bank statement items that repeatedly follow a known pattern.

These rules can support the assignment of payments to customer, supplier or general ledger accounts. They are most useful where the transaction contains reliable information and the required accounting treatment is consistent.

Processing rules should be monitored after implementation to confirm that they are reducing manual work without introducing posting errors.

Automate customer payment allocation separately

Improving SAP bank statement processing does not remove every customer clearing challenge.

A bank statement line may be imported and posted correctly while the corresponding payment still needs to be distributed across many customer invoices. This is where cash application and customer clearing automation become relevant.

Rather than expecting the bank statement alone to provide every invoice-level reference, the clearing process can use the customer’s remittance advice to establish the allocation.

How can customer payments be cleared automatically after a bank statement import?

Customer payments can be cleared automatically by matching structured remittance lines against open customer items and then posting the clearing when the corresponding payment is available in SAP.

This forms part of the wider SAP cash application process, which connects incoming customer payments with the invoices and other receivable items they are intended to settle.

A typical process is:

1. Standard SAP imports the electronic bank statement.
2. The incoming customer payment is posted through the bank statement process.
3. The customer’s remittance advice is captured in a structured format.
4. Remittance lines are validated against SAP customer and document information.
5. Matching rules identify the relevant open receivables.
6. Matched invoices and payment items are cleared.
7. Only unmatched lines, deductions and genuine exceptions are sent for review.

This division of responsibility is important. Standard SAP remains responsible for the electronic bank statement import and its initial processing. The customer clearing process uses the additional remittance detail to allocate and clear the payment.

Where does the BEST Customer Clearing module fit?

The BEST Customer Clearing module is not a bank statement import tool. Standard SAP continues to load and process the bank statement.

The BEST Customer Clearing module supports the next part of the process: allocating customer payments and clearing them against open receivables.

The module can:

• Upload customer remittance advice into SAP
• Validate remittance lines against SAP data
• Match remittance lines with open customer items
• Post detailed remittance lines to the appropriate customer accounts
• Determine the relevant customer and company code for individual lines
• Process remittances covering multiple customers and company codes
• Post SAP-standard clearing for matched items
• Manage residuals and short-payment exceptions
• Display matched and unmatched remittance lines inside SAP
• Process high volumes through batch management
• Report on customer clearing statistics

This makes it possible to replace a lump-sum payment with the detailed allocation information needed to support customer clearing.

The module can also work alongside existing OCR or remittance capture processes where these are already in place. This allows organisations to retain their current methods of receiving remittance advice while using the BEST Customer Clearing module for validation, matching and clearing inside SAP.

Does BEST remove the need for FEBAN?

No. FEBAN and the BEST Customer Clearing module handle related but distinct parts of the process.

FEBAN, or the equivalent SAP S/4HANA app, is still required for bank statement items that standard SAP cannot process automatically. BEST does not replace the electronic bank statement import or SAP’s bank accounting functionality.

However, when FEBAN exceptions relate to customer payment allocation, automating the remittance matching and clearing process can reduce the amount of manual work required after the payment arrives.

What should SAP finance teams address first?

The best starting point depends on the type of exception.

If SAP cannot identify the transaction or determine where it should be posted, review the electronic bank statement configuration, references and processing rules.

If SAP has posted the customer payment but the receivables team still has to allocate it manually across invoices, focus on remittance capture, matching and customer clearing.

Many organisations need to address both. Better SAP bank statement processing reduces avoidable FEBAN exceptions, while automated customer clearing reduces the invoice-level allocation work that remains after the payment is imported.

Reduce manual customer clearing after bank statement import

The aim should be to prevent repeatable exceptions and give SAP the information needed to complete more of the process automatically.

Standard SAP should continue to handle the bank statement import and initial processing. The BEST Customer Clearing module can then support detailed customer payment allocation, automated matching and clearing within SAP.

For finance teams processing high volumes of consolidated customer payments, this can reduce manual post-processing while preserving SAP authorisations, posting controls and visibility.

Book a demo to see how the BEST Customer Clearing module can support customer payment allocation and clearing after bank statement import.