It is possible however that the system provides the key in some other way. If this is the case you will need to convert it to base32 as that is currently the only way that KeeOtp accepts keys. There is a feature request for alternate encodings. See #7 to follow that request.
# Ensure that the key is encoded correctly. Look up the key encoding used by the service. Google, Amazon, and Dropbox all use base32 to no additional encoding is needed. The spaces will need to be stripped out.
-# If your key is encoded using base64 or hex you will need to translate that to base32.
+# If your key is encoded using base64 or hex you will need to translate that to base32.
+There are several settings that can be specified when setting up the entry in KeeOtp. In addition to the key there is a step window and a digit size.
+# The most common step window is 30 seconds. KeeOtp allows alternate time steps to be specified. Be sure that if an alternate time step is specified that it is because the verifying system has specifically said that is what they use. If the time step doesn't match the server's expected time step then the code will not ever be correct. When in doubt, leave this setting at the default 30 seconds.
+# Code size is another setting that can cause incorrect codes. The most common size is 6 but 8 is also allowed. Be sure that this number matches the verifying service's expectations. When in doubt leave this value at 6 as most services use a 6 digit code.