Quick answer
A staffing agency’s payslip Excel file should connect each approved pay record to one identifiable employee, the correct employer, an explicit pay period and a verified recipient. Separate the fields needed for delivery from the information employees should see. Keep client billing rates, margins and administrative notes out of the employee-facing record. Finish wage calculations and approval in your existing payroll process before preparing the distribution file.
Start with the employer, not the client site
A worker may perform duties at a client’s warehouse while remaining employed by the staffing agency. The client-site label can help payroll administrators reconcile assignments, but it should not replace the employer’s identity on the payslip.
Likewise, a client roster is not automatically a payroll master. It may omit a worker who transferred mid-period or include someone whose employment ended. Build the export from the approved pay population, then use the site roster as a separate reconciliation input.
For employers within the relevant Malaysian legal framework, regulation 9 of the Employment Regulations 1957 concerns providing individual wage particulars by payment day. Check jurisdiction and coverage before treating this as a rule for your operation; Sabah and Sarawak require separate review. JTKSM: Employment Regulations 1957.
A practical field checklist
The labels below are planning examples, not a mandatory Ant Payslip import schema. Review the actual mapping and preview before sending.
| Example field | Purpose | Employee-facing decision |
|---|---|---|
| Employee ID | Stable matching key | Include if useful for identification |
| Employee name | Human-readable identity | Show the approved name |
| Employer name | Identify the issuing organisation | Show the correct employer |
| Recipient email | Route the individual record | Verify; do not treat as a pay item |
| Period start / end | Identify the salary period | Show explicit dates |
| Payment date | Identify the payment being described | Show the approved date |
| Approved earnings / deductions / net pay | Explain final payroll figures | Map clear labels and approved values |
| Client site | Reconcile assignment | Show only when relevant and appropriate |
| Billing rate / margin | Commercial administration | Exclude from employee view |
| Payroll review note | Internal approval trail | Exclude from employee view |
Use text formatting for IDs with leading zeros. A displayed ID of 00127 should not silently become 127 when files move between systems. Keep one header row and avoid merged cells, subtotal rows or explanatory notes mixed into employee records.
Do not rely on cell colour to communicate a held payment. Put held records in a controlled exception list and exclude them from the send-ready population until the payroll owner confirms their treatment.
Simulated mapping example
Suppose employee AG-014 worked at two client sites during one approved pay period. Two attendance rows do not necessarily mean two payslips. Payroll must first decide the intended employee-level record structure and approve the figures.
The delivery export then contains the approved record for AG-014, its period and the verified employee email. The two client assignment notes remain in the internal reconciliation file unless their display is needed and approved. This avoids turning client billing detail into an accidental employee pay item.
If two workers have the same name, match by ID rather than taking the first matching name. If one ID has two email addresses, resolve the conflict before upload. A valid email format alone does not prove that the mailbox belongs to the worker.
Prepare the file in five steps
- Freeze the approved payroll version. Record who approved it and which period it covers.
- Select the employees due a payslip. Reconcile joins, transfers and departures separately from current site headcount.
- Match each record against a maintained contact list using a stable employee ID.
- Remove unnecessary internal columns and map the remaining fields to their intended use.
- Preview ordinary and exception records, including a duplicate name, a transfer and a record with multiple approved pay items.
The release check should ask whether the correct employee sees the correct information, not merely whether a spreadsheet uploaded successfully. Compare displayed dates, labels and values to the approved source. If a label is ambiguous, fix it before distributing the batch.
Ant Payslip can use approved Excel or CSV data to prepare and distribute individual payslips. It does not decide which agency is the employer, consolidate your payroll calculations or determine deduction legality. Those decisions stay with your payroll owner.
Before you release
- Every send-ready record has a resolved employee ID and recipient.
- Employer identity is not confused with the client location.
- The pay period and source version are recorded.
- Internal billing information is absent from the preview.
- Held and duplicate records have an owner, not an unexplained deletion.
Frequently asked questions
Can I use my existing staffing payroll spreadsheet?
You can prepare an export from it. Check the required mapping and remove internal information rather than uploading an uncontrolled working file unchanged.
Must client sites appear on employees’ payslips?
Do not assume so. Decide whether the field is needed for the employee’s record, then obtain the appropriate payroll review. A site label is not a substitute for employer identity.
Should I include formulas?
Finish and approve calculations first. Inspect the exported values and their display; the distribution stage should not become a second payroll calculation process.
What if the email address is missing?
Hold that record for verified contact correction. Do not substitute a client supervisor’s or colleague’s address simply to complete the batch.
Related guidance
See using an existing Excel spreadsheet and the Excel-to-payslip delivery workflow.
Review your export with Ant Payslip
Request a demo using a redacted staffing export to review field mapping, employee-visible information and individual delivery before a live payroll batch.
Source checked: 8 October 2026. This article addresses data preparation, not payroll calculation or a complete legal field specification.