metadata.json

[
  {
    "id": "accounting/accounting_period.md_0",
    "text": "Accounting Period Accounting Periods subdivide a fiscal year into manageable reporting intervals (monthly, quarterly, etc.). They are used to: Control transaction posting windows Lock financial records after closing Support periodic audits Once an accounting period is closed, transactions cannot be modified without explicit permissions, ensuring data integrity.",
    "source": "accounting/accounting_period.md",
    "title": "accounting_period"
  },
  {
    "id": "accounting/chart_of_accounts.md_0",
    "text": "Chart of Accounts The Chart of Accounts (CoA) is a hierarchical structure that categorizes financial transactions. Accounts are grouped under: Assets Liabilities Equity Income Expenses Each transaction posted in the system updates balances in the corresponding ledger accounts. The Chart of Accounts directly impacts financial statements such as the Balance Sheet and Profit & Loss report. Enterprise accounting logic frequently validates whether accounts belong to the correct type and hierarchy.",
    "source": "accounting/chart_of_accounts.md",
    "title": "chart_of_accounts"
  },
  {
    "id": "accounting/company.md_0",
    "text": "Company A Company represents a legal business entity for which financial books are maintained. Each Company in ERPNext defines: Default currency Country and taxation rules Associated Chart of Accounts Fiscal Year configuration Accounting transactions such as invoices, payments, and journal entries are always linked to a Company. Multi-company setups allow enterprises to manage subsidiaries or branches within a single system. Company-level settings influence accounting validations, reporting structure, and regulatory compliance.",
    "source": "accounting/company.md",
    "title": "company"
  },
  {
    "id": "accounting/fiscal_year.md_0",
    "text": "Fiscal Year A Fiscal Year defines the accounting year used for financial reporting. It consists of: Start date End date Associated accounting periods All accounting transactions must fall within an active fiscal year. ERPNext enforces validations to prevent posting entries outside defined fiscal boundaries. Fiscal years are critical for year-end closing, balance carry-forward, and statutory reporting.",
    "source": "accounting/fiscal_year.md",
    "title": "fiscal_year"
  },
  {
    "id": "accounting/general_ledger.md_0",
    "text": "General Ledger The General Ledger (GL) is the central record of all financial transactions. Each GL entry records: Account affected Debit or credit amount Voucher reference Posting date All financial documents eventually generate GL entries. Business logic often validates that GL entries remain balanced and adhere to accounting rules. Enterprise systems rely heavily on GL accuracy for compliance and reporting.",
    "source": "accounting/general_ledger.md",
    "title": "general_ledger"
  },
  {
    "id": "accounting/journal_entries.md_0",
    "text": "Journal Entries Journal Entries are manual or system-generated accounting records used to adjust balances. Common use cases: Accruals Adjustments Corrections Opening balances Journal Entries must balance total debits and credits. ERPNext enforces validation rules to prevent unbalanced or invalid entries. Approval workflows are often applied in enterprise environments.",
    "source": "accounting/journal_entries.md",
    "title": "journal_entries"
  },
  {
    "id": "accounting/opening_closing.md_0",
    "text": "Opening and Closing of Books Opening entries initialize account balances at the start of a fiscal year. Closing processes: Lock completed accounting periods Transfer balances forward Prevent retroactive modifications These processes ensure auditability and financial consistency across fiscal years.",
    "source": "accounting/opening_closing.md",
    "title": "opening_closing"
  },
  {
    "id": "accounting/payment_terms.md_0",
    "text": "Payment Terms Payment Terms define how and when payments are expected from customers or made to suppliers. They specify: Due dates Installment percentages Credit periods Payment Terms impact cash flow forecasting and accounts receivable/payable management.",
    "source": "accounting/payment_terms.md",
    "title": "payment_terms"
  },
  {
    "id": "accounting/overview.md_0",
    "text": "Accounting Module \u2013 Overview The Accounting module in ERPNext manages all financial transactions, reporting, and compliance-related activities of an enterprise. It supports: General Ledger accounting Tax configuration and calculation Period-based financial reporting Audit-compliant transaction tracking Multi-company and multi-currency setups Core accounting entities include Companies, Chart of Accounts, Fiscal Years, General Ledger entries, and Journal Vouchers. These entities interact to ensure accurate financial records and regulatory compliance. This documentation provides business context for accounting-related source code and APIs within enterprise applications.",
    "source": "accounting/overview.md",
    "title": "overview"
  },
  {
    "id": "accounting/taxes.md_0",
    "text": "Taxes The Taxes module defines tax templates, rates, and rules applied to transactions. ERPNext supports: Multiple tax types (VAT, GST, withholding tax) Inclusive and exclusive taxes Country-specific tax structures Tax configuration influences invoice calculations and GL postings. Incorrect tax setup can lead to compliance issues and financial discrepancies.",
    "source": "accounting/taxes.md",
    "title": "taxes"
  },
  {
    "id": "accounting/accounting_transactions.md_0",
    "text": "Core Accounting Transactions ERPNext accounting operations primarily involve three types of financial transactions. # Sales Invoice A Sales Invoice represents a bill issued to a customer for goods or services provided. Sales Invoices: Record revenue Update customer receivables Generate General Ledger entries # Purchase Invoice A Purchase Invoice represents a bill received from a supplier. Purchase Invoices: Record expenses Update supplier payables Generate General Ledger entries # Journal Entry Journal Entries are manual accounting transactions used for adjustments. Examples include: Accounting corrections Asset adjustments Accrual entries Payment allocations Journal Entries follow the double-entry accounting principle where total debits must equal total credits.",
    "source": "accounting/accounting_transactions.md",
    "title": "accounting_transactions"
  },
  {
    "id": "accounting/financial_reports.md_0",
    "text": "Financial Reports ERPNext provides built-in financial reports that summarize the financial health of an organization. Common reports include: Balance Sheet Displays assets, liabilities, and equity at a specific point in time. Profit and Loss Statement Shows revenue, expenses, and net profit over a reporting period. Cash Flow Statement Tracks the flow of cash within the organization. These reports are generated using data recorded in the General Ledger.",
    "source": "accounting/financial_reports.md",
    "title": "financial_reports"
  },
  {
    "id": "accounting/account.md_0",
    "text": "Account An Account represents a ledger used to record financial transactions in ERPNext. Each account belongs to the Chart of Accounts hierarchy and is categorized under one of the following groups: Assets Liabilities Equity Income Expenses Accounts can exist as: Group Accounts Used to organize other accounts within the hierarchy. Ledger Accounts Used to record financial transactions. Each account may contain attributes such as: account_name account_number account_type parent_account When creating or updating accounts, ERPNext validates the account hierarchy to ensure consistency within the Chart of Accounts.",
    "source": "accounting/account.md",
    "title": "account"
  },
  {
    "id": "accounting/account_number.md_0",
    "text": "Account Number The account_number field uniquely identifies accounts within the Chart of Accounts. Account numbers are commonly used to organize accounts according to financial reporting standards. When updating an account number, ERPNext performs several validations: The account number must be unique. Descendant accounts must preserve the hierarchy structure. Existing financial records must remain consistent. Updating account numbers may trigger updates to related ledger mappings and financial reports.",
    "source": "accounting/account_number.md",
    "title": "account_number"
  },
  {
    "id": "accounting/payment_entry.md_0",
    "text": "Payment Entry A Payment Entry records payments made to suppliers or received from customers. Payment entries support the following operations: Paying supplier invoices Receiving customer payments Allocating payments against outstanding invoices Each payment entry updates the General Ledger by creating debit and credit entries. ERPNext automatically allocates payments against outstanding references when possible. Allocation logic ensures that payment amounts are distributed across invoices based on outstanding balances.",
    "source": "accounting/payment_entry.md",
    "title": "payment_entry"
  },
  {
    "id": "accounting/payment_allocation.md_0",
    "text": "Payment Allocation Payment allocation determines how payment amounts are applied to outstanding invoices. ERPNext supports automatic and manual allocation of payments. During allocation, the system evaluates: Outstanding invoice amounts Payment amount Payment type Reference documents The allocated_amount field tracks how much of a payment is applied to each reference. Correct allocation ensures that receivables and payables remain accurate within financial reports.",
    "source": "accounting/payment_allocation.md",
    "title": "payment_allocation"
  },
  {
    "id": "accounting/exchange_rates.md_0",
    "text": "Currency Exchange Rates ERPNext supports transactions across multiple currencies. Exchange rates define the conversion rate between two currencies. The system retrieves exchange rates based on: Source currency Target currency Transaction date Exchange rate calculations ensure that financial transactions recorded in foreign currencies are converted accurately into the company's base currency. ERPNext caches exchange rate lookups to improve performance during financial processing.",
    "source": "accounting/exchange_rates.md",
    "title": "exchange_rates"
  },
  {
    "id": "accounting/invoice_processing.md_0",
    "text": "Invoice Processing Invoices represent financial documents used to record sales or purchases. ERPNext supports two primary invoice types: Sales Invoice Issued to customers for goods or services. Purchase Invoice Received from suppliers. When an invoice is submitted: Revenue or expense accounts are updated Taxes are calculated General Ledger entries are created Invoices may also create outstanding balances that must be settled through payments.",
    "source": "accounting/invoice_processing.md",
    "title": "invoice_processing"
  },
  {
    "id": "accounting/outstanding_balances.md_0",
    "text": "Outstanding Balances Outstanding balances represent unpaid amounts on financial documents such as invoices. ERPNext tracks outstanding amounts for: Customer receivables Supplier payables Outstanding balances are updated whenever payments or adjustments are applied. Payment allocation logic ensures that outstanding balances decrease as payments are recorded.",
    "source": "accounting/outstanding_balances.md",
    "title": "outstanding_balances"
  },
  {
    "id": "accounting/ledger_validation.md_0",
    "text": "Ledger Validation ERPNext enforces accounting validation rules before recording transactions. Key validation checks include: Debit and credit totals must balance Accounts must belong to the correct account type Transactions must fall within a valid fiscal year These validations ensure that financial data remains accurate and compliant with accounting principles.",
    "source": "accounting/ledger_validation.md",
    "title": "ledger_validation"
  },
  {
    "id": "accounting/report_generation.md_0",
    "text": "Financial Report Generation Financial reports summarize accounting data recorded in the General Ledger. ERPNext generates reports such as: Balance Sheet Profit and Loss Statement Trial Balance These reports rely on accurate classification of accounts and properly recorded transactions. Financial reports help organizations analyze financial performance and ensure regulatory compliance.",
    "source": "accounting/report_generation.md",
    "title": "report_generation"
  },
  {
    "id": "accounting/purchase_order.md_0",
    "text": "# Purchase Order ## Overview A **Purchase Order (PO)** is a binding contract between a company and a supplier, indicating the company's commitment to purchase a specified set of items under agreed conditions. A Purchase Order is similar to a Sales Order; however, instead of being sent to an external customer, it is used for purchasing goods or services from suppliers and maintained as part of the organization's procurement records. **Navigation:** ``` Home > Buying > Purchasing > Purchase Order ``` --- ## Buying Flow A Purchase Order is a key document in the procurement process and is used to formally request goods or services from a supplier. --- ## Prerequisites Before creating and using a Purchase Order, ensure that",
    "source": "accounting/purchase_order.md",
    "title": "purchase_order"
  },
  {
    "id": "accounting/purchase_order.md_1",
    "text": "key document in the procurement process and is used to formally request goods or services from a supplier. --- ## Prerequisites Before creating and using a Purchase Order, ensure that the following master records have been created: - Supplier - Item --- ## Creating a Purchase Order A Purchase Order can be created manually or generated automatically from: - Material Request - Supplier Quotation ### Steps to Create a Purchase Order 1. Navigate to the **Purchase Order** list and click **New**. 2. Select the **Supplier**. 3. Enter the **Required By Date**. 4. In the **Items** table: - Select the required item using the item code. - Optionally modify the required date for individual items. 5. Enter the required quantity. 6.",
    "source": "accounting/purchase_order.md",
    "title": "purchase_order"
  },
  {
    "id": "accounting/purchase_order.md_2",
    "text": "Date**. 4. In the **Items** table: - Select the required item using the item code. - Optionally modify the required date for individual items. 5. Enter the required quantity. 6. The item price will be automatically fetched if it has been configured in the Item master. 7. Configure applicable taxes and charges. 8. Save the document. 9. Submit the Purchase Order to finalize it. --- ## Key Information Captured A Purchase Order typically contains: - Supplier details - Required delivery date - Item codes and descriptions - Quantities - Item prices - Tax information - Total purchase amount --- ## Business Purpose Purchase Orders help organizations: - Maintain formal procurement records. - Communicate purchasing requirements to suppliers. - Track outstanding",
    "source": "accounting/purchase_order.md",
    "title": "purchase_order"
  },
  {
    "id": "accounting/purchase_order.md_3",
    "text": "prices - Tax information - Total purchase amount --- ## Business Purpose Purchase Orders help organizations: - Maintain formal procurement records. - Communicate purchasing requirements to suppliers. - Track outstanding purchases. - Ensure compliance with procurement procedures. - Control purchasing costs and approvals. --- ## Related Documents Purchase Orders are commonly created from: - Material Request - Supplier Quotation Purchase Orders may later result in: - Purchase Receipt - Purchase Invoice",
    "source": "accounting/purchase_order.md",
    "title": "purchase_order"
  }
]