Dailyentry Documentation

Daily Entry (Journal Entry) Controller Documentation

File: /controllers/dailyentry.php

Purpose: Manages journal entries for double-entry bookkeeping system

Last Updated: December 19, 2024

Total Functions: 8

Lines of Code: 755

---

📋 Overview

The Daily Entry Controller is the core component for managing journal entries in the double-entry bookkeeping system. It handles:

Primary Functions

Related Controllers

---

🗄️ Database Tables

Primary Tables (Direct Operations)

Table NamePurposeKey Columns
**dailyentry**Main journal entriesid, thedate, totalcreditor, totaldebtor, entryComment, userid, branchid, related, reverseofid
**dailyentrycreditor**Credit side entriesdailyentryid, accountstreeid, value, dComment, costcenterid
**dailyentrydebtor**Debit side entriesdailyentryid, accountstreeid, value, dComment, costcenterid
### Integration Tables

Table NamePurposeRelationship
**accountstree**Chart of accountsReferenced by creditor/debtor entries
**costcenter**Cost centersReferenced by creditor/debtor entries
**branch**Branch managementMulti-branch support
**programsetting**System configurationEntry behavior settings
### Financial Impact Tables

Table NamePurposeRelationship
**savedaily**Cash movementsAuto-posted from cash entries
**accountmovement**Account movementsAuto-posted from bank entries
**sellbill**Sales transactionsGenerate automatic entries
**buybill**Purchase transactionsGenerate automatic entries
---

🔧 Key Functions

1. Main Display (Default Action)

Purpose: Display journal entry interface with entry listing

Line: 214

Parameters (via $_POST):

Process Flow:

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Update Branch
IDs for Users
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Load Cost
Centers
└─────────────────┘ └──────────────────┘ └─────────────────┘

Business Logic:

2. DrawTableNew($dailyentryid, $startDate, $endDate, $layingOrder, $branchid, $print)

Purpose: Generate journal entry listing table with advanced formatting

Line: 341

Parameters:

Process Flow:

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Build Query
Filters
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Format for
Print/Screen
└─────────────────┘ └──────────────────┘ └─────────────────┘

Advanced Features:

3. reverse()

Purpose: Reverse a journal entry by creating opposite entry

Line: 591

URL: ?do=reverse&id={entry_id}

Process Flow:

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Load Original
Entry Data
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Reverse Debit
Entries to
Credit
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Reverse Credit
Entries to
Debit
└─────────────────┘ └──────────────────┘ └─────────────────┘

Critical Business Rules:

4. affectAccount($CreditorOrDebtorObj, $type)

Purpose: Update account balances based on journal entry

Line: 668

Parameters:

Double-Entry Logic:

┌─────────────┬─────────────┬─────────────┐
Account
Type
Assets (0)
Liabilities
(1)
Equity (2)
Expenses(3)
Revenue (4)
Cost (5)
└─────────────┴─────────────┴─────────────┘

5. whatToDo($accountType, $numSign, $type)

Purpose: Determine if account balance should increase or decrease

Line: 691

Parameters:

Returns: 'increase' or 'decrease'

6. openingentry

Purpose: Display opening balance entry form

Line: 286

Process:

7. openingbalance

Purpose: Display opening balance management interface

Line: 307

Process:

8. print

Purpose: Generate printable journal entry report

Line: 264

Process:

---

🔄 Business Logic Flow

Journal Entry Creation Workflow

▼
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Validate
Debit = Credit
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Error if
Unbalanced
└─────────────────┘ └──────────────────┘ └─────────────────┘
▼
┌──────────────────┐ ┌─────────────────┐
Update Account
Balances
└──────────────────┘ └─────────────────┘

Entry Reversal Workflow

▼
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Check if
Already Reversed│
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
Exit if
Already
Reversed
└─────────────────┘ └──────────────────┘ └─────────────────┘

Double-Entry Bookkeeping Rules

Fundamental Equation: Assets = Liabilities + Equity

Entry Rules:

1. Every entry must balance (Total Debits = Total Credits)

2. Account nature determines effect:

- Debit increases: Assets, Expenses, Cost of Sales

- Credit increases: Liabilities, Equity, Revenue

3. Journal entries auto-update account balances

4. Reversals create exact opposite entries

---

⚠️ Common Issues

1. Unbalanced Entries

Issue: Total debits ≠ total credits

Prevention: Client-side validation before submission

Fix: System should reject unbalanced entries

2. Branch Assignment

Issue: Entries created without branch assignment

Solution: System auto-updates entries with user's branch ID: 

// Auto-update branch IDs for entries without branches
$allnothavebranch = $dailyEntryEX->queryAllnothavebranch();
foreach ($allnothavebranch as $entry) {
    $dailyEntryEX->updatebranchid($entry->value, $entry->id);
}

3. Account Balance Corruption

Issue: Manual balance changes cause inconsistency

Prevention: Only update balances through journal entries

Fix: Rebuild balances from journal entry history

4. Reversal Chain Issues

Issue: Attempting to reverse already reversed entries

Prevention: Check reverseofid status before reversal: 

if ($olddailyEntry->reverseofid != -10) {
    // Proceed with reversal
}

5. Cost Center Allocation

Issue: Missing cost center assignments

Solution: Validate cost center requirements for expense accounts

---

🔗 Dependencies

Required Files

Critical DAOs

Plugin Integration

The system includes affectplugins.php which handles:

---

🎯 Entry Types and Status Codes

Entry Status (condition)

Reverse Status (reverseofid)

Entry Source (fromFlag)

Related Entry Grouping (related)

---

🎲 Best Practices

1. Entry Creation

2. Account Selection

3. Reversal Management

4. Multi-Branch Support

---

Critical Note: This controller is the heart of the accounting system. All financial transactions flow through journal entries. Any modifications should preserve the double-entry bookkeeping integrity and maintain proper audit trails.