BUSINESS PROCESS DOCUMENT NN AXIATA-COUPA PROCUREMENT SOLUTIONSRevison History 1 January 2018 | Coupe nal Oa Perry 2019 | Coupe Dak 4 - February 2019 | Coupa Oak 1 February 2019. | Couns | 14 March 2018 | Coupa el 21" March 2019 Coopa za 26° March 2618 Coopa = amar Proy2018 Copa — en aaa ~ coups Fina ae Project eam Projet Sponsor ‘Mohamed Aanbin Abad | Keaton Mile } Tain | Project Owner 7 a ion ler | Projet Manage: Dod Heaven Sekt njsiaa Impiomenistion Manager felt ap Blusinoss Project Lead | Adi atiawiodo Sidro | Saket Raya ‘Technical Project Lead adam Racimart. it Maker Authrzrs for Sig-of Tle spose | Motwned Adorn Per Reve | sad Tn | Senet Pj Ome ‘vn Aaa a ei Sonat | REE v0 | Product Owner NYophiYlindo | Peer Review 7 6 Seat Tile wane | Ddemawan | Per ew ise | Seno s | Gear oiny ee eso 6 Senctt re |faty ‘iPod ee Review e/a Sudiro Sign-off 5°. Tn Sariy | Pet ew as Serof ‘BUSINESS PROCESS DOCUMENT | AXIATA.COUPA PROCUREMENT SOLUTIONS.Receipts erry Eck Renaldo | Peer Review / | jo Sien-off Teaton Yenny cusan Peer Review / Sign-off Contract Management | Priyanka Thomas | Peer Review / Paruhur Sien-off “is 0 ajative geared towers UAT busines prowess design and me he fin! Go ve eign whih _bjcedto be updsted afer UAT there oe oy further proes change. ‘istribution Team In Aion to Authorizes) Pree Sponsor ‘Mohamed Alan bn Abad Peel Owner ‘Avia Ala [Pree enape——SSSSSSSSS=* él Herma a a ‘Coipa Admin ‘Shinta Waning ‘Cougs Admin ‘Mahara Fay Hon ‘Seurcing Management Die Meyta cians ‘Suing Management ‘ik Mie Priyona AP Fi - “Unda Susenty : TT Integrations Manager ‘dam Rachmanto IT Developers| rams atin — Tevelopers otra Tr Wanda ‘Change Mensgement onder ‘Change Management ‘andy Sti BUSINESS PROCESS DOCUMENT | AXIATA.COUPA PROCUREMENT SOLUTIONSTable of Contents Aebcovatons Used, TermiclogyDetntons. 10 High-Level objectives 20 Global setings 24 Chatof Accounts, 22 other Company Data 30 souring 31° Sourcing Request 382 Seung Event 33° Contacte 331 ContctsCatlog tome 33:11 ConratsCatalog toms crated via buk uplead 33:12 ConretsCsalog toms created manualy 44 Reauision Options in Covpa 441 Hosted Catal, 442° Web Form 419° FreeText Request, 42 Roguistion Metnoss. 43° Reguiston Approvals. 44 Budgetng, 45. Purchase Order Management 451 PO Cenceliton 45 Supple 481 Shipping Terms 482 Payment Terms. 50 stk PO. 80 Recening 6.1 Receiving Tlerancss 70 Ivoking 7A PO Backed Inoking 72 NonPO Backed ivccing (Supplier Create). 73. NomPO Backed invccng (Requestor Create) 74 volng Approvals 75 Invicng Tolerances 13 “ 16 18 19 a BeeSAebeRR RE ages 38 28 [BUSINESS PROCESS DOCUMENT | AKIATA-COUPA PROCUREMENT SOLUTIONS, a78 Invoicing ~ User Roles a 8.0 Milestone PO 2 8.0 UserRoles & Reston “a 92 Account SecutySetings, “ 100 Aspendi. “a Abbreviations Used S20 Source to Conrct "| rap Requisition Pay Procure toPay Terminology/Definitions EE a ee Framnsttor Rol thet provides a vet wih he permission 10 acess ars sore every | enfgsraton open nan nstance [Tsering Ever that s used to ola pina elevan bmn | auction compete fomat where mute Supers ae sematng bs. The ove goals totan te lowest rie posable. [Comme ‘A deeipon ofthe ype of rod 0 sevies Bag BUTTRESS t Content Groups asscato ures wi erent pect ype of purchang Op Content Grours* ‘They deere wat tems a Use: can oder an om wih Supls. Te Howat User> Content Group > Cont >VieutAeoess spect pes of Contact. ‘aipa Cove Cavacs | The Coupe Modul asosated wih Coir reposion. ‘Coup Modul hat proves users the aby to perform Contract colaboratin 3d Ccoupa CL (Contact| Conret authoring na system as wel ex addons advansad repostory Leste Management) | functonaly. This Modul is soparate from Core Coupa Ceci. This is notin scope for he intial lease se oa for Suppliers to login ad parm acon wih the Buyer, Ti ropaces ‘Coupa SupplerPral | many fhe ofne steps tat may happen today (os) Respond to Soureg Everts Manage Supple: speci data ‘Waagenant Haaahy | The arrangement of usre win an oGanealon Secon ASOT Tis Approval structure defines whe approves whose requstsinveies cr expanse repens. ay ‘Data that proves infra about eter dat’. Fr 82, nfs spect case, data that descrtes the Contract that canbe searched andreporid on cae "Rn ena a to do iat message set oa usar when an atin i competed aA cor occurs that fects har realm of responsi. Admits vets neay [BUSINESS PROCESS DOCUMENT | AKIATA.COUPA PROCUREMENT SOLUTIONS: wv—= ‘vey nolfeston em Ena users peal oly eceve mlteatonsfortings ‘hay do themselves. Users can aut heir setngs in My Account > Setings > Nottaons to decid whether to recive an ems, notation in Coupa, oro saticaton at al depending on the overt Hosted Catalog “Roiedeaaog st of pe epelised cla Fame The calalpe we ade ite Coup, so users can search er and add ites thircart ect wehn the ator P2P (Procure Pay) "The proses wie pursing Oa GoOU owns and ons wih a Suppl Invoice and payment. ‘castonizable document thet makss posi a Gasions nd lose 52 (Source te Comat) uestonnaret ‘more drectons than posible via standard request Questionaire con be siached to awed orm an RFQ ora Yost ai eqvet fer ifomation. Sourcing Event used aban pr-aaieaion Intermation fom 2 Supple. = Request er Proposal. Soutng Evel ured to obain quale and pring Toutes injermatin ved te award busress to a Supper RFD Request fer Quote. Used obian a price fom Sunes) RE ‘Geni atcha frm ured fo reference RFQ, RF, nd RFP ‘A sto permissions covigted and preloaded ite Coupa al alow a use to on efor ast of tasks tat aig wh cmon responses for procurement Stam users. Ono user can nave multe roles eaded te ha user pote, Aoponding upon the responibites. “The process assocaed wt the Sourcing and Coniacng faneors Type procurement sce ae nated wih a Sourcing and Cnractingprovees before {an organzaton can purchase the good or service. Sa (Sourca to Pay) The ful endo-nd procurement process combining S2C wih PP. Setaoprovais Sourcing Manager This albus users o "approve The own documets ihe Approves equal toThO document owner. Ifthe syst wl ntl such a conden and system approve. Nol applable or XL ‘Siar vole provided to Sourcing 8 Procremari sors a enables aes create Sowing Everts and crested tempts, Uses thi le can ony rmodty thor spect Seung Everts Sourcing Admin ‘Standard le provided to Sourcing & Procararvar wots hal enables acsea 10 a ‘Sourcing Manager ais (permissions) wth tre adoral biy to ext at sourcing template, vow ore Sourcing Settings, and view el al Sovrcing Events “Th company hat provides he goods and pavers tha srvces hat Cutamer Supper needs to funtion, “ “Teen & Conan] lvoraton sent Suppor tat rut bo aecopled bear gaining ony race) ‘Sourcing Event Suppers must accept by checking the be BUSINESS PROCESS DOCUMENT |AXIATA.COUPA PROCURE) SOLUTIONS1.0 High-Level Objectives ‘This Businoss Process document se ut ode and analyz your intended precast, Tie document ‘al bep us understand ata Gea lve! te feet awe tat need to be mapped ito Coupa and wil timate eae your sucess implementation Tis document ines dlgrams and screenshots tht contaln futher detals and cletaton “There are a nur of ciferont modes win Coupa hat are avaiable. Thase are detaod above and plane in abt more deta! blow ‘Sourcing lows you ost. events and get Suppers o compete for your business. Procure to Pa: This covers Requlio fo Purchase Order process Receiving: Receive Purchase Order Invoking: Processing of Invies fom your Supper ao tha they can be passed to you for payment ‘Ta overall Source to pay transactional flow of daa fro use to request and ecevegeodssenvces and ‘Super to recoWe payments deltod below and his willbe he soe focus ofthis document, [BUSINESS PROCESS DOCUMENT | AXIATA.COUPA PROCUREMENT SOLUTIONS. a~ Thissecton of the document adresses how the chart of account wile set up in Ata Coupa Instance is posible to set-up multiple chart of accounts (CoA) Hf required by your orgnzaion, Each chart of accounts is made up of one or more alphanumeric lag component (ald “segments” in Coup) that indicat where something shouldbe bled. Coupa can accommodate up t020 segments within char of accounts, but mast organization use about 2 pment for optima ve. 2.0 Global settings 2.4 Chart of Accounts Based on Xs races, ony ane Company Code wl be wed in SAP{00%) wl have Dynamic CoAS. As per hs process they wil have two Cos, one wil bused for Stock purchases and other wll be used for Non stock purchases. Below are char of acount obese up in Coupa for along wih the segment structure: 2) PX. Axa Th (001) -Stok Segment NL Stock-Stock ting PL Ata Tx (001) Stock soe fy 2) PTX pata Tx (00, teem Seament4-GL-Defauited rom Commodity sey 1k Segment 2- account Category cost center ie) picrententaned ‘Maintenance Order (F) ‘enue ‘+ Prepayment/Advance (8) ee Projects) sae men Segment 3- Account SLA Rae (Child segment 2} ae BUSINESS PROCESS DOCUMENT | AXIATA.COUPA PROCUREMENT SOLUTIONS. aA= \Whenusescreate equstions they may nt know the corect account to chase. Coup allows youte create default settings that when a ser creates a requisition, the accounts automaticly chosen bnsed onthe users defaults Below re some important key sign dscussions ‘COA Defalting |For XL proces, CoA for Stock and non Stock wil be defauted | N/m bzed on ver profile, “Budget Setup XL is using SAP EC or lhe accounting and Budaeing purport | NTA ‘Budgets wl be maintained n SAP and wil be checked call whe creating Requstons and Non-PO backed lvoe. Tae Address | io ares willbe unique foreach COA. The biktoadaressis [WA ‘not displayed onthe requistio screen in Coupa, butts Tax led wth ‘the government) onthe CSP/EXML/CSV Invoice ad then ‘enter he Total Taxon the Invoe, based onthe amount ‘mentioned inthe Ta Invoice POF. we 2. Reasiom program developed by XL wil pick up thistnvoice fetch the Taxinucice POF, wl han very the taxon Wa 3. Header Tax hnount Weld on Coup wai and he taxon We government st If al of these match then the remote spprove wil approve automatically ese eect. Wa “Incase of rejection the invice willbe automaticaly dputed back tothe Supplier. The Supplier can then resubmit the Invoice with correct tax (onthe Inice and POF] which wil saan go through the validation process. ‘Note For scenarios where GR sno performed before noice “submission, Coupe will putes nvices into Penng Receipt totus. XL wil develop a custom too to check the inoies hate In Pending Receipt status and dispute back othe supple An ‘APLinteraton method wil be used to perform ths check ‘Technical details ofthis process can be ound in the Integration Requirement Document 0) Wa ‘way match Remit-To For XL al suppliers willbe 3= Way match ‘Only one Rerit-o" information per suppl present onthe Supplier master in ERP. Coup to Send out an approved voce ERP and Remit-To information wil be defaulted in ERP WA NA ‘edisdaimer "Ris mandator for supple to read up tothe end and agree {proven by tick mark bos) to xL-disaimer for al ferent Invoicing channels (SP/eXML/CSV), otherwise ivcice cannot be submited Wk BUSINESS PROCESS DOCUMENT | AIATA-COUPA PROCUREMENT SOLUTIONS. p7.1 PO Backed Invoicing ‘The proces low above explains the PO Backed invoice proces in Coup. This section covers the process of Stock PO to invoicing in Coupa PO Backed invoice Key Biseussion Area ‘Creation of PO] 1. ForPO Barked Invoicing aX, the woes are entered by 73.1 Sacked invong | Supple. 72 m4 745 736 2 Based on Xs pace al suppers wil best for Way [N/A “Matching with tolerances configured i there are an. Note: For ony tolerance breach invole wil be automaticaly dlsputed back ote suppl. ‘When the iveice bapproved wile sent ERPTor | 79 payments vie O12Pay interface 7.30 Faktur Paki ther sa Fakiur Pla validation fled, alto Paak tol wil | NA Validation tsps, BUSINESS PROCESS DOCUMENT | AKATA.COUPA FROCUREMENT SOLUTIONS. #aktur Poa] Falta Pajak Vaidaton details wil be provided ina separate Valgate ‘document ~FoturPojak Inteprtion document. 2) ‘Wote: GR bosed IV enable, nee tobe elscussed and decided rng integration session Tolerance Breach | there is tolerance bretch onthe vice, Kwilbe daputed | 72.7a = ‘Auto. dspute | automatcaly and invoice willbe duecty sent backtothe | 718 ‘conditions supple. Conditions for auto-dgpute ate a fllons 1 voice date: dackdated invize snot allowed AL Currency: neice etrency should mateh PO etrency Quantity: voice quant should match PO quantty |v. Pree lnvoice pie should match PO price 7.2 Non-PO Backed Invoicing (Supplier Created) ‘owe 12 Non P0 Bocad Ina (Supt Grae aocess ow “Te proces flow above explain the Non-PO Backed Invoice (Supe Created) proces in Coupe, This section covers the press of Supplier creating an voice in Coupa Supple Prtal (C3) Non 0 Backedinvoce (Supplier created) ~Kay Discusion Area BUSINESS PROCESS DOCUMENT | AIATA-COUPA PROCUREMENT SOLUTIONS: avoice willbe received by he Requester and Requester wil | 724 omplete the invoice by filing up the fel incuting 725 ommodity cade, ling information, WHT code, PH, PN | 72.6 ‘nd Requester Unt and submit the invoice for approval. 3. Gee the aves approve, willbe interfaced to ERP Yor | NJ Payment “Approval law | Approval flaw fr Na PO Backed voce Guppler Created) | 72.78 t Faltur Pook 2% i Budget Owner 727 i. xUTaxTeam 7278 U8 udget creck 7278 LOR Approval-FortNon-0 invoices isbased on costcenter | 7276 and not Requester's Unt 72m XLAP Group fi. Budget Check APL Not: Te Budget Oune wl be aed tothe approval ow ate ‘AP grup tho Budget Chock API cal als. Once budgets made ‘value Budget Onn wl approve he vos, 7.3 Non-PO Backed Invoicing (Requester Created) Fig 1: Hon.P0 Baca Iain (Rogar Crowe} oes ow ‘The proces ow above explains the Nor-PO Backed voice (Requester Created) procesn Coup. This section covers the process of Requester manvalcretingan voice in Coupe BUSINESS PROCESS DOCUMENT | AXIATACOUPA FROCUREMENT SOLUTIONS. mA— Non-?0 Backed invoice (Requester created) ~Key Discussion Area TL Requester wil create the invoice from the paperinvake [73.2 | Requester have to input athe feldeincudngs 733 | + commodity code + bling formation + wnt code PPM + Requester Unt. ‘tachment for |. Requester alo have to aach the FaurPajakand abit the | 73.4 ‘Approval Invoiee for approval 2 Once the inves s approved itwilbe nteTaced ERP Tor | 737 Payment 738 “Approval Fow | Approval ow for Non PO Backed voice Requester Crested)s; | 73.68 Ie alte Pak 738 fi Budget Owner 736 fi. xe Tax Team 7386 iw, Budget Check 73.8 LOA Approval For Non 90 involeesis based on cost-center | 73.6 and not Requester’ Unt. 738 1. XLAP Group vi, Budget check AP Tolerance cheeks | Tolerance ches wil ao be performed onthe mvoie upon ite | NTR submission ‘Not: there are no tolerance breach, Invoice willbe outed for Budget check (OA and internal approval Fail on Approval | 1. The Budget Owner willbe ded tothe approval ow aRer | 73.58 Flow ‘the AP groupif he Budget Check AP call fas Z. Gnee budgets made avaliable Budget Owner will approve We | 73.68 Invoke. Gee the aves approved, willbelntefaced a ERP Yor | 737 Payment 738 BUSINESS PROCESS DOCUMENT | AXIATA-COUPA FROCUREMENT SOLUTIONS. a7.4 Invoicing Approvals, Invoing approvals Key Discussion Area = Sn OnE PO-backed | For XL process, management hierarchy approvals ae not bei | N/A Invoicing approval | used. The flowing types of approvals are required on the PD Backed invoice nthe pen oder “FP Validation Check: Remote Approver KL custom program) approves the Invoice 35 ax validation passed, | Non-?0 backed |For Won-PO Backed invoice budget owner wil be addedto the PO: | N/A Invoicing approval | Backed inoice approval low a fst approver. Approval flow has been detaleain the proces flow igure 12 & 13), ‘ditional The foloing approval chins wl be crete for approval chains | 1) Approval Chains fortoleance breaches (For PO backed and Non PO backed vies) 2) 08 approval hans for any Non PO backed Invoices 3) FaieurPajakremote approver Wa 7.5 Invoicing Tolerances Invoicing tolerance ~Key Discusion Area ‘Management ] ForKL no Management Herarchy approvals are appleable Hierarchy approvals ‘Approval requiredif percent variance on ine 0.00% 0.00% vans ‘Approval requiredit dolar variance on ine $0.00 30.00 nit pie ‘Approval required it percent varance online 0.00% 0.00% nk price BUSINESS PROCESS DOCUMENT | AXIATA.COUPA PROCUREMENT SOLUTIONS. aApproval required dolar variance on invoice ‘ine amour Approval required percent variance on Invoice ine amount ie 3000 $0.00 0.00% 30.00 30.00 30.00 $0.00 $0.00 30.00 $0.00 30.00 ‘Approval requires it ‘shiping greater than ‘Approval required it ‘shipping as a percentage ofthe total invoice is sreater than $000 0.0% 00% BUSINESS PROCESS DOCUMENT | AXIATA-COUPA PROCUREMENT SOLUTIONS. a‘Approvals require it handling charge asa percentage ofthe total Invoice ieeater than 0.00% 0.00% ‘Approvals required any misclineous $0.00 $0.00 ‘charges are greater than ‘Approvals eauredt any miscellaneous charges asa percentage 0.00% 000% ofthe total invoice ie eater than | ‘Approvals required t total taxes are greater 3000 $0.00 than ‘Approvals required t total taxes a2 percentage ofthe total Invoice is greater han ‘Approval required ftne tax compare to tax engin calulaton greater than 00% 2.00% ‘Approval require it Total tax compared to ‘tax engine calculations sreater than 0.00% 0.00% “Approval required if Yes!No eso Invoice tine Unit of [BUSINESS PROCESS DOCUMENT | AKIATA.GOUPA PROCUREMENT SOLUTIONS. aMeasure doesnot match PO ine Unit of Measure ‘Approval required it invoice Currency does esto YesiNo ‘ot mateh PO Curency Approval required it Invoice Date is backdated ee xavs xoays calendar days ‘Approval requirdit | Invoice tne unit price a eal ‘compared to catalog unit prices greater than (3) Approval required it Invoice line unt pice ‘compared to Catalog unit rice greater than (3) wa 0.00% 7.6 Invoicing - User Roles There area number of roles with the invoicing area for use ina Coupa plementation: ‘Accounts Payable: This ole ads some ations administrative ight relating to purchase orders and Invoices Uses with This role are abe to view al purchase orders and invoice in the system. Recounts Payable Users can eter invoice manaly (Hardcopy) that may hve ome om asoure outside of Covra ‘Accounting Supervisor: This leis sitar tothe Accounts Payable role, butt incodesentra ‘administrative rights. Aecourting Supersors as have accesso fitandal setup, ineucng stop of secounts invoice tolerances, budgets, exchange rats, tax codes, and payment terms ‘recounting Supervisors 2 system roe name, for XL context its equvalent as Cental anda Opertions For XL wllbe AP Team and members For XL iowillbe esd and Und BUSINESS PROCESS DOCUMENT | AXIATA.COUPA PROCUREMENT SOLUTIONS w8.0 Milestone PO fy ee a Be Pleas refer tothe figure above regarding the Milestone PO solution. t was decid that Robo Process Automation (RPA) solution wil be usedto support the AP team in veriyng Milestone PO invoice In oupa as part othe Milestone PO solution. ‘creation of] 1. The Buyer wllrete a miestone contract afer a sourcing evert has Been approved contact, snd awarded 2. Buyer wil need toad the awarded item tothe‘ Contract” 3. While creating a contract in Coupa, meso he infomation willbe populated tom ‘the sourcing event direct | Buyer i need to provide milestone information inthe Contet TAC’ ld which ilinade all the milestone information es. {0u1:0P120.006(09|:1m2:09]20.on3(Gnc]1us:00]20% (ACCHMA-GRISON (Gn){os:cn}20% (en) ‘5. Buyer wil nod to check the Milestone fag inthe Contract the contrac has milestone payment ‘reaton of [1 Fora milestone Purchase Requltion, Requester wil ate requisition ug he Requisition Iiestone Contract 2, Requester wil sec the ‘Mlestone Contract ithe contract eld on the PR page, ‘This wil populate the maestone nfoemation from te ‘Contract TAC ito PR | Mileston a Yes/No) on the PR willbe avaabe a the ne item level. Ts Mag wl etal from the contrat and requester wll not be abet change the og 44, Once the milestone PRs approved i willbe converted into PO, PO number wit ‘then be generated BUSINESS PROCESS DOCUMENT | AXLATACOUPA PROCUREMENT SOLUTIONS a= “The Contact TEC with estan information wil be copied orto the PO and wil be viable tothe supper, Receiving Tecevng for Milestone PO willbe prformedin SAP Invoicing 8 ‘Any further details on APA senavios, Role & Aecountbity wl be provided inthe RPA SOW agreement between falta Group Bh, ond KPMG Management & Risk Consulting ‘Sin. “Supplier creates voices via diferent voicing channels (CP /eCML/CS0 and Indeata milton information athe vice header lve. Nlestone Suppers ar eto 2-way match n Coupa sytem Whe the inie i received fromthe 2-vay match supplier, iwoice wil be routed tothe RPA Ifthe milestone fag i ot checked fora 2-way match supple, 2A wl perform 3 manual Sway mateh on theivoie Ifthe miestne fai checked onthe nvle, RPA wil performthe milestone check ‘onthe invoice a per the XL defined scenaioe PA wil Approve Dispute the invoice based onthe scenario chick and sent to the nest epprover Before aproving the invoice, RPA wil slat the mlstone deter rom the drop down (e8 OP/GR/GAC) at ivoiceline lve Payment wil be made to Supplier via SAP 9.0 User Roles & Restrictions 9.1 Global Roles ‘coupa has a number of standard roles avaable to customers. These areal detaledin Slob Roles tab ‘and ince the End User, min and Buyer Some of hose roles wil be used in specie Coupa modules but he Admin role will ned tobe set ata Global ve ‘Ramin | AllCoups amin or. Tatas] Sourcing Management Ten wilbeguan Eat as Approve” ole Coup ‘Approver Dashboard | Sourcing Management, Fance/AP tars wil have dashboard acess ‘cess | see dashboard reports and benchmarking. Key Inventory Role ale “Central | Below the Tat of ures with Granted Canal Recehing acon aaa Receiving | + For Sin Card: Seno access | + For Other Materia: Yunian [SUSINESS PROCESS DOCUMENT | AXATA.COUPA PROCUREMENT SOLUTIONS. a9.2 Account Security Settings ‘Thisseton adresses how you wil setup the Security Settings in your Coupa instance. tis possibleto ‘set-up Coupa has a number of eption avaiable to customers around access dependingon ther security requirements. The below questions should help us determine the setup that you requ, — Data vist by Specie soup or "ML Content Group tobe assigned to a XL users, Default Bling information ‘Below the it of HL dead biling information Gl willbe defaulted from Commodity + Aecount Category and Recut wil be defaulted frm user profile Eg Account Category Cost Center) ezount-TECH200 10.0 Appendix ‘This section captures the requirements that were identified during the design workshops. Requirement raceabilly mati (RTM) is altached inthe section. RTM can alsa be located in MS team (8) & 41 RTM: - Sourcing to Contact"? @: ram a2019 41 RIM: -Purchase Requisition to Receipt "#2488. 2 AMM: invoicing ER BUSINESS PROCESS DOCUMENT | AXIATA.COUPA FROCUREMENT SOLUTIONS, ea 3: -tnepration =o. ton End of Document: BUSINESS PROCESS DOCUMENT | AXIATA.COUPA FROCUREMENT SOLUTIONS. a