Guide · Arabic & RTL

Syrian pounds in your database and on screen.

The redenomination moved every price two places, the ISO code did not change, and the browser's default formatting rounds to whole pounds. Here is what to store, how to convert, and how to show it in Arabic and English.

Updated 16 November 2026Sources checked 16 November 2026Reviewed by Eng. Hasan Kassas

The short answer

The Central Bank of Syria announced that every 100 old pounds become 1 new pound. New notes entered circulation on 1 January 2026, and old notes stopped being valid for circulation from 31 July 2026. The ISO 4217 list of 17 September 2026 still lists the Syrian pound as SYP, number 760, with 2 minor units: no new code was issued. So the code alone cannot tell you which scale a stored price uses.

A useful consequence: an amount stored as a whole number of old pounds is exactly the same number as the new amount in hundredths (125,000 old pounds = 1,250.00 new pounds = 125000 hundredths). If you stored integers, you can switch by changing what the number means and how you display it, without touching the data. That is our reading of the arithmetic, not an official instruction.

Intl traps

What the browser prints by default

Output (Node 24, Chrome 157)Problem
NumberFormat("ar-SY", currency SYP).format(1250.5)‏١٬٢٥١ ل.س.‏Rounded to a whole pound: CLDR gives SYP 0 decimals, ISO says 2
NumberFormat("en", currency SYP, narrowSymbol)£1,250Looks like British pounds
NumberFormat("ar")1,250 (Western digits)Plain ar and ar-SY give different digits
Any Arabic currency outputstarts and ends with U+200FInvisible right-to-left marks break string comparisons and parsing
Tested code

Convert, format and parse

Three functions: keep old integer amounts as new hundredths, format new pounds with two decimals in Arabic or English, and parse what people type in either digit system back to an integer:

// Syrian pound amounts: old vs new scale, display, and parsing what users type.
// Central Bank of Syria: 100 old pounds = 1 new pound. ISO 4217 code is still SYP (2 minor units).
// So an integer amount in OLD pounds is exactly the same number as NEW pounds in hundredths.
const OLD_PER_NEW = 100;

function oldToNewMinor(oldPounds) {            // 125000 old  -> 125000 hundredths = 1,250.00 new
  if (!Number.isInteger(oldPounds)) throw new Error("old amounts are whole pounds");
  return oldPounds;                            // same integer, new meaning: no data migration needed
}

function formatNewPounds(minor, lang = "ar", digits = "arab") {
  const locale = lang === "ar" ? `ar-SY-u-nu-${digits}` : "en-SY";
  return new Intl.NumberFormat(locale, {
    style: "currency", currency: "SYP",
    currencyDisplay: lang === "ar" ? "symbol" : "code",
    minimumFractionDigits: 2, maximumFractionDigits: 2, // Intl defaults SYP to 0 decimals
  }).format(minor / OLD_PER_NEW);
}

// Accepts 1,250.50 · ١٬٢٥٠٫٥٠ · ۱۲۵۰ ; returns hundredths (integer) or null.
function parseToMinor(input) {
  const s = String(input)
    .replace(/[٠-٩]/g, (d) => d.charCodeAt(0) - 0x0660)
    .replace(/[۰-۹]/g, (d) => d.charCodeAt(0) - 0x06F0)
    .replace(/[\s,٬‏‎]/g, "")
    .replace(/٫/g, ".");
  const m = /^(\d+)(?:\.(\d{1,2}))?$/.exec(s);
  return m ? Number(m[1]) * 100 + Number((m[2] || "0").padEnd(2, "0")) : null;
}

15 test cases pass: Arabic-Indic, Western and Persian digits, Arabic and Western separators, the RLM marks and no-break space in Intl's output, the rounding and £ pitfalls, and rejection of more than two decimals. Try it in the Syrian pound formatter.

Migration

Moving a price database to the new pound

  1. List every money column and its scale

    Prices, balances, fees, delivery charges, discounts, and anything cached in apps or search indexes. Write down which are still in old pounds.

  2. If amounts are whole old pounds, do not convert them

    Reinterpret the same integers as new-pound hundredths and change only the display, which divides by 100 and shows two decimals.

  3. If amounts are decimals or floats, make them integers first

    Floating-point money drifts. Convert to integer hundredths of the new pound in one migration, and check totals before and after.

  4. Mark old records

    Receipts and invoices issued before the switch were in old pounds. Store the scale or the issue date with them so a reprint shows the amount the customer actually paid.

  5. Accept both digit systems in every input

    People type ١٢٥٠ and 1250. Parse both, as parseToMinor does, and reject anything with more than two decimals.

  6. Never hard-code exchange rates

    The Central Bank publishes official rates in the new pound and they change. Read them from your source each day and store the rate you used with each transaction.

FAQ

Common questions

Yes. The ISO 4217 list published on 17 September 2026 still lists the Syrian pound as SYP, numeric code 760, with 2 minor units.

Sources

Where these facts come from

  1. Central Bank: 100 old pounds convert to 1 new poundSANA, via Arab News · 29 Dec 2025
  2. New banknotes in circulation from 1 January 2026Al Jazeera · 5 Jan 2026
  3. Old notes no longer valid for circulation from 31 July 2026Arab News · 30 Jul 2026
  4. ISO 4217 list one (SYP, 760, 2 minor units)SIX, ISO 4217 Maintenance Agency · 17 Sep 2026
  5. Official exchange rates, quoted in the new poundCentral Bank of Syria · accessed 16 Nov 2026
  6. CLDR currency data (SYP digits="0")Unicode CLDR · accessed 16 Nov 2026
  7. Intl.NumberFormat() constructorMDN Web Docs · accessed 16 Nov 2026

Redenomination dates from news agencies (medium confidence); ISO and Central Bank pages checked 16 November 2026. Code tested with Node 24 and Chrome 157.

Prices or payments in a Syrian app?

Tell us what you are building. We will help you get the money parts right.