Resources / Business Office / Pay approvals

How school districts route timesheet and extra-duty pay approvals before payroll

The short answer

Timesheet and extra-duty pay both have to be approved before payroll can pay them, and that approval is a separate step from recording the hours. Who signs off depends on the type of pay: an hourly timesheet needs a supervisor to confirm the hours were worked, while extra-duty pay like a coaching stipend, an after-school duty, or summer curriculum work also needs a check that the duty was authorized and coded to the right budget, so districts that handle it well use rule-based routing that sends each claim to the right approvers for its pay type. The pressure is the calendar, because every claim has to clear its approvals before the payroll cutoff or a staff member's check comes late or wrong. A process that routes each claim automatically by pay type, and shows the business office what is still unapproved as the cutoff approaches, is what keeps pay correct and on time without a scramble every period.

On this page

Why your existing systems do not cover it How districts handle it now Where it goes wrong

What doing it well actually requires Common questions How Flow Forms handles it

Why your existing systems do not cover it

A payroll system is built to pay people, not to run the approvals that authorize the pay. A time clock is built to record when hourly staff are on the clock. Both do their jobs well, and neither one owns the step in between, where a claim has to be reviewed, authorized, and signed off before it becomes a payment.

That step is especially exposed for extra-duty pay. Extra-duty work is usually not clocked, because it is not a shift. It is a stipend or a one-time duty: coaching a season, advising a club, covering an event, tutoring after school, writing curriculum over the summer, subbing during a prep period. There is no punch-in for any of that. It arrives as a claim that someone has to approve, confirm was authorized, and code to the correct account, and that is the part neither the time clock nor payroll was designed to handle.

How districts handle it now

For regular hourly staff, a timesheet gets filled out on paper or in a spreadsheet, a supervisor signs it, it goes to the business office, and someone keys it into payroll. For extra-duty pay, a coach or an advisor submits hours or a stipend claim, a principal or an athletic director approves it, and the business office checks that the duty was authorized at the right rate, codes it to the correct stipend line or grant, and enters it before the cutoff.

Underneath both is a person tracking what has come in and what is still missing, and starting to chase approvals as the payroll deadline gets close. The extra-duty side is the harder one, because the authorization, the rate, and the budget code often live in different places, an email here, a negotiated agreement there, a grant document somewhere else, and the business office has to reconcile all of it against a claim before it can be paid.

Where it goes wrong

The failure shows up on the calendar. An extra-duty claim comes in the afternoon before the payroll cutoff with no supervisor approval attached yet, and someone has to run it down in the last hours. A stipend gets paid at the wrong rate because the authorization sat in an email no one checked against the claim. A season of event-supervision duties gets submitted in one stack at the end, and the business office cannot tell at a glance which of them were already approved and which are new.

The consequence is not abstract. It is an employee whose check is short, or late, or paid for something that was never authorized. And when an auditor or a grant monitor later asks who approved a given stipend and when, the answer has to be assembled out of inboxes, because the approval was never captured with the claim in the first place.

What doing it well actually requires

Handling timesheet and extra-duty pay well comes down to routing each claim by what kind of pay it is and capturing the approval with the claim, and it has a few specific parts.

The routing follows the pay type

A clocked hourly timesheet, a flat stipend, and a grant-funded duty do not take the same path. Each should route to the approvers that pay type actually requires, so a stipend that needs an athletic director and a grant sign-off does not travel the same one-step path as a straightforward hourly claim.

Authorization is checked before the work is paid

Whether a person was approved for this duty, at this rate, from this budget, should be tied to the claim itself, not confirmed later against a separate email. Checking it up front is what prevents the wrong-rate payment and the unauthorized stipend, which are far harder to unwind after payroll has run.

The business office can see what is still unapproved before the cutoff

Visibility runs against the payroll calendar. Anyone should be able to see which claims are still waiting on an approval as the deadline approaches, so the cutoff does not arrive as a surprise stack that has to be chased in an afternoon.

The record shows who approved each claim and when

Every approval is captured with a name and a timestamp alongside the claim, which matters most for stipends and duties coded to grants or activity funds, where a monitor will later expect to see exactly who authorized the pay and against which budget.

Common questions

Questions we hear from every business office.

What is extra-duty pay, and why does it route differently from a regular timesheet?

Extra-duty pay is compensation for work outside a regular assignment: coaching stipends, club advising, event supervision, after-school tutoring, summer curriculum work. Unlike clocked hourly time, it usually is not punched on a time clock and often depends on a prior authorization and a specific budget code, so it needs an approval path that confirms the duty was authorized, not just that hours happened.

Does this replace our payroll system or our time clock?

No. Payroll still pays, and the time clock still records hourly shifts. The approval and routing that happen before a claim reaches payroll are the part those systems do not run, and that is the only part this handles.

How do we make sure extra-duty work is authorized before it gets paid?

By tying the authorization to the claim so it is checked as part of the approval, rather than confirmed separately after the fact. When the routing itself verifies that the person, the rate, and the budget were approved, an unauthorized or mis-rated claim gets caught before payroll runs instead of after.

How do we get approvals in before the payroll cutoff?

With visibility against the payroll calendar and reminders that run on their own. When the business office can see which claims are still unapproved as the cutoff nears, and approvers are prompted automatically, the deadline stops depending on one person manually chasing sign-offs.

Can approvals for grant-funded or activity-fund duties be tracked separately?

Yes. Claims can route by budget or funding source so that grant- and activity-fund-coded duties carry the additional approvals they require, and each one keeps a record of who approved it and when, which is what a grant monitor or auditor asks for.

How Flow Forms handles it

Flow Forms routes timesheet and extra-duty pay claims to the right approvers by pay type, checks that each claim was authorized at the right rate and budget as part of the approval, and shows the business office which claims are still outstanding as the payroll cutoff approaches. Every approval is captured with a name and a timestamp alongside the claim. Your payroll system and your time clock stay exactly where they are; this handles the approval and routing that have to happen before a claim reaches payroll.

Districts route both regular timesheets and extra-duty pay this way, from coaching stipends and event-supervision duties to summer curriculum work, with each claim coded to the right budget before anything is paid.

See how it would work for your district →