Overview
The General Ledger in Dizlog is where you can see a complete list of all accounting entries that have been posted across the system.
Every time you post a journal entry, pay a bill, record a bill payment, or the system posts entries from POS sales, inventory transfers, and other modules, the details are stored in the Ledger entity and exposed through the Ledger (Transaction List) screen.
This screen is read-only: you use it to review, search, filter, and export ledger lines. Any changes must be done in the original source document (for example, in Journal Entry or Bill).
Key Features
Based on the backend services and frontend guides, the General Ledger module offers these core capabilities:
Central list of ledger transactions
Transactions are stored in the Ledger entity and managed by LedgerService and LedgerController.
The UI shows a Ledger (Transaction List) with columns such as Date, Source, Description, Reference, Debit, Credit, Net Amount, Tax, Account Name.
Filtering and search
Filter by date range, account, and location.
Search by name, description, or reference number using the search box at the top of the page.
Drill-down context via source information
The Source column shows where the entry came from (for example, MPOS for POS sales, BILL for supplier bills, EXPENSE for expenses).
The Reference column shows the document number (such as a bill number or expense reference) you can use to locate the original document in its own module.
Automatic totals
The bottom row shows totals for Debit, Credit, and Net Amount for the filtered list, helping you quickly check if debits and credits balance for the selected period.
Export and print options
Icons on the upper-right of the table allow you to download or print the current view for reporting or sharing.
Modules that Connect to the General Ledger
From the backend wiring, the ledger receives postings from several key modules:
General Accounting – Journal Entry
Journal entries are stored in Journal and JournalItem and managed by JournalService/JournalController; they post to the ledger.
Financials – Accounts Payable
Bills and Bill Payments (BillPayment, BillPaymentItem, BillPaymentDiscount), and related history all connect to the ledger via BillPaymentService.
Accounts Payable Vouchers, Cheque Vouchers, Cheques and other AP entities are also registered alongside the ledger module, indicating that their postings feed into it.
POS / Sales
POS transactions (CashRegisterTransaction) and product sales use mapped Chart of Accounts IDs for Sales Revenue and Cost of Goods Sold. The documentation states that checkout posting “uses mapped accounts” and that ledger entries group revenue and COGS by the mapped accounts.
Inventory & Transfer Orders
Stock transfers and return transfer orders (StockTransfer, StockTransferOrder) integrate with LedgerService; the spec calls out “Ledger Service” as an integration point for stock transfer and return movements.
Chart of Accounts / Financial Accounts
The ledger uses the Chart of Accounts stored in FinancialAccount and loaded by DefaultChartOfAccountsService.
This is maintained in settings modules such as Expense & Income Categories and related account-import screens.
Together, this means the General Ledger is the single place where you see the accounting impact of:
Journal entries
Supplier bills and expenses
Bill payments and AP vouchers
Cheques and cheque vouchers
POS / sales transactions
Inventory transfer and return orders
Getting Started
1. Navigate to the General Ledger
Log in to Dizlog.
In the left navigation menu, go to Financials.
Under General Accounting, click General Ledger (or Ledger (Transaction List), depending on your menu label).
The Ledger screen will open, showing the most recent transactions and filters at the top.
2. Ensure your Chart of Accounts is set up
Before the ledger can show meaningful data, your Chart of Accounts must exist in the database. This is managed by the DefaultChartOfAccountsService and stored as FinancialAccount records.
In practice, this means:
Your accountant or implementer has already created or imported your accounts in the relevant settings area (for example, Expense & Income Categories / Import Accounts).
Products, services, and other modules have been mapped to the correct accounts where needed.
3. Make sure transactions are posted
The ledger only shows posted or completed transactions from other modules. Common examples:
Journal entries with status POSTED (not drafts).
Bills and expenses that have been submitted/approved and, where applicable, paid.
POS sales that have been checked out.
Stock transfers that have reached the proper status where ledger posting happens (for example, IN_TRANSIT/RECEIVED based on the transfer order spec).
How to Use
A. View ledger transactions for a period
Open the General Ledger screen.
At the top right of the filters, set the Date range:
Click the date field and choose the start and end dates.
Leave Account set to All if you want every account, or choose a specific account to narrow the list.
Choose a Location (or leave as All) if you only want entries from one branch or store.
Click the search icon (if present) or let the page refresh automatically.
Scroll through the list to review each entry:
Date – when the entry was posted.
Source – where it came from (BILL, MPOS, EXPENSE, etc.).
Description – short text from the source document.
Reference – the originating document number.
Debit / Credit – amounts posted to the account.
Net Amount – the net impact for that row (commonly debit minus credit).
Tax – associated tax, if any.
Account Name – the ledger account used.
At the bottom, check the Total row to see the sum of Debit, Credit, and Net Amount for the filtered period.
B. Find all entries for a specific account
In the Account dropdown, pick the account you want to review (for example, Sales/Revenue or Accounts Payable).
Set the Date range you care about.
Optionally, choose a Location if you only want that branch.
Use the search box to further narrow results by description or reference, if needed.
Review the filtered list and totals.
This is useful when reconciling a specific account or preparing financial statements that also depend on FinancialAccount and FinancialStatement data.
C. Locate the ledger impact of a specific document
Suppose you want to see how a particular bill or journal entry hit the ledger.
Note the reference number from the original module (for example, the bill number or journal number).
Go to General Ledger.
In the Search Name / Description / Reference Number box, type that reference and press Enter.
The list will show all ledger rows linked to that document in the Reference column.
Use the account, date, or location filters if you still see many rows.
D. Export or print the ledger list
Apply filters (date, account, location, search) until the list shows what you need.
Click one of the icons on the top-right of the table:
Download / Export icon – exports the current view (for example to a file).
Print icon – prints the current list.
Follow your browser’s prompts to save or print.
Troubleshooting
1. “A transaction I expect is not showing in the ledger.”
Check the following:
Date range – Make sure the Date filter includes the transaction’s posting date.
Account filter – If you selected a specific account, confirm the transaction actually posts to that account. The mapping is controlled by your chart of accounts and product/account configuration.
Location – Verify you’re on the correct Location or use All.
Status of source document –
Journal entries must be posted, not draft.
Bills, expenses, and AP vouchers must be at a finalized/approved status so that the BillPayment or related services have posted them to the ledger.
If everything looks correct but the entry is still missing, your finance admin should review the original document and its mapped accounts.
2. “The debit and credit totals don’t look right.”
Make sure filters (date, account, location) match the period you are reconciling.
Remember that Net Amount is the net effect for the displayed rows; if you filter by a single account, Net Amount should reflect that account’s movement only.
If you are comparing the ledger to Financial Statements, know that both use the same FinancialAccount records and ledger data, so mismatches are usually due to different filters or missing postings.
3. “I need to change a ledger entry.”
The ledger is designed as an audit trail and cannot be edited directly. Entries are created by services such as JournalService, BillPaymentService, LedgerService, and others.
To correct an error:
Go to the original module:
Journal Entry
Bill / Expense / Bill Payment
Accounts Payable Voucher / Cheque / Cheque Voucher
POS sale or Inventory transfer (as applicable)
Edit, reverse, or cancel the original document using the options provided there.
Once saved/posted, the system will create new ledger entries reflecting the correction.
4. “Why are some descriptions or references hard to understand?”
Descriptions come directly from the source document (for example, a bill description or journal line description).
Reference is usually the original document number (bill number, journal number, expense reference, etc.).
If the description is unclear, open the original document in its own module and review the full details there.
5. “Exported data doesn’t match what I see on screen.”
The export always reflects the current filters on the ledger screen.
If the file looks different:
Confirm the date, account, and location filters are set exactly as when you exported.
Re-export after verifying the filters.
With these steps, you can use the General Ledger module as your main window into all financial activity inside Dizlog—reviewing, filtering, and exporting the detailed transaction history that is fed by Journal Entry, Accounts Payable, POS, Inventory, and other connected modules.