AAP study plan

Map the end-to-end lifecycle of an ACH entry across ODFI, ACH Operator, and RDFI, labeling each participant's role and timing obligations.

Define 30 core ACH terms (e.g., Originator, Receiver, TPSP, Third-Party Sender, Entry, Batch) in your own words without referencing notes.

Sequence the key NACHA Operating Rules articles and identify which article governs origination, returns, and NOCs.

Differentiate ACH from wire, card, and check payments across speed, cost, finality, and reversibility.

Explain the legal framework layers: NACHA Rules, Regulation E, UCC Article 4A, and federal/state law, citing one example where each applies.

Trace the return-entry lifecycle from RDFI decision through ACH Operator to ODFI and Originator, including timing windows.

Categorize at least 25 return reason codes by cause (administrative, account, authorization, fraud) and match each to the responsible party.

Draft the required actions and deadlines for an unauthorized return (R05/R07/R10/R11) versus an administrative return (R01/R02/R03).

Compare NOC handling for changed account numbers versus incorrect routing numbers, including the Originator's obligation to update.

Calculate return-rate thresholds and identify when an ODFI must take action on excessive returns.

Diagnose five exception scenarios (late return, dishonored return, contested dishonored return) and select the correct response and deadline.

Outline the disputed-entry process including Written Statement of Unauthorized Debit requirements and consumer liability timelines under Regulation E.

Build a fraud typology table covering payroll diversion, vendor impersonation, account takeover, and authorized push payment scams.

Design a monitoring rule set with thresholds for return rates, NOC rates, and unusual origination patterns.

Explain the ODFI's and Originator's warranty and indemnification obligations when an entry is returned or disputed.

Differentiate the responsibilities of an ODFI, Third-Party Sender, and Third-Party Service Provider in origination and risk control.

List the due diligence and contractual elements an ODFI must obtain from a Third-Party Sender before origination.

Identify red flags for third-party sender risk, including commingled funds, unsupported MCCs, and rapid volume growth.

Draft a risk-assessment outline for onboarding a new originator using exposure limits and monitoring triggers.

Match at least 10 fraud scenarios to the correct preventive control (e.g., account validation, positive pay, OFAC screening).

Compare consumer and corporate account entries, including authorization requirements, return rights, and SEC code selection.

Select the correct SEC code (WEB, TEL, CCD, PPD, ARC, BOC, POP, IAT) for eight origination scenarios.

Diagram the origination workflow from authorization capture through batch creation, file transmission, and settlement.

Explain receipt obligations for RDFIs, including posting, availability, and stop-payment handling.

Identify record-format fields in an ACH file and describe the purpose of the batch header, entry detail, and addenda records.

Explain Same Day ACH windows, dollar limits, and which entry types are eligible for same-day processing.

Compare IAT entry requirements, including formatting, OFAC screening, and accompanying addenda records.

Map the responsibilities of a Third-Party Service Provider versus a Third-Party Sender in Same Day ACH and IAT origination.

Describe emerging payment developments and how they interact with traditional ACH (e.g., real-time payments, API-initiated entries).

Identify compliance obligations for cross-border entries, including gateway operators and foreign payment system rules.

Evaluate five emerging-payment use cases and determine whether ACH, Same Day ACH, or another rail is appropriate.

Explain the risk controls specific to IAT, including screening, data privacy, and returns.

Differentiate consumer and business use cases for account-to-account payments, recurring debits, and push-to-card disbursements.

Analyze how API-driven origination changes authorization, validation, and error-resolution responsibilities.

Summarize regulatory expectations for emerging payment channels, including UDAAP and consumer protection considerations.

Complete two full-length timed practice exams and record domain-level scores.

Re-teach the three weakest domains using a one-page summary for each.

Resolve every missed practice question into a corrected rule statement with citation to the relevant rule area.

Build a final 50-item rapid-review sheet covering deadlines, reason codes, SEC codes, and limits.

Simulate exam-day pacing with a 90-minute mixed-topic session and no notes.