Offering hourly payroll: Clarify time data before taking it on

A company paying hourly wages wants external payroll support. Employee numbers give your payroll office an initial sense of size. The service itself needs another question answered: What do the supplied hours mean, and how do they become clearly assigned payroll information? Even a fully completed file helps little if the business and your office interpret a column differently. An agreed handover shows what preparation the customer provides and what processing your team can actually undertake.

This guide helps you decide whether the time data handover is sufficiently described for a proposal or needs further professional clarification. The suggested lists and examples are your own organisational aids, rather than automatic features of an enquiry or particular software. All examples are explicitly fictional. The text determines no entitlement to remuneration, tax treatment, working time rules or permissible retention arrangements. Refer those questions to the appropriate professionals for the individual case before processing.

Describe the hours being supplied

Ask the business to explain a typical time entry. Does it come from time recording, a confirmed summary or manual compilation? Does the number describe attendance, hours already selected for payment or another agreed quantity? Do not silently equate these meanings. Record the value, unit and substantive origin. The payroll team can then assess what further decision is needed before using it as a processing basis.

Next ask what preparation has already taken place. Were breaks recorded separately, certain times grouped, or entries left unchecked? First understand the actual information available. This does not prescribe a universal rule about which time may be paid or deducted. The responsible customer representative explains the confirmed basis; unresolved assessment questions remain visible. “Hours list” becomes a comprehensible description of what your office actually receives.

Agree an unambiguous unit and notation

Work through an invented entry together. “7:30” may be defined as seven hours and thirty minutes. The same duration could be expressed as 7.5 decimal hours. Your team must therefore not interpret “7.30” from its visual similarity alone. Ask which format the source actually uses and which meaning is confirmed. Record the explanation alongside the intended handover format so later colleagues do not read the same number differently.

Only then consider the actual export facility. The existing application may provide a suitable format, or further preparation may be needed. Promise no automatic conversion or direct import before your specialists have checked the real method. For the proposal, establish whether the customer supplies confirmed values in the agreed unit or your office undertakes specified preparation. Give that work an explicit place in the scope so it does not fall between the two parties.

Keep person and payroll period together

Ask how each entry is assigned to the correct person. A name alone can be ambiguous when employees have similar names or spellings vary. Clarify the identification actually used with the customer and your team. Use wholly invented identifiers in the initial discussion; no real employee list is needed. What matters is whether everyone can explain which person and agreed period a particular entry represents.

Test the period boundary with a fictional shift crossing midnight, starting on the last day of one month and ending on the first of the next. How does the business supply that information, and who confirms its allocation for payroll? Do not define a universal allocation rule yourself. Record the decision needed and how the confirmed choice should be recognisable in the supplied data. A filename does not answer this when the contents span periods.

Separate time descriptions and remuneration decisions

A label such as night, travel or additional work does not fully explain the facts. Ask which confirmed treatment applies and who is responsible for it. A time entry and a decision about an additional payment are different pieces of information. If your service includes allocation to agreed payroll items, describe that task explicitly. Clarify unresolved employment, tax or social insurance questions individually. An available payroll code in the software is not automatic professional approval.

Also consider entries that do not simply represent an hour worked. The customer may record an absence separately. Ask what it means and how it should be handled under the specific engagement, without deriving a remuneration rule from an abbreviation. Your result is a readable allocation with a confirmed basis or a precisely identified open question. Both are more useful than a completed table containing unstated assumptions.

Check completeness against expected submissions

Discuss how both parties recognise that the agreed compilation is complete. A blank cell could mean no hours should be reported, a check is pending, or a person is missing. Distinguish these meanings clearly. What confirmation does the business provide for a deliberately blank entry? Your team should recognise whether it is processing a confirmed version or facing an unanswered question.

Consider multiple submissions for one person. If two sites supply separate portions, the compilation must show what belongs together. Discuss who is responsible for the complete customer submission and how duplicate entries should become apparent. A total comparison can support an internal organisational check, but does not itself prove correct remuneration. Describe the comparison as a limited task. Matching another list’s total does not justify promising general freedom from errors.

Give later changes an identifiable reference

Ask about correcting hours already handed over. Will the customer supply a complete replacement compilation or an identified individual change? Either route needs a clear reference to the previous version. Record the person, period and entry affected. This also establishes whether your office processes replacement files or specified change notifications. A second attachment without explanation leaves it unclear whether it replaces or supplements something.

Then consider late information relating to an earlier period. Describe the facts and route to clarification first. The responsible professional determines whether and how a particular payroll requires correction. For cooperation, make it apparent that the new information concerns an older version and should not silently become additional hours in the current period. Agree who answers the question and how the confirmed processing instruction reaches your team.

Use a connected fictional example

An explicitly fictional business supplies a monthly summary for two employees with invented identifiers. One entry contains seven hours and thirty minutes; another includes an unchecked report from a second site. There is also a shift spanning the month boundary. Ask those involved to explain every entry without relying on personal recollection. The example should reveal shared meanings and the answers still missing before intended processing.

Next introduce a version clearly marked as replacing that summary, with one hours entry changed. Can your colleague explain which old version it replaces and what remains unchanged? Can the customer explain the same thing? If not, clarify that particular handover point. The example need not produce actual payroll. For the proposal it provides a usable description of work and outstanding prerequisites without real personal data for a general sales discussion.

Decide preparation scope deliberately

Compare two service boundaries. In the first, the business supplies professionally confirmed information in the agreed units and allocation; your office undertakes the expressly agreed subsequent processing. In the second, your team also prepares data, for example a specified format transfer. Check feasibility and authority before offering it. More preparation is not universally better: What matters is the work the customer wants to delegate and what your office can describe reliably.

Summarise the handover together: Source, meaning and unit of values, person, period, confirmed allocation, completeness confirmation and replacement handling. Put open professional decisions beside the relevant item. A colleague should understand what information arrives and what work they undertake. This description replaces neither technical setup, professional assessment of real payroll nor legal evaluation. It gives the customer a concrete basis for comparing your service with their own preparation.

Clarify a change of time source separately

Finally discuss later changes to time recording. A new system may export identically named columns with different meanings or notation. Agree that the changed source is described and checked with a suitable example before use. Do not inherit the old allocation merely because the filename looks familiar. Customers know what change to report; your team can inspect the affected handover without redefining the entire arrangement without assessment.

Distinguish plans and confirmed submissions

Include a work schedule if the customer identifies it as a starting point. Ask explicitly whether it contains planned assignments or confirmed actual information. Both documents may name the same person and period yet mean different things. The agreed description should make this apparent to your team. A plan does not become a confirmed submission by being the most recently received file.

Ask the customer to explain confirmation using a fictional changed assignment. Who can say which version is intended for processing? Record that answer beside the source description. If it remains unresolved, identify that prerequisite before the proposal so your office does not treat an unchecked plan as confirmed hours.

Professional basis and limits

Section 108 GewO describes information on the payroll period and composition of remuneration. It proves no particular import feature and does not determine the treatment of individual hours. The proposed data clarification is organisational advice; individual professional assessment remains necessary.

Meet suitable hourly payroll customers

Payroll leads from webRichtung open discussions about external support with companies in Germany. Employee range, current arrangements, preferred start, location and contact details provide a starting point. Establish hourly payment, time formats and special requirements personally; these are not promised additional enquiry fields. Register your service and prepare the order in webRichtung Customer. You see the current price before placing a binding order.