OneGate rejection codes can be confusing. This guide provides detailed explanations of each code category, common causes, and specific resolution steps to help you quickly fix issues and resubmit.
Key Takeaways
- Rejection codes indicate specific error types
- Technical errors usually require file regeneration
- Business rule errors need data investigation
- File naming issues are the easiest to fix
- Documentation speeds up future resolutions
Rejection Code Structure
OneGate codes follow patterns:
• OG-Txx: Technical/format errors
• OG-Bxx: Business validation errors
• OG-Axx: Authentication/access errors
• OG-Sxx: System/infrastructure errors
• BV-xxxx: EBA business validation rules
The code prefix helps identify the error category quickly.
Technical Rejections
Common technical rejections:
• OG-T01: Invalid XML structure
• OG-T02: Schema validation failure
• OG-T03: Encoding error (not UTF-8)
• OG-T04: Invalid file name format
• OG-T05: Unsupported taxonomy version
These require fixing the XBRL generation process.
Business Rule Rejections
Business rule rejections (OG-Bxx) indicate data issues: • OG-B01: Cross-table inconsistency • OG-B02: Missing required template • OG-B03: Invalid reporting period • OG-B04: Entity identifier mismatch These require investigating source data and validation rules.
Authentication Errors
Authentication issues:
• OG-A01: Certificate expired
• OG-A02: Certificate not authorized
• OG-A03: Institution not registered
• OG-A04: User not authorized for collection
Contact your institution's administrator or BdF support for access issues.
Resolution Process
Error resolution workflow:
1. Note the exact rejection code
2. Review error message details
3. Identify error category
4. Apply appropriate fix
5. Revalidate locally
6. Increment file version number
7. Resubmit
8. Document resolution
Maintain a resolution log for recurring issues.