P
-
Paid to Date
This is the date to which the employee is being paid up to. It needs to be in the format of dd/mm/yy. This will default to the paid to date set on the payrun setup. Muli do allow overwriting in the Timesheet Maintenance mode.If an employee is taking Annual Leave, then the end date of the holidays would be the paid to date. (If they are being paid in advance past the end of the nominated pay period).
Normally only the “Pay Person” has security to change the "Paid to" date and the details of Leave would be entered in Timesheet Note 221 for processing.
-
Payment Duration (days)
The paid to date is used to calculate the payment duration for calculation of tax. There is a check made by the system that if the duration calculated using the paid to date is different to the duration of the last timesheet for this employee, then an information box will pop up to tell you that. -
Payment of Account - When we subcontract with somebody then we agree to pay or be paid the contract sum on completion, and that payments received/paid along the way do not acknowledge the value of work done (or variations), but are simply payment of accounts.
-
Payment Terms - The period that payment is due after the receipt of goods and any settlement discount associated with payment.
-
Payment Value (AP) - The value to be paid to Supplier/Subcontractor after all adjustments.
-
Payroll - The process includes a suite of 100 applications: Tracking where working hours are spent; Paying a person for worked (or other method of determining remuneration for work done); Charging projects (fully loaded cost) for allocated hours; Managing Payroll on-costs such as superannuation; Managing the various forms of Leave; Managing the financial process and accounting provision accounts.
-
Payroll Company
The payroll company for the payrun.(Who owns the employees) -
Payroll Management Note 225
This is the note maintained in the Employee Master File to assist the Payperson in managing the payroll process. This note has an additional indicator flag to indicate the record needs to be read prior to completing the payroll preparation.The employee Leave entitlements may be displayed. F6 - Leave entitlements pop up window.
-
Payrun
There may be 2 active payruns existing at the same time, due to the new/next period being set up prior to completion of the previous payrun.
Only active timesheets are able to be viewed.
All payruns (across all companies) share a common payrun numbering system. Defaults to the next payrun number for new payruns and will be prefixed with the Company Number. -
Personnel2Do (RPC Human Resources)
To provide a management tool for all the activities required to ensure a person is correctly trained and developed within the companies development guidelines. May be used to manage key personnel of other organisations that need a level of verified training. -
Practical Completion Days(+/-)
The number of days over or under the adjusted contractual completion date. -
Prescribed Payments - The Government Taxation method of taxing earnings of specific industries at the point of income.
-
Print Default - Each Muli User may set a default printer using the F2
-
Print Drill
A small number of reports offer drill options which provide a drill down option to the linkages provided in the report. The drill option is used in the Project Review process. -
Print Email - The printing options for email and fax require the recipient to be registered as a RPC or Organisation.
-
Print Fax - The printing options for email and fax require the recipient to be registered as a RPC or Organisation.
-
Print Select - Allows for the selection of a printer from all printers allocated on the system.
-
Print View - A video view of a Muli Report. You may wish to check the contents prior to printing a single hard copy of a page or full report.
-
Printer
Press F3 – Enquire to see the printers that are available, then type the number of the new printer that you want to add, making sure that it does not already exist, eg
if you have no printers then type '1'
if you have 1,2 & 3 then type '4' or any number that is not 1, 2 or 3
Press enter. -
Priority 495 or Processing Status 495 - The code enterred determines teh urgency of items - for example an Incoming document could be placed in the Red In-Box based upon the code entered here.
-
Probability
The likelihood of a specific event or outcome, measured by the ratio of specific events or outcomes to the total number of possible events or outcomes. Probability is expressed as a number between 0 and 1, with 0 indicating an impossible event or outcome and 1 indicating an event or outcome is certain. -
Profit Centre Access Levels - In establishing a User's access rights on the system, two separate access codes are applied. You may enter a single profile for all companies on the database or you may wish to limit User access to a particular company within the group.
-
Program Access Control (RPC Login Code 212)
The predicted total Muli system has been allocated 300 individual security elements each of which may be allocated at a value of 0 (no access) to 9 (special B with differing controls in between. With Version N Muli may have a number of program access with controls under way in any application. We aim to provide all Users when a control limitation is encountered with its relevant number so management may consider the risk profile. Where data in a report is not visual to a User, then a line below the total will say “Above values have transactions security excluded “.
0- No access
1- Own record only
2- Access authorised projects only
3- View - no add/change
4- Add change(no delete)
5- Add change delete (no overhead)
6- Project manager (no overhead)
7- Access include overheads (overhead)
8- Key operator
9- Special -
Project - The Project in the Muli System refers to each major head contract that is executed - each head contract should be reflected by a project. Small repetitive activities may be combined as a project, i.e. plant hire, maintenance services, etc.
-
Project (Area M2) - A value must be entered “1” if no initial knowledge of area. The basis of measurement should be defined by the user and applied to all projects, normally the “net letable area”.
-
Project (Cashflow Number) - Optional field. Where Cashflow is utilised, then the initial Cashflow number is recorded here as a basis for doing future comparisons between initial Intended and revised Expected or Achieved as a review tool.
-
Project Contract Signed - Has the formal head contract been signed by all the parties.
-
Project (Contract Sum) - This contract value is a Lump Sum Contract (excluding GST); includes project margin.
In a Cost based Contract, there should be a target contract value to be used for budgeting purposes.
-
Project Contribution - Used by Muli to define the difference between Project Income/ Contract Value and Project Cost.
-
Project Feature A-D 244 - A company needs to define its markets and then quantify the features that are important to a Client and then qualify elements that are individual highlights of services or features provided for each project the provision exists for linking the feature to the project.
-
Project First Transaction - The date when the first action occurred on the project. Could be years prior to the signing of a formal contract. Muli use the first and last transaction date to manage the recording of project history data.
– First Transaction Date 6d Valid date prior to which no transactions are undertaken or entered on Muli. -
Project Last Transaction - The date after which no further transactions will occur. Usually the 30 June after end of defects liability period. No transactions may be entered outside the dates.
-
Project Headers
Where a profit centre has been set up allowing for individual project headers, then the artwork company header containing legal identify, ABN, Name, Address, Phone, Fax, etc (axxx 30mm high by xx wide) may be linked in this artwork and will occur on all project correspondence, ie Orders, Subcontracts, Payment Advices.
Users need to be careful to do project only payments runs.
-
Project – Last Transaction Date 6d Valid date where the project is totally complete including release of all retentions and final profit take-up. Normally 30 June following completion of Defects Liability Period.
-
Project Management Phases - In the construction industry phases are defined by the identifiable areas of work which are logical for the control of financial planning and scheduling. Examples would include: separate building; floors of a building; in a major engineering project, the separate major sections. The danger in making phases too discrete is that it would be too difficult for employees to complete their timesheets.
-
Project Margin - The value of the contribution made by a project to cover over- heads and profit.
-
Project Market
-
Project Master
In Muli, all work is managed by projects. Our financial year for each overhead company is a project.
Normally speaking a large value contract is negotiated and managed as a project.
On very major projects it may be that as Scopes of Work are defined and authorised by the Board, they would be executed as smaller projects in their own right. Each project will have a defined Scope of Works and a Budget which is equal to a contract value.
There are special classes of projects called Minor Works.
-
Project Number - Most data is entered and stored based on project, allocation, order number. So, to speed up/simplify data entry, Muli provides an option of just entering the Order Number at the project field and the application will fill in the next three fields.
All processes in Muli are linked to a project.
The project number is made up as follows:
- C = Company Number A-Z , 1-9
- P = Profit Centre (A-Z)
Note: all overhead projects are located in profit centre Z with the financial year of the project being the first 2-digits following Z representing the year. Ie: Overhead for company D for the financial year 2008-2009 is DZ09000. It is recommended that responsibility overheads for the relevant overheads would be numbered DZ09001, etc.
There is no need for normal projects to include a financial year prefix, although we would recommend your first construction project be DF00100, next DF00101, etc. This reduces keying errors with long lists of zero's.
Remember, with construction management projects, you need to assign a second Complementary Project which may be the next sequential project or the same project number in a different profit centre.
-
Project Number #NNNNN
This number is allocated according to the parameters required for your business.
6-digits allocated as follows: 200204
- 1- Company or Profit Centre Number (necessary)
- 2-3 Financial Year
- 4-6 Project Sequence Number
Company or Profit Centre Number - As defined in Company/Profit Centre Maintenance.
Financial Year - Only suggested to be used within the system for Overhead Projects, eg: 207000 Profit Centre #2 / Financial Year 2006/2007
Project Sequence Number - This is a simple sequential application of the next available number as a new project is created. The sequential number may be sequenced for each Profit Centre or across all Profit Centres allowing the same sequence number to be used by:
- Construction
- Plant Hire
- Electrical
- Development
- Holdings
This may prove beneficial in developing cross-company analysis from the database.
-
Project Order - Most transactions/processes in Muli are linked to an order. To enable the necessary input by a User, we normally ask for: Project/Order; Allocation; Order. If you know the order number and enter same at the Project/Order prompt, Muli will recognise it as an order, populate the 3 fields and move to the next question. If you do not know the order number, then F3 on Project will give you a list of active projects and will allow you to chose your project. Likewise, F3 on Allocation will display the allocations allocated to the project and F3 on Order will enable you to chose the applicable order. In some cases (F10 ADD) will enable you to raise an Order on the fly if your required Order does not exist.
-
Project/Order/number - This entry field is part of Invoice Entry and allows the entry/selection of the Unumber as a selection method of processing an invoice.
-
Project Other - Income Projects may have income on other than allocation 1001-1148, ie: tenement fit-out that is project orientated income, usually on an invoice rather than a contract basis.
-
Project (Region Code) - The Region Code setting is used as the basis for grouping projects by region and limiting Suppliers' and Subcontractors' Enquire to default to selected region.
-
Project Retention
-
Project Risk Indicator
-
Project Risk2do Indicator
The project Risk2do indicator provides a summary status of outstanding Risk2do items and summarise them by status.
- Box 1 Red Urgent
- Box 2 Orange Due
- Box 3 Green Due Course
- Box 4 Grey Completed
Clicking on or selecting 18 or Change will open a summary of Risk items on the project sequenced in priority order to allow maintenance.
-
Project Roles and Responsibilities - Companies need to review who they believe are the players involved in a project. This may include all employees involved, all consultants, clients, client representatives and others such as adjacent owners, tenants and major decision influencers. From a roles perspective, it may be an organisation but key players should be entered on Muli as RPC's and linked to the organisation they represent.
-
Project Roll Register
Previous Muli versions allowed for a small number of project associated and then only the last person filling the role.
With Version N users have extended flexibility to define what notes will be recorded against projects and record each person filling the note along with the time-frame of responsibility. The flexibility is there to record everybody who had a role to play in completing the project input.
Project Master Maintenance 02010M
-
Project Short Name - To assist the document display of management directories. Muli adds the project short name to the project number when creating data directories on the computer to aid browsing of data.
-
Project Skeleton Type [Code xxx]
The Muli skeleton concept is to enable like projects to be managed and reviewed on a common basis.
Project skeletons are categorised to a number of major subsections so Muli's internal controls will manage the projects (and their security) using different rules.
-
01-20 Minor Works Projects
Allocations 2000 – 7999 may be used as individual Minor Works Projects with both income and expense in one allocation. -
21-79 Normal Projects
Allocation range 1000-9997 -
81-89 Responsibility Overheads
Used for controlling branches, costs are generally allocated in the range 1800-1900 -
91-99 Overhead Project
Each year an Overhead Project is raised into which all overhead transactions for the year are processed, allocation range 0001-0999
The elements of a project skeleton may only be selected from the standard elements in 1.?
Associated with the skeleton selection are the default set of Risk Items that will be applied to the project at the start.
-
-
Project (Status Code 245) - The allowable codes are set by Muli to provide a project based transaction control. Codes include:
- S = Stopped
- C = Completed
No further controls ???
-
Project (Thumbnail Display) - A standard thumbnail display runtime is utilised to add another dimension to major user interface.
-
Project Timings
-
Project View Menu
Project View presents project based menu and an extended summary of project data for a project manager. This menu will be his primary Muli User interface.
The Project View Menu may be accessed from the Master Menu or Project Master.
Project Who
-
Provisional Cost - Costs allowed for by the project team for activities or functions performed by a subcontractor or supplier as a result of a site instruction or similar.
-
Purchase Order - The commitment for the supply only of standard goods and services (off-site) should be based on the concept of bulk order.
ABOUT MULI | PRIVACY | CONTACT | TERMS OF USE | LINKS | SITE MAP | 
