0%

Disbursement Integration & General Ledger Posting

Our platform is designed for seamless integration with third-party systems, including banks’ core systems and general ledger (GL) solutions.

For each SCF lifecycle event (disbursement, accrual, repayment), the system generates the appropriate GL entries based on predefined accounting rules. These entries are posted automatically to the bank’s general ledger.

This ensures efficient disbursement processing, accurate accounting, and streamlined payment operations. As long as the target system provides APIs, we can establish a robust integration.

Integration Capabilities

1. Disbursement Processing

  • API-Driven Integration: Disbursement instructions and status updates can be sent or received via secure APIs, allowing real-time communication with external systems.

  • Automated Disbursement: The system can automate the disbursement of funds to suppliers or beneficiaries based on pre-defined business rules.

2. General Ledger (GL) Posting

There are two primary approaches for posting disbursement transactions to the general ledger:

a. Direct Posting via API

  • How it works: Our system can generate GL entries and post them directly to the bank’s general ledger using secure APIs.

  • Benefits: Real-time synchronization, reduced manual intervention, and improved accuracy.

  • Use Case: Ideal when the bank’s core system exposes APIs for GL posting.

b. End Result Transfer to Core System

  • How it works: Our system compiles the final disbursement data and sends it to the bank’s core system (e.g., Kurbanlık system) via API or file transfer.

  • Bank’s Role: The bank’s core system then processes these entries and posts them to the general ledger.

  • Benefits: Leverages existing bank workflows and controls.

Note: Both methods ensure that all disbursement transactions are accurately reflected in the general ledger. The choice depends on the bank’s technical capabilities and integration preferences.

Payment Integration (Including SWIFT Payments)
  • API Connectivity: The platform supports integration with the bank’s core payment systems via APIs, enabling the creation and processing of domestic and international (SWIFT) payments.

  • Payment Creation: Payments can be initiated by our system or by the bank’s core system, depending on the agreed workflow.

  • Flexibility: As long as the core system provides APIs, we can connect and automate payment creation, status tracking, and reconciliation.

Integration Workflow Example
  1. Disbursement Initiation: System triggers a disbursement based on an approved transaction.

  2. API Call: Disbursement details are sent to the core system or GL via API or SFTP.

  3. GL Posting: Either our system posts directly to the GL, or the core system processes the entries.

  4. Payment Processing: Payment instructions (including SWIFT) are sent via API to the bank’s payment engine.

  5. Confirmation & Reconciliation: Status updates and confirmations are synchronized between systems.

Disbursement Posting Examples

Business Event

Accounting Entry

Disburse funds to customer

Dr Loan Account / Cr Customer Account

Collect upfront fees

Dr Customer Account / Cr Deferred Income

Accrual Posting Examples

Business Event

Accounting Entry

Accrue interest daily (in arrears)

Dr Interest Receivable / Cr Interest Income

Recognise advance interest over time

Dr Deferred Income / Cr Interest Income

Repayment Posting Examples

Business Event

Accounting Entry

Principal repayment

Dr Customer Account / Cr Loan Account

Interest repayment

Dr Customer Account / Cr Interest Receivable

Fund Movement Clarification

In certain banks, GL postings alone are sufficient to trigger actual fund movements between internal accounts. In these cases:

  • No separate payments integration is required

  • Accounting and payment execution are combined into a single integration

  • Implementation complexity and delivery timelines are reduced

However, for clients who do not hold accounts with the bank (i.e. external customers):

  • GL postings will cover accounting only

  • A separate payments integration (typically via SWIFT or another external payment channel) is required to enable outbound fund transfers

Summary
  • API-First Approach: Integration is possible with any third-party system that exposes APIs.

  • Availability of SFTP: While APIs are recommended we also do support SFTPs.

  • Flexible Architecture: Supports both direct GL posting and end-result transfer to the bank’s core system.

  • Comprehensive Payment Integration: Enables both domestic and international payments, including SWIFT, via API.

  • Scalability: Designed to adapt to evolving banking and financial system requirements.