YouTube2Text

Accenture Procure to Pay (P2P) Interview Questions & Answers — Transcript

by CandiMentor · 2,311 words · 421 segments · language en · Watch on YouTube

Full transcript

  1. 0:00Preparing for a procure to pay P2P at
  2. 0:02Accenture interview? You've reached
  3. 0:04Candy Mentor and this video is for you.
  4. 0:07We'll walk through 20 key questions
  5. 0:09you're likely to face. For each
  6. 0:11question, you'll see a sample answer
  7. 0:13followed by the key points to cover.
  8. 0:15Subscribe, like, and share, and drop a
  9. 0:17topic request in the comments. Question
  10. 0:20one, what is procure to pay and why is
  11. 0:23it important for a business?
  12. 0:25Procure to pay is the endto-end process
  13. 0:28from identifying a purchasing need to
  14. 0:30paying the supplier. It usually starts
  15. 0:33with a purchase requisition, moves to
  16. 0:35purchase order creation, goods or
  17. 0:37service receipt, invoice matching,
  18. 0:39approval, and finally payment. In an
  19. 0:42Accenture style delivery environment, I
  20. 0:45would stress standardization,
  21. 0:46compliance, and measurable SLAs's
  22. 0:49because P2P directly affects working
  23. 0:51capital, supplier relationships, audit
  24. 0:54readiness, and the accuracy of financial
  25. 0:56reporting. While answering, focus on the
  26. 0:59full process flow, business impact,
  27. 1:02compliance angle, supplier relationship
  28. 1:04impact, and why Accenture emphasizes
  29. 1:06standardized, measurable P2P operations
  30. 1:09for global clients. Question two, walk
  31. 1:12me through the complete P2P cycle. I
  32. 1:15would walk through it sequentially. A
  33. 1:17business user raises a purchase
  34. 1:19requisition which is approved based on
  35. 1:21authority limits and budget. Procurement
  36. 1:24converts it into a purchase order and
  37. 1:26sends it to the vendor. Once goods or
  38. 1:28services are received, the receipt is
  39. 1:30recorded. The vendor invoice is then
  40. 1:32captured and matched against the PO and
  41. 1:35receipt. If it matches, it is posted and
  42. 1:37paid through the payment run. Make sure
  43. 1:40to cover requisition, approval, PO
  44. 1:43creation, supplier fulfillment, goods
  45. 1:45receipt, invoice processing, matching,
  46. 1:48exception handling, payment run, and
  47. 1:50accounting entries in a clear sequence.
  48. 1:53Question three, what is the difference
  49. 1:55between a purchase requisition and a
  50. 1:57purchase order? A purchase requisition
  51. 2:00is an internal request to buy goods or
  52. 2:02services. A purchase order is the formal
  53. 2:05document sent to the supplier. The
  54. 2:08requisition captures the need, quantity,
  55. 2:10estimated price, cost center, and
  56. 2:12approvals. The PO creates the external
  57. 2:15commercial commitment including price,
  58. 2:18delivery terms, tax and vendor details.
  59. 2:21If the requisition is wrong, the PO and
  60. 2:24invoice matching can fail later. So,
  61. 2:26data quality at this stage is very
  62. 2:28important. In your answer, talk about
  63. 2:31internal versus external documents,
  64. 2:33approval requirements, commercial
  65. 2:35commitment, system flow, and how errors
  66. 2:37at requisition stage can affect
  67. 2:39downstream P2P processing.
  68. 2:42Question four, explain two-way match,
  69. 2:45three-way match, and four-way match in
  70. 2:47invoice processing. Two-way match
  71. 2:50compares the supplier invoice with the
  72. 2:52purchase order, mainly checking price
  73. 2:53and quantity. Three-way match adds the
  74. 2:55goods receipt, so the invoice must agree
  75. 2:57with both the purchase order and what
  76. 2:59was actually received. Four-way match
  77. 3:02includes an inspection or quality
  78. 3:03acceptance document, often used for
  79. 3:06regulated or quality sensitive items.
  80. 3:08Matching is a core P2P control because
  81. 3:10it prevents paying for incorrect
  82. 3:12quantities, wrong prices, undelivered
  83. 3:14goods, or rejected items. Be sure to
  84. 3:18mention what documents are compared when
  85. 3:20each match type is used, typical
  86. 3:22tolerances, and why matching is a key
  87. 3:25control against overpayment or incorrect
  88. 3:27payment.
  89. 3:29Question five, what would you do if an
  90. 3:32invoice fails three-way matching? First,
  91. 3:35I would identify whether the mismatch is
  92. 3:37price, quantity, tax, vendor, or receipt
  93. 3:40related. Then, I would check the PO,
  94. 3:42goods receipt, invoice image, and system
  95. 3:45tolerance limits. If goods are not
  96. 3:47receeded, I would follow up with the
  97. 3:49receiving team. If price differs, I
  98. 3:51would involve procurement or the buyer.
  99. 3:53I would not force post the invoice
  100. 3:55unless there is proper approval because
  101. 3:57bypassing controls creates audit and
  102. 3:59overpayment risk. While answering, focus
  103. 4:02on identifying the mismatch type,
  104. 4:05checking source documents, coordinating
  105. 4:07with procurement, receiving teams and
  106. 4:09vendors, using workflow tools, and
  107. 4:11avoiding manual bypass without approval.
  108. 4:14Question six, what are common reasons
  109. 4:17invoices go into exception and how do
  110. 4:19you reduce them? Common invoice
  111. 4:22exceptions include PO price mismatches,
  112. 4:25missing goods receipts, quantity
  113. 4:27differences, incorrect tax, invalid
  114. 4:29vendor details, duplicate invoice
  115. 4:31numbers, and missing approvals for
  116. 4:33non-PO invoices. To reduce them, I would
  117. 4:36analyze exception trends by vendor,
  118. 4:38buyer, and category. Then I would fix
  119. 4:41master data issues, train vendors on
  120. 4:43invoice requirements, improve PO
  121. 4:45discipline, and strengthen receipt
  122. 4:47follow-up. The goal is not just carrying
  123. 4:49exceptions, but reducing repeat causes.
  124. 4:53Make sure to cover PO mismatch, missing
  125. 4:55GR, duplicate invoices, incorrect vendor
  126. 4:58data, tax issues, coding errors, root
  127. 5:01cause analysis, vendor education, and
  128. 5:04process improvement metrics. Question
  129. 5:07seven, how do you identify and prevent
  130. 5:09duplicate payments in P2P? Duplicate
  131. 5:12payment prevention starts with clean
  132. 5:14vendor master data and strong invoice
  133. 5:17controls. The system should check
  134. 5:19invoice number, vendor amount, currency,
  135. 5:22invoice date, and sometimes bank
  136. 5:24account. I would also watch for
  137. 5:26variations like leading zeros, spaces,
  138. 5:29different invoice formats or duplicate
  139. 5:31vendors. Before payment runs, exception
  140. 5:34reports should be reviewed. After
  141. 5:36payment, analytics can identify
  142. 5:38suspicious patterns. Prevention matters
  143. 5:40because recovery is slower and can
  144. 5:42damage supplier trust. In your answer,
  145. 5:46discuss duplicate checks using vendor
  146. 5:48invoice number, amount, date, bank
  147. 5:51account, system validations, payment
  148. 5:53holds, vendor master controls, and post
  149. 5:56payment analytics. Question eight, what
  150. 5:59is vendor master data and why is it
  151. 6:01critical in P2P? Vendor master data is
  152. 6:04the central record containing supplier
  153. 6:06name, address, tax registration, payment
  154. 6:09terms, bank details, currency, contact
  155. 6:12information, and status. It drives how
  156. 6:15invoices are posted and payments are
  157. 6:17made. Poor master data can cause failed
  158. 6:19payments, duplicate vendors, tax errors,
  159. 6:22or even fraud. In a controlled P2P
  160. 6:25process, vendor creation and changes
  161. 6:27should be approved, documented, and
  162. 6:29segregated from invoice processing and
  163. 6:31payment execution. Be sure to mention
  164. 6:34vendor onboarding, tax details, payment
  165. 6:37terms, bank information, duplicate
  166. 6:39vendors, segregation of duties, approval
  167. 6:42controls, and how master data quality
  168. 6:44affects invoice and payment accuracy.
  169. 6:47Question nine, how would you handle a
  170. 6:50vendor complaining about delayed
  171. 6:52payment? I would first acknowledge the
  172. 6:55vendor professionally and ask for
  173. 6:57invoice number, PO number, amount, and
  174. 6:59date. Then I would check whether the
  175. 7:02invoice was received, posted, blocked,
  176. 7:04under approval or scheduled for payment.
  177. 7:07If it is blocked, I would identify the
  178. 7:09reason and coordinate with procurement,
  179. 7:12receiving or the requesttor. I would
  180. 7:14communicate the status clearly to the
  181. 7:16vendor and avoid promising payment
  182. 7:18unless it is confirmed in the system.
  183. 7:22While answering, focus on professional
  184. 7:25communication, checking invoice status,
  185. 7:27identifying blockers, validating payment
  186. 7:29terms, coordinating internally,
  187. 7:32documenting actions, and protecting both
  188. 7:34supplier relationship and process
  189. 7:36controls.
  190. 7:38Question 10. What is GRIR clearing and
  191. 7:42why does it matter? GRIR is a clearing
  192. 7:46account used when goods are received
  193. 7:48before the supplier invoice is posted or
  194. 7:50vice versa. When goods are received, the
  195. 7:54system credits GRIR and records
  196. 7:56inventory or expense. When the invoice
  197. 7:59is posted, GRIR is debited and the
  198. 8:02vendor liability is credited. Ideally,
  199. 8:05both sides clear. Open balances indicate
  200. 8:08missing invoices, missing receipts,
  201. 8:10quantity differences, or timing issues.
  202. 8:13So, regular aging and reconciliation are
  203. 8:16important for accurate liabilities.
  204. 8:18Make sure to explain the goods receipt,
  205. 8:20invoice receipt concept, temporary
  206. 8:23liability accounting, common open item
  207. 8:26causes, reconciliation, aging review,
  208. 8:29and impact on acrruels and financial
  209. 8:31statements. Question 11. What controls
  210. 8:34would you expect in a strong P2P
  211. 8:37process?
  212. 8:38A strong P2P process has controls at
  213. 8:41every stage. requisitions and POS meet
  214. 8:44approval based on spend limits. Vendor
  215. 8:47creation and bank changes should be
  216. 8:48independently reviewed. Invoices should
  217. 8:51go through matching, duplicate checks,
  218. 8:53tax validation, and approval workflows
  219. 8:55where required. Payment runs should be
  220. 8:58reviewed and authorized by someone
  221. 9:00separate from invoice processing. Good
  222. 9:02controls also include audit trails,
  223. 9:04tolerance limits, access restrictions,
  224. 9:07and exception dashboards for management
  225. 9:09review. In your answer, cover approval
  226. 9:12matrices, segregation of duties,
  227. 9:15three-way match, vendor master
  228. 9:17approvals, duplicate checks, payment
  229. 9:19authorization, audit trails, tolerance
  230. 9:21limits, and exception monitoring.
  231. 9:24Question 12. What is the difference
  232. 9:26between PO invoices and non-PO invoices?
  233. 9:29A PO invoice is linked to an approved
  234. 9:32purchase order, so it can be matched
  235. 9:34against agreed price, quantity, and
  236. 9:36receipt. A non-PO invoice has no
  237. 9:39purchase order. So, it normally requires
  238. 9:41manual coding, cost center allocation,
  239. 9:43and business approval before posting.
  240. 9:46Non-PO invoices are common for
  241. 9:48utilities, legal fees, or one-time
  242. 9:50services, but they carry higher control
  243. 9:52risk. That is why companies try to
  244. 9:54increase PO compliance and reduce
  245. 9:56unnecessary non-PO spend.
  246. 10:00Be sure to distinguish procurement
  247. 10:02backed purchases from invoices without
  248. 10:04purchase orders. Explain approval risk,
  249. 10:06coding requirements, matching
  250. 10:08differences, and why companies push
  251. 10:10higher PO compliance. Question 13. How
  252. 10:13do payment terms affect working capital
  253. 10:16in P2P? Payment terms determine when
  254. 10:19cash leaves the company, so they
  255. 10:20directly affect working capital and days
  256. 10:22payable outstanding. Longer terms
  257. 10:25preserve cash, but they must be agreed
  258. 10:27with suppliers and managed ethically.
  259. 10:29Shorter terms may be used to capture
  260. 10:31early payment discounts or support
  261. 10:33strategic vendors. In P2P, the key is
  262. 10:36paying neither too early nor too late.
  263. 10:38Accurate invoice processing helps the
  264. 10:41company optimize cash while maintaining
  265. 10:43supplier trust. While answering, focus
  266. 10:46on cash flow timing, DPO, supplier
  267. 10:49negotiations, early payment discounts,
  268. 10:52late payment penalties, compliance with
  269. 10:54agreed terms, and balancing savings with
  270. 10:56supplier relationships.
  271. 10:58Question 14. What KPIs would you track
  272. 11:00in a P2P process?
  273. 11:03I would track invoice cycle time,
  274. 11:05percentage of invoices processed within
  275. 11:07SLA, first pass match rate, exception
  276. 11:10rate, duplicate payment rate, on-time
  277. 11:13payment percentage, PO compliance,
  278. 11:15vendor query volume, and touchless
  279. 11:17processing rate for finance impact. I
  280. 11:20would also review discount capture and
  281. 11:22aged GRI balances. These KPIs show
  282. 11:26whether the process is fast, controlled,
  283. 11:28and scalable. At Accenture, I would
  284. 11:30expect a strong focus on dashboards,
  285. 11:32root cause analysis, and continuous
  286. 11:35improvement. Make sure to mention
  287. 11:37operational efficiency, quality,
  288. 11:39compliance, and cash metrics, including
  289. 11:42invoice cycle time, first pass yield,
  290. 11:44exception rate, duplicate payments,
  291. 11:47on-time payment, and touchless
  292. 11:48processing. Question 15. How would you
  293. 11:52prioritize work if there are hundreds of
  294. 11:54invoices pending? I would prioritize
  295. 11:57using a combination of SLA due dates,
  296. 11:59payment terms, invoice value, supplier
  297. 12:02criticality, and discount opportunities.
  298. 12:05Invoices close to due date or affecting
  299. 12:07key suppliers would come first. I would
  300. 12:10also separate clean invoices from
  301. 12:12exceptions because clean items can be
  302. 12:14processed quickly while blocked items
  303. 12:16need follow-up. For high volume
  304. 12:18backlogs, I would use aging reports,
  305. 12:21assign ownership, track daily clearance,
  306. 12:23and escalate recurring bottlenecks
  307. 12:25early. In your answer, discuss SLA
  308. 12:28prioritization, payment due dates,
  309. 12:31discount opportunities, blocked
  310. 12:33invoices, critical suppliers, aging
  311. 12:35buckets, high value items, and clear
  312. 12:38communication with stakeholders.
  313. 12:40Question 16. What accounting entries are
  314. 12:43typically recorded in the P2P cycle? For
  315. 12:46goods, when the receipt is recorded,
  316. 12:48inventory or expense is debited and GRIR
  317. 12:52is credited. When the invoice is posted,
  318. 12:54GRIR is debited and the vendor payable
  319. 12:57is credited. When payment is made,
  320. 12:59vendor payable is debited and bank is
  321. 13:02credited. For non-PO expense invoices,
  322. 13:04the expense may be debited directly and
  323. 13:07vendor payable credited. The exact
  324. 13:09entries depend on the ERP setup, taxes,
  325. 13:12and whether receipt-based accounting is
  326. 13:13used. Be sure to cover receipt
  327. 13:16accounting, invoice posting, vendor
  328. 13:19liability, expense or inventory
  329. 13:21recognition, GRIR clearing, payment
  330. 13:24entry, and how timing differs between
  331. 13:26goods receipt and invoice receipt.
  332. 13:29Question 17. How do you ensure
  333. 13:31compliance with tax requirements while
  334. 13:33processing invoices? I would ensure the
  335. 13:36invoice has the required legal details
  336. 13:39such as supplier tax registration,
  337. 13:41invoice number, date, taxable value, tax
  338. 13:44amount, and correct entity information.
  339. 13:47Then I would verify that the correct tax
  340. 13:49code is applied based on vendor,
  341. 13:51location, goods or services and local
  342. 13:54rules. If withholding tax applies, it
  343. 13:56must be calculated correctly. Any
  344. 13:59unclear tax treatment should be
  345. 14:00escalated rather than guessed because
  346. 14:03tax errors can create compliance
  347. 14:04exposure. While answering, focus on
  348. 14:08validating tax registration, tax codes,
  349. 14:10invoice format, place of supply,
  350. 14:13withholding tax if applicable, ERP
  351. 14:16controls, escalation, and audit
  352. 14:18documentation.
  353. 14:20Question 18. What experience or
  354. 14:22understanding do you have of ERP tools
  355. 14:24used in P2P? I understand that P2P is
  356. 14:28usually managed through ERP systems such
  357. 14:30as SAP, Oracle or Koopa supported by
  358. 14:33invoice workflow and OCR tools. The ERP
  359. 14:36maintains vendors, POS, receipts,
  360. 14:38invoices, approvals and payment data. My
  361. 14:41focus would be on using the system
  362. 14:42accurately, checking source documents,
  363. 14:44reading status codes, clearing
  364. 14:46exceptions, and generating reports. Even
  365. 14:49if the client platform differs, the core
  366. 14:51process logic remains the same, so I can
  367. 14:53adapt quickly.
  368. 14:55Make sure to mention SAP, Oracle or
  369. 14:59similar systems if relevant, invoice
  370. 15:01workflow tools, OCR reporting,
  371. 15:04transaction codes conceptually, data
  372. 15:06accuracy and adaptability to client
  373. 15:08specific platforms. Question 19. Tell me
  374. 15:12about a P2P process improvement you
  375. 15:15would suggest to a client. I would start
  376. 15:18by reviewing data to identify the
  377. 15:20biggest pain point such as high
  378. 15:22exception rates or long invoice cycle
  379. 15:24times. If many invoices fail because of
  380. 15:27missing PO numbers, I would recommend
  381. 15:29vendor communication, invoice submission
  382. 15:31rules, and system validation at intake.
  383. 15:34If manual processing is high, OCR and
  384. 15:37workflow automation can help. The
  385. 15:39improvement should be measured through
  386. 15:41KPIs like first pass match rate, cycle
  387. 15:44time, and reduced vendor queries. In
  388. 15:46your answer, talk about diagnosing pain
  389. 15:49points, using data, increasing
  390. 15:51automation, reducing exceptions,
  391. 15:53improving vendor compliance,
  392. 15:54standardizing processes, and measuring
  393. 15:57benefits through KPIs.
  394. 16:01Question 20. Why do you want to work in
  395. 16:04P2P at Accenture? I am interested in P2P
  396. 16:08because it combines finance, controls,
  397. 16:11operations, and client service in a
  398. 16:13practical way. At Accenture, the
  399. 16:15attraction is the scale. Working with
  400. 16:18global clients, standardized processes,
  401. 16:20ERP tools, automation, and performance
  402. 16:23metrics. I would get exposure to real
  403. 16:26business issues like supplier delays,
  404. 16:28working capital, and compliance. I also
  405. 16:30like that P2P rewards attention to
  406. 16:33detail, ownership, and continuous
  407. 16:35improvement, which match how I work.
  408. 16:38Be sure to connect your motivation to
  409. 16:40finance operations, client service,
  410. 16:43process discipline, technology,
  411. 16:45continuous improvement, global delivery
  412. 16:47environment, learning opportunity, and
  413. 16:49Accentur's consulting and operations
  414. 16:51scale. If you are still with us,
  415. 16:54congratulations. You are much ahead of
  416. 16:56the rest and serious about preparing for
  417. 16:58your interview. We hope we were able to
  418. 17:00add value to your preparation and create
  419. 17:03some helpful content. Do not forget to
  420. 17:05like and share this video. Your small
  421. 17:08act can do great things for us.

About this transcript

This page contains the full transcript of Accenture Procure to Pay (P2P) Interview Questions & Answers by CandiMentor , generated from the public captions YouTube serves with the video. The transcript has 2,311 words across 421 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.