The chart of accounts is the backbone of Penahak. Every module resolves its postings to a ledger here, so it is worth structuring carefully before you start trading.
Structure
Accounts are organised into multi-level groups, each ledger carrying a general-ledger identifier used as the reference by other modules. Sub-ledgers hang beneath control accounts — individual customers under receivables, individual vendors under payables.
Control ledgers to map
- Sales revenue, split by the categories you want to report on.
- Purchase and direct costs, plus a cost of goods sold route for stock-backed sales.
- VAT input and output, and TDS.
- Discount given, discount received and round-off.
- Cash in hand, each bank account, and each settlement ledger for card, QR and wallet providers.
- Receivables, payables and a city-ledger/company receivable if you bill companies.
- Advance and deposit ledgers for money taken before the service is delivered.
Dimensions
Beyond the ledger itself, postings can carry cost centre, class, area, agent and user-defined fields. Set these up if you want profitability by outlet, region or salesperson — retrofitting them later means the historical data will not have them.
Where other modules post
POS sales, restaurant bills, hotel folios, payroll and production all resolve to ledgers defined here. If a mapping is missing, the relevant setup gate will block the operation rather than guess.
Did this answer your question? If not, our support team can look at your actual configuration.
Contact support