Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues and Suggested Solutions in ERPNext #45445

Open
rizwan100mu opened this issue Jan 24, 2025 · 1 comment
Open

Issues and Suggested Solutions in ERPNext #45445

rizwan100mu opened this issue Jan 24, 2025 · 1 comment
Assignees

Comments

@rizwan100mu
Copy link

  1. Optional Journal Entries for Linked Supplier and Customer

Issue:
When a Supplier and Customer are linked as the same entity in ERPNext, journal entries between them are generated automatically, which may not always be required.

Suggested Solution:
Provide an option to make such journal entries optional, allowing users to decide whether they should be created automatically or handled manually.


  1. Item-wise VAT Rounding Issue

Issue:
In KSA ZATCA Phase 2, VAT rates are restricted to 2 decimal places. This causes discrepancies where the sum of item-wise VAT amounts (rounded to 2 decimals) differs from the total invoice VAT, leading to invoice rejection by the ZATCA portal.

Suggested Solution:
Adjust the VAT calculation logic to ensure consistency between item-wise VAT amounts and the total invoice VAT, adhering to ZATCA's 2-decimal rounding requirement.


  1. Sales Invoice Cancellation and Stock Unlink Option

Issue:
Under ZATCA Phase 2 regulations, sales invoices cannot be canceled. However, items sold from stock cannot always be canceled or amended due to linked purchase receipts.

Suggested Solution:
Add an option in the Sales Invoice to "unlink item stock," allowing adjustments to be made without affecting the associated stock entries.


  1. Customer Type and VAT Information in Customer Module

Issue:
To meet ZATCA regulations, there is no clear distinction between B2B and B2C customers, and VAT-related information is not enforced for B2B customers.

Suggested Solution:

Add a checkbox in the Customer module to classify customers as either B2B or B2C.

If the customer is marked as B2B, make VAT-related fields (e.g., VAT number) mandatory.


  1. Shared Warehouse for Multiple Companies

Issue:
When multiple companies are set up in ERPNext, it can be challenging to manage warehouses that are shared across these companies.

Suggested Solution:
Provide an option to configure warehouses as "shared" across multiple companies, enabling seamless stock management and transactions for both entities.


  1. Company Abbreviation in Document IDs

Issue:
When multiple companies are used in ERPNext, it is difficult to identify documents associated with a specific company.

Suggested Solution:
Include the company abbreviation (abbr) in the IDs of all documents (e.g., Sales Invoices, Purchase Receipts) to ensure better identification and management of records across multiple companies.


Let me know if additional formatting is needed!

@mihir-kandoi
Copy link
Contributor

Would it be possible for you create 6 different issues for the same? Makes it easier to track.

@mihir-kandoi mihir-kandoi self-assigned this Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants