Why is my accounting software not connecting to my bank?

Bank connection problems often start with simple triggers. Expired passwords or multi-factor authentication (MFA) resets on your bank’s side can block the feed. Financial institutions sometimes roll out API changes that require an updated integration on the accounting software sync side. Network timeouts, server maintenance, and certificate errors also interrupt transactions. Always confirm the bank’s status page before diving into deeper troubleshooting.

Log into your accounting platform and navigate to the bank feeds or connected accounts section. Verify that the login credentials match your current bank profile and that MFA prompts haven’t been missed. Look for a “Reconnect” or “Refresh” button—manually triggering a sync often clears stale sessions. If the connection shows as “expired” or “error,” remove the bank and re-add it to generate a fresh API token. This simple step resolves many integration issues without further effort.

API errors typically surface as “400 Bad Request,” “401 Unauthorized,” or “500 Internal Server Error” in connection logs. A 401 almost always means invalid credentials or a revoked access token—re-authenticate first. A 400 indicates your software is sending malformed requests, which may require an update from the vendor. Server-side 500 errors on the bank’s end are temporary; wait a few hours and try again. If error codes persist after reauthorizing, the accounting software’s AI agent can guide you through a diagnostic workflow, checking for known integration issues with your specific bank.

For complex cases—repeated API errors, data mapping failures, or connections that drop after a few days—the shared support inbox connects you directly with a human team. The support staff already sees your account context, including recent sync attempts and error logs, so you don’t have to re-explain the situation. Use this channel when automated troubleshooting doesn’t restore your accounting software sync within a reasonable window.

How do I troubleshoot connection errors?

Start by verifying your bank login credentials and any pending MFA approvals. Then, manually refresh or remove and re-add the bank in your accounting software. Check the bank’s service status page for outages. If the error persists, consult the software’s AI agent for a step-by-step diagnosis tailored to your financial institution.

What are common API issues?

Most API errors are authentication-related (401 Unauthorized) due to expired tokens or password changes. Others include request format errors (400 Bad Request) after an API update, rate limiting (429 Too Many Requests) from excessive polling, and server faults (500) on the bank’s side. Reauthorizing the connection and spacing out sync intervals can mitigate many of these problems.

Why is my data not updating?

Data stops updating when the connection loses authorization, the sync schedule is paused, or the bank’s feed format changes and requires a new mapping. Some banks enforce data-retention windows that can cause gaps. Review sync status in your software; if it shows “connected” but no transactions, force a manual refresh. If the issue continues, reach out via the shared support inbox for a deeper look at the integration.