feat(CRED-32): Fineract-Odoo Journal Entries Integration #82

hayederr · 2025-09-10T07:55:51Z

Fineract-Odoo Journal Entries Integration

Overview

This module provides seamless integration between Apache Fineract and Odoo ERP system for automated journal entries synchronization. The integration ensures that all accounting transactions recorded in Fineract are automatically synchronized to Odoo, maintaining consistency between both systems.

Background & Problem Statement

Before Integration

In the original Fineract system:

Journal entries were created automatically for loan transactions (disbursements, repayments, etc.)
These entries were stored in the acc_gl_journal_entry table
No mechanism existed to track which entries were synced to external systems
Manual intervention was required to synchronize accounting data to external ERPs

Problems Addressed

Data Synchronization: Automatic sync of journal entries to Odoo
Tracking: Monitor which entries are successfully synced vs. failed
Reliability: Retry mechanism for failed syncs
Auditability: Complete audit trail of sync operations
Performance: Batch processing of pending entries

Solution Architecture

Core Components

Event Listener: Captures journal entry creation events
Tracking System: Records sync status for each journal entry
Scheduled Job: Processes pending entries in batches
Error Handling: Tracks and retries failed synchronizations

Integration Points

Fineract Event System: LoanJournalEntryCreatedBusinessEvent
Spring Batch Jobs: Scheduled processing
Odoo REST API: External system integration

Event-Driven Flow

1. Journal Entry Creation (Existing Fineract Flow)

Loan Transaction → Accounting Processor → Journal Entry Creation → Database Storage

Key Files Involved:

CustomCashBasedAccountingProcessorForLoan.java - Processes loan accounting transactions
AccountingProcessorHelper.java - Core journal entry persistence logic

Event Trigger Location:

// File: AccountingProcessorHelper.java
// Method: persistJournalEntry()
// Line: ~1284

public JournalEntry persistJournalEntry(JournalEntry journalEntry) {
    boolean isNew = journalEntry.isNew();
    JournalEntry savedJournalEntry = this.glJournalEntryRepository.saveAndFlush(journalEntry);
    if (isNew && journalEntry.getLoanTransactionId() != null) {
        businessEventNotifierService.notifyPostBusinessEvent(new LoanJournalEntryCreatedBusinessEvent(savedJournalEntry));
    }
    return savedJournalEntry;
}

2. Event Capture & Tracking (Our Integration)

Journal Entry Event → Event Listener → Create Tracking Record → Pending Sync

Implementation:

// File: JournalEntryOdooTrackingService.java
// Listens to: LoanJournalEntryCreatedBusinessEvent

@PostConstruct
public void addListeners() {
    businessEventNotifierService.addPostBusinessEventListener(LoanJournalEntryCreatedBusinessEvent.class, event -> {
        JournalEntry journalEntry = event.get();
        createTrackingRecord(journalEntry);
    });
}

3. Scheduled Synchronization

Scheduled Job → Fetch Pending Entries → Sync to Odoo → Update Status

Implementation:

// File: OdooJournalEntriesSyncJobTasklet.java
// Schedule: Every 1 hour (0 0 * * * ?)

List<JournalEntryOdooSync> pendingEntries = journalEntryOdooSyncRepository.findPendingEntries();
for (JournalEntryOdooSync sync : pendingEntries) {
    // Sync to Odoo and update status
}

Implementation Details

1. Event System Integration

Event Class Used:

LoanJournalEntryCreatedBusinessEvent (Fineract core)
Location: fineract-loan/src/main/java/org/apache/fineract/infrastructure/event/business/domain/journalentry/

Event Characteristics:

Triggered automatically when journal entries are persisted
Provides access to the complete JournalEntry object
Fires for loan-related transactions only
Implements NoExternalEvent (internal use only)

Our Event Listener:

// File: custom/crediblex/integration/odoo/src/main/java/com/crediblex/fineract/integration/odoo/service/JournalEntryOdooTrackingService.java

@Service
@ConditionalOnProperty(name = "odoo.enabled", havingValue = "true")
public class JournalEntryOdooTrackingService {
    // Automatically creates tracking records for all journal entries
}

