Payroll in US version

ara3n

Hello was reading the newsletter by MS and it mentioned that payroll will be treated effective Oct. 06 as a sepparate addon. Does that mean We won't see the 14 mill range objects in base navision anymore?
I have very few clients that use them. So I guess it's a good thing having less tables in base navision.

themave

As and end user what does this mean to us ?

ara3n

depends if you are using payroll or not. If you are not using payroll, you'll have less tables. If you are using payroll, nothing, it just NSC will have to load the Payroll objects if you are going to use payroll.

themave

Yes we are using payroll, a better question would be how is support different with an add-on v.s. standard Navision

Not that support for payroll is really any good now anyways. We manually update the tax tables, and modify the reports, seems that is faster to do it ourselfs, then wait for updated tax tables. It seems they don't know California exist.

Miklos_Hollender

Try to tell 'em, like. "You know... does Conan or Terminator 2 ring a bell? It's the place governed by him... "

ara3n

I guess we just have to wait and see themave.

Captain_DX4

themave wrote:

Yes we are using payroll, a better question would be how is support different with an add-on v.s. standard Navision

Not that support for payroll is really any good now anyways. We manually update the tax tables, and modify the reports, seems that is faster to do it ourselfs, then wait for updated tax tables. It seems they don't know California exist.

The company that supports the Payroll objects is a Canadian company, formally known as VisionPay. You seem to be stuck in the unfortunate situation that usually works the other way around, when dealing with support between Canada and the US (I usually find that Canada gets second-tier support in some instances when I've tried to look for quicker responses).

I've done a couple payroll implementations and yes, VisionPay's support isn't as good as it should be some of the time, but those were Canadian implementations, so I wouldn't know how well US support would be. I would hedge a guess that one of the reasons MS doesn't want to list payroll as core-functionality anymore because dealing with that lack-of-good-support from VisionPay is most likely too frustrating for them.

However, VisionPay is still working on the payroll and as far as I've heard hasn't made any indication that they are going to stop supporting it going forward, no matter if it is core-functionality or an add-on. I'd say that you shouldn't have anything to worry about progressing forward, except that your support seems sucky at best already. *pats head*

You have the functionality built into your license, so going forward you will be able to maintain that. VisionPay will be coding for oncoming versions, exactly the same way Lanham or any of the other NAV add-on companies maintain their products. If you don't buy upgrade versions, then it would be up to your NSC to integrate the old payroll functionality into the new database, or get you to leave the old payroll system behind. The add-on status doesn't change how you pay support to MS. New functionality that comes out in oncoming versions will need to be purchased from your NSC and billed by MS.

All-in-all, shouldn't be any different from what you are experiencing now.

kriki

[Topic moved from Upcoming version NAV 5.1 forum to Navision forum]