Business Need
A client using SAP Business ByDesign required greater control over how their outgoing payment files were generated. Their banking processes required payment files in specific ISO 20022 CHILE (pain.001.001.03) formats, with variations depending on transaction conditions.
However, the standard system does not support generating payment files based on such conditional parameters. This creates a limitation when payment file structures need to adapt dynamically to business requirements.
In this case, payment file generation needed to be driven by key factors such as:
- Currency
- Document Date
- Bank Processing Date
Without the ability to incorporate these parameters into file generation, it becomes difficult to ensure that payment files are consistently aligned with banking requirements.
Solution Overview
To address this limitation, the Outgoing Bank Transfer – Payment File Generation solution extends the standard SAP Business ByDesign process through backend enhancements along with supporting UI configuration.
Payments are created using the standard outgoing bank transfer process, with UI configuration ensuring that approvals are completed before payments proceed further in the process (standard approval workflow).
Once the payment reaches the required status, custom backend logic processes and structures the payment data based on defined business rules. Based on these conditions, the system generates bank-compliant payment files in multiple XML formats, including ISO 20022 CHILE. Where required, the logic also separates and generates multiple files to handle different format requirements.
All generated files are stored as attachments within a Custom Business Object (CBO), providing a controlled extension of the standard process while maintaining system integrity and enabling centralized file management.
This approach ensures that payment files are generated in alignment with business and banking requirements, without impacting the standard SAP Business ByDesign workflow.
Solution Details & Functional Flow
Step 1: Payment Creation from Standard Outgoing Bank Transfer
Users initiate the process by creating payments using the standard Outgoing Bank Transfer functionality in SAP Business ByDesign, ensuring consistency with existing financial processes.
Payment Management - Payment Monitoring
Step 2: Configuration & Approval Control
Approval configuration ensures that only validated payments proceed further, preventing incorrect or incomplete transactions from moving to file generation.
Payment Monitoring – Object Page
Step 3: Approval Process – Ready to Transfer
Once a payment is created, users review the transaction details and trigger the Approve Payment action as part of the standard workflow.
- Upon approval, the system updates the payment status to Ready to Transfer
- Only payments in this status are eligible for file generation
- Users can then trigger Create Payment File / Batch Payment File
This step ensures that file generation is strictly controlled and aligned with approved transactions.
Step 4: Data Parsing Action
A custom action, Parse Payment Data, is implemented to prepare the payment information for file generation.
This action:
- Reads payment header and line-item data from the custom business object.
- Header-level data includes company, bank, payment reference, amount, currency, and other key information.
- Item-level data captures payment line details required for bank file generation.
- Structures the data according to predefined XML schemas.
- Performs format-specific validations to ensure compliance.
The parsed data is stored internally for subsequent XML file generation.
Step 5: XML File Generation Action
The Generate XML File action intelligently handles multiple payment records based on the required file format:
- If all selected records belong to the same XML format, the system generates one consolidated XML file.
- If selected records belong to different XML formats, the system automatically splits the data and generates separate XML files, one per format.
This ensures:
- Bank-compliant file creation
- Reduced file volume when formats are identical
- Clear separation when different format requirements exist
Each generated XML file is stored against the custom business object for controlled management.
Custom File Generation Logic
The system generates XML files in specific formats according to business rules for Document Date, Expected Bank Value Date, and Currency:
- Document Date = Expected Bank Value Date, Currency = CLP → LO_HV format
- Expected Bank Value Date = Next Business Day from Document Date, Currency = CLP → LO_LV format
- Document Date = Expected Bank Value Date, Currency = USD → US_CH format
- Document Date = Expected Bank Value Date, Currency = USD to any other currency (except CLP) → US_AU format
This logic ensures that payment files are accurately formatted for each bank requirement while maintaining flexibility and compliance.
Custom Object – list Screen
Custom Object – Storing Attachment files
XML File snippet
Technical Highlights
- Custom Business Object (CBO): Developed using the SAP Business ByDesign extensibility framework to manage payment files securely and efficiently.
- UI Configuration: Required configurations generate payment file.
- Custom Actions: Two key backend actions implemented:
- Parse Payment Data – Reads, structures, and validates payment header and line-item data.
- Generate XML File – Generates bank-compliant XML files based on defined formats and business rules.
- Separation of Concerns: Clear separation between standard payment creation and custom processing logic to maintain system integrity.
- Status-Driven Processing: Payment lifecycle tracked through defined statuses: Created → Ready to Transfer → File Generated.
- Support for Multiple Formats: Ability to generate multiple XML formats from a single payment source, based on currency, document date, and bank processing rules.
Pros and Cons
Pros
- Accurate Format Mapping: Payment files are generated in the correct format based on transaction conditions, reducing bank validation failures
- Eliminates Manual File Handling: No need to manually split or adjust payment files for different formats or processing dates
- Controlled File Generation: Only approved payments (Ready to Transfer) are processed, ensuring data integrity
- Efficient Multi-Format Handling: Multiple XML formats can be generated from a single payment run without duplication
- Audit & Traceability: Files stored in the CBO provide clear visibility and tracking of generated outputs
Cons
- Configuration Dependency: Business rules must be accurately defined and aligned with bank requirements during setup
- Maintenance Overhead: Changes in bank formats or rules require updates to custom logic
Conclusion
This solution extends the standard SAP Business ByDesign payment process to handle scenarios where payment file generation must adapt to transaction-specific conditions.
By introducing rule-based logic within the existing workflow, it enables accurate and consistent file generation across different formats without requiring manual intervention. At the same time, it maintains control through approvals and structured file management using the Custom Business Object.
The result is a more reliable and scalable approach to managing outgoing payment files in environments with varying banking requirements.
