While clearing transactions electronically in bank reconciliations, we have run into the limit of SQL Server's integer column when check numbers are converted form a string into a number.  We followed KB article https://kb.blackbaud.com/articles/Article/62355 to get around the issue, but we foresee this as being an issue every month for us and possibly others.  If the column specification was increased to bigint, this would be resolved.