The export won't run
The export button is disabled
Every document in the batch must show Ready. One document showing Needs input or Supplier unmatched blocks the whole batch.
Look down the document rail for the non-Ready pill and fix that document, or drop it from the batch and export the rest.
The API push half of the switch is greyed out
The footer switch offers File and API push. Push is selectable only when your plan includes direct API push and the document's format supports it.
- A padlock on it means the plan is what's holding it back — check Billing & plan.
- No padlock, just greyed out, means this format delivers by file only.
An error message appears instead of a download
When an export can't be produced, no file downloads — the reason appears as an on-screen message instead:
| Message | Meaning |
|---|---|
nothing to export — all selected documents are blocked or unresolved |
Nothing in the batch is exportable. Fix the flagged documents. |
no documents selected |
The selection was lost. Re-select and try again. |
select at most 100 documents |
Batch limit. Split it. |
… has no import file — those documents are delivered by API push. Export the rest separately, or push them. |
At least one document in the batch is set to a format with no import file (AutoCount Cloud). Switch that document's format in the workspace, or split the batch and push those instead. |
no exportable documents found |
The selected documents no longer exist or aren't yours. Refresh and re-select. |
not authorized |
Your session expired. Sign in again. |
Validation messages by document format
These appear on the document, and block it from the export file.
SQL Account — Purchase Invoice (eStream)
| Message | Fix |
|---|---|
| "SQL Account requires a counterparty Code" | Pick the supplier. |
| "Line needs ItemCode or Account" | Give the line an item code. |
| "Line needs a Description_DTL" | The line description is empty. Type it in. |
| "Missing/invalid Qty" | Enter the quantity. |
| "No DocNo — one will be generated" | Warning only. Nothing to do, but entering the real invoice number is better for reconciliation later. |
SQL Account — Supplier Invoice (ARAP)
| Message | Fix |
|---|---|
| "ARAP requires a supplier Code" | Pick the supplier. |
| "ARAP requires a DocNo (invoice no)" | Enter the supplier's invoice number. |
| Needs accounts warning | Lines have no GL account. Assign accounts in the workspace, or set a fallback GL account in Settings → Workflow. |
AutoCount Cloud
| Message | Fix |
|---|---|
| "AutoCount requires a supplier (creditor) Code" | Pick the supplier. |
| "AutoCount requires the supplier invoice no" | Enter the invoice number. |
| "Line sum 1,240.50 ≠ document total 1,245.00 — fix in review" | Reconcile the lines. See A document is Blocked. If your totals never reconcile by design, an admin can waive this in Workflow. |
| "N line(s) have no GL account — assign accounts in Prepare" | Assign GL accounts to those lines. |
"Export failed — please try again."
A generic failure. Try once. If it repeats with the same batch, try exporting one document from that batch to find whether a single document is the cause, then contact support with that document id.
The file exported but SQL Account rejects the import
beres produced a valid file; your accounting system disagreed with its contents. Usually one of:
- A supplier or item code that exists in beres but was deleted or renamed in the accounting system. Re-sync your master data.
- A document date in a closed accounting period.
- A duplicate invoice number your accounting system already holds.
The accounting system's own error message names the offending row — start there.