The push didn't reach my accounting system

Symptom: you pushed a batch, no error appeared, but the documents never turned Processed and nothing shows up in your accounting system.

First, rule out the ordinary causes

• Give it a moment. The push runs in the background. Documents flip to Processed one at a time as they land.
• Check you actually pushed. On a file target the action produces a download, not a push. Only SQL Account (eStream), SQL Account ARAP, and AutoCount Cloud push over the API, and only on a plan with direct API access.
• Check the right account book. On AutoCount Cloud, entries go to the account book id in your settings. If that's wrong, the push succeeds — into somewhere you aren't looking.

Find out why it failed

The push runs in the background, so the page reports the batch as sent before the individual documents land. A failure shows up on the document itself, not on the page you pushed from.

Look for a ⚠ warning icon next to the document in your Inbox or Documents list. Hover it — the tooltip reads "Push failed: … — fix the cause, then push again" and names the underlying reason.

If a document didn't turn Processed, treat it as failed rather than still pending.

Likely causes

Credentials no longer valid

The commonest cause, and it affects every document at once rather than a few. Keys get rotated in the accounting system and beres is still holding the old ones.

Go to Settings → Export target and click Test connection. If it fails, re-enter the credentials. See Connect your accounting API.

If credentials were never entered at all, the underlying error is "SQL Account credentials not configured for this org — set the org's API keys and host in Settings → Export target".

SQL Account: maximum concurrent database connections reached

If the warning says "You have reached maximum N concurrent database connections. There are N users logon currently.", every SQL Account database connection allowed by your license is already in use. The API cannot open another connection, so the push cannot proceed.

Ask someone to log off SQL Account. Once a connection is free, push the document again normally.

A supplier has no code in the accounting system

The document carries a supplier code that beres knows but your accounting system doesn't — usually a code that was deleted or renamed after you imported master data. Re-sync your master data and push again.

Lines have no GL account

On ARAP and AutoCount, every line needs a GL account before it can be posted. Assign accounts in the workspace, or set a fallback GL account in Settings → Export policy.

AutoCount: supplier settings the document can't carry

AutoCount requires a credit term and a purchase location on a purchase invoice. These come from your settings rather than from the document, so a missing one cannot be caught during review — it only fails at push time, per document.

If AutoCount pushes fail while everything looks Ready in review, this is the first thing to check with support.

Retrying

Fix the cause, then push the document again the normal way — select it and push, exactly as the first time.

Pushing is safe to repeat. A document already in your accounting system is never posted twice, so a retry cannot create duplicates. This also means you can safely re-push a whole batch when only some of it failed: the ones that succeeded are skipped.

If the same document fails repeatedly with the same reason and the tooltip doesn't tell you enough to act on, contact support with the document id and the exact message.

What to tell support

• The document ids that didn't turn Processed.
• Your export target and, for AutoCount, your account book id.
• Whether Test connection passes right now.
• Whether it's some documents or all of them — that distinction separates a credentials problem from a data problem.