-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Migration Guide To ERPNext Version 16
If you create Sales Invoices via API, you sometimes want to fetch unbilled timesheets from the linked project. So far, this was the default behavior. Now you'll need to make an additional API call: PUT /api/v2/document/Sales%20Invoice/SINV-0001/method/add_timesheet_data
The whitelisted method erpnext.accounts.doctype.bank_account.bank_account.make_bank_account has been removed. It used to return a new Bank Account linked to a specific party. Instead, we use frappe.new_doc in the frontend directly. (Removal PR)
The whitelisted method erpnext.accounts.doctype.pricing_rule.pricing_rule.make_pricing_rule and the frontend util erpnext.utils.make_pricing_rule have been removed. They used to return a new Pricing Rule linked to a specific Customer or Supplier. Instead, we use frappe.new_doc in the frontend directly. (Removal PR)
Since v12, ERPNext used to store duplicates of submitted Sales Invoices and Payment Entries in a separate table, linked by a chained hash. This feature was originally designed for France but also enabled for Germany in an attempt to comply with some parts of KassenSichV. Because German POS compliance depends on a certified TSE, ERPNext cannot be compliant on its own, so the duplicate ledger provided no compliance benefit and has been removed. (Removal PR)
Detailed Migration Guide
ERPNext has migrated from a legacy JSON field (item_wise_tax_detail) to a fully relational child table (Item Wise Tax Detail) for tracking tax breakdowns at the item level.(PR Link)
The Tax Withholding is refactored to use a new Tax Withholding Entry child table for detailed tracking.