brotherton-erpnext/erpnext/accounts
2023-03-31 11:10:50 +05:30
..
accounts_dashboard/accounts
custom style: format code with black 2022-03-28 18:52:46 +05:30
dashboard_chart
dashboard_chart_source perf: use get_cached_value instead of db.get_value in accounts module 2022-11-03 13:38:48 +05:30
doctype fix: Column value mismatch in COA blank template (#34658) 2023-03-31 11:10:50 +05:30
form_tour fix: minor onboarding fixes 2022-01-18 18:38:59 +05:30
module_onboarding/accounts fix(minor): move variants to separate tab (#31354) 2022-06-15 16:08:05 +05:30
notification
number_card
onboarding_step fix(minor): move variants to separate tab (#31354) 2022-06-15 16:08:05 +05:30
page
print_format fix: server error while viewing gst e-invoice 2022-04-04 14:40:07 +05:30
print_format_field_template
report fix: Party Name in SOA print when viewed from Customer/Supplier master (#34597) 2023-03-28 15:36:16 +05:30
test fix: remove non-maintained Tax Detail report and missing workspace links (#34192) 2023-03-21 16:23:27 +05:30
workspace/accounting fix: remove non-maintained Tax Detail report and missing workspace links (#34192) 2023-03-21 16:23:27 +05:30
__init__.py
deferred_revenue.py fix: Deferred revenue date comparison (#33515) 2023-01-03 17:51:41 +05:30
general_ledger.py chore: Improve validation message 2023-03-23 19:14:12 +05:30
party.py fix: Tax Category not able to set hence it calculating zero tax for item whoes tax template set (#34525) 2023-03-28 16:48:03 +05:30
README.md docs: specification of payment ledger 2022-06-17 17:57:07 +05:30
test_party.py style: format code with black 2022-03-28 18:52:46 +05:30
utils.py fix: removing redundant validation 2023-03-28 13:44:23 +05:30

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:

  • Journal Entries
  • Sales Invoice (Itemised)
  • Purchase Invoice (Itemised)

All accounting entries are stored in the General Ledger

Payment 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.

Key Fields

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

Design

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:

  1. Consider an invoice for ₹100 and a partial payment of ₹80 against that invoice. Payment Ledger will have following entries.
voucher_no against_voucher_no amount
SINV-01 SINV-01 100
PAY-01 SINV-01 -80
  1. Reconcile a Credit Note against an invoice using a Journal Entry

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