Multicash format for Bank Statement processing

Multicash is an electronic bank statement format, especially prevalen in Germany and rest of Europe. Multicash is a product of a German company Omikron. The format is widely recognized by various banking systems for communication with customers' ERP systems. SAP supports multicash format as a standard functionality. The format consists of two files in format AUSZUG.TXT and UMSATZ.TXT. AUSZUG.TXT format contains the header information for the bank account statements, while UMSATZ.TXT contains transaction level information. 

Format Details 

AUSZUG.TXT

Semicolon Delimited

Field#	Field type	Minimum	Maximum	optional	Description
1	Alphanumeric	0	12		bank key
2	Alphanumeric	0	24		bank account number
3	Numeric (Integer)	1	4		statement number
4	DD.MM.YYYY	8	8		statement date
5	Alphanumeric	3	3		currency key
6	Amount	1	18.2		opening balance amount
7	Amount	1	18.2		debit total
8	Amount	1	18.2		credit total
9	Amount	1	18.2		closing balance amount
10	Alphanumeric	0	35		Bank account holder
11	Alphanumeric	0	35	X	special account name
12	DD.MM.YYYY	8	8	X	life start
13	DD.MM.YYYY	8	8	X	life end
14		0	0		Not Used
15		0	0		Not Used
16		0	0		Not Used
17		0	0		Not Used
18	Numeric	1	5		number of records in statement

UMSATZ.TXT

Semicolon Delimited

Field#	Field type	Minimum	Maximum	optional	Description
1	Alphanumeric	0	12		Bank key
2	Alphanumeric	0	24		Bank account number
3	Numeric	1	4		Statement number
4	DD.MM.YYYY	8	8		Value date
5	Numeric	1	10	X	Primary note number
6	Alphanumeric	0	27	X	Note to payee 1
7	Alphanumeric	0	27	X	Bank posting text
8		0	0		Not used
9	Alphanumeric	0	4	X	Text key
10	Alphanumeric	0	16	X	Check number
11	Amount	1	18.2		Amount
12		0	0		Not used
13		0	0		Not used
14	DD.MM.YYYY	8	8		Posting Date
15		0	0		Not used
16		0	0		Not used
17	Alphanumeric	0	27	X	Note to payee 2
18	Alphanumeric	0	27	X	Note to payee 3
19	Alphanumeric	0	27	X	Note to payee 4
20	Alphanumeric	0	27	X	Note to payee 5
21	Alphanumeric	0	27	X	Note to payee 6
22	Alphanumeric	0	27	X	Note to payee 7
23	Alphanumeric	0	27	X	Note to payee 8
24	Alphanumeric	0	27	X	Note to payee 9
25	Alphanumeric	0	27	X	Note to payee 10
26	Alphanumeric	0	27	X	Note to payee 11
27	Alphanumeric	0	27	X	Note to payee 12
28	Alphanumeric	0	27	X	Note to payee 13
29	Alphanumeric	0	27	X	Note to payee 14
30	Alphanumeric	0	27	X	Business partner
31	Alphanumeric	0	27	X	Business partner
32	Alphanumeric	0	12	X	Bank key of the partner's bank
33	Alphanumeric	0	24	X	Bank account number of the partner
34	Alphanumeric	0	3	X	Business transaction code
35		0	0		Not Used

SAP Transaction for processing Multicash files: 

FEBC - Convert various formats to multicash format 

FF_5 - Import Bank Statement with multicash format 

RFEBKATX (program) - Test Tool for to create open items and bank statement files.

Issue/Solution: Errors with IDOC message type PEXR002/REMADV

Message type PEXR2002/REMADV, can used to create remittance advice for customer using EDI 820 or other common formats. The following errors are common to appear in basic type PEXR2002 and message type REMADV as the mapping of IDOC fields to customer or company code is not very intuitive.

FD 16 - Company code could not be determined for intermediate document 
FD 17 - Customer/vendor could not be determined for intermediate document

To resolve the errors above, it's very important to understand how standard SAP function module to process Remittance Advice determines the relevant Customer or Company Code records.

Customer Determination
The Customer to whom remittance advice is to be posted is determined using segment with the following alternatives

1. Based on Partner Profile, as configured in WE19 if the partner is of type "KU" - customer
2. If partner type is not "KU", Segment E1EDKA1 is checked the following order of precedence where the partner function E1EDKA1-PARVW = "AG"

• Based on field LIFNR (Vendor) if Partner Function (PARVW) = "AG" (Sold to Party) against KNA1-KUNNR (Customer Account Number)

• Yes: Field LIFNR in the IDOC is validated against KUNNR in table KNA1

• Based on Our Number at Vendor/Customer (Name1) if the Partner Function (PARVW) = "AG" (Sold to Party) againt KNBK-KOINT , where KNBK-KOINT is Customer's Bank Account Holder Name as maintained in customer master Payment Transaction tab  

Company Code Determination 

1. Based on configuration in OBCA 

• Company Code Name assigned to the partner type and partner number is checked against the fields PARTN and NAME1 in segement E1EDKA1, where Partner Function (PARVW) = "BE"

2. Based on Details of the bank account in segment E1IDB02 where Partner function(PARVW)= "BB"

Some more details may be found in SAP Note 63485
https://service.sap.com/sap/support/notes/63485