8. Export policy
The settings that decide how strict beres is before a document can be exported. Admin only, at Settings → Export policy (/settings?panel=policy).
Which settings appear depends on your export target. Require an item code and Fallback GL account apply on targets that book lines by stock item — SQL Account (eStream) and AutoCount Cloud; on SQL Account ARAP, lines are booked by GL account instead and the panel shows an explanation in their place. Allow export when the line items don't add up to the document total appears only on SQL Account ARAP.
Require an item code on every line
On — every line must carry a stock item code before the document can be exported. Documents with unmatched lines stay Blocked until someone picks a code.
Off — lines can export without an item code, falling back to the GL account instead.
Turn it on if you track inventory. A purchase invoice line without an item code doesn't move stock, so a missing code silently breaks your inventory figures. Being blocked at review is much cheaper than discovering the gap at stock-take.
Turn it off if you don't. Forcing item codes on an organization that books everything to an expense account just creates work.
Fallback GL account
The account used when a line has no item code — either because the setting above is off, or because the target books by account.
Set this to a general purchases or expense account. It is a safety net, not a filing decision: everything landing here needs reclassifying later, so if you find most lines using the fallback, that's a signal your master data is incomplete rather than that the fallback is working.
Allow export when the line items don't add up to the document total
Shown on SQL Account — ARAP (IV / DN / CN) only, because that target books the invoice's printed total as the document amount. Off by default.
Off — a document whose line amounts don't sum to the printed total is Blocked until someone reconciles it in review.
On — the same difference becomes a warning instead of a blocker. The document still shows "Line sum … ≠ document total …" in review; it just stops being held back. Your accounting system receives the printed total either way — turning this on doesn't change a single exported figure, only whether beres waits for a person.
Turn it on if your invoices bundle tax or rounding into the total, so the lines legitimately never add up and every such document would otherwise need a manual pass.
Leave it off otherwise. A mismatch is usually a mis-read quantity or rate, and that's worth catching — see A document is Blocked.
Because it waives a check, beres records who turned it on and when, and shows that under the setting.
The waiver follows the target, not just the switch: move to an export target that derives its own total from the lines and mismatches are blocked again, with no change to this setting.
Choosing item code vs fallback
| Your situation | Require item code | Fallback GL account |
|---|---|---|
| You track stock in SQL Account or AutoCount | On | Set anyway, for odd lines |
| You book purchases to expense accounts | Off | Required |
| You're not sure yet | Off to start | Required |
Starting permissive and tightening later is easier than the reverse: turning the requirement on mid-stream doesn't retrospectively block documents you've already exported.