Error mapping design pattern for Java [on hold]

I'm implementing an application, which receives around 70 error messages or codes from another depending application. I need to map those 70 error messages or code to 5 custom error messages before sending to end user.

Is there any better design pattern to implement this for java? Will chain of responsibility pattern work for this use case?