NV2 Payroll contains support for Canadian and U.S.A. payroll. Both may be used in the same set of books.
Complete information on each country's payroll is available here:
In this section we introduce basic NewViews payroll objects and their underlying relationships to give you a big picture without getting bogged down in the inevitable complexity of the details associated with payroll.
Each arrow in the diagram above represents a collection relationship between two types of objects. For example, a payroll object has a collection of employee objects, and correspondingly, each employee references, i.e. points to, its payroll; hence the arrow. A payroll also has a collection of payrun objects and a collection of paychecks, but more on this later.
You can have more than one payroll object, each with a different set of employees. There are a number of reasons why you would need different payrolls. For example, one payroll might be used to pay weekly employees and another for monthly employees. In addition to varying pay periods, different types of employees might be subject to different jurisdictions such as states or provinces, or to different government regulations or incentive programs. The point is that you can have any number of payrolls, each used to group similar employees that you want to pay at the same time using similar rules.
When pay day arrives for a payroll - say it's the month end and you want to pay employees belonging to a monthly payroll - you add a new payrun object to the monthly payroll object and process it. A paycheck is generated for each employee in the payroll's collection of employees. These paychecks form the payrun's collection of paychecks. Note that because the payrun has this collection, it is also possible to unprocess the payrun, thus deleting the paychecks (audit records of such operations would always be generated).
The paychecks are also automatically added to a payroll journal. In this sense paychecks are no different from other types of NewViews transactions in that all are added to journals of various types. The main difference between paychecks and most other NewViews transactions is that they are created and added to a journal automatically by a payrun, and they are not added or manipulated directly by users on the payroll journal.
Paychecks also show up in the paycheck collections of payrolls and employees. A payroll's paychecks are all of the paychecks for all employees on that payroll, and an employee's paychecks are all paychecks ever remitted to that employee.
Each employee has a collection of accounts. These accounts are real NewViews accounts and their total-to fields hook them into the financial reporting structure of the set of books. An employee can have any number of accounts and is thus capable of tracking financial payroll information of arbitrary complexity. However, an employee's starting set of payroll accounts is generally added automatically by NewViews.
A paycheck has a collection of line item details and these post to the employee payroll accounts. So paychecks show up in the employee's account ledgers, i.e., postings.
Before you process a payrun you are given an opportunity to enter information specific to the paychecks that will be generated by the payrun. This information is called a paylist, and it is generally information for each employee such as the number of hours worked during the pay period. More on paylists later.
NewViews timecard transactions are compatible with NewViews payroll. You add a timecard to a timecard journal, select an employee, and enter details on timecard line items. These line items most often post to accounts that accrue wages payables for the employee. The diagram below shows the structure of timecards added to a timecard journal.
At the end of a pay period when you add a payrun and process it, paychecks are generated to pay down the wages payable that accrued due to the timecards. At this time each timecard is attached to the paycheck that was used to pay it. The diagram below shows the result off adding and processing the payrun.
Although we show a lot of arrows, most were already shown earlier for (non-timecard) paychecks, or else serve exactly the same purpose for timecards as they did for paychecks. The only arrows of interest are the red arrows. One shows that a timecard references the paycheck that paid it, and that paycheck has a corresponding collection of the timecards it paid. The other red arrow shows that the timecard, like a paycheck, is connected to a payrun, in this case the payrun that generated the paychecks used to pay it.
Note that every object that has a collection of paychecks, i.e. payrolls, payruns, and employees, also has a corresponding collection of timecards that were paid by those paychecks.