Check your WPS salary file before the bank rejects it.

Why files get rejected

These are the causes we see most often. Each one rejects the whole file, not just the line it appears on.

• The control record is in the wrong place. The SCR line must be the last line, after every employee row — not a header at the top. Several widely-read online guides get this backwards. Gateway error 00803.
• The total doesn't match to the fils. The tolerance is zero. One fils of rounding drift rejects everything — error 00802. Ten workers on AED 1,234.10 adds up to 12341.000000000002 in ordinary computer arithmetic, which is enough to fail.
• The employee count is wrong after someone is added or removed by hand. Error 00801.
• A thousands separator in an amount. The comma is the field separator, so 50,750.30 silently splits the row and shifts every column after it.
• An IBAN with a typo. A UAE IBAN is 23 characters and carries a checksum — we verify it.
• The salary month written the wrong way round. It is MMYYYY — month first. August 2026 is 082026, not 202608.
• The file saved from Excel as "CSV UTF-8", which adds an invisible marker at the start and breaks the plain-ASCII rule.

What this tool does not check

It checks the file. It cannot check anything the bank looks up in the MOHRE database — whether a labour card is still valid, whether the establishment ID is registered, or whether the salary matches the filed contract. And it deliberately does not tell you whether you are compliant: a file can pass every check here and still leave you below the 85% threshold. Those are two different questions, and confusing them is how employers get caught out.