How it works

Before uploading any files, you define a mapping rule that describes your file structure. Use the visual editor to map fields from your source format onto the corresponding fields in the Coator standard schema. You can set default values, apply string transformations, and handle conditional logic.

• Supports CSV, XML, fixed-width, and delimited formats
• Mappings are saved and reusable across all future uploads
• Validate against a sample file before saving

Upload your debt portfolio file through the Coator web interface or via API. Select the mapping rule that matches the file format. Coator parses the file, applies the mapping, and runs the result through schema validation.

• Upload via browser or REST API
• Supports large files with thousands of claims
• Validation errors are surfaced per-row with clear messages

After transformation, Coator shows you a summary of the portfolio: how many claims were processed, any validation warnings, and a preview of the standardised data. You can review and approve before the file is made available to agencies.

• Per-claim validation against the standard schema
• Warnings for missing optional fields
• Approve or reject before delivery

Once approved, Coator produces a validated standard XML document conforming to the Coator schema. This is the canonical representation of the portfolio that all downstream delivery uses as its source.

• Validated against the published XSD
• Versioned and immutable once approved
• Stored securely with full audit trail

Before delivery, claims pass through business rules configured on the agency's connector. Each rule defines one or more field conditions — if all conditions match, the claim is rejected with a specific message. Rules are fully defined by the agency and can be enabled or disabled at any time.

• Custom rules per connector, defined by the agency
• Conditions can compare fields to literal values or other fields
• Rejected claims get a distinct status with a claim-level message

The agency receives the portfolio via their configured connector — native Coator protocol, REST API, or SFTP. If the agency has its own import format, Coator applies an outbound mapping to re-transform the standard file into their preferred structure before delivery.

• Native connector, REST API, or SFTP delivery
• Optional outbound mapping to any target format
• Delivery confirmed and logged with timestamp