- SAP Managed Tags:
Recently we have received several questions from partners and customers how to map transaction types when creating bank statements by the ManageBankStatementIn web service in SAP Business ByDesign. With this blog post I want to provide some more information around this topic.
Depending on the import format of bank statements, such as BAI2, MT940 or ISO20022 file formats, different transaction types are provided. As the name suggests these transaction types help to identify the type of transaction being reported on the bank statement. As an example, the BAI2 transaction type <142> represents an ACH Credit Received transaction in the bank statement. This is an incoming direct debit payment. As the name suggests transaction types help to identify the type of transaction being reported on the bank statement. By mapping this information either to the BusinessProcessVariantType or the PaymentTransactionCategory fields in the web service, the system can allocate the transaction appropriately during the bank statement processing. Together with additional information provided for the bank statement transaction, for example details in the memo line, an automatic clearing by the system is possible.
For the mapping of the bank transaction type in the web service, you can either use the BusinessProcessVariantType or the PaymentTransactionCategory field. You do not need to provide information for both fields.
Below is a list of the relevant BusinessProcessVariantType or PaymentTransactionCategory codes.
BusinessProcessVariantType
PaymentTransactionCategories
In SAP Business ByDesign we provide default mappings for transaction types for several file formats. These configuration settings are getting used when uploading a bank statement. For further information read the Bank Statements Quick Guide document in our SAP Business ByDesign Library. In case needed, customers can change these configuration settings.
The activity in the business configuration is called Automatically Generated Bank Statements. When opening Edit import formats for automatic generated bank statements the below screen is displayed.
For each file format External Transaction Codes (bank transaction types) are mapped to the Business Process Variant Types. These default settings can be helpful when defining the mappings in the web service, especially when you use the Business Process Variant Type Codes for the mapping.
When using the ManageAccountingEntryIn web service in SAP Business ByDesign this further information shall support you to set up the right mapping for the bank transaction types.
Depending on the import format of bank statements, such as BAI2, MT940 or ISO20022 file formats, different transaction types are provided. As the name suggests these transaction types help to identify the type of transaction being reported on the bank statement. As an example, the BAI2 transaction type <142> represents an ACH Credit Received transaction in the bank statement. This is an incoming direct debit payment. As the name suggests transaction types help to identify the type of transaction being reported on the bank statement. By mapping this information either to the BusinessProcessVariantType or the PaymentTransactionCategory fields in the web service, the system can allocate the transaction appropriately during the bank statement processing. Together with additional information provided for the bank statement transaction, for example details in the memo line, an automatic clearing by the system is possible.
For the mapping of the bank transaction type in the web service, you can either use the BusinessProcessVariantType or the PaymentTransactionCategory field. You do not need to provide information for both fields.
Below is a list of the relevant BusinessProcessVariantType or PaymentTransactionCategory codes.
BusinessProcessVariantType
| Code | Description |
| 42 | Payment Processing - Of Outgoing Bank Transfer |
| 43 | Payment Processing - Of Outgoing Real Time Bank Transfer |
| 44 | Payment Processing - Of Incoming Direct Debit |
| 45 | Payment Processing - Of Outgoing Check Payment |
| 46 | Payment Processing - Of Incoming Payment Card Payment |
| 47 | Payment Processing - Of Outgoing Bill of Exchange |
| 48 | Payment Processing - Of Incoming Bank Transfer |
| 49 | Payment Processing - Of Outgoing Direct Debit |
| 50 | Payment Processing - Of Incoming Check With Lockbox |
| 51 | Payment Processing - Of Incoming Check With Check Deposit |
| 52 | Payment Processing - Of Incoming Bill of Exchange |
| 53 | Payment Processing - Of Outgoing Bank Fees |
| 54 | Payment Processing - Of Outgoing Interest |
| 55 | Payment Processing - Of Incoming Interest |
| 56 | Payment Processing - Of Outgoing Payment Returns |
| 57 | Payment Processing - Of Incoming Payment Returns |
| 58 | Payment Processing - Of Incoming Cash Payment |
| 59 | Payment Processing - Of Outgoing Cash Payment |
| 60 | Payment Processing - Of Cash Transfer |
| 197 | Payment Processing - Of Outgoing Bill of Exchange Drawn |
| 198 | Payment Processing - Of Outgoing Bill of Exchange via Commercial Transfer |
| 200 | Payment Processing - Of Incoming Bill of Exchange Drawn |
| 201 | Payment Processing - Of Incoming Bill of Exchange via Commercial Transfer |
| 351 | Payment Processing - Of Outgoing Payment Card Payment |
| 404 | Payment Processing - Of Outgoing External Payment |
| 405 | Payment Processing - Of Incoming External Payment |
| 406 | Payment Processing - Of Outgoing Cash Outpayment Order |
PaymentTransactionCategories
| Code | Description |
| 1 | Outgoing Bank Transfer |
| 2 | Outgoing Wire Transfer |
| 3 | Outgoing Direct Debit |
| 4 | Outgoing Check |
| 5 | Outgoing Credit Card Payment |
| 6 | Outgoing Cash |
| 7 | Bill of Exchange Payable Without Acceptance |
| 8 | Bill of Exchange Payable with Acceptance |
| 9 | Bill of Exchange Payable Sole Bill |
| 10 | Bill of Exchange Payable Commercial Transfer |
| 11 | Outgoing Return of an Incoming Payment |
| 12 | Outgoing Bank Interest |
| 13 | Bank Charge |
| 14 | Other Outgoing Payments |
| 15 | Incoming Bank Transfer |
| 16 | Incoming Wire Transfer |
| 17 | Incoming Direct Debit |
| 18 | Incoming Check |
| 19 | Incoming Credit Card Payment |
| 20 | Incoming Cash |
| 21 | Bill of Exchange Receivable Without Acceptance |
| 22 | Bill of Exchange Receivable with Acceptance |
| 23 | Bill of Exchange Receivable Sole Bill |
| 24 | Bill of Exchange Receivable Commercial Transfer |
| 25 | Incoming Return of an Outgoing Payment |
| 26 | Incoming Bank Interest |
| 27 | Other Incoming Payments |
| 28 | Check Deposit |
| 29 | Bill of Exchange Deposit |
| 30 | Incoming Payment by check deposit via Lockbox |
| 31 | Outgoing External Payment |
| 32 | Incoming External Payment |
| 33 | Outgoing Cash Outpayment |
| 35 | Incoming Cash Transfer |
| 36 | Outgoing Cash Transfer |
In SAP Business ByDesign we provide default mappings for transaction types for several file formats. These configuration settings are getting used when uploading a bank statement. For further information read the Bank Statements Quick Guide document in our SAP Business ByDesign Library. In case needed, customers can change these configuration settings.
The activity in the business configuration is called Automatically Generated Bank Statements. When opening Edit import formats for automatic generated bank statements the below screen is displayed.
For each file format External Transaction Codes (bank transaction types) are mapped to the Business Process Variant Types. These default settings can be helpful when defining the mappings in the web service, especially when you use the Business Process Variant Type Codes for the mapping.
When using the ManageAccountingEntryIn web service in SAP Business ByDesign this further information shall support you to set up the right mapping for the bank transaction types.
2 Comments
