Regional & Geographic Approvals

this guide shows you how to configure approval workflows that route based on geographic regions, territories, sales divisions, or international business requirements what are regional approvals? regional approvals route records to different approvers based on geographic criteria such as sales territory or region country or country group business unit or division currency of the deal regulatory jurisdiction quote submitted │ ├─── na region ────► na sales vp │ ├─── emea region ──► emea sales director │ ├─── apac region ──► apac regional manager │ └─── latam region ─► latam country manager business scenarios covered scenario description regional sales leadership route to regional vp/director based on territory country specific compliance additional approvals for certain jurisdictions currency based authorization different limits based on deal currency multi region deals global accounts requiring multiple regional approvals territory based manager lookup dynamic approver based on account territory owner scenario 1 basic regional routing requirement route approvals to the appropriate regional sales leader based on the account's region prerequisites ensure your account object has a region field (e g , region c ) with values like na , emea , apac , latam configuration create four parallel paths , one for each region path a north america setting value approval path name na approval entry criteria account region c = 'na' step na sales approval approver type role role na sales vp path b emea setting value approval path name emea approval entry criteria account region c = 'emea' step emea sales approval approver type role role emea sales director path c apac setting value approval path name apac approval entry criteria account region c = 'apac' step apac sales approval approver type role role apac regional manager path d latam setting value approval path name latam approval entry criteria account region c = 'latam' step latam sales approval approver type role role latam country manager note enable "skip if not applicable" on each path so deals from other regions aren't blocked \[screenshot regional paths configuration] scenario 2 dynamic regional approver lookup requirement automatically route to the appropriate regional leader without maintaining separate paths using user lookup with formula 1\ create a formula field on quote field regional approver c (formula returning user id) case( account region c, 'na', '005xxxxxxxxxxxx', / na vp user id / 'emea', '005xxxxxxxxxxxx', / emea director user id / 'apac', '005xxxxxxxxxxxx', / apac manager user id / 'latam', '005xxxxxxxxxxxx', / latam manager user id / '005xxxxxxxxxxxx' / default approver / ) 2\ create single approval step setting value approval step name regional sales approval approver type user lookup lookup path regional approver c using group lookup alternatively, use groups for each region 1\ create regional groups in salesforce na sales approvers emea sales approvers apac sales approvers latam sales approvers 2\ create formula field field regional group c (formula returning group api name) case( account region c, 'na', 'na sales approvers', 'emea', 'emea sales approvers', 'apac', 'apac sales approvers', 'latam', 'latam sales approvers', 'global sales approvers' ) 3\ create group lookup approver setting value approver name regional sales team type group lookup group lookup field regional group c scenario 3 country specific compliance approvals requirement certain countries require additional legal/compliance review due to regulations configuration create a separate compliance path that triggers for specific countries compliance path setting value approval path name compliance review depends on (none parallel with sales path) entry criteria condition 1 account billingcountry in ( germany , france , brazil , china , india ) or use a formula requires compliance review c = true compliance step setting value approval step name regional compliance approval approver type group group regional compliance team country specific approver mapping for more granular country routing, use a matrix country compliance approver germany eu data protection officer france eu legal team brazil latam compliance china apac legal + government relations india apac compliance scenario 4 currency based authorization limits requirement approval thresholds vary by currency $100k usd threshold equals different amounts in other currencies using currency adjusted formula 1\ create normalized amount field field amount usd equivalent c (formula) case( currencyisocode, 'usd', amount, 'eur', amount 1 10, / convert eur to usd / 'gbp', amount 1 27, / convert gbp to usd / 'jpy', amount 0 0067, / convert jpy to usd / amount / default use original / ) note update conversion rates periodically or use salesforce's currency management 2\ configure entry criteria using normalized amount setting value condition type clause field amount usd equivalent c operator greater than value 100000 alternative regional amount thresholds create region specific thresholds region threshold (local currency) na $100,000 usd emea €90,000 eur apac ¥15,000,000 jpy latam r$500,000 brl use separate paths with currency appropriate conditions scenario 5 multi region global account approvals requirement global accounts spanning multiple regions need approval from all affected regional leaders configuration parallel regional paths create multiple paths that trigger based on where the account has presence process structure global account quote submitted │ ┌─────────┼─────────┬─────────┐ ▼ ▼ ▼ ▼ ┌───────┐ ┌───────┐ ┌───────┐ ┌───────┐ │ na │ │ emea │ │ apac │ │global │ │ path │ │ path │ │ path │ │account│ │ │ │ │ │ │ │ mgmt │ └───────┘ └───────┘ └───────┘ └───────┘ │ │ │ │ ▼ ▼ ▼ ▼ all paths must complete for final approval path entry criteria path entry criteria na path account has na operations c = true emea path account has emea operations c = true apac path account has apac operations c = true global account account global account c = true global account management step setting value approval step name global account approval approver type user lookup lookup path account global account manager c scenario 6 territory based manager lookup requirement route to the territory owner's manager, not a static regional approver using dynamic lookup path 1\ ensure territory assignment the quote or account should have a territory field linking to a user account territory owner c (lookup to user) 2\ configure user lookup approver setting value approver name territory manager type user lookup lookup path account territory owner r managerid this dynamically finds the account's territory owner that user's manager assigns approval to that manager escalation chain by territory for multi level approval based on territory step lookup path territory owner account territory owner c territory manager account territory owner r managerid regional vp account territory owner r manager managerid scenario 7 timezone based routing requirement route to approvers in the same timezone as the customer for faster response using timezone formula 1\ create timezone mapping field field approval timezone c (formula) case( account billingcountry, 'united states', 'americas', 'canada', 'americas', 'mexico', 'americas', 'united kingdom', 'emea', 'germany', 'emea', 'france', 'emea', 'japan', 'apac', 'australia', 'apac', 'singapore', 'apac', 'global' ) 2\ route to timezone matched approvers setting value approver type group lookup group lookup field approval timezone c & ' approvers' groups americas approvers , emea approvers , apac approvers , global approvers best practices do's use formula fields for dynamic routing easier to maintain than hardcoded paths create catch all regions handle accounts without region assignment document regional thresholds keep a reference of approval limits by region consider timezone coverage ensure approvers available during business hours don'ts don't create too many parallel paths consolidate with dynamic lookups when possible don't hardcode user ids in formulas use custom settings or custom metadata types don't forget default handling what happens when region is blank? troubleshooting issue cause solution wrong regional approver region field not populated add validation rule requiring region no approver found region value doesn't match formula case add catch all default case multiple regions triggering parallel paths without proper criteria make entry criteria mutually exclusive currency conversion off exchange rates outdated update formula or use dated exchange rates related guides deal desk routing docid\ uwih3wye4e4ez7cbjvcy4 team based routing patterns approval matrices docid\ pmcr5xpdwndph0zwj6pti region as matrix dimension customer segment approvals docid\ mr d0rl2ctanpyo onlcb segment based variations need help? check our troubleshooting guide docid\ sgpxdyp dpg9a9uanwlis or faq docid\ relcvm0ggisy7rghm2jml