Audience: Business Owners, CFOs, Financial Controllers, Operations Leads
Topic: Collections, Reconciliation & Ledger Management
Overview
For any lending operation, from a single retail store to a national franchise, cash flow is oxygen. The PayPlan Payment Engine is designed to be more than just a transaction processor; it acts as your automated financial controller.
This system is built to solve the two biggest anxieties in lending:
-
"Will do I get paid?" (Servicing & Collections)
-
“How do I track payments?” (Reconciliation & Audit)
This guide details the sophisticated logic PayPlan uses to recover revenue automatically, the specific banking codes that drive those decisions, and how the immutable ledger ensures every cent is accounted for.
1. The "Smart" Collection Engine
Manual collections are inefficient and error-prone. PayPlan automates the recovery process using a rules-based engine designed to maximize success rates while maintaining a positive customer relationship.
How the Logic Works
When a scheduled payment fails, the system initiates a specific recovery workflow defined by your configuration:
-
Initial Failure Detection: The system identifies the failure immediately (for Cards) or upon return (for ACH).
-
Strategic Delay: The system waits a configurable period (e.g., 3 days). This is critical; retrying immediately often results in a second decline. The delay gives the borrower time to deposit funds.
-
Retry Execution: The system automatically re-attempts the charge.
-
Autopay Safeguards: If all attempts fail across all methods, the system disables Autopay to prevent racking up bank fees for your customer and flags the account for manual intervention.
Retry Schedules by Package
-
Starter Tier (The "Set & Forget" Model): We utilize a battle-tested, fixed schedule optimized for weekly/monthly pay cycles. If a standard Friday payment fails:
-
Debit Card
-
Attempt 2: Automatically occurs on the following Monday.
-
Attempt 3: Automatically occurs on the following Thursday.
-
Please note that we recommend that you DO NOT manually re-run a card the same day and to wait until the next day.
-
-
ACH
-
Attempt 2: Automatically occurs on the following Tuesday (which is the standard reject window for ACH)
-
ACH Attempt 3: Automatically occurs on the following Thursday (which is the standard reject window for ACH)
-
-
-
Core & Above (Custom Strategies are available): Advanced lenders can configure bespoke retry frequencies (e.g., every 2 days) and specific fallback rules (e.g., "Retry Card 3x, then switch to ACH")
2. Ledger Integrity: Your Source of Truth
For a Controller or CFO, a "failed payment" isn't just a missed deposit; it's a potential accounting nightmare. PayPlan eliminates this risk by maintaining a Ledger-Based Account Register.
Tracking Payments
If a payment completely fails after all retry attempts, the system acts as your bookkeeper:
-
Accrual Integrity: The missed principal and interest are not written off. They remain on the ledger as "Past Due," ensuring your Total Outstanding Balance is always mathematically accurate.
-
Automated Fee Application: If configured, Late Fees or NSF Fees are instantly applied to the ledger, increasing the balance owed without manual calculation.
-
Term Adjustment: The system automatically tracks and adjusts all current and past due amounts, and continues to collect the original scheduled periodic payment until every dollar contracted is recovered.
-
Why? Changing the 'term' implies we modify the agreement or adjust the maturity date, which is not correct. And we can't auto-debit a final payment amount larger than the regularly scheduled payments - so, we keep collecting the approved auto-debit amount.
-
The Result: Your Servicing Center dashboard is always a real-time reflection of your portfolio's true value.
3. Total Operational Visibility
Trust requires transparency. PayPlan provides deep visibility into every financial event.
The Payment Logs (Audit Trail)
Every attempt to move money is permanently recorded.
-
Granular Detail: View the exact timestamp (UTC), amount, and method for every successful, failed, or refunded transaction.
-
Error Clarity: We don't just say "Failed." We provide the specific Network Response Code (e.g., "R01 Insufficient Funds" or "Do Not Honor"), giving you the exact reason provided by the banking network.
The Communication Logs
Know exactly what your customer knows.
-
Automated Alerts: When a payment fails, the borrower is notified immediately via SMS and Email to update their payment method.
-
Proof of Notice: The system logs every message sent. If a borrower claims, "I didn't know I was late," you can pull the Communication Log to show exactly when the notification was delivered.
4. Reference: Decoding Bank Response Codes
The system automatically distinguishes between "Temporary" failures (which it retries) and "Permanent" failures (which require your attention).
A. Credit & Debit Card Responses
System Action: Retries automatically for temporary issues; Stops for permanent ones.
|
Code |
Code Description |
Failure Type |
Explanation |
|
00 |
Approved or completed successfully |
Success |
The transaction was approved and successfully completed. |
|
01 |
Refer to card issuer |
Permanent Failure |
The cardholder’s bank must be contacted for approval. |
|
02 |
Refer to card issuer’s special conditions |
Permanent Failure |
Additional information or action is required as per the issuer's conditions. |
|
03 |
Invalid merchant |
Permanent Failure |
The merchant is not properly configured or authorized for this transaction. |
|
04 |
Pick-up |
Permanent Failure |
The card is reported lost or stolen and should be retained. |
|
05 |
Do not honor |
Permanent Failure |
The transaction was declined without a specific reason. |
|
06 |
Error |
Temporary Failure |
An unspecified processing error occurred. |
|
07 |
Pick-up card, special conditions |
Permanent Failure |
The card should be retained due to suspected fraud or other specific issues. |
|
10 |
Approved for partial amount |
Manual Intervention |
Only part of the transaction amount is approved, typically for prepaid cards or limits. |
|
11 |
Approved (VIP) |
Success |
The transaction was approved under VIP conditions. |
|
12 |
Invalid transaction |
Permanent Failure |
The transaction type is not allowed for this card or account. |
|
13 |
Invalid amount |
Temporary Failure |
The transaction amount is invalid (e.g., negative, too large, or improperly formatted). |
|
14 |
Invalid card number |
Permanent Failure |
The card number provided does not exist or is invalid. |
|
15 |
No such issuer |
Permanent Failure |
The issuing bank is not recognized or does not exist. |
|
19 |
Re-enter transaction |
Temporary Failure |
A processing issue occurred; the transaction should be retried. |
|
21 |
No action taken |
Temporary Failure |
The transaction could not be completed; no changes were made. |
|
25 |
Unable to locate record on file |
Permanent Failure |
The card or transaction record cannot be found. |
|
28 |
File update record locked out |
Temporary Failure |
A temporary issue prevents access to the record. |
|
39 |
No credit account |
Permanent Failure |
The cardholder does not have a credit account. |
|
41 |
Lost card, pick-up |
Permanent Failure |
The card is reported lost and should be retained. |
|
43 |
Stolen card, pick-up |
Permanent Failure |
The card is reported stolen and should be retained. |
|
46 |
Closed account |
Permanent Failure |
The account associated with the card is closed. |
|
51 |
Insufficient funds |
Temporary Failure |
The account has insufficient funds for the transaction. |
|
52 |
No checking account |
Permanent Failure |
The account linked to the card is not a checking account. |
|
53 |
No savings account |
Permanent Failure |
The account linked to the card is not a savings account. |
|
54 |
Expired card |
Permanent Failure |
The card is expired and cannot be used for transactions. |
|
55 |
Incorrect PIN |
Manual Intervention |
The entered Personal Identification Number (PIN) is incorrect. |
|
57 |
Transaction not permitted to cardholder |
Permanent Failure |
The transaction is not allowed for the cardholder. |
|
58 |
Transaction not permitted |
Permanent Failure |
The transaction is not permitted for this card type. |
|
59 |
Suspected fraud |
Permanent Failure |
The transaction was declined due to suspected fraudulent activity. |
|
61 |
Exceeds withdrawal amount limit |
Manual Intervention |
The transaction amount exceeds the allowed withdrawal limit. |
|
62 |
Restricted card |
Permanent Failure |
The card is restricted and cannot be used for this transaction. |
|
63 |
Security violation |
Manual Intervention |
A security concern or chargeback issue occurred. |
|
64 |
Original amount incorrect |
Manual Intervention |
The transaction amount provided does not match the original. |
|
65 |
Exceeds withdrawal frequency limit |
Permanent Failure |
The card has exceeded the allowed number of transactions. |
|
75 |
Allowable number of PIN tries exceeded |
Permanent Failure |
The PIN was entered incorrectly too many times. |
|
76 |
Key synchronization error (FIS) |
Temporary Failure |
A system or cryptographic synchronization issue occurred. |
|
78 |
Invalid/nonexistent account specified |
Permanent Failure |
The specified account does not exist or is not eligible for the transaction. |
|
79 |
Invalid digital signature |
Permanent Failure |
A digital signature error occurred. |
|
80 |
Stale dated transaction (Star SM) |
Permanent Failure |
The transaction date is invalid or too old to be processed. |
|
82 |
Issuer decline/count exceeds limit |
Temporary Failure |
The issuer declined due to a processing or limit issue. |
|
83 |
Fraud, card-absent environment |
Manual Intervention |
The transaction was flagged as fraud in a card-not-present scenario. |
|
85 |
Issuer has no reason to decline |
Success |
The card is functioning normally, but no reason for decline is provided. |
|
86 |
Cannot verify PIN (VISANet) |
Manual Intervention |
The PIN could not be verified. |
|
89 |
CVV verification failed |
Manual Intervention |
The CVV value is incorrect, but no pick-up is requested. |
|
91 |
Issuer or switch is inoperative |
Temporary Failure |
The issuer or processing network is temporarily unavailable. |
|
92 |
Financial institution unknown for routing |
Permanent Failure |
The routing information for the transaction is invalid. |
|
93 |
Transaction cannot be completed, violation of law |
Permanent Failure |
The transaction violates regulations or policies. |
|
96 |
System malfunction |
Temporary Failure |
A technical error occurred during processing. |
|
N0 |
Authorization life cycle unacceptable |
Permanent Failure |
The authorization is no longer valid. |
|
N3 |
Non-receipt of requested item |
Manual Intervention |
The issuer did not receive the required documentation. |
|
N4 |
Transaction exceeds floor limit |
Manual Intervention |
The transaction amount exceeds the permitted floor limit. |
|
N5 |
Declined authorization |
Permanent Failure |
The authorization request was declined. |
|
N7 |
Decline for CVV2 failure |
Permanent Failure |
The CVV2 (security code) did not match. |
|
Q1 |
Card authentication failed |
Permanent Failure |
The card authentication process failed. |
|
R0 |
Fraudulent transaction prior to embossed valid date |
Permanent Failure |
The card was used before its valid-from date. |
|
R1 |
Credit not received |
Manual Intervention |
The cardholder disputes that the credit has been applied. |
|
R3 |
Approved with overdraft protection |
Success |
The transaction was approved, and overdraft protection was applied. |
|
RR |
Unknown backend processing error |
Temporary Failure |
An error occurred in the backend processing systems. |
|
ZR |
Unsupported card |
Permanent Failure |
The card type is not supported by the network. |
|
ZZ |
Used for testing only |
Success |
The code is for testing purposes and not used in production transactions. |
B. ACH (Bank Transfer) Return Codes
|
Return Code |
Name |
Allowable Time for Return |
Temporary or Permanent Return / Manual Intervention |
Best Practice |
|
R01 |
Insufficient Funds |
2 banking days |
Temporary |
Wait 2-5 days and reattempt; funds may become available. |
|
R02 |
Account Closed |
2 banking days |
Permanent |
Do not reattempt; contact the customer for updated account information. |
|
R03 |
No Account/Unable to Locate Account |
2 banking days |
Permanent |
Do not reattempt; verify account details with the customer. |
|
R04 |
Invalid Account Number Structure |
2 banking days |
Permanent |
Do not reattempt; confirm account structure with the customer. |
|
R05 |
Unauthorized Debit to Consumer Account Using Corporate SEC Code |
2 banking days |
Permanent / Manual Intervention |
Do not reattempt; contact customer and review authorization procedures. |
|
R06 |
Returned per ODFI's Request |
2 banking days |
Permanent |
Do not reattempt; consult ODFI for more information. |
|
R07 |
Authorization Revoked by Customer |
60 calendar days |
Permanent |
Do not reattempt without a new authorization from the customer. |
|
R08 |
Payment Stopped |
2 banking days |
Permanent |
Do not reattempt unless the stop payment has been lifted by the customer. |
|
R09 |
Uncollected Funds |
2 banking days |
Temporary |
Wait a few days and reattempt; funds may clear. |
|
R10 |
Customer Advises Not Authorized |
60 calendar days |
Permanent |
Do not reattempt without confirming authorization details. |
|
R11 |
Customer Advises Entry Not in Accordance with Terms of Authorization |
60 calendar days |
Permanent |
Do not reattempt without correcting the underlying error and re-approving. |
|
R12 |
Account Sold to Another DFI |
2 banking days |
Permanent |
Do not reattempt; contact customer for new account details. |
|
R13 |
Invalid ACH Routing Number |
2 banking days |
Permanent |
Do not reattempt; verify routing information with the customer. |
|
R14 |
Representative Payee Deceased |
2 banking days |
Permanent |
Do not reattempt; follow up with customer on account status. |
|
R15 |
Beneficiary or Account Holder Deceased |
2 banking days |
Permanent |
Do not reattempt; follow procedures for deceased account holders. |
|
R16 |
Account Frozen |
2 banking days |
Permanent |
Do not reattempt; contact the customer for more information. |
|
R17 |
File Record Edit Criteria |
2 banking days |
Permanent |
Do not reattempt; correct file record errors before resubmitting. |
|
R20 |
Non-Transaction Account |
2 banking days |
Permanent |
Do not reattempt; confirm account type with customer (non-transaction accounts can’t accept debits). |
|
R21 |
Invalid Company Identification |
2 banking days |
Permanent |
Do not reattempt; correct company ID and verify before resubmitting. |
|
R22 |
Invalid Individual ID Number |
2 banking days |
Permanent |
Do not reattempt; verify and correct individual ID details. |
|
R23 |
Credit Entry Refused by Receiver |
2 banking days |
Permanent |
Do not reattempt; contact receiver to understand refusal reason. |
|
R24 |
Duplicate Entry |
2 banking days |
Permanent |
Do not reattempt; identify duplicate and avoid resubmission. |
|
R25 |
Addenda Error |
2 banking days |
Permanent |
Do not reattempt; correct addenda information before resubmitting. |
|
R26 |
Mandatory Field Error |
2 banking days |
Permanent |
Do not reattempt; correct missing or invalid fields. |
|
R27 |
Trace Number Error |
2 banking days |
Permanent |
Do not reattempt; correct trace number and resubmit if necessary. |
|
R28 |
Routing Number Check Digit Error |
2 banking days |
Permanent |
Do not reattempt; verify routing number for accuracy. |
|
R29 |
Corporate Customer Advises Not Authorized |
2 banking days |
Permanent |
Do not reattempt without obtaining new authorization. |
|
R31 |
Permissible Return Entry (CCD and CTX Only) |
2 banking days |
Permanent |
Do not reattempt; contact ODFI to resolve return reason. |
|
R32 |
RDFI Non-Settlement |
2 banking days |
Permanent |
Do not reattempt; consult RDFI for settlement resolution. |
|
R33 |
Return of XCK Entry |
2 banking days |
Permanent |
Do not reattempt; consult ODFI for clarification on XCK returns. |
|
R34 |
Limited Participation DFI |
2 banking days |
Permanent |
Do not reattempt; contact ODFI to understand DFI restrictions. |
|
R35 |
Return of Improper Debit Entry |
60 calendar days |
Permanent |
Do not reattempt; review transaction for compliance and resolve. |
|
R36 |
Return of Improper Credit Entry |
2 banking days |
Permanent |
Do not reattempt; review credit entry for accuracy. |
|
R37 |
Source Document Presented for Payment |
2 banking days |
Permanent |
Do not reattempt; check if source document is valid. |
|
R38 |
Stop Payment on Source Document |
2 banking days |
Permanent |
Do not reattempt; stop payment request must be honored. |
|
R39 |
Improper Source Document |
2 banking days |
Permanent |
Do not reattempt; correct document issue before proceeding. |
|
R40 |
Return of ENR Entry |
2 banking days |
Permanent |
Do not reattempt; resolve ENR (Enrollment) errors. |
|
R41 |
Invalid Transaction Code |
2 banking days |
Permanent |
Do not reattempt; correct transaction code for accuracy. |
|
R42 |
Routing Number/Check Digit Error |
2 banking days |
Permanent |
Do not reattempt; verify and correct routing number errors. |
|
R43 |
Invalid DFI Account Number |
2 banking days |
Permanent |
Do not reattempt; correct DFI account number before resubmitting. |
|
R50 |
State Law Affecting RCK Acceptance |
60 calendar days |
Permanent |
Do not reattempt; comply with state law requirements. |
|
R51 |
Item Related to RCK Entry Is Ineligible |
60 calendar days |
Permanent |
Do not reattempt; resolve ineligibility before proceeding. |
|
R52 |
Stop Payment on Item Related to RCK Entry |
60 calendar days |
Permanent |
Do not reattempt; ensure stop payment status is respected. |
|
R53 |
Item and RCK Entry Presented for Payment |
60 calendar days |
Permanent |
Do not reattempt; address double presentation of items. |
|
R60 |
System or Processor Reserved |
N/A |
Permanent Error |
Used by Flex for Previously Processed Transactions with Permanent Failures. |
5. Best Practices & Limitations
To ensure the highest success rates, we recommend the following configurations based on our data across millions of applications.
Recommended Configuration (Core+):
-
Limit Retries: We recommend 2-3 retries per payment method. Retrying more than this rarely succeeds and can upset customers.
-
Use Fallback: Always configure the system to switch to the Secondary Method after the Primary Method fails twice.
System Limitations to Note:
-
No Progressive Delays: The delay interval is fixed (e.g., always 3 days). The system does not currently support "progressive" delays (e.g., wait 1 day, then 3 days, then 7 days).
-
No "Smart" Prioritization: If a customer has multiple backup cards, the system selects the next one in line; you cannot rank them manually.
Summary of Benefits
|
Feature |
Operational Benefit |
Financial Benefit |
|
Automated Retries |
Reduces manual collections calls by 40%+. |
Recovers "lost" revenue without human intervention. |
|
Fallback Logic |
Continues collection even if a card is lost/stolen. |
Increases probability of successful settlement. |
|
Ledger Accounting |
Eliminates "shadow accounting" and spreadsheet tracking. |
Ensures 100% accuracy for P&L and tax reporting. |
|
Compliance Logging |
Provides a defensible audit trail for every action. |
Mitigates risk in case of borrower disputes. |
Next Steps
-
Starter Users: Your system is pre-configured with our optimized "Friday-Monday-Thursday" retry logic. No action is needed.
-
Core/Pro/Enterprise: To customize your retry frequency, max attempts, or fallback rules, please contact your Implementation Manager.