Almadar A finance team split between an office in Al Olaya and a back-office function near Al Malaz will record the same transaction two different ways without a written policy telling both sides which one is correct.
This is more technically specific than the broader policies and procedures work covering general operational processes, and it directly supports both technical accounting advisory and any framework transition, since a documented policy manual is what a transition ultimately gets restated against.
Why an undocumented policy quietly creates inconsistency
Without a written policy, revenue recognition timing, provisioning thresholds, and capitalization criteria all live in the collective memory of whoever has been doing the job longest, which works reasonably well until that person is on leave, changes roles, or a new team member applies their own reasonable but different judgment to the same transaction type.
What a proper manual actually covers
Specific accounting policies for every material transaction type your business actually encounters, revenue recognition by contract type, provisioning methodology, capitalization thresholds, foreign currency treatment, written in enough detail that a new finance hire can apply them consistently without needing to ask a senior colleague every time a judgment call arises.
A common Saudi scenario
A Riyadh-headquartered group with a manufacturing subsidiary and a trading arm often has genuinely different accounting policy needs, inventory valuation and long-term contract accounting matter for the manufacturing entity, while the trading entity's policy questions center more on revenue recognition timing and FX translation.
What we deliver
A documented policy manual covering your specific material transaction types, written in plain enough language that it's actually usable day to day rather than a technical document nobody but the person who wrote it can interpret.
Building it from actual transactions, not a generic template
The most useful manuals are built by working through your business's real recent transactions and documenting the policy that was actually applied, correcting it where needed, rather than starting from a generic industry template that describes transaction types your business doesn't actually have.
Groups spanning Riyadh with genuinely different business lines under one ownership structure typically need entity-specific policy sections addressing their distinct transaction types, sitting under one consistent group-wide policy framework rather than one identical manual applied uniformly to businesses that operate completely differently.