11 apr

Clearing transaction (SAP B1)

Versino Financial Suite

Clearing transaction (also: clearing entry or Journal entry) is a posting in SAP Business One that reconciles a difference between internal house bank account transactions and an external bank statement to zero. The reconciliation process is therefore a prerequisite for the successful completion of the bank reconciliation process.

Context

In the context of bank reconciliation, SAP Business One matches the transactions recorded in the system for a house bank account with the lines on an imported or manually entered bank statement. If the totals do not match – for example, because bank charges or interest income have not yet been posted in the system – SAP Business One blocks the completion of the reconciliation. The reconciliation process resolves this difference through a journal entry to the relevant expense or revenue account. SAP Business One automatically opens the journal entry window as soon as the user confirms a difference.

The reconciliation process is used in two settlement modes:

  • Manual tuning The user captures missing transactions directly from the reconciliation window using the "Adjustment" button.
  • Two-sided matching: The system recognises the difference between SAP general ledger lines (left) and bank statement lines (right) and prompts the user to create an offsetting entry.

Procedure

  1. Click the "Adjustment" button in the voting window (manual tuning) or confirm the automatic prompt (two-sided adjustment).
  2. Select document type "Journal entry".
  3. The appropriate Effort- or select the income/expense account (e.g. bank charges).
  4. Enter the difference amount and add the journal entry.
  5. Assign a voting number before closing the vote — the date of the bank statement is recommended.

Demarcation

The reconciliation process is not a regular incoming or outgoing payment, but exclusively a correction element within the reconciliation process. It does not serve to cancel transactions already booked in the system, but rather supplements missing items that only appear on the external statement.


 

SPRINT & SWIRL

Sprint and Swirl: How an AI agent divides work and learns from trials

This series deals with artificial intelligence in conjunction with SAP Business One. It takes a close look at fundamental AI principles...
LATS

LATS: Considering several paths simultaneously with AI — and the availability check in SAP B1

This series focuses on artificial intelligence in conjunction with SAP Business One. Not as a collection of product announcements, but as...
ReAct and RLEF

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...
Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
Wird geladen …