List Of FNB Error Codes In South Africa. Encountering FNB error codes during banking transactions or service usage with First National Bank (FNB) can disrupt the seamless banking experience. FNB error codes are specific identifiers denoting various issues that might arise within the bank’s systems. Understanding these codes and their implications is crucial for users to address encountered problems effectively. This article aims to shed light on FNB error codes, their meanings, common occurrences, and steps users can take to troubleshoot and resolve these issues, ensuring smoother banking experiences.
What Are FNB Error Codes?
FNB error codes are specific alphanumeric or numerical identifiers used within the First National Bank (FNB) system to indicate issues or errors encountered during banking transactions or while utilizing FNB’s services. These error codes serve as a diagnostic tool, helping to identify and communicate the nature of the problem that occurred during a transaction or when accessing banking services.
Each FNB error code typically corresponds to a particular error condition or situation within the bank’s system. These codes can encompass a range of issues, such as temporary service unavailability, authentication problems, transaction failures, system errors, or network-related issues.
Understanding and interpreting FNB error codes is crucial for both customers and bank personnel, as they help pinpoint the cause of the problem, enabling users to take appropriate steps to resolve the issue or seek assistance from FNB’s support services for further guidance.
List Of FNB Error Codes In South Africa
Here is a table presenting the reversal reason codes along with their respective reject reasons and FNB codes:
Reversal Reason Codes
| Reason Code | Reject Reason | FNB Code |
|---|---|---|
| RR01 | Incorrect Creditor Account Number | 3151 |
| RR02 | Incorrect Debtor Account Number | 1079 |
| RR03 | Closed Creditor Account Number | 3152 |
| RR04 | Closed Debtor Account Number | 1076 |
| RR05 | Blocked Creditor Account | 3153 |
| RR06 | Blocked Debtor Account | 1073 |
| RR07 | End Customer Deceased | 1077 |
| RR08 | Incorrect Creditor Agent Account | 3154 |
| RR09 | Incorrect Debtor Agent Account | 3155 |
| RR10 | Insufficient funds | 1069 |
| RR11 | Incorrect Related Transaction Reference | 3156 |
| RR12 | Unrecognized Initiating Party | 3157 |
| RR13 | Regulatory Reason | 3188 |
| RR14 | Not Allowed Payment (Credit) | 3158 |
| RR15 | Not Allowed Payment (Debit) | 3159 |
| RR16 | Refund Request by End Customer | 3160 |
| RR17 | Response / Request received after Cut-off Time | 3161 |
| NA01 | Resolution response exceeds SLA cut-off | 814 |
| NA04 | Payment stopped (by account holder) | 1071 |
| NA28 | Recall / withdrawal | 3162 |
| NA30 | No authorization to debit | 1070 |
| NA32 | Debit in contravention of the authorized payer | 3163 |
| NA34 | Authorization cancelled | 3164 |
| NA36 | Previously stopped via Stop Payment Advice | 3165 |
| INV1 | Invalid Supplier | 3166 |
| TX01 | Incorrect Tax Reference Number supplied | 3167 |
This table outlines the various reason codes, reject reasons, and corresponding FNB codes used in the context of reversal reasons for financial transactions.
Transaction Status Reason Codes
| Industry | Reason Code | Reject Reason | FNB Code |
|---|---|---|---|
| TR | 1 | Invalid Instruction ID | 2025 |
| TR | 2 | Supplier not registered against User Code | 2026 |
| TR | 3 | Status of Supplier not active | 2027 |
| TR | 4 | Duplicate End to End ID | 2028 |
| TR | 5 | Invalid date specified in End to End ID | 2029 |
| TR | 6 | User Code in End to End ID does not match Header | 2030 |
| TR | 7 | Generation Number in End to End ID does not match Header | 2031 |
| TR | 8 | Invalid Sequence Number in End to End ID | 2032 |
| TR | 9 | Invalid Tracking Days specified | 131 |
| TR | 10 | Transaction Limit exceeded | 2033 |
| TR | 11 | Transaction Amount is zero | 2034 |
| TR | 12 | Invalid Charge Bearer | 2035 |
| TR | 13 | Invalid Creditor Name | 2036 |
| TR | 14 | Invalid Creditor Organisation BIC Code | 2037 |
| TR | 15 | Invalid Creditor ID Issuer | 2038 |
| TR | 16 | Invalid Creditor Account Number | 2039 |
| TR | 17 | Invalid Creditor Account Type | 2040 |
| TR | 18 | Creditor Agent BIC does not match Instructing Agent BIC in Header | 2041 |
| TR | 19 | Invalid Debtor Name | 2042 |
| TR | 20 | Invalid Debtor Organisation BIC Code | 2043 |
| TR | 21 | Invalid Debtor Account Number | 2044 |
| TR | 22 | Invalid Debtor Account Type | 2045 |
| TR | 23 | Invalid Entry Class Code | 133 |
| TR | 24 | No match on Instruction ID | 2046 |
| TR | 25 | Supplier No longer valid | 2047 |
| TR | 26 | No match on End-to-end ID | 2048 |
| TR | 27 | Debtor BIC does not match original request | 2049 |
| TR | 28 | Debtor Issuer not valid | 2050 |
| TR | 29 | Debtor Account number does not match the original request | 2051 |
| ndustry | Reason Code | Reject Reason | FNB Code |
|---|---|---|---|
| TR | 30 | Debtor Account Type does not match the original request | 2052 |
| TR | 31 | Debtor Agent BIC does not match the original request | 2053 |
| TR | 32 | Creditor Agent BIC does not match the original request | 2054 |
| TR | 33 | Creditor BIC does not match the original request | 2055 |
| TR | 34 | Creditor Account does not match the original request | 2056 |
| TR | 35 | Creditor Account Type does not match the original request | 2057 |
| TR | 36 | Original Message ID Indicated does not match a valid transaction | 2058 |
| TR | 37 | Invalid Original Message name ID | 2059 |
| TR | 38 | Invalid Group Status | 2060 |
| TR | 39 | Invalid Transaction Status | 2061 |
| TR | 40 | Invalid Transaction Status Reason | 2062 |
| TR | 41 | Invalid Missing Information Code | 2063 |
| TR | 42 | Invalid Incorrect Information Code | 2064 |
| TR | 43 | Group cancellation section and Transaction cancellation section have been specified | 2065 |
| TR | 44 | Invalid Group Cancellation indicator specified | 2066 |
| TR | 45 | Invalid Cancellation Reason code specified | 2067 |
| TR | 46 | Invalid BIC Code | 2068 |
| TR | 47 | Invalid Status Confirmation Code | 2069 |
| TR | 48 | Invalid Status Code | 2070 |
| TR | 49 | Invalid Status Reason Code | 2071 |
| TR | 50 | Original Settlement Amount does not match original transaction | 2072 |
| TR | 51 | Invalid Returned Amount | 2073 |
| TR | 52 | Returned Amount Exceeds Original Interbank Settlement Total | 2074 |
| TR | 53 | Invalid Return Reason Code | 2075 |
| TR | 54 | Debtor Agent specified does not match the original transaction | 2076 |
| TR | 55 | Creditor Agent specified does not match the original transaction | 2077 |
| TR | 56 | Invalid Creditor Agent BIC Code | 2078 |
| TR | 57 | Creditor Organization Not Present nor Postal Address | 3168 |
| TR | 58 | Postal Address Not Present nor Creditor Organization | 3169 |
| Industry | Reason Code | Reject Reason | FNB Code |
|---|---|---|---|
| TR | 59 | Interbank Settlement Date Does Not Match Group Header Interbank Settlement Date | 3187 |
| TR | 60 | Transaction Expired | 3170 |
| TR | 61 | Session Expired | 3171 |
| TR | 62 | Invalid Debtor Agent BIC | 3172 |
| TR | 63 | Duplicate Transaction Id | 3173 |
| TR | 64 | Supplier Not Registered | 3174 |
| TR | 65 | Creditor Account CDV Failed | 3175 |
| TR | 66 | Debtor Account CDV Failed | 3176 |
| TR | 67 | Transaction Duplicate Threshold Reached | 3177 |
| TR | 68 | Rejected Transaction Threshold Reached | 3178 |
| TR | 69 | Duplicate Case Id | 3179 |
| TR | 70 | Invalid Date Specified in Case Id | 3180 |
| TR | 71 | User Code in Case ID Does Not Match Assignment ID | 3181 |
| TR | 72 | Generation Number in Case ID Does Not Match Header | 3182 |
| TR | 73 | Invalid Sequence Number in Case Id | 3183 |
| TR | 74 | Cancellation Request Received | 3184 |
| TR | 75 | Insufficient Funds (Pending) | 1084 |
| TR | 76 | Insufficient Funds (Rejected) | 1069 |
| TR | 77 | Stop Payment (Rejected) | 3185 |
| TR | 78 | No query on specified End-to-End ID | 3186 |
| TR | 79 | Non-Business Day and No tracking | 179 |
| TR | 80 | ENDOPOR Sequence invalid | 180 |
Cancellation response Status Reason Codes
| Reason Code | Reject Reason | FNB Code |
|---|---|---|
| 1 | Valid mandate supplied | 2080 |
| 2 | Customer decision | 2081 |
| 3 | Unable to action | 3150 |
| 4 | Unable to contact customer | 2083 |
| 5 | Cancellation applied to transaction | 2084 |
| 6 | Pending cancellation | 2085 |
| 7 | Insufficient Funds | 2086 |
| 8 | Legal Decision | 2087 |
| 9 | No Original Transaction Received | 2088 |
| A | Closed Account Number | 2089 |
| B | Already Actioned | 2090 |
Transaction Cancellation Reason Codes
| Industry | Reason Code | Reject Reason | FNB Code |
|---|---|---|---|
| Industry | 1 | System Error – Duplicate | 936 |
| Industry | 2 | System Error – Malfunction | 937 |
| Industry | 3 | Customer Requested Cancellation | 933 |
| Industry | 4 | Suspected Fraud | 934 |
| Industry | 5 | Mandate Invalid | 935 |
| Industry | 6 | Recall | 938 |
FNB Error Codes FAQs
Here’s a set of FAQs related to FNB error codes:
1. What Are FNB Error Codes?
- Answer: FNB error codes are specific identifiers used within First National Bank’s system to denote issues or errors encountered during banking transactions or service usage. They help diagnose and communicate the nature of encountered problems.
2. Why Do I Encounter FNB Error Codes?
- Answer: FNB error codes typically arise due to various reasons, such as temporary system unavailability, authentication failures, transaction issues, or network-related problems during banking activities.
3. How Can I Resolve FNB Error Codes?
- Answer: Resolving FNB error codes depends on the specific code and its context. Troubleshooting might involve retrying the transaction, checking internet connectivity, verifying account details, or contacting FNB’s support for guidance.
4. Can FNB Error Codes Affect Transactions?
- Answer: Yes, FNB error codes can impact transactions by causing interruptions or failures during banking activities, hindering the completion of transactions or services.
5. Are FNB Error Codes Common?
- Answer: FNB error codes are encountered occasionally, often arising due to temporary issues within the bank’s systems or during specific transactional processes.
6. Where Can I Find Information About Specific FNB Error Codes?
- Answer: FNB’s official support channels, website, or customer service representatives can provide information about specific error codes and their resolutions.
7. Do FNB Error Codes Vary in Meaning?
- Answer: Yes, the meanings of FNB error codes can differ based on the context or nature of the encountered issue. Each code typically represents a specific error condition within FNB’s system.
8. Should I Be Concerned About FNB Error Codes?
- Answer: While FNB error codes might temporarily disrupt transactions or services, they often denote common issues that can be resolved by following recommended troubleshooting steps or seeking assistance from FNB’s support.
Understanding these FAQs can provide insights into the nature of FNB error codes, their potential impact, and steps to resolve encountered issues, ensuring smoother banking experiences for users.
Conclusion
FNB error codes serve as indicators of underlying issues within the bank’s systems during transactions or service usage. While encountering these codes can be inconvenient, understanding their meanings and following recommended troubleshooting steps often leads to resolution. By being informed about common FNB error codes and their potential causes, users can navigate these issues with confidence, seek appropriate assistance from FNB’s support channels, and ensure a smoother banking journey. Always remember that while error codes may momentarily disrupt transactions, prompt action and support accessibility often lead to swift resolutions, enabling users to continue their banking activities seamlessly.
Image Courtesy: htxt
