goAML Rejection Error Code Library

Invalid data type or format

A field value does not match the required XML Schema data type. The most common cause is a date in the wrong format (DD/MM/YYYY instead of ISO 8601), but ERR_001 also covers decimal fields containing text, boolean fields with invalid values, and STR narrative fields that are empty when content is expected.

String length violation

A text field is either shorter than the required minimum length or longer than the allowed maximum length defined in the XSD. Common in narrative fields (truncated) and reference fields (too long).

Invalid enumeration value

A code field contains a value that is not in the permitted enumeration list defined by the XSD. The schema is strict — even a value that is clearly correct in intent (e.g. 'Ksh' for Kenyan Shillings) is rejected if it does not exactly match the defined code.

Missing required element

A mandatory XML element (minOccurs='1' in the XSD) is absent from the submitted file. The goAML schema requires a specific set of fields for every report — omitting any one of them causes a fatal schema error.

Pattern constraint violation

A field value does not match the regular expression pattern defined in the XSD. This applies to structured fields where the format is constrained by a pattern in addition to the data type.

Invalid XML structure or element order

The XML elements are present but in the wrong order, or nested incorrectly according to the XSD's sequence and choice constraints. The goAML schema uses xs:sequence (strict ordering) in several places — elements must appear in the defined order.

File encoding or format error

The submitted file is not a valid UTF-8 encoded XML file, contains a byte-order mark (BOM), has an incorrect file extension, or was corrupted during upload. The goAML portal requires clean UTF-8 XML with no BOM.

Duplicate report reference

The report reference number in your submission has already been used in a previous submission for your institution. Each goAML report must have a unique reference number. The FRC portal maintains a registry of all reference numbers per reporting entity.

XML cannot be parsed

The submitted file is so malformed that the goAML portal cannot parse it at all. This is the most severe schema error — no structured error file is generated, only a generic portal error message. The XML has a syntax error that prevents the parser from reading any of its content.

Data content validation failure

ERR_045 is the FRC's general-purpose business rule error code. It covers violations of Kenya-specific data rules that go beyond XSD schema compliance: the data is structurally valid XML but fails a business logic check in the FRC's validation engine. The error message in the rejection file specifies which rule was violated.