As of right now, we believe this is a possible error when running payment confirmations in the GL destination when a custom field is involved. As of right now, the system doesn't seem to let through custom fields in GL payment confirmations. We have one client (Amerihome) that has dealt with this and no solution has been found as of yet. The team is working on a fix.
The error will look like this: