Moody's is notifying clients that Batch ID values will soon exceed the range of a 32-bit integer.

What's changing

Batch ID values will grow beyond the range that fits in a standard 32-bit integer (values above 2,147,483,647). This affects every delivery channel where Batch ID is provided, including the API (SOAP and REST), SFTP response files (both XML and pipe-delimited formats), and reports. 

Based on current volumes, Batch ID values are expected to exceed the 32-bit limit in December 2026. Moody's expects to have all supporting changes deployed by end of August 2026; this deployment does not change the format or values you receive today. Values will grow naturally as volumes increase.

Who this affects

Any integration that stores or parses the Batch ID field using a 32-bit integer type (for example, int in Java/C#, or a database column defined as INT/INTEGER). This includes Batch ID appearing in API responses, SFTP response file headers, and SFTP pipe-delimited alert records (where Batch ID is part of nearly every row, not just the header). Once Batch ID values exceed the 32-bit limit, these integrations may encounter errors, truncated values, or data corruption.

What to do

Prior to October 31, 2026:

• Review how your integration stores and parses the Batch ID field across all channels you use (API, SFTP response files, reports).
• Confirm that storage (database columns, variables, message formats) uses a 64-bit integer type (e.g., BIGINT, long, Long, Int64) rather than a 32-bit type.
• If you consume SFTP pipe-delimited response files, confirm your parsing of the compound alert-record key (Batch ID plus Inquiry ID) also supports the larger value.
• If you generate code from Moody's Swagger definitions or from a service's live WSDL endpoint, confirm the generated types and your downstream storage use 64-bit integer or string types, or you can regenerate after Moody's deployment completes. 
• Test your parsing and storage with a synthetic Batch ID value greater than 2,147,483,647 (e.g., 3,000,000,000).

Timeline

• Act now. This change is safe to make immediately and does not depend on any Moody's deployment. Updating early removes the risk entirely.
• Complete and confirm your updates no later than October 31, 2026. Treat this as a backstop, not a target. It exists to leave buffer before the projected crossover, and waiting until Q4 risks colliding with your own year-end change-freeze windows.
• Based on current volumes, Batch ID values are projected to exceed the 32-bit limit in December 2026. This projection can move earlier if volumes grow; it is not a guaranteed date.
• No action is required if your integration already uses 64-bit types.

Questions? Contact your Moody's account representative or support team.