Verato is upgrading the batch processing engine behind Verato Connect Batch. The upgrade delivers faster, more scalable processing, support for multi-domain batch files, and cleaner, more consistent output files.
As your upgrade date approaches, Verato Support will open a case to remind you of the timeline.
What's improving
- Faster, more scalable processing. Connect Batch now runs on a modern processing framework designed for larger batch volumes.
- Multi-domain support. Connect Batch now supports the Verato multi-domain API. Your batch files can include all clusters and attributes supported by the postIdentity API, not just a single domain.
- Cleaner, more consistent output. Output files now standardize data formats and provide more focused error reporting, making results easier to review and use downstream.
Upgrade timeline
| Environment | Target start date |
|---|---|
| Non-production | Monday, November 16, 2026 |
| Production | Mid-January 2027 (we will update this article with the exact date in early January 2027) |
Customer action
No action is required for the upgrade itself. However, the output files will change. Before your non-production upgrade date, review the changes below and confirm that any downstream processes that read Connect Batch output can handle:
- Uppercased and standardized demographic values
- Error rows that contain only error and tracking columns
- Multiple
UPDATE_SOURCEvalues separated by~, and the newADD_SOURCEvalue
We recommend validating your downstream processes against non-production output before the production upgrade. If you have questions, contact Verato Support or reply to your upgrade reminder case.
What you'll see in your new output files
Data standardization
Demographics in the output file are now standardized the same way they are in the API response.
| Current behavior | After the upgrade |
|---|---|
| The input row is copied into the output file as is. | All values are uppercased, and certain data types are normalized. |
Standardization includes, but is not limited to:
- Dates are formatted as YYYY-MM-DD (1/2/2000 → 2000-01-02).
- Addresses are standardized:
- Directions are abbreviated (South → S).
- Street suffixes are abbreviated (Road → RD, Street → ST).
- Unit designators are abbreviated (Apartment → APT).
- SSNs have hyphens removed (123-45-6789 → 123456789).
- Phone numbers have hyphens removed (200-555-0000 → 2005550000).
- Genders are normalized (Female → F, Male → M).
- Email addresses are uppercased.
Example
Input row:
...|Jane||Doe||123-45-6789|1/2/2000|Female|314 South Main Road|Apartment 42|Springfield|MA|01103|1234|200-555-0000|jane.doe@example.com|...
Current output row (demographics copied from the input file as is):
...|Jane||Doe||123-45-6789|1/2/2000|Female|314 South Main Road|Apartment 42|Springfield|MA|01103|1234|200-555-0000|jane.doe@example.com|...
Upgraded output row (demographics standardized):
...|JANE||DOE||123456789|2000-01-02|F|314 S MAIN RD|APT 42|SPRINGFIELD|MA|01103|1234|2005550000|JANE.DOE@EXAMPLE.COM|...
Streamlined error rows
Rows that result in an error no longer contain demographic data.
| Current behavior | After the upgrade |
|---|---|
| Error rows include the input demographics, copied as is. | Error rows contain only the errorMessage, errorType, errorTimestamp, trackingId, and auditId columns. |
Example
Input row:
...|Jane||Doe||123-45-6789|1/2/2000|Female|314 South Main Road|Apartment 42|Springfield|MA|01103|1234|200-555-0000|jane.doe@example.com||
Current output row (demographics copied from the input file as is):
...|Jane||Doe||123-45-6789|1/2/2000|Female|314 South Main Road|Apartment 42|Springfield|MA|01103|1234|200-555-0000|jane.doe@example.com|||postIdentityService.default failure: unauthorized.request : The client is not authorized for the requested operation: no write permissions on source: not-a-source|technicalError|2026-11-05T20:06:19.255727790Z||6aece0370aba656a1db3e10d
Upgraded output row (no demographics):
|||||||||||||||||||||||||postIdentityService.default failure: unauthorized.request : The client is not authorized for the requested operation: no write permissions on source: not-a-source|technicalError|2026-11-05T20:06:19.255727790Z||6aece0370aba656a1db3e10d
Updated error messages
Error message text may change after the upgrade. If your processes parse error messages, use the errorType value rather than the message text.
Expanded eventType column
The eventType column shows how Source + Native ID records changed within the Link ID in that row.
| Value | Meaning | How many per row |
|---|---|---|
ADD_SOURCE | The submitted Source + Native ID is new and had no previously assigned Link ID. | At most one |
UPDATE_SOURCE | One or more Source + Native ID records had their previously assigned Link ID changed. | One per pre-existing Link ID linked into this row's Link ID, separated by ~ |
ADD_SOURCE and UPDATE_SOURCE are mutually exclusive. A row contains one or the other, never both.
The record that receives a Link ID change may be the one you submitted, or a different record. A different record changes when your submission causes two or more pre-existing Link IDs to link together through transitive linking during matching. Each UPDATE_SOURCE value corresponds to one previous Link ID, which may have contained one or more Source + Native ID records.
| Current behavior | After the upgrade |
|---|---|
Only the first UPDATE_SOURCE appears. ADD_SOURCE never appears. | One UPDATE_SOURCE appears per Link ID linked into the row's Link ID, separated by ~. ADD_SOURCE appears when the row's Source + Native ID is new. |
Examples
Current behavior: at least one other Link ID was linked into this Link ID.
...|eventType|... ...|UPDATE_SOURCE|...
After the upgrade: exactly two other Link IDs were linked into this Link ID.
...|eventType|... ...|UPDATE_SOURCE~UPDATE_SOURCE|...
After the upgrade: Source SRC_A with Native ID abc123 is new and was not previously in any Link ID.
...|Source Code|Native ID|...|eventType|... ...|SRC_A|abc123|...|ADD_SOURCE|...
Comments
0 comments
Article is closed for comments.