How to Fix “Invalid Result – This Request Could Not Be Processed by the Web Service” When Connecting to KashFlow

If you’re seeing the error:

Invalid result
This request could not be processed by the web service.

when trying to connect to KashFlow, it usually means that the relevant options have not been fully enabled inside KashFlow.

Below is a clear guide you can follow (or provide to your customer) to resolve this.

What the Error Usually Means

This message typically indicates that the feature or account you’re trying to access via the API is not fully enabled or configured in KashFlow. In most cases, you must:

1. Enable the appropriate settings in Chart of Accounts, and
2. Enable/allow access in API Settings.

If either part is incomplete, KashFlow’s web service returns the “Invalid result” error.

Steps to Resolve the Issue

1. Check Chart of Accounts Settings in KashFlow

1. Log in to your KashFlow account.
2. Go to Settings (or the equivalent menu in your version).
3. Open Chart of Accounts.
4. Locate the tick box to enable the journals. 
5. Confirm that:
   • The account(s) are active.
   • Any required flags or options for online/API usage are enabled, if applicable.

2. Check and Enable API Settings

1. In KashFlow, go to Account Settings.
2. Look for API Settings, API Access, or similar.
3. Ensure that:
   • The API is enabled for your account.
   • The API key / credentials used by your integration are correct and active.
   • Any IP restrictions or security settings are correctly configured to allow your system to connect.

If the API is disabled or partially configured, KashFlow’s web service won’t be able to process your request and will return the “Invalid result” error.

When to Contact KashFlow Support

If you’ve:

• Enabled the options in Chart of Accounts, and
• Confirmed the API Settings are correctly configured,

but you still get the same error, the next step is to contact KashFlow Support directly. They can:

• Check if there are any account-level restrictions or missing permissions.
• Verify your API configuration.
• Review their logs to see why the request is failing.