If you're running cash anomaly detection on a multi-country SAP landscape, weekends matter. The default rule “transactions outside the working week need a second look” only works if the engine knows your working week.

Most cash anomaly tools were built for Western markets where Saturday and Sunday are the weekend. Run them on a Saudi finance team's bank statements and Saturday traffic — entirely normal in SA, BH, QA, KW, OM, YE, EG, and IQ — gets flagged as anomalous. Your Treasurer spends Sundays clearing false positives.

What “weekend anomaly” means

A weekend transaction is one that posts to the bank on a non-business day in the country where the bank operates. The rule fires because:

• Genuinely scheduled transactions usually post Monday through Friday (in Western markets) or Sunday through Thursday (in much of the GCC)
• Weekend transactions are more often manual interventions, batch errors, or fraud attempts
• Reviewing them weekly is cheaper than reviewing every transaction

For the rule to be useful, the engine has to know what “weekend” means for the bank in question. Country-aware Fri/Sat handling is the answer.

The countries Fin4Sight handles today

The Bank Intelligence Cockpit's anomaly engine has a country-aware Fri/Sat allow-list for the following countries, where the working week is Sunday-Thursday and Friday-Saturday are the weekend:

• Saudi Arabia (SA)
• Bahrain (BH)
• Qatar (QA)
• Kuwait (KW)
• Oman (OM)
• Yemen (YE)
• Egypt (EG)
• Iraq (IQ)

For these countries, a Saturday transaction is treated as a normal working-week transaction, not a weekend anomaly. A Friday transaction triggers the weekend rule, as does any transaction on a country-specific public holiday once that's wired in.

For all other countries, the default Western Sat/Sun weekend rule applies. The engine picks the right rule based on the bank's country code, not on which company code the transaction belongs to.

Why per-bank and not per-company-code

A multi-country group with a Saudi entity and a German entity has bank accounts in both countries. The Saudi entity's bank operates Sun-Thu; the German entity's bank operates Mon-Fri. Country-aware weekend rules apply per bank account, not per CompanyCode, because the question being asked is about the bank's working schedule.

A finance group running both can compare weekend anomaly counts across entities without one country's normal traffic flooding the other's exception queue.

What's still on the roadmap

Country-specific public holidays are not yet wired into the weekend rule. A transaction on Saudi National Day or Eid al-Fitr won't currently fire the weekend rule unless it lands on a Friday or Saturday. Holiday calendars are on the roadmap.

UAE switched its weekend to Saturday-Sunday in 2022; the GCC allow-list does not include UAE because it follows the Western weekend now. If your team needs UAE handling for entities still observing the older schedule, talk to us.

The other anomaly rules in the same engine

The weekend rule is one of 10. The full set covers deterministic rules (duplicates, round-number transactions, weekend with country-aware Fri/Sat, large outliers, frequency spikes, new counterparty, FX out-of-market, currency mismatch) and statistical rules (z-score and IQR on amounts and frequency).

Each rule fires with severity. Each comes with a “why” panel — what the threshold was, what the underlying figure is. The reconciliation queue routes anomalies into a case state machine with bulk actions.

For finance teams in the GCC

If your team has burned hours clearing Saturday “anomalies” out of every cash review, the country-aware engine is what cash anomaly detection should have looked like from the start. Bring a sample bank statement; we'll show you the rule firing on the right days, not all the days.