2. Database Tracking System

New Table: journal_entry_odoo_sync

Column	Type	Description
id	bigint	Primary key
journal_entry_id	bigint	FK to `acc_gl_journal_entry`
is_posted_to_odoo	boolean	Sync status
created_at	timestamp	Record creation time
posted_at	timestamp	Successful sync time
odoo_move_id	bigint	Odoo move reference
error_message	varchar(1000)	Failure details

Entity Class:

// File: custom/crediblex/integration/odoo/src/main/java/com/crediblex/fineract/integration/odoo/domain/JournalEntryOdooSync.java

@Entity
@Table(name = "journal_entry_odoo_sync")
public class JournalEntryOdooSync extends AbstractPersistableCustom {
    // Complete tracking entity with lifecycle methods
}

3. Repository & Data Access

Repository Interface:

// File: custom/crediblex/integration/odoo/src/main/java/com/crediblex/fineract/integration/odoo/domain/JournalEntryOdooSyncRepository.java

@Repository
public interface JournalEntryOdooSyncRepository extends JpaRepository<JournalEntryOdooSync, Long> {
    List<JournalEntryOdooSync> findPendingEntries();
    List<JournalEntryOdooSync> findFailedEntries();
    long countUnpostedEntries();
}

4. Scheduled Job Implementation

Job Configuration:

// File: custom/crediblex/integration/job/src/main/java/com/crediblex/fineract/integration/job/OdooJournalEntriesSyncJobConfiguration.java

@Configuration
public class OdooJournalEntriesSyncJobConfiguration {
    // Spring Batch job definition with 1-hour schedule
}

Job Registration:

<!-- File: custom/crediblex/infrastructure/starter/src/main/resources/db/custom-changelog/0025-add-odoo-journal-entries-sync-job.xml -->
<insert tableName="job">
    <column name="cron_expression" value="0 0 * * * ?"/>
    <column name="short_name" value="ODOJSYNC"/>
</insert>

Database Schema

Migration Files

Job Registration:

custom/crediblex/infrastructure/starter/src/main/resources/db/custom-changelog/0025-add-odoo-journal-entries-sync-job.xml

Tracking Table:

custom/crediblex/infrastructure/starter/src/main/resources/db/custom-changelog/0026-create-journal-entry-odoo-sync-table.xml

Schema Diagram

acc_gl_journal_entry (Existing)
        │
        │ (1:1)
        ▼
journal_entry_odoo_sync (New)
        │
        │ (Tracks sync status)
        ▼
Odoo ERP System

Configuration

Application Properties

# File: fineract-provider/src/main/resources/application.properties

