|
2 anni fa | |
---|---|---|
.. | ||
accounts_dashboard/accounts | 2 anni fa | |
custom | 2 anni fa | |
dashboard_chart | 2 anni fa | |
dashboard_chart_source | 2 anni fa | |
doctype | 2 anni fa | |
form_tour | 2 anni fa | |
module_onboarding/accounts | 2 anni fa | |
notification | 2 anni fa | |
number_card | 2 anni fa | |
onboarding_step | 2 anni fa | |
page | 2 anni fa | |
print_format | 2 anni fa | |
print_format_field_template | 2 anni fa | |
report | 2 anni fa | |
test | 2 anni fa | |
workspace/accounting | 2 anni fa | |
README.md | 2 anni fa | |
__init__.py | 2 anni fa | |
deferred_revenue.py | 2 anni fa | |
general_ledger.py | 2 anni fa | |
party.py | 2 anni fa | |
test_party.py | 2 anni fa | |
utils.py | 2 anni fa |
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 |