CAPA (CNCF) common mistakes
CAPA · Understand the traps and how to avoid them.
Treating the three-way match as a two-way match: approving an invoice because the amount matches the purchase order without confirming the goods receipt quantity and price agree.
Candidates conflate 'invoice matches PO' with 'invoice is payable' and skip the receipt leg, especially when the invoice total equals the PO total but the received quantity is short.
What to do instead
For every match question, walk the three legs explicitly: PO (ordered qty, unit price), receiving report (received qty, condition), invoice (billed qty, unit price, terms). State which leg fails before choosing an outcome.
Confusing a debit memo with a credit memo: describing the buyer's reduction of a payable as a credit memo, or the supplier's reduction of a receivable as a debit memo.
Both memos adjust an invoice, so candidates remember 'adjustment' but not whose books the adjustment sits in or which side of the ledger it hits.
What to do instead
Anchor on the buyer's perspective: a debit memo debits accounts payable (reduces what the buyer owes) and is issued by the buyer; a credit memo is issued by the supplier and reduces the supplier's receivable. Recite the buyer-side rule before answering.
Applying a cash discount after the discount period because the invoice date was used instead of the later of receipt date or invoice date per the stated terms.
Terms such as 2/10 net 30 are read from the invoice date by habit, and candidates ignore FOB or receipt-based starting points when the question specifies them.
What to do instead
Identify the discount start date stated in the terms, compute the last discount day, and compare it to the payment date. If the question gives a receipt date later than the invoice date, use the date the terms specify, not the earlier one.
Booking an invoice with no PO and no receipt as a normal matched transaction, or rejecting it outright, instead of routing it as a non-PO invoice requiring approval and coding.
Candidates assume every invoice must match a PO, so they either force a match that does not exist or declare the invoice invalid.
What to do instead
Classify the invoice first: PO-backed, non-PO, or recurring/contract. Non-PO invoices follow a separate approval-and-coding path with budget or manager sign-off; they are not three-way matched and are not automatically rejected.
Failing to separate segregation-of-duties conflicts: allowing the same person to create a vendor, enter an invoice, and release payment.
Candidates focus on whether the transaction is accurate and overlook who performs each step, so a 'correct' transaction passes review even though controls are broken.
What to do instead
For any process question, map the four duties: vendor master maintenance, invoice entry/approval, payment release, and reconciliation. Flag any single role holding two or more of these, regardless of transaction accuracy.
Missing the duplicate-payment risk when vendor master data changes: a new bank account or remit-to address on an existing vendor is treated as routine maintenance.
Candidates treat vendor master changes as data entry rather than a fraud and control event, so they do not require independent verification.
What to do instead
Apply a change-control rule: bank detail and remit-to changes require independent callback verification to a known contact and a second approver, and are logged. Name this control when the scenario involves altered payment instructions.
Misreading FOB terms: assuming FOB destination means the buyer owns goods in transit and should accrue the liability at shipment.
The two FOB terms are easily swapped, and candidates conflate ownership transfer with who pays freight.
What to do instead
Memorize: FOB shipping point transfers title at shipment (buyer owns in transit, accrues earlier); FOB destination transfers title at receipt (seller bears transit risk). Match the accrual timing to the title transfer point.
Ignoring the accrual cutoff: recording an invoice received after period end in the new period even though the goods were received before period end.
Candidates key off the invoice date rather than the receipt date, so late-arriving invoices are booked in the wrong period and the period-end liability is understated.
What to do instead
Use the receipt date to determine the period for goods received but not invoiced; accrue the estimated liability at period end and reverse it when the invoice arrives. State the receipt date and the accrual entry explicitly.
Treating a partial receipt as a full match: approving payment for the full invoice quantity when only part of the order has been received.
The invoice total matches the PO total, so candidates approve, overlooking that the receipt line shows a short quantity and the balance is not yet due.
What to do instead
Compare billed quantity to received quantity line by line. Pay only for received goods unless the terms allow prepayment or progress billing, and hold the unmatched balance as an open receipt until the remainder arrives.
Overlooking the payment run controls: releasing a payment without confirming the invoice was approved, the vendor is active and not on hold, and the payment method matches the vendor record.
Candidates treat payment as the mechanical end of the process and do not check the pre-payment gate, so a held or unapproved invoice gets paid.
What to do instead
Before releasing payment, verify four gates: invoice approved, vendor active and not blocked, no duplicate payment already issued, and payment method and bank details match the master record. List the gates in the answer.