Accenture Procure to Pay (P2P) Interview Questions & Answers — Transcript
Full transcript
- 0:00Preparing for a procure to pay P2P at
- 0:02Accenture interview? You've reached
- 0:04Candy Mentor and this video is for you.
- 0:07We'll walk through 20 key questions
- 0:09you're likely to face. For each
- 0:11question, you'll see a sample answer
- 0:13followed by the key points to cover.
- 0:15Subscribe, like, and share, and drop a
- 0:17topic request in the comments. Question
- 0:20one, what is procure to pay and why is
- 0:23it important for a business?
- 0:25Procure to pay is the endto-end process
- 0:28from identifying a purchasing need to
- 0:30paying the supplier. It usually starts
- 0:33with a purchase requisition, moves to
- 0:35purchase order creation, goods or
- 0:37service receipt, invoice matching,
- 0:39approval, and finally payment. In an
- 0:42Accenture style delivery environment, I
- 0:45would stress standardization,
- 0:46compliance, and measurable SLAs's
- 0:49because P2P directly affects working
- 0:51capital, supplier relationships, audit
- 0:54readiness, and the accuracy of financial
- 0:56reporting. While answering, focus on the
- 0:59full process flow, business impact,
- 1:02compliance angle, supplier relationship
- 1:04impact, and why Accenture emphasizes
- 1:06standardized, measurable P2P operations
- 1:09for global clients. Question two, walk
- 1:12me through the complete P2P cycle. I
- 1:15would walk through it sequentially. A
- 1:17business user raises a purchase
- 1:19requisition which is approved based on
- 1:21authority limits and budget. Procurement
- 1:24converts it into a purchase order and
- 1:26sends it to the vendor. Once goods or
- 1:28services are received, the receipt is
- 1:30recorded. The vendor invoice is then
- 1:32captured and matched against the PO and
- 1:35receipt. If it matches, it is posted and
- 1:37paid through the payment run. Make sure
- 1:40to cover requisition, approval, PO
- 1:43creation, supplier fulfillment, goods
- 1:45receipt, invoice processing, matching,
- 1:48exception handling, payment run, and
- 1:50accounting entries in a clear sequence.
- 1:53Question three, what is the difference
- 1:55between a purchase requisition and a
- 1:57purchase order? A purchase requisition
- 2:00is an internal request to buy goods or
- 2:02services. A purchase order is the formal
- 2:05document sent to the supplier. The
- 2:08requisition captures the need, quantity,
- 2:10estimated price, cost center, and
- 2:12approvals. The PO creates the external
- 2:15commercial commitment including price,
- 2:18delivery terms, tax and vendor details.
- 2:21If the requisition is wrong, the PO and
- 2:24invoice matching can fail later. So,
- 2:26data quality at this stage is very
- 2:28important. In your answer, talk about
- 2:31internal versus external documents,
- 2:33approval requirements, commercial
- 2:35commitment, system flow, and how errors
- 2:37at requisition stage can affect
- 2:39downstream P2P processing.
- 2:42Question four, explain two-way match,
- 2:45three-way match, and four-way match in
- 2:47invoice processing. Two-way match
- 2:50compares the supplier invoice with the
- 2:52purchase order, mainly checking price
- 2:53and quantity. Three-way match adds the
- 2:55goods receipt, so the invoice must agree
- 2:57with both the purchase order and what
- 2:59was actually received. Four-way match
- 3:02includes an inspection or quality
- 3:03acceptance document, often used for
- 3:06regulated or quality sensitive items.
- 3:08Matching is a core P2P control because
- 3:10it prevents paying for incorrect
- 3:12quantities, wrong prices, undelivered
- 3:14goods, or rejected items. Be sure to
- 3:18mention what documents are compared when
- 3:20each match type is used, typical
- 3:22tolerances, and why matching is a key
- 3:25control against overpayment or incorrect
- 3:27payment.
- 3:29Question five, what would you do if an
- 3:32invoice fails three-way matching? First,
- 3:35I would identify whether the mismatch is
- 3:37price, quantity, tax, vendor, or receipt
- 3:40related. Then, I would check the PO,
- 3:42goods receipt, invoice image, and system
- 3:45tolerance limits. If goods are not
- 3:47receeded, I would follow up with the
- 3:49receiving team. If price differs, I
- 3:51would involve procurement or the buyer.
- 3:53I would not force post the invoice
- 3:55unless there is proper approval because
- 3:57bypassing controls creates audit and
- 3:59overpayment risk. While answering, focus
- 4:02on identifying the mismatch type,
- 4:05checking source documents, coordinating
- 4:07with procurement, receiving teams and
- 4:09vendors, using workflow tools, and
- 4:11avoiding manual bypass without approval.
- 4:14Question six, what are common reasons
- 4:17invoices go into exception and how do
- 4:19you reduce them? Common invoice
- 4:22exceptions include PO price mismatches,
- 4:25missing goods receipts, quantity
- 4:27differences, incorrect tax, invalid
- 4:29vendor details, duplicate invoice
- 4:31numbers, and missing approvals for
- 4:33non-PO invoices. To reduce them, I would
- 4:36analyze exception trends by vendor,
- 4:38buyer, and category. Then I would fix
- 4:41master data issues, train vendors on
- 4:43invoice requirements, improve PO
- 4:45discipline, and strengthen receipt
- 4:47follow-up. The goal is not just carrying
- 4:49exceptions, but reducing repeat causes.
- 4:53Make sure to cover PO mismatch, missing
- 4:55GR, duplicate invoices, incorrect vendor
- 4:58data, tax issues, coding errors, root
- 5:01cause analysis, vendor education, and
- 5:04process improvement metrics. Question
- 5:07seven, how do you identify and prevent
- 5:09duplicate payments in P2P? Duplicate
- 5:12payment prevention starts with clean
- 5:14vendor master data and strong invoice
- 5:17controls. The system should check
- 5:19invoice number, vendor amount, currency,
- 5:22invoice date, and sometimes bank
- 5:24account. I would also watch for
- 5:26variations like leading zeros, spaces,
- 5:29different invoice formats or duplicate
- 5:31vendors. Before payment runs, exception
- 5:34reports should be reviewed. After
- 5:36payment, analytics can identify
- 5:38suspicious patterns. Prevention matters
- 5:40because recovery is slower and can
- 5:42damage supplier trust. In your answer,
- 5:46discuss duplicate checks using vendor
- 5:48invoice number, amount, date, bank
- 5:51account, system validations, payment
- 5:53holds, vendor master controls, and post
- 5:56payment analytics. Question eight, what
- 5:59is vendor master data and why is it
- 6:01critical in P2P? Vendor master data is
- 6:04the central record containing supplier
- 6:06name, address, tax registration, payment
- 6:09terms, bank details, currency, contact
- 6:12information, and status. It drives how
- 6:15invoices are posted and payments are
- 6:17made. Poor master data can cause failed
- 6:19payments, duplicate vendors, tax errors,
- 6:22or even fraud. In a controlled P2P
- 6:25process, vendor creation and changes
- 6:27should be approved, documented, and
- 6:29segregated from invoice processing and
- 6:31payment execution. Be sure to mention
- 6:34vendor onboarding, tax details, payment
- 6:37terms, bank information, duplicate
- 6:39vendors, segregation of duties, approval
- 6:42controls, and how master data quality
- 6:44affects invoice and payment accuracy.
- 6:47Question nine, how would you handle a
- 6:50vendor complaining about delayed
- 6:52payment? I would first acknowledge the
- 6:55vendor professionally and ask for
- 6:57invoice number, PO number, amount, and
- 6:59date. Then I would check whether the
- 7:02invoice was received, posted, blocked,
- 7:04under approval or scheduled for payment.
- 7:07If it is blocked, I would identify the
- 7:09reason and coordinate with procurement,
- 7:12receiving or the requesttor. I would
- 7:14communicate the status clearly to the
- 7:16vendor and avoid promising payment
- 7:18unless it is confirmed in the system.
- 7:22While answering, focus on professional
- 7:25communication, checking invoice status,
- 7:27identifying blockers, validating payment
- 7:29terms, coordinating internally,
- 7:32documenting actions, and protecting both
- 7:34supplier relationship and process
- 7:36controls.
- 7:38Question 10. What is GRIR clearing and
- 7:42why does it matter? GRIR is a clearing
- 7:46account used when goods are received
- 7:48before the supplier invoice is posted or
- 7:50vice versa. When goods are received, the
- 7:54system credits GRIR and records
- 7:56inventory or expense. When the invoice
- 7:59is posted, GRIR is debited and the
- 8:02vendor liability is credited. Ideally,
- 8:05both sides clear. Open balances indicate
- 8:08missing invoices, missing receipts,
- 8:10quantity differences, or timing issues.
- 8:13So, regular aging and reconciliation are
- 8:16important for accurate liabilities.
- 8:18Make sure to explain the goods receipt,
- 8:20invoice receipt concept, temporary
- 8:23liability accounting, common open item
- 8:26causes, reconciliation, aging review,
- 8:29and impact on acrruels and financial
- 8:31statements. Question 11. What controls
- 8:34would you expect in a strong P2P
- 8:37process?
- 8:38A strong P2P process has controls at
- 8:41every stage. requisitions and POS meet
- 8:44approval based on spend limits. Vendor
- 8:47creation and bank changes should be
- 8:48independently reviewed. Invoices should
- 8:51go through matching, duplicate checks,
- 8:53tax validation, and approval workflows
- 8:55where required. Payment runs should be
- 8:58reviewed and authorized by someone
- 9:00separate from invoice processing. Good
- 9:02controls also include audit trails,
- 9:04tolerance limits, access restrictions,
- 9:07and exception dashboards for management
- 9:09review. In your answer, cover approval
- 9:12matrices, segregation of duties,
- 9:15three-way match, vendor master
- 9:17approvals, duplicate checks, payment
- 9:19authorization, audit trails, tolerance
- 9:21limits, and exception monitoring.
- 9:24Question 12. What is the difference
- 9:26between PO invoices and non-PO invoices?
- 9:29A PO invoice is linked to an approved
- 9:32purchase order, so it can be matched
- 9:34against agreed price, quantity, and
- 9:36receipt. A non-PO invoice has no
- 9:39purchase order. So, it normally requires
- 9:41manual coding, cost center allocation,
- 9:43and business approval before posting.
- 9:46Non-PO invoices are common for
- 9:48utilities, legal fees, or one-time
- 9:50services, but they carry higher control
- 9:52risk. That is why companies try to
- 9:54increase PO compliance and reduce
- 9:56unnecessary non-PO spend.
- 10:00Be sure to distinguish procurement
- 10:02backed purchases from invoices without
- 10:04purchase orders. Explain approval risk,
- 10:06coding requirements, matching
- 10:08differences, and why companies push
- 10:10higher PO compliance. Question 13. How
- 10:13do payment terms affect working capital
- 10:16in P2P? Payment terms determine when
- 10:19cash leaves the company, so they
- 10:20directly affect working capital and days
- 10:22payable outstanding. Longer terms
- 10:25preserve cash, but they must be agreed
- 10:27with suppliers and managed ethically.
- 10:29Shorter terms may be used to capture
- 10:31early payment discounts or support
- 10:33strategic vendors. In P2P, the key is
- 10:36paying neither too early nor too late.
- 10:38Accurate invoice processing helps the
- 10:41company optimize cash while maintaining
- 10:43supplier trust. While answering, focus
- 10:46on cash flow timing, DPO, supplier
- 10:49negotiations, early payment discounts,
- 10:52late payment penalties, compliance with
- 10:54agreed terms, and balancing savings with
- 10:56supplier relationships.
- 10:58Question 14. What KPIs would you track
- 11:00in a P2P process?
- 11:03I would track invoice cycle time,
- 11:05percentage of invoices processed within
- 11:07SLA, first pass match rate, exception
- 11:10rate, duplicate payment rate, on-time
- 11:13payment percentage, PO compliance,
- 11:15vendor query volume, and touchless
- 11:17processing rate for finance impact. I
- 11:20would also review discount capture and
- 11:22aged GRI balances. These KPIs show
- 11:26whether the process is fast, controlled,
- 11:28and scalable. At Accenture, I would
- 11:30expect a strong focus on dashboards,
- 11:32root cause analysis, and continuous
- 11:35improvement. Make sure to mention
- 11:37operational efficiency, quality,
- 11:39compliance, and cash metrics, including
- 11:42invoice cycle time, first pass yield,
- 11:44exception rate, duplicate payments,
- 11:47on-time payment, and touchless
- 11:48processing. Question 15. How would you
- 11:52prioritize work if there are hundreds of
- 11:54invoices pending? I would prioritize
- 11:57using a combination of SLA due dates,
- 11:59payment terms, invoice value, supplier
- 12:02criticality, and discount opportunities.
- 12:05Invoices close to due date or affecting
- 12:07key suppliers would come first. I would
- 12:10also separate clean invoices from
- 12:12exceptions because clean items can be
- 12:14processed quickly while blocked items
- 12:16need follow-up. For high volume
- 12:18backlogs, I would use aging reports,
- 12:21assign ownership, track daily clearance,
- 12:23and escalate recurring bottlenecks
- 12:25early. In your answer, discuss SLA
- 12:28prioritization, payment due dates,
- 12:31discount opportunities, blocked
- 12:33invoices, critical suppliers, aging
- 12:35buckets, high value items, and clear
- 12:38communication with stakeholders.
- 12:40Question 16. What accounting entries are
- 12:43typically recorded in the P2P cycle? For
- 12:46goods, when the receipt is recorded,
- 12:48inventory or expense is debited and GRIR
- 12:52is credited. When the invoice is posted,
- 12:54GRIR is debited and the vendor payable
- 12:57is credited. When payment is made,
- 12:59vendor payable is debited and bank is
- 13:02credited. For non-PO expense invoices,
- 13:04the expense may be debited directly and
- 13:07vendor payable credited. The exact
- 13:09entries depend on the ERP setup, taxes,
- 13:12and whether receipt-based accounting is
- 13:13used. Be sure to cover receipt
- 13:16accounting, invoice posting, vendor
- 13:19liability, expense or inventory
- 13:21recognition, GRIR clearing, payment
- 13:24entry, and how timing differs between
- 13:26goods receipt and invoice receipt.
- 13:29Question 17. How do you ensure
- 13:31compliance with tax requirements while
- 13:33processing invoices? I would ensure the
- 13:36invoice has the required legal details
- 13:39such as supplier tax registration,
- 13:41invoice number, date, taxable value, tax
- 13:44amount, and correct entity information.
- 13:47Then I would verify that the correct tax
- 13:49code is applied based on vendor,
- 13:51location, goods or services and local
- 13:54rules. If withholding tax applies, it
- 13:56must be calculated correctly. Any
- 13:59unclear tax treatment should be
- 14:00escalated rather than guessed because
- 14:03tax errors can create compliance
- 14:04exposure. While answering, focus on
- 14:08validating tax registration, tax codes,
- 14:10invoice format, place of supply,
- 14:13withholding tax if applicable, ERP
- 14:16controls, escalation, and audit
- 14:18documentation.
- 14:20Question 18. What experience or
- 14:22understanding do you have of ERP tools
- 14:24used in P2P? I understand that P2P is
- 14:28usually managed through ERP systems such
- 14:30as SAP, Oracle or Koopa supported by
- 14:33invoice workflow and OCR tools. The ERP
- 14:36maintains vendors, POS, receipts,
- 14:38invoices, approvals and payment data. My
- 14:41focus would be on using the system
- 14:42accurately, checking source documents,
- 14:44reading status codes, clearing
- 14:46exceptions, and generating reports. Even
- 14:49if the client platform differs, the core
- 14:51process logic remains the same, so I can
- 14:53adapt quickly.
- 14:55Make sure to mention SAP, Oracle or
- 14:59similar systems if relevant, invoice
- 15:01workflow tools, OCR reporting,
- 15:04transaction codes conceptually, data
- 15:06accuracy and adaptability to client
- 15:08specific platforms. Question 19. Tell me
- 15:12about a P2P process improvement you
- 15:15would suggest to a client. I would start
- 15:18by reviewing data to identify the
- 15:20biggest pain point such as high
- 15:22exception rates or long invoice cycle
- 15:24times. If many invoices fail because of
- 15:27missing PO numbers, I would recommend
- 15:29vendor communication, invoice submission
- 15:31rules, and system validation at intake.
- 15:34If manual processing is high, OCR and
- 15:37workflow automation can help. The
- 15:39improvement should be measured through
- 15:41KPIs like first pass match rate, cycle
- 15:44time, and reduced vendor queries. In
- 15:46your answer, talk about diagnosing pain
- 15:49points, using data, increasing
- 15:51automation, reducing exceptions,
- 15:53improving vendor compliance,
- 15:54standardizing processes, and measuring
- 15:57benefits through KPIs.
- 16:01Question 20. Why do you want to work in
- 16:04P2P at Accenture? I am interested in P2P
- 16:08because it combines finance, controls,
- 16:11operations, and client service in a
- 16:13practical way. At Accenture, the
- 16:15attraction is the scale. Working with
- 16:18global clients, standardized processes,
- 16:20ERP tools, automation, and performance
- 16:23metrics. I would get exposure to real
- 16:26business issues like supplier delays,
- 16:28working capital, and compliance. I also
- 16:30like that P2P rewards attention to
- 16:33detail, ownership, and continuous
- 16:35improvement, which match how I work.
- 16:38Be sure to connect your motivation to
- 16:40finance operations, client service,
- 16:43process discipline, technology,
- 16:45continuous improvement, global delivery
- 16:47environment, learning opportunity, and
- 16:49Accentur's consulting and operations
- 16:51scale. If you are still with us,
- 16:54congratulations. You are much ahead of
- 16:56the rest and serious about preparing for
- 16:58your interview. We hope we were able to
- 17:00add value to your preparation and create
- 17:03some helpful content. Do not forget to
- 17:05like and share this video. Your small
- 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.