‹ Reports
The Dispatch

OSS Report: frappe/erpnext


ERPNext Faces Financial Reporting Challenges Amidst Active Development

ERPNext, an open-source ERP software, continues to evolve with active contributions addressing critical bugs and feature enhancements, though financial reporting inaccuracies pose significant challenges.

ERPNext is designed to streamline business management across various domains such as accounting, CRM, and manufacturing. Built on the Frappe Framework, it leverages Python and JavaScript for its operations.

Recent activities highlight a focus on resolving issues related to financial calculations and transaction complexities. The development team is actively engaged in fixing bugs and enhancing features, with notable collaboration among members like Ruthra Kumar and Khushi Rawat. However, unresolved issues in financial modules suggest ongoing risks for users relying on accurate reporting.

Recent Activity

Recent issues and pull requests (PRs) indicate a concerted effort to address critical bugs and enhance user experience. Notable issues include discrepancies in financial reports (#42991) and stock valuation errors (#42992). These are complemented by PRs focusing on bug fixes in financial reporting (#42989) and user experience improvements (#42974).

Team Members and Recent Contributions

  1. David Arnold (blaggacao)

    • Fixed editorconfig for JSON files.
    • Collaborated on various fixes.
  2. Ruthra Kumar (ruthra-kumar)

    • Linked utility report with bank reconciliation.
    • Improved UX on Bank Clearance tool.
    • Fixed payment entry issues.
  3. Khushi Rawat (khushi8112)

    • Implemented asset capitalization fixes.
    • Added finance book filter in reports.
  4. Nihantra Patel (Nihantra-Patel)

    • Enhanced payment entry functionality.
  5. Raffael Meyer (barredterra)

    • Worked on translation improvements.
  6. Venkatesh (venkat102)

    • Adjusted bank reconciliation statements.
  7. Rohit Waghchaure (rohitwaghchaure)

    • Addressed timeout issues in stock entries.

Of Note

Quantified Reports

Quantify Issues



Recent GitHub Issues Activity

Timespan Opened Closed Comments Labeled Milestones
7 Days 23 8 36 0 1
30 Days 98 45 147 1 1
90 Days 294 172 395 1 1
All Time 15436 13618 - - -

Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.

Quantify commits



Quantified Commit Activity Over 30 Days

Developer Avatar Branches PRs Commits Files Changes
Frappe PR Bot 5 11/9/0 55 10 474883
Nabin Hait 4 3/3/0 7 114 3854
ruthra kumar 11 11/11/0 94 28 1416
Raffael Meyer 5 9/8/0 22 41 1175
None (mergify[bot]) 9 95/87/4 26 33 1087
rohitwaghchaure 3 17/17/0 27 42 958
Khushi Rawat 6 7/6/0 27 15 836
Lakshit Jain 7 6/2/1 12 6 202
Nihantra C. Patel 2 3/2/0 5 5 135
Dietmar Fischer 1 0/0/0 2 1 31
Shariq Ansari 2 1/0/0 4 2 24
Venkatesh 3 2/2/0 5 3 20
Nicolas Pereira (hqnicolas) 1 2/1/1 1 4 10
Smit Vora 2 3/0/0 2 1 8
Frappe Bot 2 0/0/0 3 1 6
David Arnold 1 1/1/0 1 2 5
Michelle Alva 1 0/0/0 1 1 2
Parameshwari Palanisamy 2 1/1/0 2 1 2
HENRY Florian (FHenry) 0 4/0/1 0 0 0
Rushabh Mehta 0 0/0/0 0 0 0
Kevin Shenk (batonac) 0 1/0/0 0 0 0
None (bhickta) 0 1/0/0 0 0 0
None (lbrandh) 0 1/0/0 0 0 0
Martin Heini (maheini) 0 1/0/0 0 0 0
Carlos (Carlos9k) 0 1/0/1 0 0 0
Phanupong Janthapoon (kurogeek) 0 1/1/0 0 0 0
None (mahowell) 0 1/0/0 0 0 0
Ninad Parikh (Ninad1306) 0 1/0/0 0 0 0
None (Sanket322) 0 1/0/0 0 0 0
None (Zalmelahi) 0 1/0/1 0 0 0
Sagar Vora (sagarvora) 0 1/0/0 0 0 0
Vishnu VS (Vishnu7025) 0 2/0/0 0 0 0
None (jabir-elat) 0 2/0/2 0 0 0
NIYAZ RAZAK (niyazrazak) 0 1/0/0 0 0 0
Diógenes Souza (devdiogenes) 0 1/0/0 0 0 0
Türker Tunalı (TurkerTunali) 0 4/0/2 0 0 0
Kerolles Fathy (KerollesFathy) 0 1/0/0 0 0 0
None (rahulgupta8848) 0 1/0/0 0 0 0
Faris Mohamed (faris-mohamed10) 0 1/0/0 0 0 0

PRs: created by that dev and opened/merged/closed-unmerged during the period

Detailed Reports

Report On: Fetch issues



Recent Activity Analysis

The ERPNext project has seen significant recent activity, with 1,818 open issues currently logged. Notably, there are several critical bugs and feature requests that indicate ongoing challenges in areas such as accounting, stock management, and user permissions. The presence of multiple unresolved issues related to financial calculations and document submissions suggests potential risks for users relying on the system for accurate financial reporting and operational efficiency.

A recurring theme among the issues is the complexity of handling transactions across various modules, particularly in relation to pricing rules, tax calculations, and inventory management. This complexity may lead to user frustration and operational inefficiencies.

Issue Details

Recently Created Issues

  1. Issue #42992: Wrong Stock value after sale return

    • Priority: Bug
    • Status: Open
    • Created: 0 days ago
    • Description: Stock value becomes zero after creating a stock return from delivery note.
  2. Issue #42991: Accounts Payable Summary Report not matching the General Ledger for Party Type Employee

    • Priority: Bug
    • Status: Open
    • Created: 0 days ago
    • Description: Discrepancies between Accounts Payable Summary Report and General Ledger for Employees.
  3. Issue #42987: Commission Rules like Pricing Rule

    • Priority: Feature Request
    • Status: Open
    • Created: 1 day ago
    • Description: Request to develop a feature for Commission Rules similar to existing Pricing Rules.
  4. Issue #42973: Stock Valuation Method on a Per-Company Basis

    • Priority: Feature Request
    • Status: Open
    • Created: 2 days ago
    • Description: Proposal to allow setting stock valuation methods on a per-company basis.
  5. Issue #42972: Add Currency from Report Trial Balance for Party

    • Priority: Feature Request
    • Status: Open
    • Created: 2 days ago
    • Description: Request to display balances based on currency according to conversion factors in trial balance report.

Recently Updated Issues

  1. Issue #42961: Error Log re819fr3fq: 'Title' will get truncated, as max characters allowed is 140

    • Priority: Bug
    • Status: Open (Edited)
    • Last Updated: 2 days ago
    • Description: Error occurring across multiple doctypes due to title length exceeding character limit.
  2. Issue #42935: Duplicate items and outdated item price in the Point-of-Sale (POS) item list

    • Priority: Bug
    • Status: Open (Edited)
    • Last Updated: 3 days ago
    • Description: Items displayed twice in POS if they have newer prices; issue persists after version update.
  3. Issue #42934: make_payment_request does not set ignore_permissions=True by default anymore

    • Priority: Bug
    • Status: Open (Edited)
    • Last Updated: 1 day ago
    • Description: Change in behavior affecting payment request submissions by guests.
  4. Issue #42932: in BOM Creator the BOM of the sub assembly is not fetched automatically.

    • Priority: Feature Request
    • Status: Open (Edited)
    • Last Updated: 1 day ago
    • Description: Sub assembly BOM should auto-populate when creating a BOM.
  5. Issue #42900: Incorrect Payment Entry grand total outstanding calculation for Journal Entry references.

    • Priority: Bug
    • Status: Open (Edited)
    • Last Updated: 5 days ago
    • Description: Payment Entry's grand total calculation incorrect when using Journal entry as reference.

Summary of Implications

The analysis of recent issues highlights critical areas needing attention within ERPNext, particularly concerning financial reporting accuracy and user experience during transaction processing. The high volume of unresolved bugs indicates potential risks for users relying on these functionalities for daily operations. The need for enhancements in handling complex pricing rules and multi-currency transactions is evident, suggesting that further development focus is required to address these challenges effectively.

Report On: Fetch pull requests



Overview

The analysis of the pull requests (PRs) for the ERPNext project reveals a total of 84 open PRs, showcasing a diverse range of fixes, features, and enhancements aimed at improving the functionality and usability of the software. The recent activity indicates a continuous effort by contributors to address bugs, enhance user experience, and implement new features.

Summary of Pull Requests

  1. PR #42993: fix: added app permission check for apps page
    Created 0 days ago. Introduces a permission check for accessing the apps page, enhancing security by ensuring only authorized users can access certain functionalities.

  2. PR #42989: fix: Wrong allocated_amount for sales_team in gross_profit report
    Created 1 day ago. Corrects the calculation of allocated amounts in the gross profit report, addressing a significant reporting error that could mislead financial assessments.

  3. PR #42988: fix: adjust price insertion logic for internal suppliers/customers
    Created 1 day ago. Fixes an issue with price fetching logic for internal transactions, ensuring accurate pricing is applied.

  4. PR #42978: fix: duplicate items and outdated item price in POS
    Created 1 day ago. Resolves issues with outdated pricing displayed on the POS screen, improving accuracy in customer transactions.

  5. PR #42974: fix: retain date filter when redirecting in Profit and Loss report
    Created 2 days ago. Enhances user experience by maintaining filter settings during report navigation.

  6. PR #42969: fix: A project without tasks should be able to complete
    Created 2 days ago. Fixes a bug preventing projects without tasks from being marked as complete.

  7. PR #42965: fix: resolve gl entries duplication in asset purchase workflow (backport #41845)
    Created 2 days ago. Addresses duplication issues in general ledger entries during asset purchases.

  8. PR #42962: refactor: plaid connection
    Created 2 days ago. Improves performance and error handling in the Plaid bank connector.

  9. PR #42956: fix(Item): error message on tax rate (backport #42955)
    Created 3 days ago. Enhances error messaging related to tax rates for better user clarity.

  10. PR #42953: fix: sync translations from crowdin
    Created 3 days ago. Updates translations for various languages, maintaining localization efforts.

  11. PR #42928: fix: getting scrap items from sub assemblies by fetching scrap items for parent BOM
    Created 4 days ago. Fixes issues with scrap item retrieval during stock entry creation from work orders.

  12. PR #42926: fix: link Purchase Invoice and Receipt Items to Asset
    Created 4 days ago. Introduces fields linking purchase invoice items to assets for better tracking.

  13. PR #42925: fix: Replace add_if_empty with reset_value flag
    Created 4 days ago. Updates tax handling logic to improve data integrity during document processing.

  14. PR #42902: Update default sales tax for Switzerland
    Created 5 days ago. Adjusts sales tax rates in compliance with new regulations in Switzerland.

  15. PR #42901: fix: Serial and Batch Bundle Buying Flow
    Created 5 days ago. Addresses issues with serial number management during internal transfers.

16-84. Additional PRs cover various fixes, enhancements, and feature additions across different modules within ERPNext, demonstrating active engagement from contributors to improve the system's functionality and user experience.

Analysis of Pull Requests

The recent pull requests reflect a robust engagement from contributors focused on enhancing ERPNext's functionality through bug fixes, feature improvements, and usability enhancements across various modules such as accounting, inventory management, and project management.

Common Themes

  • Bug Fixes: A significant portion of the PRs addresses critical bugs that affect financial reporting accuracy (e.g., PRs related to gross profit reports and allocated amounts). This highlights an ongoing commitment to maintaining data integrity within the application.
  • User Experience Improvements: Several PRs focus on refining user interactions with the software (e.g., retaining filters in reports and fixing outdated prices in POS). This indicates a strong emphasis on usability, which is crucial for user satisfaction.
  • Security Enhancements: The introduction of permission checks (e.g., PR #42993) reflects an awareness of security concerns, ensuring that only authorized users can access sensitive functionalities.
  • Localization Efforts: The synchronization of translations (e.g., PR #42953) shows an ongoing commitment to making ERPNext accessible to a global audience by supporting multiple languages.
  • Performance Optimizations: Some PRs aim at improving performance (e.g., refactoring connections), which is essential for scalability as user demand grows.

Notable Anomalies

  • The presence of many open PRs (84) suggests either a high volume of contributions or potential bottlenecks in the review process that may delay merging.
  • Some older PRs remain unmerged or inactive, indicating possible challenges in maintaining momentum within the contribution pipeline or prioritization conflicts among various features and fixes.
  • The frequent backports indicate that contributors are actively maintaining compatibility across different versions of ERPNext, which is crucial for users who may not be on the latest release.

Conclusion

The current state of pull requests in ERPNext demonstrates a vibrant community actively working towards enhancing the software's capabilities while addressing critical issues that affect user experience and data integrity. However, attention should be given to managing open PRs efficiently to ensure timely updates and maintain contributor engagement over time.

Report On: Fetch commits



Repo Commits Analysis

Development Team and Recent Activity

Team Members and Recent Contributions

  1. David Arnold (blaggacao)

    • Recent Activity:
    • Fixed editorconfig for JSON files.
    • Collaborated with Khushi Rawat on various fixes.
  2. Ruthra Kumar (ruthra-kumar)

    • Recent Activity:
    • Linked utility report with bank reconciliation statement.
    • Improved UX on the Bank Clearance tool.
    • Fixed multiple issues related to payment entries and bank reconciliation.
    • Worked on various refactors and bug fixes across multiple modules, including asset management and payment requests.
  3. Khushi Rawat (khushi8112)

    • Recent Activity:
    • Implemented fixes for capitalization issues related to assets.
    • Added finance book filter in depreciation reports.
    • Collaborated with Ruthra Kumar on several features and bug fixes.
  4. Nihantra Patel (Nihantra-Patel)

    • Recent Activity:
    • Contributed to fixing payment request issues and enhancing the payment entry functionality.
  5. Raffael Meyer (barredterra)

    • Recent Activity:
    • Worked on various translation fixes and improvements across the ERPNext application.
  6. Venkatesh (venkat102)

    • Recent Activity:
    • Made adjustments to bank reconciliation statements and fixed issues related to payment entries.
  7. Rohit Waghchaure (rohitwaghchaure)

    • Recent Activity:
    • Addressed various bugs, including timeout issues in stock entries and depreciation calculations.
  8. Others: Several other contributors have been involved in translation fixes, performance improvements, and minor bug fixes.

Patterns, Themes, and Conclusions

  • Active Collaboration: There is significant collaboration among team members, particularly between Ruthra Kumar and Khushi Rawat, indicating a strong teamwork dynamic in addressing complex issues.

  • Focus on Bug Fixes and Refactoring: The majority of recent commits involve fixing bugs, improving existing features, and refactoring code for better maintainability. This suggests a commitment to enhancing software quality.

  • Feature Enhancements: New features such as improved UX for tools like Bank Clearance and additional filters in reports indicate ongoing development aimed at user experience improvement.

  • Translation Updates: Regular updates to translations reflect an effort to support a diverse user base, enhancing accessibility for non-English speakers.

  • High Volume of Commits: The number of commits from key contributors indicates an active development cycle, with a focus on both new features and resolving existing issues.

Overall, the ERPNext development team demonstrates a robust approach to maintaining and enhancing the software through active collaboration, consistent bug resolution, and feature development.