I have a feeling this is something that is probably a very simple answer right in front of me and I'm missing it.
On the Vendor Bill entry form, our 'Department' field is auto-populating, and I'm trying to determine what's sourcing the auto-populate.
We use Squareworks AWA Approval Flows for our AP, so we have a 'Bill Owner' field, populated from the Employee list.
I have ruled out that the 'Department' auto-population is sourcing from the 'Bill Owner' field or from the Employee/User who is actively entering the bill.
There is not a 'Department' field presenting/populating on our Vendor records, so its not populating from there.
The 'Department' on the 'Account' in the header of the Vendor Bill does not have 'Department' populated, so its not sourcing from that.
In the examples I've reviewed to this point, the Vendor Bills are not generated from a Purchase Order/do not have a PO as Related Record, so its not sourcing from PO.
There are no SuiteFlow workflows running against our Vendor Bill form that populates the 'Department', and I see no Scripts that would impact it either.
While I realize the 'Department' selected at the line level is where GL impact will occur, I've read in a few places that a selection in the header 'Department' field will flow down to any Tax lines.
The desired setting would be for 'Department' to be available at the header level to be populated as needed/wanted for reporting purposes, but it needs to not auto-populate.
Any suggestions for options to continue exploring where the auto-populate might be sourcing from?