beres Help

Export to your accounting system

Getting reviewed documents out of beres and into your books. There are two ways, and you pick between them in the review workspace.

Before you can export

Every document in the batch must show Ready. The button stays disabled otherwise, with the tooltip "Every document must be ready before you can export".

Pick the delivery

At the bottom right of the workspace is a two-way switch: File and API push. The button beside it follows your choice and says exactly what it will do — Export 9 as file or Push 9 to accounting system.

File is available on every plan. API push is selectable only when your plan includes it and your document format supports it; otherwise that half of the switch is greyed out, with a padlock when it's the plan holding it back. When push is available it is selected by default.

The workspace footer control: a two-way switch reading File and API push, beside a button reading Push 3 to accounting system.
The switch picks how the batch goes out; the button follows it.

Option A — download an import file

Available on both SQL Account formats — Purchase Invoice (eStream) and Supplier Invoice (ARAP).

Choose File and export the batch. You get an Excel file which you then import in SQL Account as you normally would.

Import the file in SQL Account the same way you import any other. beres produces the file; it does not perform the import.

Option B — push over the API

Available on both SQL Account formats and on AutoCount Cloud, which is push-only — there is no file. API push is included on every current public plan, but saved credentials are required — see Connect your accounting API.

Choose API push and push the batch. The entries are created in your accounting system directly; nothing to download, nothing to import.

Two things to know:

Mixed formats in one batch

A batch is delivered one way, and each document carries its own format. If any document in the batch is set to a format that cannot be delivered the way you picked, beres refuses the whole batch and names the format rather than silently dropping those documents: "Purchase Invoice can't be pushed directly — download those as an import file instead." Switch that document's format in the workspace, or split the batch.

Getting a batch open in the first place

On a system that can produce import files, tick rows in Documents and click Prepare for export. On a push-only system such as AutoCount Cloud that bulk button isn't offered; open documents from the Inbox instead and push from the workspace.

Marking documents Processed yourself

On file targets, each row in Documents has a Processed toggle. Generating an export file sets it for you, but you can set it by hand — useful if you keyed a document in manually.

The toggle only applies to cleanly extracted documents on file targets. On API-push targets it is set by the push itself and is not yours to change.

Common messages

Message Meaning
"Direct API push isn't enabled on your plan." Current public plans include API push. Check Billing & plan for your organization's assigned plan; contact support if the message remains.
"Your export target doesn't support direct API push." Your target is file-only. Download the file.
"Nothing to push — N already pushed." Everything selected is already in your accounting system.
"You have reached maximum N concurrent database connections. There are N users logon currently." SQL Account has no free database connection for the API. Ask someone to log off SQL Account, then push again.
"Export failed — please try again." Try once more; if it repeats, contact support.
"Push failed — please try again." As above.

If the export downloads a small file that isn't a spreadsheet

When an export can't be produced, nothing downloads and the reason appears on screen — usually "nothing to export — all selected documents are blocked or unresolved". Go back and fix the flagged documents.

If documents never turn Processed after a push

The push failed somewhere between beres and your accounting system. Look for a ⚠ warning icon next to the document — the tooltip names the reason and reads "Push failed: … — fix the cause, then push again".

Fix the cause, then push the document again the normal way. Re-pushing a batch is safe: documents already delivered are skipped, never posted twice.

Common causes: API credentials no longer valid, SQL Account's concurrent database connection limit being full, a supplier without a code in your accounting system, or lines with no GL account. See The push didn't reach my accounting system.