200 Print Level – In limited reports (1.11 Muli Codes) the option of print level is provided to enable Users to create a limited required data report for general usage without showing all available data by default, a Project Person (5), Accounts Person(7).
200 Include Usage Control up to – This provides a quick way of limiting the report detail to that which is useful to the User’s needs.
Usage Control 200 – This provides a dual purpose control.
201 Note Project – Free format note field to allow storage of additional information relative to the project.
202 Note Project Role
202 Risk Priority – Allows the User to indicate a relative priority of 1-5.
Defect Description 203
204 Note Budget
210 Note Amendment/Order
Progress Claim Notice 211 – An invoice raised for a client.
212 Program Access Control
213 Note Remittance – This feature allows companies to provide generalised notes on the remittance advice. It could be notice of shutdown periods, holidays, seasons greeting, etc.
216 Form Type – It is the paper size that you want to print on
Muli regions allow Users to group project, people and organisations by a 2-coded process. By default in Australia the first character represents the State and the second the sub-region of the state. AA – representing “All Areas” would apply to organisations that supply country wide services – such as Insurance.
221 Timesheet Note/Payroll Management
This note provides a facility for the employee and/or the manager to pass special pay information / questions to the Payperson. It always starts empty for a payrun. Where pay sequences are not accessible to the Timesheet Maintenance, then details are entered as a note, ie: Leave past end of pay period.
This note goes on the pay packet or pay advice of the next payrun. At the end of the payrun it is cleared out.
222 Country Code
In relation to telephones relates to the prefix in the dialing code to call the phone number from another country ie Sydney 612 Melbourne 613.
222 Emergency Contact
Each database operates in a single currency. Where an order is not in the database currency, then at settlement the transaction is brought back to local currency as the basis for producing the goal accounts. Each country has a defined currency that at a point in time has a given exchange rate with the currencies of another country. All orders and payments need to include the clear definition of the exchange rate.
Muli operates in a Local currancy (in Australia $Aus) and provide a option to complete accounts payable and receivable transactions in other currencies.
223 Note Qualifications
224 GPS Type – There are a number of ways in which digital GPS data may be stored. This code allows clear definition.
224 Note Employee History
225 Payroll Management Note
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.
This is a permanent note to enable pay person information to be recorded (a separate flag will be installed in Version N2 to remind the pay person to read same at pay processing).
225 Registration Point
226 Broadcast Pay Advice note
226 Email Action
227 Presence – This status is maintained in background by Muli to provide a quick understanding of the contact status of each User.
230 Accounts (A/C)
Processing Point (Def = HO Head Office) Where companies have multiple accounts processing points, this will ensure all transactions on this project are forwarded to the correct location.
Large companies may establish processing points across groups of companies for regional management. Where this is done, it is logical that the payment process would utilise the processing point for payment grouping. Most users would not use this facility and would therefore accept “All”.
230 Accounts(A/C) Processing Point – Processing Point (Def = HO Head Office) Where companies have multiple accounts processing points, this will ensure all transactions on this project are forwarded to the correct location.
231 Preferred usage – a single number from 1 to 9 indicating our satisfaction with using this supplier. 1 indicates most preferred, 9 indicating that no further transactions should be placed on this supplier.
232 Risk Rating – a single number from 1 to 9, indicating a credit risk assessment for Customers. The code is entered in Accounts Receivable – Customer tab. At the Lowest Risk level are Federal & State Government departments, and the highest level is simpley defined as “Risky” It is more a measure of asset backing rather than a promise of promt payment.
237 QA status
Allows the linking of RPC data and Organisations to other Organisations. Roles include Director, Foreman, Accounts Payable etc and these are a separate list to those shown as Project Roles (Role 271)
240 Contract – Head Contract Type – individual head contract name is displayed in the background to determine: L = Lump Sum Progress Claim C = CostPlus Progress Claim W = Contract Value equals V = Invoice Project (Contract Value = Invoiced) O = Overhead (Sundry Invoice)
Invoiced (V) – Used where the contract value is not pre-targeted (Cost+) or Agreed Lump Sum and only sundry invoices or Minor Works AR may be raised on the project defined in this way. As part of the Trial Balance process, the revised contract value is updated to the value of Accounts Receivable invoices raised.
Complementary (M) – Where a Cost+ project is created, it is normal to create its Complementary partner. The complementary partner may be consecutive project no. or where a construction managed project is in a different company/profit centre, then the same suffix would generally be used.
Project Lump Sum (L) – When a client has agreed to a Lump Sum contract value, the revised contract value may be changed by obtaining an approved variation and will invoice the client using a lump sum progress claim.
Project Cost Based (C) – Where a contract has been entered into where the risk of costs being different to budget remains with the client. Muli still expects a budget to be developed to enable proper client reporting using the Cost Based Progress Claim. Even with Cost Based project changes to scope, should be managed with variations for changes in Scope of Works.
There should be no project contribution (9980) in a cost based project but agreed margins would be handled by journal between the cost based project and its associated complementary project (M).
Most cost based projects will require a complementary project to be associated to manage the items in the contract for which the contractor assumes risk.
Minor Works Job (J) – Allows for logical operation for managing small short duration jobs such as Repair & Maintenance or factory management of small jobs. This concept allows all allocations between 2001 and 7998 to be used as standalone projects with all income and expense relating to the job occurring within the one allocation.
Where the facility is used to manage a number of small jobs but requires some starting expense, then normal preliminary allocations are available for normal use, ie Site Sheds, Area Supervision; Phones, etc. Each of these smaller jobs has its own master record (10.1) which defines basic information and control.
Sales & Inventory (Future) – Provides an accounting management interface for the processing and reporting of the various defined sales and stock management processes.
Asset & Equipment (Future) – Provides the accounting management interface for processing and reporting the various defined income and expense categories.
Responsibility Overhead ® – This is a special type of project used to control Branch/Profit Centre overheads, generally uses allocations 1800 to 1898.
General Ledger – There is a general ledger project raised for each company one per financial year. All general ledgers may only exist in Profit Centre Z. Allocations 0001 – 0998 are only available for a general ledger project with all accounts allocated to the Profit & Loss or Balance Sheet by its sequence number.
242 The Project Status Control
Active (A) – All projects start out in this condition allowing full functionality.
Budgets Frozen (B) – Once management establishes the project budget, it is “frozen” stopping the project team from moving money around to hide real variances.
(P) – Only in minor jobs – Stops the creation of new jobs while allowing the completion of already entered jobs.
(O) – No more Orders (or Amendments) – Stops the raising of new orders or amendments to orders, thus when managers review a completed project and agree all costs have been identified and committed, the placing of the S flag Stops project cost creep. May be reversed by senior management when a verifiable reason is obtained.
Completed (C) = Finished – When management and the project team agree that the project is completed and the last transaction date is in the past, the C flag can be applied. Muli, in the background verify that the Revised Contract Value = Invoiced to Client = Received from Client = Project Paid (which includes project contribution taken). The C flag cannot be set until the accounting transactions are adjusted to meet the above test.
Finished ( F ) – This is set by Muli as part of the Trial Balance General Ledger process and only for projects that have been previously manually set as C, in the financial year prior to the one being run. Once a project is set as F, no further actions can be taken on this project.
Hidden (H) – Whilst a project is hidden, all but a few selected people with a high security level will be able to look at the details.
Deleted (D) – Not yet supported. When all transactions are removed from a project.
Note: Status F,C,H all require high access levels for reporting. Only H can still have transactions.
243 Accounts Control – This is the combination of 241 and 242 and is applied to each project as an internal control on the way accounting processes are applied and depending on the stage of the project, what is allowed to occur.
V = Invoice – Income is determined by the value of invoices raised
G = General Ledger
T = Template Project (no orders)
Accounts management is the combination of 241 – Accounts Control 242 – Project Status
244 Project Feature
245 Project (Status Code 245) – The allowable codes are set by Muli to provide a project based transaction control. Codes include:
No further controls ???
245 Project Type Source
247 Stage – With Version N we introduced project stages that enable Users to define a project by logical areas such as floors, external works, prestart and close off. This stage facility provides an automatic grouping for modules such as Module 11 Subcontractor Claim break-up and Scheduling.
251 Variation Reason
252 Variation Status
253 Extn of Time Status
254 Budget Load Status
Depending on the business, there are a number of Roles required to ensure projects are completed to meet corporate goals. Each of these identified roles should be established in Code 271 and the relevant provider may be linked to the project.
272 Signoff Level
Where a RPC is established, each RPC is given authority to sign (authorise activities or verify actions) at various levels.
280 Description (Note)
281 Payment Terms – Default Payment Terms are part of the Supplier’s Static Details and each time a Purchase Order or Subcontract is raised then these default terms can be overriden if required.
282 Retention – In construction, it is normal for contract conditions to include a retention clause, ie retain 10% until 5% of (adjusted) contract value is retained from progress claims and this is reduced to 5% at practical completion, and the final money is repaid after the defect liability is complete.
283 Expense Grouping – Expenses can be grouped and reported upon using a 2-character code from the Muli 283 code table. Examples where thi scould be useful include grouping togetrher R&D expenses.
285 Expense Type – (default gives GST code and therefore GST Calc Rules)Senior Management may add additional Codes which they consider better defines Reimbursment Expense Groups
288 Approval – In Muli we allow the allocation of Approvers by project or just use overall RPC authorisations
291 Other Type