How GCC Statement Formats Differ, and Why It Matters

That no two banks share a statement schema is true within a single country. Extending across the GCC adds a second layer, and this one is not about column order — it is about currency, calendar and script conventions that change the meaning of correctly-read characters.

Minor units: the error that is exactly ten times

Currencies in the region do not all have two decimal places, and this is not a stylistic variation — it is defined in the currency itself:

A pipeline that assumes two decimals — a reasonable assumption almost everywhere in the world — misreads every amount on an Omani, Bahraini or Kuwaiti statement by a factor of ten. The failure is uniform, which makes it easy to catch if anything checks and invisible if nothing does.

What catches it is the balance identity: opening balance plus the sum of movements must equal the closing balance, and a systematic factor-of-ten error breaks that arithmetic on the first statement. This is the strongest practical argument for running the reconciliation check on every document rather than sampling — it converts a silent misinterpretation into a hard failure.

Calendars and dates

Statements from Saudi institutions may carry Hijri dates, sometimes alongside Gregorian ones. A system that assumes a Gregorian calendar will either fail to parse the date or — worse — parse it as a Gregorian date and produce a value that is plausible and wrong by centuries. Whether any given statement uses Hijri, Gregorian or both varies by institution and product, so this is something to establish per issuer rather than per country.

Ordering conventions add a quieter risk. A date rendered numerically as 03/04 is ambiguous between two readings, and the resolution is a convention rather than something visible in the characters. For most purposes this does not matter; for anything time-sensitive — an affordability window, a salary cycle, an obligation due date — reading the month as the day silently reorders the whole statement.

Weekend conventions also differ across the region and have changed in recent years, which shifts when value dates cluster. That matters for inference rather than extraction: a salary credit that appears to land two days late may simply be a weekend effect in that jurisdiction.

Numerals and script, which are two separate problems

Amounts may be rendered in Western digits or Eastern Arabic numerals (٠١٢٣٤٥٦٧٨٩), and both can appear on one document. This has to be handled at character recognition rather than by transliterating a wrong answer afterwards, and it interacts with the decimal question above: an Eastern-numeral amount with three decimal places on an Omani statement combines both difficulties in one field.

Separately, narration is frequently bilingual — Arabic headers over English transaction descriptions, or both scripts inside a single narration field. Because Arabic runs right to left inside a left-to-right table, text extracted in file order can emerge scrambled relative to the page. That is a reading-order problem, not a language problem, and it is solved by anchoring to layout position rather than by better language handling.

What this means for how you buy

The practical consequence is that "works in the GCC" is not a capability claim — it is six of them. A system proven on UAE statements has not been tested against three-decimal currencies, may never have encountered a Hijri date, and may have been evaluated entirely on Latin-script narration.

So the question to a vendor is per-country and per-issuer: which countries have you processed, which currencies, and can you show field-level accuracy for each. A single regional figure averages across populations that behave differently and tells you nothing about the one you are about to run.