Paymaster has been developed in New Zealand to match the needs of both small and large organizations. Utilizing an easily customizable back-end, that calculates the results to help meet the diverse requirements of your specific payroll. Complex tax laws, leave, varying pay rates, allowances, superannuation are just some of the things our payroll system can handle. It can also handle cost accounting by analyzing and reporting wage costs to multiple branches and departments, different pay rates, etc. Full reporting features are available.
Paymaster runs under Gnome on Linux, and uses a PostgreSQL database to store all information, so you can be sure your payroll records are locked away safe and secure. Designed to seamlessly run in a networked environment, WAN and LAN, you can even connect to your database via the Internet. The best part about Paymaster is that it is open source, which means it is totally free to download and use.
Details About The Software:
Pay periods
Pay periods are weekly, forth nightly or monthly payment to employees. Every employee is assigned a pay period which they are paid on. Every time a batch is created for that pay period they get paid whatever hours they are due.
Batches
Batches are run every pay period and are a collection of employee transactions. These transactions create all the journal entries that will occur for the employee. A batch can only be processed once and when the processing occurs it will add these journal entries. Once everyones hours have been entered in you can process the batch.
Employee Transactions
In a batch every employee will have a list of transactions that will be run for them. These transactions act as functions and calculate such things as gross pay, tax, leave etc. They require inputs like quantity and pay period, along with the results of other employee transactions to calculate their results.
Standing pay from employee records will be copied as a series of employee transactions if their pay period matches the batches pay period.
You can remove and add employee transactions into their pay, each one will have a bearing on the final pay the employee will receive.
Transactions
Transactions are functions that are linked to the employee transactions. A transaction will have a series of input ledgers and output ledgers. It will also return an amount that will be displayed in the employee transaction list. When the pay is processed, the transaction will generate a series of journal entries based upon these inputs. These journal entries will set the balances of the varies ledgers.
Default pay
Default pay (also known as standing pay) is a list of transactions that get added automatically whenever a batch is created. These transactions will be copied into the employee transactions. By changing your tax code, pay rate or leave entitlement your standing pay will get modified automatically. Whats useful about standing pay is you can go in and set up a set of standard transactions that occur every pay period for an employee like allowances or deductions.
Ledgers
Every employee and the company have a series of ledgers. These ledgers are where journal entries end up. If you are familiar with accounting you know the debit and credit principles. Every transaction which occurs will create a series of debit and credits to a number of different ledges of both the employees and the companies. Company wages expense ledger will be debited, employees gross wages will be credited.
Below are a few images that show what the software will look like. (Some changes have been made in recent versions.)
- : 1.2
Number of Positive Ratings:
2
Number of Negative Ratings:
82
| User Rating |
Leave a Reply
You must be logged in to post a comment.