WPS Codes and Routing Codes in the UAE

The phrase has no single referent, and most of the confusion in a failed salary run comes from two people using it to mean two different things. The Wages Protection System uses four families of number, and only one of them is a routing code.

Every one of these is validated by the system before a wage is recorded as paid, and the validation is unforgiving: a well-formed number that belongs to the wrong field fails as hard as a malformed one.

The routing code is the number the Central Bank of the UAE assigns to an institution so that the Wages Protection System knows where money is going. The Ministry's specification describes it in the employee record as "the 9 digit head office routing code as assigned to the AGENT by CBUAE", validated against the master database the system holds. It is a head-office code, not a branch code, which is why the same nine digits serve every branch of the same institution.

An "agent" here is the Wages Protection System's own term for the bank, exchange house or financial institution that actually pays the worker. It is not a job title and it is not an intermediary you appoint separately: for most employers with fully banked staff, the agent and the employer's bank are the same institution and the same routing code appears twice in the file. For employers whose workers are paid through an exchange house, they are two different institutions and two different codes.

That is the trap. The salary file carries a routing code in two places and they mean opposite ends of the transfer. Field 03 of each employee record is the routing code of the agent where that worker is paid. Field 03 of the salary control record is the routing code of the employer's own bank, the institution being debited. Copying one into the other produces a file that either fails the master-database check or, worse, describes a payment route that was never intended.

This is the single most-searched version of the question, and the honest answer is that we could not find a published master list and will not reproduce an unofficial one. What we checked, on 21 August 2026: the UAE Government Portal's page on payment of wages, which sets out the Wages Protection System obligation and the penalty ladder but carries no routing table; and both openly hosted copies of the system's own file specification, which describe the routing code as validated against a master database held inside WPS rather than published. The Central Bank of the UAE's own site returns an access error to automated requests from this network, so we cannot state what it does or does not publish: only that no government-published list was reachable. The practical consequence is straightforward. Your routing code is issued to you as part of onboarding, by the bank or exchange house that will act as your agent, and it belongs in your WPS registration pack alongside your employer unique ID.

Ask for it in writing, on the institution's own letterhead or in its corporate banking portal, and reconcile it against the first file that is accepted rather than the first file that is sent. Routing codes copied from a blog post, a payroll-software help page or a competitor's sample file are the wrong place to start. Institutions merge, are absorbed and are rebranded; the codes attach to the institution the Central Bank recognises, not to the brand on the branch. An out-of-date nine-digit code is not obviously wrong on the page, which is precisely what makes it expensive.

The employer unique ID, often called the establishment ID or company code, is the thirteen-digit number the labour ministry assigns to your establishment. It is the number the Wages Protection System uses to decide whether the wages of your workers have been paid, and it is therefore the number that the entire compliance record hangs from. The specification is precise about its shape. It is validated against the master database, it must be padded with leading zeros where it is shorter than thirteen digits, and the system's own rejection code 00506 reads "Employer ID is invalid and it must be a valid 13 digit number". Losing a leading zero in a spreadsheet is one of the two or three most common causes of a rejected file, because the number looks correct to a human reader and is one character short to the validator. It appears twice in every submission: in field 02 of the salary control record, and as the first thirteen characters of the file name.

Those two must agree. The Ministry's guide notes that the establishment ID is printed on documents the ministry has already issued to you, so the reliable source is your own establishment file rather than a re-typed copy. Group structures are the other place this goes wrong. The system will not accept employees of one employer mixed into another employer's file: the guide states that files mixing employers are rejected outright, so a group with four licences sends four files with four employer IDs, however unified the HR function is.

Each worker is identified in the salary file by the personal number issued by the labour ministry: the fourteen-digit figure printed on the face of the labour card. The specification is emphatic that no substitute works: asked which number to use, it answers that the personal ID is to be used and that "any other number will fail validation". That rules out the numbers employers reach for first. It is not the Emirates ID number, not the passport number, not the visa or residence file number, and not your own internal employee code. The current bank reference allows the field to run from fourteen up to thirty-five characters, which reflects later identifier formats, but the fourteen-digit personal number remains the reliable value. UAE nationals are inside this, not outside it. The Ministry's guidance states that the same personal ID applies to Emirati staff and that a national who does not hold a labour card will need to obtain one. Nationality changes what happens to pensions and end-of-service entitlement; it does not change how a person is identified to the Wages Protection System. One employee cannot appear twice in the same file. If a worker needs a correction and a supplementary payment in the same month, that is two files, not two records.

When the Wages Protection System refuses a file, the response comes back as a NAK, a rejected-file acknowledgement, carrying a five-digit code and a short description, which your bank generally forwards to the email address on your WPS registration. The codes are the fastest diagnosis available, and they separate a formatting problem from an identity problem in one line. The list below is from the Ministry and Central Bank specification. Read it as indicative: the guide itself states that the codes are valid as at publication, that additions and deletions are possible, that they are issued to banks, exchange houses and third-party providers from time to time, and that updating the documents is at the Central Bank's sole discretion. Your agent holds the current list.

Every code on this page is validated inside the Wages Protection System against a database you cannot read, so the only reliable confirmation is an accepted file. Do that confirmation deliberately, on a cycle where a rejection is survivable, rather than discovering it on the last working day of a month.

The sequence below is what a clean onboarding looks like. It exists because each of the three identifiers fails in a different way: the routing code fails against the master database, the employer ID fails on padding, and the employee personal number fails per line.

We will not give you a bank-by-bank routing code table. No UAE government source we could reach publishes one, the codes are validated against a database inside the system rather than against anything printed, and a stale nine-digit number is invisible until a payroll run fails. Ask your agent. We will not tell you your employer unique ID, and there is no public lookup for it that we can verify. It comes from your own establishment file with the labour ministry. We will not restate a fine figure here. Late or missing wage transfers escalate on a published ladder under Ministerial Resolution No. 340 of 2026, work permits are suspended, then the establishment's file, with the consequences widening by headcount, and that ladder belongs on one page, kept current, rather than repeated in four places where three copies quietly go out of date. The version circulating on payroll-software sites is generally the superseded 2022 schedule.