ADP Time Card Import Template: Fields and Setup

An ADP time card import template is a structured file for transferring employee time records into an ADP timekeeping or payroll system. There is no single template that works for every ADP product or employer: use the format and field rules specified for your account, and treat the generic worksheet below as a planning aid until you confirm it matches your import setup.

Why the template depends on your ADP setup

“ADP” refers to multiple workforce, timekeeping, and payroll products, and employers can configure them differently. An import that works for one organization may be rejected by another because its field names, identifiers, earning codes, date rules, or file layout do not match. The import may also be configured to accept punches, calculated hours, or a particular combination of time and job information.

For that reason, a downloadable spreadsheet found online should not be assumed to be an official or universally compatible ADP template. Start by checking the instructions provided for your product and account, or ask the ADP administrator, payroll team, or implementation contact who manages the import. They can tell you whether the file should be a spreadsheet, a comma-separated file, or another format, and which columns the import actually recognizes.

It helps to distinguish a time card worksheet from an import file. A worksheet can help a manager collect and review hours. An import file must follow the receiving system’s exact rules. You may use the worksheet below to organize records, but do not upload it until you have checked its columns and formatting against your account’s requirements.

Identify the fields your import needs

Before building a file, determine what one row represents. It might represent one employee’s shift, one time entry, or one punch such as a clock-in or clock-out. This choice affects the columns and the way records are entered. A shift-based worksheet can be convenient for review, while a system configured for individual punches may require a separate row for each event. Follow the import specification rather than combining formats by guesswork.

Common information to confirm includes:

• Employee identifier: Use the identifier recognized by the receiving account, such as an employee ID. Names alone may be ambiguous, especially when employees share a name or their names are entered differently.
• Work date and time: Confirm the required date order, time notation, and whether a shift crossing midnight is recorded on its start date, split across dates, or handled another way.
• Hours or punches: Find out whether the import expects start and end times, total hours, individual punches, or specific fields for each.
• Breaks and pay categories: Check whether unpaid breaks, overtime, paid leave, or other earnings are entered as separate values or represented by approved codes.
• Organization details: Department, job, location, or labor allocation fields may be required for some employees or optional for others.
• Row and file rules: Ask about required headers, accepted separators, blank fields, duplicate records, and any control totals or approval indicators.

Do not invent earning, department, or job codes. Codes are often specific to an employer’s configuration, and a plausible-looking value can still be invalid or map to the wrong category. Request the approved list from the person responsible for the import.

Blank ADP time card import worksheet template

This generic shift worksheet is for collecting information before preparing an import. It is not a guaranteed upload-ready file. Use one row per shift only if that matches your process, and remove or rename fields to match the exact import specification. If the system requires one row per punch or a different structure, rebuild the file accordingly.

Prepare and review the file

A careful workflow reduces avoidable errors and makes it easier to trace a problem. Keep an untouched copy of the source records, and record which pay period and employees the proposed import covers. If you are preparing the file for someone else, include the date range and the name of the person who assembled it so questions can be routed promptly.

1. Obtain the current import instructions. Confirm the product, import type, required columns, file format, and accepted values with the account administrator or payroll contact.
2. Collect approved time records. Use the organization’s normal timekeeping and approval process. Do not treat an unapproved worksheet as a substitute for required review.
3. Enter records consistently. Use the expected employee identifiers, date and time formats, and codes. Preserve leading zeroes in IDs if they are meaningful; some spreadsheet applications may otherwise remove them.
4. Check the data against source records. Look for missing entries, duplicate rows, incorrect dates, unexpected hours, and mismatched employee or job details.
5. Save or export in the specified format. Confirm that the saved file has the required extension and that the export did not alter dates, codes, or separators.
6. Use a test or preview step if available. Review any validation results before finalizing an import, and resolve errors rather than repeatedly uploading an unchanged file.
7. Reconcile after processing. Compare the resulting time records with the approved source and investigate rejected, duplicated, or changed entries.

Formatting details that commonly matter

Spreadsheet programs can silently change values. An employee ID such as 004217 may display as 4217 if the column is treated as a number. A date such as 10/11/2026 can also be interpreted differently depending on regional settings. If the import instructions require a particular representation, preserve it in the exported file and inspect the actual saved output, not just the spreadsheet view.

