View Profile
Personal Profile
Career Summary
Job Skills
Software Skills
Business Skills

Match
History
Upload/Send CV

PHP Moonligting Job

Position Details

Job ID:

1671

Last Updated (mm/dd/yyyy):

2014-08-26 01:41:30 PM

Position category:

Position Name:

PHP Moonligting Job

Similar Experience:

120+

Total Experience:

120+

Project Location:

Anywhere

Job Type:

Contracting/Permanent

Pay:

Fixed Price quotation

Academic Qualification/s:

Degree / Diploma adv.

Industrial Qualification/s:

Relevant adv

Position Active:

No

Relocation Assistance:

No

Workpermit Assistance:

No


Job Description:
This document serves to outline the functionality, processes and systems that the intended software should deliver.

The Process

The system process for the software we seek should work as follows:

The Users

Authorised individuals (probably in the region of around 150), should be able to go to a secure URL where they will need to enter a username, password and a One-Time Pin (OTP) received on their cell phone via a sms. Upon logging in successfully, the user should be immediately shown an electronic requisition form (example attached) for completion. At the bottom of the form should be a ‘Submit” button when complete. There must be the option at this point to attach a document (invoice etc) to the requisition.

The Authoriser(s)

Upon the completion and submission of the requisition by the user, it should generate an email to the authoriser indicating that they have requisitions to approve. They too should go to the secure URL, where they enter a username, login and OTP. As an additional security measure, the authorisers should have an SSL certificate on their devices on which they authorise. These authorisers should have the option to either “Authorise” or “Decline” by way of buttons again. Should the decline option be selected, it should produce a pop-up screen requiring an explanation that upon completion, is sent back to the user by way of an email. At this stage of the process there should also be an option to tick an “Urgent” box in the payment needs to be expedited. The authoriser must have an option where they can enter the email address to which a proof of payment must be sent.

The Approver(s)

The Approvers should receive an email, once the authorisers have authorised a requisition, indicating there are requisitions for approval. They too should go to the secure URL, where they enter a username, login and OTP. As an additional security measure, the approvers should have an SSL certificate on their devices on which they approve. These approvers should have the option to either “Approve” or “Decline” by way of buttons again. Should the decline option be selected, it should produce a pop-up screen requiring an explanation that upon completion, is sent back to the user by way of an email. At this stage of the process there should also be an option to tick an “Urgent” box in the payment needs to be expedited.

At this level there must be one more function, and that is a box into which I can create a ‘group’ or select, from a drop down menu an existing group into which the requisition must be filed. This way all requisitions pertaining to a project can be viewed by simply viewing that group.

Upon the Approver, approving the requisition an email must be generated to the Senior Bookkeeper informing him that he needs to allocate each requisition to one of the companies.

The approver must also have the option to ‘Refer to Chair” any requisition that is deemed necessary to do so. It must then generate an email indicating to the Chairperson that there is a requisition that must approve. They too should go to the secure URL, where they enter a username, login and OTP. As an additional security measure, the approvers should have an SSL certificate on their devices on which they approve. These approvers should have the option to either “Approve” or “Decline” by way of buttons again.

The Bookkeepers

Upon the Approver, approving the requisition an email must be generated to the Senior Bookkeeper informing him that he needs to allocate each requisition to one of the companies. He too should go to the secure URL, where they enter a username, login and OTP. As an additional security measure, he should have an SSL certificate on the devices on which he will allocate companies to each requisition approved. He should select, from a drop down menu, which company the requisition should be paid from and the system should allocate that company and a reference number, in sequential order, to each requisition.

Upon allocating each requisition to a company, an email should be generated to the junior bookkeepers indicating they have requisitions to load and release. They too should go to the secure URL, where they enter a username, login and OTP. As an additional security measure, the bookkeepers should have an SSL certificate on their devices which they use. At this point there must be the option to print all approved requisitions.

This would be the final process related part of the cycle.

A list of all Requisitions

The system must produce a list of all requisitions from users into a list. The single line of information for each requisition should show: the user, the description of the payment, the amount and the time and date submitted as well as where it is in the process (e.g: submitted, authorised, approved, loaded, released, invoiced).

Users, authorisers and approvers must be able to view these requisitions and the information above, exclusively for the requisitions they have either submitted (user), authorised (authoriser) or approved (approver).

Supporting Documents

Some requisitions will come with an invoice attached from the user (indicated above). Others (most) will only be available after the payment.

From the list of all requisitions (point 2), should be the option for a user or authoriser or bookkeeper to scan an invoice against a specific requisition. Upon any requisition having an attached supporting document, an email must be generated to the Administrator to approve the invoice as being acceptable or decline it with comments as to why it is not acceptable.

Once it is approved as acceptable, it must show on the list of requisitions as “invoiced.” Once this is done, all “invoiced” requisitions should be removed by the requisition list, and appear in another list called “Supported Expenses.”

Audit Trail

Once a requisition has been successfully “invoiced” and is listed within the “Supported Expenses” group, it must show upon request the audit trail. This audit trail must show the following information: The user, and time it was submitted, the authoriser, and what time it was authorised, the approver and what time is was approved.

Budgets

Each requisition will allocate the expense to one of our budgets and a line-item within it. These are available on excel spreadsheets. When the requisition appears for the user, authoriser or approver it must indicate how much money will be left in that line item of that budget should the payment be approved.

Urgent Requisitions

Any requisition marked as urgent must go through the same system, but should be flagged, highlighted or preferably at the top of the list of requisitions for the approver and the bookkeepers.

Mobile Friendly

It would be an option we would like to consider to have this entire system functional on tablets and smartphones. This would be a major advantage to the people involved in the process.

Redundancy

The system has to be setup whereby an individual, from the level of authoriser and above in the process, is able to allocate a designated alternative to take over their duties in the event that they are away. This should also be able to be done for all authorisers, approvers, bookkeepers by people listed as administrators.

Administrators must have full access and full functionality at all levels of the system.

Searches

The list of requisitions and supported requisitions must be searchable at the approver, bookkeeper, and administrator levels by dates, users, authorisers, and company codes assigned by the senior bookkeeper.

Potential earnings of this venture is estimated to be in the millions and would be very profitable according to industry insiders.
Format: Skill Description (Rating 1-5,Experience in Months)
Rating: 1-Beginner, 2-Below Average, 3-Average, 4-Above Average, 5-Expert

Required Job Skills:
SDLC : Systems Analysis, Programming (Back-End)(Lng)

Required Software Skills:
Lng PHP (5,54-60)

Required Business Skills:
Financial (3,24-30)