|
há 2 anos | |
---|---|---|
.. | ||
accounts_dashboard/accounts | há 2 anos | |
custom | há 2 anos | |
dashboard_chart | há 2 anos | |
dashboard_chart_source | há 2 anos | |
doctype | há 2 anos | |
form_tour | há 2 anos | |
module_onboarding/accounts | há 2 anos | |
notification | há 2 anos | |
number_card | há 2 anos | |
onboarding_step | há 2 anos | |
page | há 2 anos | |
print_format | há 2 anos | |
print_format_field_template | há 2 anos | |
report | há 2 anos | |
test | há 2 anos | |
workspace/accounting | há 2 anos | |
README.md | há 2 anos | |
__init__.py | há 2 anos | |
deferred_revenue.py | há 2 anos | |
general_ledger.py | há 2 anos | |
party.py | há 2 anos | |
test_party.py | há 2 anos | |
utils.py | há 2 anos |
Accounts module contains masters and transactions to manage a traditional double entry accounting system.
Accounting heads are called “Accounts” and they can be groups in a tree like “Chart of Accounts”
Entries are:
All accounting entries are stored in the General Ledger
Transactions on Receivable and Payable Account types will also be stored in Payment Ledger
. This is so that payment reconciliation process only requires update on this ledger.
Field | Description |
---|---|
account_type |
Receivable/Payable |
account |
Accounting head |
party |
Party Name |
voucher_no |
Voucher No |
against_voucher_no |
Linked voucher(secondary effect) |
amount |
can be +ve/-ve |
debit
and credit
have been replaced with account_type
and amount
. against_voucher_no
is populated for all entries. So, outstanding amount can be calculated by summing up amount only using against_voucher_no
.
Ex:
voucher_no | against_voucher_no | amount |
---|---|---|
SINV-01 | SINV-01 | 100 |
PAY-01 | SINV-01 | -80 |
An invoice for ₹100 partially reconciled against a credit of ₹70 using a Journal Entry. Payment Ledger will have the following entries.
voucher_no | against_voucher_no | amount |
---|---|---|
SINV-01 | SINV-01 | 100 |
CR-NOTE-01 | CR-NOTE-01 | -70 |
JE-01 | CR-NOTE-01 | +70 |
JE-01 | SINV-01 | -70 |