Other details to verify include whether the file requires a header row, whether headers must match exact names, how commas or other separators are handled, and whether text containing a separator must be quoted. Avoid adding titles, totals, merged cells, formulas, extra tabs, or explanatory notes unless the specification permits them. A worksheet designed for humans may contain helpful formatting that an import process cannot read.

Time values deserve special attention. Confirm how the system represents overnight shifts, daylight-saving changes, rounding, and unpaid breaks. Do not calculate total hours from start and end times using an assumption that has not been approved. For example, an overnight shift ending after midnight can produce a negative duration in a simple spreadsheet formula unless the date logic is handled correctly. If the import accepts hours rather than punches, check whether breaks should already be deducted and how precision is represented.

Common import problems and how to investigate them

A rejected file does not necessarily mean the time records are wrong. It may indicate a structural mismatch, such as an unexpected header, unsupported file type, or a required field left blank. Read the validation message and compare it with the import instructions. Change only the relevant issue, then review the revised file before trying again.

• Employee not found: Check for a mistyped ID, removed leading zero, inactive record, or identifier from a different system.
• Invalid code: Verify the earning, department, job, or location value against the organization’s approved codes. Do not substitute a similar code without authorization.
• Invalid date or time: Check the required format, date range, time notation, and handling of shifts that cross midnight.
• Duplicate entry: Compare the file with prior uploads and the receiving system’s duplicate rules. Avoid uploading again until you know whether the first attempt partially processed.
• Hours do not match: Recheck break treatment, decimal precision, shift boundaries, and whether the system expects punches or calculated duration.
• Columns appear shifted: Inspect separators, quotation marks, unexpected commas, blank columns, and any change made during export.

If only some rows fail, preserve the error report and identify whether the accepted rows were already added. Re-uploading the full file without checking can create duplicates in some workflows. Ask the administrator how to correct rejected rows and whether an import can be reversed or amended; the available process depends on the account and the stage of payroll processing.

Protect employee time data

Time card files can contain employee identifiers, schedules, work locations, and other workplace information. Share them only with people who need them for timekeeping or payroll, use organization-approved storage and transfer methods, and avoid sending files to personal accounts or leaving printed copies unattended. Keep only the records required for the task, and follow your employer’s retention and deletion practices.

Before sending a file, check the recipient and attachment, especially when multiple employees or pay periods are included. If a file is sent to the wrong person or contains information it should not, follow your organization’s incident-reporting process promptly. A blank generic template should not contain real employee details when it is being shared as an example.

When to use a worksheet instead of an import

A spreadsheet is useful for collecting or checking time when the authorized process allows it, but it does not replace a configured timekeeping workflow. If managers enter hours directly into an approved ADP interface, a separate import may add unnecessary reconciliation work. If time comes from another system, an import can be appropriate only when the receiving account has a supported process and the records can be mapped reliably.

Alternatives include entering or correcting time through the organization’s established timekeeping method, asking the payroll team to prepare an approved import, or using a supported integration configured for the account. Choose based on who owns the data, how approvals are recorded, and how errors can be traced. The fastest-looking method is not necessarily the safest if it bypasses review or produces records that cannot be reconciled.

Frequently Asked Questions

Is there one universal ADP time card import template?
No. Requirements can differ by ADP product, employer configuration, and import type. Obtain the current specification for the account that will receive the file.

Can I upload the blank template on this page?
Not without checking it first. It is a generic worksheet for organizing shift data, not a confirmed upload format. Match its fields, row structure, codes, and file type to your account’s instructions before importing.

Should I enter total hours or clock-in and clock-out times?
Use whichever representation the import is configured to accept. Do not enter both as a workaround unless the instructions explicitly require or allow both, because the system may reject or interpret conflicting values.

Can I use employee names instead of employee IDs?
Only if the import specification says names are accepted and explains how employees are matched. An approved unique identifier is generally easier to validate than a name that may be duplicated or formatted differently.

Why does a spreadsheet change my employee IDs or dates?
Spreadsheet applications may automatically treat IDs as numbers and dates according to regional settings. Format and export fields as required by the import instructions, then inspect the saved file for altered values before submitting it.

Who should I contact if the import fails?
Start with the person responsible for timekeeping or payroll imports in your organization. Provide the error message and relevant file details through an approved channel, but do not send employee data more widely than necessary.

Related

• Quote Receipt Template: What to Include
• Receipt Book Template: What to Include and How to Use It
• Purchase Order Record Template: What to Include