# Odoo Integration Configuration
odoo.enabled=true
odoo.url=${ODOO_URL:http://localhost:8069}
odoo.database=${ODOO_DATABASE:odoo}
odoo.username=${ODOO_USERNAME:admin}
odoo.password=${ODOO_PASSWORD:admin}
odoo.connection-timeout=${ODOO_CONNECTION_TIMEOUT:30000}
odoo.read-timeout=${ODOO_READ_TIMEOUT:60000}
odoo.max-retries=${ODOO_MAX_RETRIES:3}
odoo.retry-delay=${ODOO_RETRY_DELAY:1000}

Environment Variables

ODOO_URL=http://your-odoo-instance:8069
ODOO_DATABASE=your_database
ODOO_USERNAME=your_username
ODOO_PASSWORD=your_password

⚠️ Important Configuration Notes

Balancing Account Setup: Update the getBalancingAccountId() method in OdooJournalEntryService.java:

private Integer getBalancingAccountId(JournalEntry fineractEntry) {
    // Replace 999999 with actual account ID from your Odoo instance
    return 999999; // This should be a valid suspense/clearing account
}

Account Mapping: Ensure Fineract GL account codes match or can be mapped to Odoo account codes
Journal Setup: Verify that appropriate journals exist in Odoo:
- General journal for miscellaneous entries
- Specific journals for different transaction types if needed
User Permissions: Ensure the Odoo user has proper permissions:
- Create and post accounting entries
- Read account and journal information
- Access to relevant accounting features

Usage

1. Automatic Tracking

Once deployed, the system automatically:

Captures all new journal entry creations
Creates tracking records in journal_entry_odoo_sync
Marks entries as pending for synchronization

2. Scheduled Synchronization

The job runs every hour and:

Fetches all pending entries
Attempts to sync each to Odoo
Updates status (success/failure)
Logs results for monitoring

3. Manual Operations

Check Pending Entries:

SELECT COUNT(*) FROM journal_entry_odoo_sync WHERE is_posted_to_odoo = false;

View Failed Entries:

SELECT * FROM journal_entry_odoo_sync
WHERE is_posted_to_odoo = false AND error_message IS NOT NULL;

Retry Failed Entries:

UPDATE journal_entry_odoo_sync
SET error_message = NULL
WHERE is_posted_to_odoo = false AND error_message IS NOT NULL;

Monitoring & Troubleshooting

Log Messages

INFO  - Created Odoo sync tracking record for journal entry ID: 12345
INFO  - Found 25 pending journal entries to sync to Odoo
INFO  - Successfully posted journal entry 12345 to Odoo with move ID: 67890
WARN  - Marked journal entry 12346 as failed to post to Odoo: Connection timeout

Key Metrics

Pending Entries: journalEntryOdooSyncRepository.countUnpostedEntries()
Success Rate: Ratio of successful vs. total sync attempts
Error Patterns: Common failure reasons in error_message

Common Issues

Odoo Connection Failures: Check network connectivity and credentials
Data Validation Errors: Verify journal entry data format
Performance Issues: Monitor batch size and processing time

File Structure

custom/crediblex/
├── integration/
│   ├── odoo/src/main/java/com/crediblex/fineract/integration/odoo/
│   │   ├── client/
│   │   │   └── OdooApiClient.java                           # Enhanced Odoo API client
│   │   ├── domain/
│   │   │   ├── JournalEntryOdooSync.java                    # Tracking entity
│   │   │   └── JournalEntryOdooSyncRepository.java          # Data access
│   │   ├── service/
│   │   │   ├── JournalEntryOdooTrackingService.java         # Event listener
│   │   │   ├── OdooIntegrationReadPlatformService.java      # Service interface (enhanced)
│   │   │   ├── OdooIntegrationReadPlatformServiceImpl.java  # Service implementation (enhanced)
│   │   │   └── OdooJournalEntryService.java                 # Journal entry posting service
│   │   ├── config/
│   │   │   └── OdooProperties.java                          # Configuration properties
│   │   ├── exception/
│   │   │   └── [exception classes]                          # Odoo-specific exceptions
│   │   └── api/
│   │       └── OdooIntegrationApiResource.java              # REST endpoints
│   └── job/src/main/java/com/crediblex/fineract/integration/job/
│       ├── OdooJournalEntriesSyncJobTasklet.java           # Sync job implementation
│       └── OdooJournalEntriesSyncJobConfiguration.java     # Job configuration
├── infrastructure/starter/src/main/resources/db/custom-changelog/
│   ├── 0025-add-odoo-journal-entries-sync-job.xml         # Job registration
│   └── 0026-create-journal-entry-odoo-sync-table.xml      # Tracking table
└── accounting/journalentry/src/main/java/com/crediblex/fineract/accounting/journalentry/service/
    └── CustomCashBasedAccountingProcessorForLoan.java     # Custom accounting processor

Core Fineract Files (Referenced)

fineract-provider/src/main/java/org/apache/fineract/
├── accounting/journalentry/service/
│   └── AccountingProcessorHelper.java                      # Event trigger point
└── infrastructure/event/business/domain/journalentry/
    └── LoanJournalEntryCreatedBusinessEvent.java          # Event class

fineract-loan/src/main/java/org/apache/fineract/
└── infrastructure/event/business/domain/journalentry/
    └── LoanJournalEntryCreatedBusinessEvent.java          # Event implementation

Benefits

1. Reliability

Automatic Tracking: No manual intervention required
Error Recovery: Failed syncs are tracked and can be retried
Data Integrity: Ensures all journal entries are accounted for

2. Performance

Batch Processing: Efficient handling of multiple entries
Asynchronous: Non-blocking journal entry creation
Configurable: Adjustable sync frequency and batch sizes

3. Auditability

Complete Trail: Full history of sync operations
Status Tracking: Real-time visibility into sync status
Error Details: Detailed failure information for troubleshooting

4. Maintainability

Non-Intrusive: Minimal changes to core Fineract code
Configurable: Easy to enable/disable via properties
Extensible: Easy to add new sync targets or modify logic

Next Steps

✅ Completed Implementation

✅ Event-Driven Tracking: Automatic capture of journal entry creation events
✅ Database Schema: Tracking table with proper relationships and indexes
✅ Scheduled Jobs: Hourly batch processing of pending entries
✅ Odoo API Integration: Complete Odoo service implementation with:
- Authentication and session management
- Account mapping between Fineract and Odoo
- Journal entry posting with proper debit/credit balance
- Account move creation and posting (draft → posted)
- Error handling and retry mechanisms

🔧 Configuration Required

Account Mapping: Update getBalancingAccountId() method in OdooJournalEntryService with actual Odoo account IDs
Journal Configuration: Ensure appropriate journals exist in Odoo for different transaction types
Environment Setup: Configure Odoo connection properties in application.properties

🚀 Future Enhancements

Advanced Account Mapping: Implement business logic for automatic account mapping based on:
- Transaction types (loan disbursement, repayment, interest, fees)
- Office/branch specific accounts
- Product-specific accounts
Retry Logic: Implement exponential backoff for failed syncs
Monitoring Dashboard: Create UI for tracking sync status and performance metrics
Performance Optimization:
- Batch processing optimization
- Account mapping cache improvements
- Parallel processing for large volumes
Error Notification: Add alerts for sync failures and system issues

📋 Implementation Details

The complete Odoo integration now includes:

Enhanced OdooApiClient: Extended existing client with executeKw, search, searchRead, create, and postAccountMove methods
Enhanced OdooIntegrationReadPlatformService: Added account mapping functionality with caching to existing service
OdooJournalEntryService: High-level service for posting journal entries with validation
Enhanced Job Tasklet: Uses real Odoo services instead of simulation code

🏗️ Architecture Benefits

Reused Existing Components: Enhanced existing services instead of creating duplicates
Clean Separation: API client handles low-level operations, service handles business logic
Proper Caching: Account mappings cached to reduce API calls
Error Handling: Comprehensive error handling and logging at each level

Last Updated: September 2025
Version: 1.0
Author: Crediblex Development Team

…ion for journal entries

…ceptions and controllers, and implement new service structure - Simplified OdooApiClient by removing unnecessary exception handling and logging. - Added OdooIntegrationReadPlatformService and its implementation for better separation of concerns. - Removed OdooJournalService and related controller classes to reduce complexity. - Updated OdooProperties to include an API key field. - Deleted outdated application-odoo.yml configuration file. - Cleaned up Gradle build files by removing unused dependencies and configurations. - Enhanced logging for connection tests and authentication processes.

… and tasklet implementation

…ibleX Fineract Integration

…ion details

…ngelog

…e update

…d error handling

…ryOdooSync class

…d error handling

…mprovements

…Odoo tracking service

…d loan retrieval

…improved accuracy

… script

…e changes

…tation

Copilot

Pull Request Overview

Copilot reviewed 33 out of 33 changed files in this pull request and generated no new comments.

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

…vent

Copilot

Pull Request Overview

Copilot reviewed 33 out of 33 changed files in this pull request and generated 1 comment.

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

...ava/com/crediblex/fineract/integration/odoo/service/JournalEntryOdooTrackingServiceTest.java

- Cleaned up imports and removed unused code in OdooIntegrationApiResource and OdooApiClient. - Simplified HTTP client configuration in OdooApiClient. - Streamlined connection testing and account mapping logic in OdooIntegrationReadPlatformServiceImpl. - Enhanced error handling and logging in OdooJournalEntryService. - Consolidated move line creation logic for journal entries. - Improved test coverage and assertions in JournalEntryOdooTrackingServiceTest. - Updated CrediblexIntegrationAutoConfiguration for better component scanning.

…PlatformServiceJpaRepositoryImpl

Copilot

Pull Request Overview

Copilot reviewed 33 out of 33 changed files in this pull request and generated 14 comments.

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

.../com/crediblex/fineract/integration/odoo/service/OdooIntegrationReadPlatformServiceImpl.java

...ava/com/crediblex/fineract/integration/odoo/service/JournalEntryOdooTrackingServiceTest.java

…classes

…yOdooSync classes

Copilot

Pull Request Overview

Copilot reviewed 33 out of 33 changed files in this pull request and generated 1 comment.

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

.../com/crediblex/fineract/integration/odoo/service/OdooIntegrationReadPlatformServiceImpl.java

Napho · 2025-10-01T06:23:41Z

fineract-provider/src/main/resources/application.properties

+# Odoo Integration Configuration
+odoo.enabled=true
+odoo.url=${ODOO_URL:http://localhost:8069}
+odoo.database=${ODOO_DATABASE:odoo}


Why dont you add a properties file in the cusotm module with these properties?

what do you mean ? isn't these env vars supposed to go here ?

Napho · 2025-10-01T06:25:14Z

...oo/src/main/java/com/crediblex/fineract/integration/odoo/api/OdooIntegrationApiResource.java

+    @ApiResponses({
+            @ApiResponse(responseCode = "200", description = "OK", content = @Content(schema = @Schema(implementation = Map.class))) })
+    public String testConnection(@Context final UriInfo uriInfo) {
+        this.context.authenticatedUser().validateHasReadPermission(RESOURCE_NAME_FOR_PERMISSION);


I dont see any migration adding this permission to fineract.

It was just test endpoint I made for myself to check Odoo connection - we don't need this permission so I'll remove it

… Odoo integration

…onization

… integration services

Copilot

Pull Request Overview

Copilot reviewed 32 out of 32 changed files in this pull request and generated 11 comments.

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

Copilot · 2025-10-02T06:52:18Z

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

+        // - Product type
+        // - etc.
+
+        return 999999; // Replace with actual account ID from your Odoo instance


This hardcoded account ID should be configurable. Consider moving this to application properties or making it configurable through the OdooProperties class to avoid requiring code changes for different environments.

Copilot · 2025-10-02T06:52:18Z

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

+        // Basic move information
+        moveValues.put("journal_id", journalId);
+        moveValues.put("date", fineractEntry.getTransactionDate().format(DateTimeFormatter.ISO_LOCAL_DATE));
+        moveValues.put("ref", "Haider JE " + fineractEntry.getId());


The hardcoded 'Haider' prefix should be configurable or removed. This appears to be environment-specific and should be made generic or configurable through properties.

Copilot · 2025-10-02T06:52:18Z

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

+            debitLine.put("account_id", accountId);
+            debitLine.put("debit", amount);
+            debitLine.put("credit", BigDecimal.ZERO);
+            debitLine.put("name", fineractEntry.getDescription() != null ? fineractEntry.getDescription() : "Haider Journal Entry");


Multiple hardcoded 'Haider' references should be made configurable or use a generic naming convention. These appear to be environment-specific and reduce code portability.

Copilot · 2025-10-02T06:52:19Z

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

+            creditLine.put("account_id", accountId);
+            creditLine.put("debit", BigDecimal.ZERO);
+            creditLine.put("credit", amount);
+            creditLine.put("name", fineractEntry.getDescription() != null ? fineractEntry.getDescription() : "Haider Journal Entry");


Multiple hardcoded 'Haider' references should be made configurable or use a generic naming convention. These appear to be environment-specific and reduce code portability.

Copilot · 2025-10-02T06:52:19Z

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

+                    line.put("credit", netAmount.abs());
+                }
+
+                line.put("name", "Haider consolidated entry for account " + accountId);


Multiple hardcoded 'Haider' references should be made configurable or use a generic naming convention. These appear to be environment-specific and reduce code portability.

Suggested change

line.put("name", "Haider consolidated entry for account " + accountId);

line.put("name", "Consolidated entry for account " + accountId);

Copilot · 2025-10-02T06:52:19Z

...ava/com/crediblex/fineract/integration/odoo/service/JournalEntryOdooTrackingServiceTest.java

+import com.crediblex.fineract.integration.odoo.data.ExtendedSavingsAccountSummaryData;
+import com.crediblex.fineract.integration.odoo.domain.JournalEntryOdooSyncRepository;
+import com.crediblex.fineract.integration.odoo.event.LoanJournalEntryCreatedBusinessEvent;
+import com.crediblex.fineract.integration.odoo.event.SavingsJournalEntryCreatedBusinessEvent;
+import com.crediblex.fineract.portfolio.client.service.CredXAccountDetailsReadPlatformServiceJpaRepositoryImpl;


Import statements reference incorrect package paths. ExtendedSavingsAccountSummaryData should be imported from the portfolio.accountdetails package, and the service class should reference the correct accountdetails package structure.

Suggested change

import com.crediblex.fineract.integration.odoo.data.ExtendedSavingsAccountSummaryData;

import com.crediblex.fineract.integration.odoo.domain.JournalEntryOdooSyncRepository;

import com.crediblex.fineract.integration.odoo.event.LoanJournalEntryCreatedBusinessEvent;

import com.crediblex.fineract.integration.odoo.event.SavingsJournalEntryCreatedBusinessEvent;

import com.crediblex.fineract.portfolio.client.service.CredXAccountDetailsReadPlatformServiceJpaRepositoryImpl;

import org.apache.fineract.portfolio.accountdetails.data.ExtendedSavingsAccountSummaryData;

import com.crediblex.fineract.integration.odoo.domain.JournalEntryOdooSyncRepository;

import com.crediblex.fineract.integration.odoo.event.LoanJournalEntryCreatedBusinessEvent;

import com.crediblex.fineract.integration.odoo.event.SavingsJournalEntryCreatedBusinessEvent;

import org.apache.fineract.portfolio.accountdetails.service.CredXAccountDetailsReadPlatformServiceJpaRepositoryImpl;

Copilot · 2025-10-02T06:52:20Z

.../com/crediblex/fineract/integration/odoo/service/OdooIntegrationReadPlatformServiceImpl.java

+    private Map<String, Set<String>> initializeJournalGlCodeMapping() {
+        Map<String, Set<String>> mapping = new HashMap<>();
+
+        // BNK5 journal for specific GL codes


[nitpick] The hardcoded journal mapping configuration should be documented with comments explaining what each GL code represents and why they're mapped to BNK5 journal. This will help with maintenance and future configuration changes.

Suggested change

// BNK5 journal for specific GL codes

// BNK5 journal for specific GL codes.

// The following GL codes are mapped to the BNK5 journal for the following reasons:

// 100031 - Main Bank Account: Represents the organization's primary bank account.

// 300004 - Loan Disbursement Account: Used for disbursing loans to clients.

// 200065 - Loan Repayment Account: Used for receiving loan repayments from clients.

// 200040 - Interest Income Account: Used for recording interest income from loans.

// These accounts are mapped to the BNK5 journal because all transactions involving these GL codes

// are processed through the BNK5 bank journal in Odoo, ensuring proper reconciliation and reporting.

Copilot · 2025-10-02T06:52:20Z

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

+
+            // Credit line (balancing entry) - you might need to determine this based on business logic
+            Map<String, Object> creditLine = new HashMap<>();
+            creditLine.put("account_id", getBalancingAccountId(fineractEntry));


The balancing account logic is overly simplified and uses a hardcoded account ID. Consider implementing proper business logic to determine the appropriate balancing account based on transaction type, office, or other business rules.

Copilot · 2025-10-02T06:52:20Z

...o/src/main/java/com/crediblex/fineract/integration/odoo/service/OdooJournalEntryService.java

+
+            // Debit line (balancing entry)
+            Map<String, Object> debitLine = new HashMap<>();
+            debitLine.put("account_id", getBalancingAccountId(fineractEntry));


The balancing account logic is overly simplified and uses a hardcoded account ID. Consider implementing proper business logic to determine the appropriate balancing account based on transaction type, office, or other business rules.

Copilot · 2025-10-02T06:52:20Z

custom/crediblex/integration/odoo/dependencies.gradle

+ * specific language governing permissions and limitations
+ * under the License.
+ */
+


Duplicate dependency declaration for jakarta.ws.rs-api. The dependency is declared twice (lines 30 and 47) which is redundant and should be cleaned up.

hayederr added 10 commits September 10, 2025 12:55

feat: Add CredibleX Fineract Integration Module

daef6c6

feat: Implement Odoo integration with connection test and configuration

7844a0f

feat: Add Odoo integration with controllers, services, and configurat…

9ac3660

…ion for journal entries

feat: Add Odoo Journal Entries Sync Job with necessary configurations…

4e83dfc

… and tasklet implementation

refactor: Remove unused dependencies and configuration files for Cred…

1e3ed62

…ibleX Fineract Integration

feat: Enhance webhook payload with affected installments and transact…

8cf1a64

…ion details

feat: Add Odoo Journal Entries Sync Job configuration to database cha…

ca52d8c

…ngelog

fix: Update create_time to use 'now()' and remove redundant short_nam…

bf8ad3a

…e update

feat: Implement Odoo journal entries synchronization with tracking an…

e9dd2ac

…d error handling

Copilot AI review requested due to automatic review settings September 18, 2025 18:39

This comment was marked as outdated.

Sign in to view

hayederr added 2 commits September 19, 2025 11:56

fix: Specify generic type for AbstractPersistableCustom in JournalEnt…

79bf838

…ryOdooSync class

feat: Implement Odoo journal entry posting service with validation an…

6bebaf1

…d error handling

Copilot AI review requested due to automatic review settings September 19, 2025 12:34

This comment was marked as outdated.

Sign in to view

hayederr added 4 commits September 23, 2025 16:45

feat: Add loan_id to journal entry sync for grouping and processing i…

fbe5609

…mprovements

feat: Add SavingsJournalEntryCreatedBusinessEvent and integrate with …

b90f8ae

…Odoo tracking service

feat: Enhance Odoo integration with savings account support and linke…

f9482a7

…d loan retrieval

feat: Update journal search criteria to use specific code 'BNK5' for …

a539224

…improved accuracy

Copilot AI review requested due to automatic review settings September 25, 2025 06:50

hayederr changed the title ~~feat: Add CredibleX Fineract Integration Module~~ feat(CRED-32): Added Odoo Integration Sep 25, 2025

hayederr requested review from Napho, caasiremos and hamzafarooqX September 25, 2025 06:51

This comment was marked as outdated.

Sign in to view

hayederr changed the title ~~feat(CRED-32): Added Odoo Integration~~ feat(CRED-32): Fineract-Odoo Journal Entries Integration Sep 25, 2025

hayederr added 2 commits September 25, 2025 13:59

feat: Update PostgreSQL configuration and remove Odoo connection test…

f5b7f62

… script

fix: Correct typo in encryption property name in application.properties

08542e0

Copilot AI review requested due to automatic review settings September 25, 2025 09:00

This comment was marked as outdated.

Sign in to view

hayederr added 4 commits September 25, 2025 14:12

Merge branch 'develop' into cred-32/odoo-integration

ee40bb4

Merge branch 'develop' into cred-32/odoo-integration

c289551

feat(CRED-XXX): Add Odoo journal entries sync job and related databas…

a05bf3b

…e changes

fix: Clean up formatting in Odoo journal entry implementation documen…

7b6b5a8

…tation

Copilot AI review requested due to automatic review settings September 30, 2025 23:54

Copilot AI reviewed Sep 30, 2025

View reviewed changes

hayederr added 2 commits October 1, 2025 04:56

fix: Ensure newline at end of file in application.properties

749daa9

fix: Reorder import statements in SavingsJournalEntryCreatedBusinessE…

db57df5

…vent

Copilot AI review requested due to automatic review settings October 1, 2025 00:41

Copilot AI reviewed Oct 1, 2025

View reviewed changes

...ava/com/crediblex/fineract/integration/odoo/service/JournalEntryOdooTrackingServiceTest.java Outdated Show resolved Hide resolved

hayederr added 2 commits October 1, 2025 05:49

fix: Improve formatting of Javadoc comment in CredXAccountDetailsRead…

a0ca521

…PlatformServiceJpaRepositoryImpl

Copilot AI review requested due to automatic review settings October 1, 2025 00:55

Copilot AI reviewed Oct 1, 2025

View reviewed changes

hayederr added 2 commits October 1, 2025 06:15

fix: Organize and optimize import statements across Odoo integration …

9ecffae

…classes

fix: Remove unused import statements in OdooApiClient and JournalEntr…

e03693c

…yOdooSync classes

Copilot AI review requested due to automatic review settings October 1, 2025 01:19

Copilot AI reviewed Oct 1, 2025

View reviewed changes

.../com/crediblex/fineract/integration/odoo/service/OdooIntegrationReadPlatformServiceImpl.java Outdated Show resolved Hide resolved

fiter-julius-oketayot previously approved these changes Oct 1, 2025

View reviewed changes

Napho requested changes Oct 1, 2025

View reviewed changes

hayederr added 3 commits October 1, 2025 15:21

feat: Implement dynamic journal mapping based on GL account codes for…

9f95dca

… Odoo integration

fix: Enhance error handling and logging for Odoo journal entry synchr…

2e1b94b

…onization

fix: Improve error handling and logging in Odoo integration services

7a2331f

hayederr dismissed fiter-julius-oketayot’s stale review via 7a2331f October 2, 2025 06:45

fix: Refactor logging and error messages for improved clarity in Odoo…

9fad344

… integration services

Copilot AI review requested due to automatic review settings October 2, 2025 06:50

Copilot AI reviewed Oct 2, 2025

View reviewed changes

	line.put("name", "Haider consolidated entry for account " + accountId);
	line.put("name", "Consolidated entry for account " + accountId);

-        // BNK5 journal for specific GL codes
+        // BNK5 journal for specific GL codes.
+        // The following GL codes are mapped to the BNK5 journal for the following reasons:
+        //   100031 - Main Bank Account: Represents the organization's primary bank account.
+        //   300004 - Loan Disbursement Account: Used for disbursing loans to clients.
+        //   200065 - Loan Repayment Account: Used for receiving loan repayments from clients.
+        //   200040 - Interest Income Account: Used for recording interest income from loans.
+        // These accounts are mapped to the BNK5 journal because all transactions involving these GL codes
+        // are processed through the BNK5 bank journal in Odoo, ensuring proper reconciliation and reporting.

feat(CRED-32): Fineract-Odoo Journal Entries Integration #82

Are you sure you want to change the base?

feat(CRED-32): Fineract-Odoo Journal Entries Integration #82

Uh oh!

Conversation

hayederr commented Sep 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Fineract-Odoo Journal Entries Integration

Overview

Table of Contents

Background & Problem Statement

Before Integration

Problems Addressed

Solution Architecture

Core Components

Integration Points

Event-Driven Flow

1. Journal Entry Creation (Existing Fineract Flow)

2. Event Capture & Tracking (Our Integration)

3. Scheduled Synchronization

Implementation Details

1. Event System Integration

2. Database Tracking System

3. Repository & Data Access

4. Scheduled Job Implementation

Database Schema

Migration Files

Schema Diagram

Configuration

Application Properties

Environment Variables

⚠️ Important Configuration Notes

Usage

1. Automatic Tracking

2. Scheduled Synchronization

3. Manual Operations

Monitoring & Troubleshooting

Log Messages

Key Metrics

Common Issues

File Structure

Core Fineract Files (Referenced)

Benefits

1. Reliability

2. Performance

3. Auditability

4. Maintainability

Next Steps

✅ Completed Implementation

🔧 Configuration Required

🚀 Future Enhancements

📋 Implementation Details

🏗️ Architecture Benefits

Uh oh!

This comment was marked as outdated.

Uh oh!

This comment was marked as outdated.

Uh oh!

This comment was marked as outdated.

Uh oh!

This comment was marked as outdated.

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

hayederr commented Sep 10, 2025 •

edited

Loading