Rethinking Payroll Entry

[theopen-institute]

The Payroll Entry doctype is at present very unintuitive. It generates Pay Slips, and it generates Journal Entries, but it doesn't maintain any reference to those things after it has been submitted. A user could go cancel each of the pay slips or amend the journal entry, but the payroll entry doc would never know. If the payroll entry is cancelled, nothing happens to the journal entry or pay slips.

At minimum, the Payroll Entry doctype should maintain reference to the Pay Slips it represents, and also to the Journal Entry it creates.

Even better, it should write directly to the General Ledger rather than requiring a separate Journal Entry, as the name -- Payroll Entry -- seems to imply it should.

My organization would be happy to initiate some work on this, but I am reluctant to make changes like this without some public discussion first. I made a few posts on the forum (see here and here), but they didn't attract much attention.

Thoughts? This has been a significant snag as we've tried to roll out ERPNext at several of our subsidiaries, but we'd like to make sure any changes we make are accepted by the general community rather than just a fork.

Thanks in advance!

[clarkejj]

see also frappe/erpnext#12070

[ruchamahabal]

Already has been addressed in the linked issue and it works as expected with linking post v11