What is a SIF file?

What is a SIF file for?

Under WPS, an employer does not simply transfer wages. It hands a file to a bank or exchange house that is registered as a WPS agent, the agent pays each employee from it, and the same file becomes the record the Ministry of Human Resources and Emiratisation (MOHRE) uses to confirm that wages were paid. The SIF is that file. It is plain text, one row per line, in a fixed order of fields, and it is produced once a month for each pay period.

Because a machine reads it, it is unforgiving. A human reading a payslip will forgive a transposed digit in a bank code; the agent's validator will not, and the whole file bounces.

What does a SIF contain?

Two kinds of row. The exact field list, order and formats are set by the ministry and your agent, so treat this as the shape rather than the specification.

Employee detail rows, one per employee paid in the period, typically carry:

• The employee's identifier as held by the ministry.
• The routing code of the bank or agent that holds the employee's account or card, and the account identifier itself.
• The start and end dates of the pay period, and the number of days it covers.
• The fixed pay for the period, the variable pay for the period, and the number of leave days taken.

The salary control row, one per file, typically carries:

• The employer's identifier as held by the ministry, and the routing code of the employer's bank.
• The file's creation date and time, and the salary month it relates to.
• The number of detail rows, and the total amount those rows add up to.
• The payment currency and an employer reference.

The control row is the file's own checksum: if the count or the total does not match the detail rows, the file is rejected before anyone is paid.

How is a SIF produced and submitted?

1. Finish the pay run. Hours, leave, advances and deductions for the period are final, and the payslips are frozen so the figures hold still while the file is made.
2. Generate the file from those frozen figures, one detail row per employee and the control row from their sum.
3. Upload it through your WPS agent's portal, together with the funds to cover the total.
4. Wait for acceptance. The agent's validator checks identifiers, routing codes, dates and totals; a rejection comes back with a reason.
5. Keep the accepted file with the month's payroll records as the evidence that the month was paid.

Why is a SIF rejected?

The same reasons a WPS submission fails, seen from the file's side: an employee identifier that does not match the ministry's record, a routing code that does not belong to the employee's bank or card, a period that overlaps the last file, a date in the wrong format, or a control row whose count or total was not refreshed after a late change. Each is caught by generating the file from one clean staff record rather than maintaining a second copy of the same data in a spreadsheet at month end. The UAE WPS payroll guide walks the monthly cycle and the common rejections in order.

SIF or the bank's own WPS file: which one do I need?

Whichever your agent accepts. Some banks take the standard SIF as it is. Others provide their own upload template, sometimes a spreadsheet, that carries the same fields in a different arrangement. The information is identical; only the container differs. This is why a payroll system for the UAE should produce both from the same completed run, so the choice of bank never means retyping the month.

How PlayAreaOS produces the SIF

Completing a month in payroll freezes the payslips and exports the file in one step, so the rows the agent validates and the figures each employee reads are the same set of numbers rather than two copies of it. Gratuity and end-of-service, the air ticket and leave are settled in that same run, from the staff records the rota already keeps.