please make sure that the security is in place because we have some customers that created the business event to emial the pay stub and then realize that other people could see all employees Hi @pbennett , Could you please elaborate on “”security is in place” ? I have found no reference security in regards to emailing Pay Stubs. Are you referring to a basic feature to password protect the PDF file with something only the employee knows.? If so how is this implemented? Thanks.
Has no one shared how to do this?
Hello, I am attempting to create an ACH Export to go along with the Wells Fargo Payment Manager through the batch payments screen. I found out from Acumatica that we cannot utilize the Cash Account Details, or VendorAccountDetails in an Export scenario based on the Batch Payment screen. The ticket was moved to Acumatica services, and they quoted an obscene amount to write this. Has anyone tied into WF Payment Manger? If so, would you be willing to give a little direction as to how this was accomplished? Thanks in advance! Curious if you ever came up with a solution?
In comparing the export scenario in both environments I have notice the error message “This object doesn’t exist.” , in the environment that is NOT working.
Found this is the Request Profiler along with the above error message : at PX.Data.PXFirstChanceExceptionLogger.ProfilerFirstChanceException(Object o, FirstChanceExceptionEventArgs args) at PX.Data.PXDatabaseProviderBase.insert(Type table, PXDataFieldAssign[] pars, String commandText, Boolean switchAllowed, companySetting setting) at PX.Data.PXDatabaseProviderBase.Insert(Type table, PXDataFieldAssign[] pars) at PX.Data.PXDatabase.Insert(Type table, PXDataFieldAssign[] pars) at PX.Data.PXGraph.ProviderInsert(Type table, PXDataFieldAssign[] pars) at PX.Data.PXCache`1.PersistInserted(Object row, Boolean bypassInterceptor) at PX.Data.PXCache`1.Persist(PXDBOperation operation) at PX.Data.PXGraph.Persist(Type cacheType, PXDBOperation operation) at PX.Data.PXGraph.Persist() at PX.Data.PXSave`1.<Handler>d__2.MoveNext() at PX.Data.PXAction`1.<Press>d__38.MoveNext() at PX.Data.PXAction`1.PressImpl(Boolean internalCall, Boolean externalCall) at PX.Data.PXActi
New setup. I had it working in a test environment cannot get it to work in live Environment, not sure what I am missing. Payment Methods- Payment Methods - SETTINGS FOR USE IN AP Cash Accounts: Vendors - PAYMENT
The workaround we went with is temporarily setting the Employees compensation to 26X their regular yearly compensation, this populates the correct biweekly pay in the Paycheck Earnings.
Hi Mike, I should have mentioned I am on build 21.210.0030 and trying to bring in YTD data for payroll go-live. I have tried keying the entry in the Paycheck manually and for Salary employees I am not able to modify the “Rate” field. I have tried click clicking the “Manual Rate” box but nothing happens when I click it as if it were disabled.
Hi Mike, Thanks for the reply I had tried setting the “Manual Rate” to True. It was not in the import scenario I had to add it. The flag gets set when Importing however the Rate is not being populated. I have tried modifying the rate manually after the record has been imported but it seems that If the Employee Compensation “Unit of Pay” is set to “Year” I am unable to change the Rate on the record. Two question. Would you be able to post your “Import PR Paycheck Earnings.xml” here? Which build of Acumatica are you using? Thanks mikedavidson07
Thank you Laura, that did the trick. Just needed to save the Paycheck Header before the “Calculate” was enabled. After pressing Calculate the Tax Codes populated and the YTD values were zero.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.