- Log all field values before create() call for both debit and credit entries
- Help identify which fields are empty or incorrect
- Debug the exact values being passed to Bookkeeping objects
- Show field-by-field breakdown to find missing values
- Use bookkeeping->id > 0 to check if entry was created successfully
- create() method returns 0 but entry is actually created with valid ID
- This is a common Dolibarr pattern where create() returns 0 for success
- Check actual entry ID to determine success instead of return value
- Check if account numbers exist in chart of accounts before creating entries
- Add detailed debugging for error messages and entry IDs
- Validate account existence to prevent creation failures
- Show exact error messages from Bookkeeping class
- Remove excessive debugging and field validation
- Use minimal field set like working example
- Add try/catch block for proper error handling
- Use dol_now() for doc_date like working example
- Simplify to essential fields only: doc_date, doc_ref, code_journal, numero_compte, label_compte, montant, sens, fk_doc, fk_user_author
- Start transaction with db->begin() before creating entries
- Commit transaction with db->commit() after all entries created
- Rollback transaction with db->rollback() on any failure
- Follow Dolibarr best practices for accounting entry creation
- Ensure entries are properly committed to database
- Check if account number exists in accounting_account table
- Compare with existing accounting entries to see field differences
- Help identify if account validation is causing the -1 return
- Debug the exact validation requirements
- Add date_creation and tms timestamps
- Add fk_user_creation and fk_user_modification fields
- These fields might be required by Dolibarr's Bookkeeping validation
- Ensure all required fields are set before create() call
- Log all Bookkeeping field values before create() call
- Check if journal code 'OD' exists in accounting_journal table
- Help identify which field or validation is causing the -1 return
- Debug the exact field values being passed to create()
- Show actual result value and type from create() method
- Help identify why result is truthy but not > 0
- Show both result value and error message in failure case
- Debug the exact return value from Bookkeeping::create()
- Remove direct SQL insert fallback that bypasses Dolibarr logic
- Use proper result checking: if (result > 0) for success
- Log actual entry IDs when successfully created
- Use bookkeeping->error for proper error messages
- Maintain Dolibarr's internal validation and business logic
- Add detailed debugging to check what's actually in accounting_bookkeeping table
- Add direct SQL insert fallback when Bookkeeping::create() fails
- Show recent entries in table to debug the issue
- Ensure entries are actually saved to database
- Create separate Bookkeeping instances for debit and credit
- Follow Dolibarr pattern: one entry per debit, one per credit
- Each entry has single montant with proper sens (D/C)
- Separate debug logging for debit vs credit entries
- Ensures proper double-entry bookkeeping structure
- Move Bookkeeping instantiation inside the loop
- Create fresh instance for each accounting entry
- Prevents field contamination between entries
- Ensures each entry is processed independently
- Use correct field names for Bookkeeping class
- Set all required fields: doc_date, doc_ref, code_journal, numero_compte, etc.
- Use proper debit/credit logic with sens field
- Set journal code to 'OD' for VAT declarations
- Link entries to declaration via fk_doc
- Update verification query to use correct field names
- Replace Bookkeeping::create() with direct SQL INSERT
- Bookkeeping class was returning success but not actually saving records
- Add detailed SQL logging to track insert operations
- Ensure entries are actually committed to database
- Add verification query after each bookkeeping create call
- Add final verification to count total entries created
- Help identify if entries are actually being saved to database
- Add debug logs to track bank account ID from config
- Add debug logs to show bank account query and results
- Help identify why bank account code is empty
- Add debug logs to track each accounting entry being created
- Add debug logs to track bookkeeping create results
- Help identify why entries are not being saved to database
- Add user parameter to createODJournalEntries method signature
- Pass user parameter from createAccountingEntries to createODJournalEntries
- Fixes user parameter getting lost between createAccountingEntries and saveAccountingEntries
- Add debug logs to track user parameter through method calls
- Update createAccountingEntries to accept user parameter
- Remove redundant global user declarations
- Pass user parameter through entire accounting creation chain
- Add user parameter to submitDeclaration method signature
- Pass user object from view file to submitDeclaration method
- Remove redundant global user declaration
- Fixes null user parameter in bookkeeping create method
- Use htdocs/accountancy/class/bookkeeping.class.php
- Replace direct SQL with proper Dolibarr Bookkeeping class
- Maintains proper Dolibarr integration and error handling
- Remove dependency on non-existent AccountingBookkeeping class
- Use direct SQL INSERT into accounting_bookkeeping table
- Fixes 'Failed opening required' error for accounting class
- Creates accounting entries directly in database
- Add debug logs to track method calls and return values
- Help diagnose why account details are not being found
- Track account count returned by getCA3LineDetails
- Add debug logs to track CA-3 lines found
- Add debug logs to track OD entries creation
- Add debug logs to track line 8, 20, and balancing entries
- Help diagnose why no OD journal entries are being created
- Temporarily disable status validation to allow re-submission
- Add resetDeclarationStatus() method for testing
- Add reset button for submitted declarations
- Add French language strings for reset functionality
- Allows multiple submission attempts during testing
- Remove duplicate 'Create accounting entries' toggle from journal configuration
- Use existing 'Auto-create accounting entries' setting for submission workflow
- Clean up unused language strings
- Consolidate accounting entry control into single, clear setting
- Add comprehensive accounting integration with OD and bank journal entries
- Create configurable accounting entries toggle in setup
- Implement submission workflow with accounting entry creation
- Add proper error handling and validation
- Support VAT refund threshold logic for account selection
- Integrate with Dolibarr's AccountingBookkeeping class
- Add French language strings for new features
- Changed PDF generation path from /documents/declarationtva/validated/ to /declarationtva/validated/
- Updated hasValidatedDocument() to look in /declarationtva/validated/
- Updated getValidatedPDFPath() to look in /declarationtva/validated/
- This removes the duplicate /documents in the file path
- Files will now be saved in /var/lib/dolibarr/declarationtva/validated/
- URLs will be /dolibarr/documents/declarationtva/validated/ (single /documents)
- Updated generateDetailedCA3PDF to save PDFs in /documents/declarationtva/validated/
- Updated hasValidatedDocument to look in /documents/declarationtva/validated/
- Updated getValidatedPDFPath to look in /documents/declarationtva/validated/
- Removed year/month directory structure
- Should now match the actual file location where PDFs are saved
- URLs should now work correctly
- Removed all error_log debug statements from production code
- Cleaned up hasValidatedDocument method
- Cleaned up declaration list processing
- Code is now production-ready
- PDF detection and generation are working correctly
- Added comprehensive error_log statements to track PDF detection
- Logs declaration ID, number, directory paths, and search patterns
- Shows all PDF files found in the directory
- Will help identify why PDF detection is failing
- Debug info will appear in PHP error logs
- Updated hasValidatedDocument() to use flexible file pattern matching
- Updated getValidatedPDFPath() with same flexible pattern
- First tries exact pattern: CA3_[declaration_number]_*.pdf
- Falls back to flexible pattern: CA3_*[declaration_number]*.pdf
- Should now detect PDFs with complex filenames like CA3_CA3-2025-05-20251002184011_2025-10-06.pdf
- Declaration list should now show green PDF icons for validated declarations
- Modified generateDetailedCA3PDF to save PDFs directly to /documents/declarationtva/YYYY/MM/
- Updated saveValidatedPDF to handle PDFs already in correct location
- Added debugging messages to show PDF generation success/failure
- Fixed path mismatch between PDF generation and document detection
- PDFs should now be properly generated and detected in declaration list
- Modified hasValidatedDocument() to check file system instead of database
- Added getValidatedPDFPath() method to get PDF file path
- Updated declaration list to show clickable PDF download links
- Added DownloadPDF translation in French and English
- PDF icons now link directly to downloadable PDF files
- Fixed issue where validated declarations didn't show PDF availability
- Added ECM integration toggle for easy enable/disable
- Temporarily disabled ECM integration to prevent fatal errors
- Added debugging logs to track ECM files path resolution
- PDF saving to disk still works without ECM integration
- Declaration validation will work without document management
- Can be re-enabled once ECM files path is properly resolved
- Create dedicated VAT declarations folder structure under Dolibarr documents
- Organize by year and month: /documents/declarationtva/YYYY/MM/
- Updated PDF saving to use proper directory structure
- Enhanced ECM file records with proper filepath and descriptions
- Added helper methods for directory management
- Better document organization following Dolibarr conventions
- VAT declarations now have their own dedicated space
