How to find time

Hello, Linda -

The letters FTE can represent the words "full time equivalent."

See a more complete explanation here:
https://en.wikipedia.org/wiki/Full-time_equivalent

This is a link to a shorter explanation:
http://www.businessdictionary.com/definition/full-time-equivalent-FTE.html

By US federal law a full-time employee is one who works on average at least 30 hours per week, or 130 hours per month.

You likely mean this to be the 'Average' number of employees per day rather than percentage. However you need to work out based on hr's per day that each employee can work. Lets assume though that they work full time, 8hrs per day. Then you would work out as follows:
3223.5 /8 /28 /306 = 0.047 employees per day

If they only work 1 hr per day it would be:
3223.5 /28 /306 = 0.376 employees per day

Each employee would need to work:
3223.5 /306 = 10.53hrs per month

Employees must, with two exceptions, receive at least eight hours free from work between shifts, whether they are "split shifts," "on call shifts," "back-to-back" shifts or ordinary daily shifts.
Rest between shifts is not required if:

• the total time worked during both shifts does not exceed 13 hours; or
• the employer and employee agree in writing to reduce or forego the eight-hour rest period.

Example
Monica works in a restaurant. She is on split shifts, working from 11:30 am to 2:30 pm and then from 4:00 pm to 7:00 pm. The total time of her two shifts is 6 hours. Monica does not need to have eight hours off between the shifts because her total hours worked on the shifts do not exceed 13 hours.
Note: The requirement for rest between shifts operates simultaneously with the requirement for daily rest; an employee's schedule must satisfy both requirements. For example, an employee might agree in writing to work two eight-hour shifts in a row without any time free from work between them (the employee's agreement means there is no violation of the rest between shifts rule), but if that results in the employee receiving less than 11 consecutive hours off in a day, the employer will be in violation of the daily rest rule* and therefore it is not permitted.
* Unlike the case with the rest between shifts requirement, an employee cannot agree to waive the daily rest requirement.

69% eficiency = 50 hours

Your labor cost is $512/hour, therefore the total cost for 850 hours is $262,144.

Change the default from salary to hourly on the employee file.
www.cpahispano.com

http://employee-monitoring1.software.informer.com/3.1/

follow the above link and download employee monitoring opensource software

Firstly you need to determine/state whether you are using a database application, such as Access, MtSQL or MS SQL and programming them to do create this application, or are you using a programming development tool such as Visual Studio, ASP.NET, PHP or the like, as the solution and guidance will be different for each.
In terms of the data design, you should store the data necessary to identify each employee uniquely and each data point per employee needed to calculate their payroll. You should then store the generic (applys to all employees) such as tax rates, in separate tables and call on it to calculate wages and other paystub data.
For instance, the employee first and last names and tax ID should be a sufficient unique identifier. Create a table for just employees, their names, tax ID, start date, schedule, pay rate, number of deductions, direct bank payment data, etc., and whatever else you decide you need for each employee. You can calculate their wages by multiplying their rate by their schedule and applying the appropriate tax rate and medical/witholding deductions as you go, so calculated data does not need to be stored and consume database space. 
You'll likely need a separate table for common data such as tax rates, one for deductions/witholdings, one for holidays, one for vacation accrual rates, one for medical rates, etc. This data if common to employees does not need to be stored per individual, as that would cause redundant replication of data. If the employees are on an hourly rate, rather than a set salary/wage, then you'll need a table of worked hours per employee, akin to their timesheet data. If you use a timesheet/timecard, the entering and storing only the totals and keeping the physical timesheet for backup records should suffice.
Once you design and populate your database as suggested above, then it's a relatively-simple task of calculating the computed paystub data and storing the salient resulting datapoints for the record.
Consider a reporting application, such as Crystal Reports, for your printing needs, as its far easier to configure Crystal or similar product to format reports, paystubs, checks, etc., than coding these from scratch.
Hope this helps.