Symptom
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Upload a ZENGINKYO bank statement file using the Import Bank Statement - Japan app.
-
Review the imported bank statement data.
-
Notice that some transaction items from the source file are not imported or displayed.
Cause
The ZENGINKYO bank statement file itself and the individual items within the file do not inherently contain a unique key.
When a bank statement is uploaded using the Import Bank Statement – Japan app, the system relies on a composite key to identify duplicate files or transaction items. This composite key consists of the File ID provided during upload and key attributes of each transaction item (such as posting date, balance, and other relevant fields).
If the same File ID is reused, the system may treat some transaction items as duplicates and therefore ignore them. As a result, certain items are not imported or displayed, even though no error message is raised.
Please note that this composite key logic is not reset by fiscal year or calendar year.
Resolution
Keywords
import bank statement Japan, ZENGINKYO, file id, duplicate detection, item not imported, bank statement import, depreciation lists, s/4hana cloud, fi-loc-fi-jp-ivs, duplicate file id, bank statement upload, missing transaction , KBA , FI-LOC-FI-JP-IVS , Invoice Summary , Problem
SAP Knowledge Base Article - Public