Glossary

Terms used in beres, in plain language.

Alias A remembered link between what a document says and what your accounting system calls it — "SYARIKAT MAKANAN SB" on a delivery order to supplier code 400-S012. Aliases are built from your master data and grown every time someone confirms a code during review.

Blocked A document missing something essential, most often the supplier code. It cannot be exported until fixed. See Document statuses.

Chart of accounts Your list of GL account codes. Required by the ARAP and AutoCount Cloud targets, which book lines by account rather than by stock item.

Connect link A single-use, 15-minute link that binds one Telegram chat to your organization. Generated per person under Settings → Channels.

Document One PDF or image received by email or Telegram — a purchase invoice, delivery order, or similar. Each accepted email attachment becomes its own document.

Document email Your organization's private address for email ingestion. Attachments sent or forwarded there become documents. Admins can copy, pause, resume, or rotate it under Settings → Channels. See Send documents by email.

Export Producing an Excel import file from reviewed documents, which you then import into your accounting system. Contrast with push.

Export target The accounting system beres prepares documents for. Determines which fields are mandatory, which master-data lists you need, and whether push is available. See Choose your export target.

Extraction Reading a document to pull out the supplier, date, document number, and line items.

Failed The document could not be read at all — a system error, not a data problem. On a paid plan you can retry it yourself from the Documents list, up to twice. On the Free plan there is no retry button; send the document again.

GL account General ledger account — the expense or income code a line is booked to, like "Food Purchases". Used by ARAP and AutoCount Cloud.

Invalid The terminal state after someone reported a document as unusable and support confirmed it. It no longer counts against your monthly allowance.

Master data Your own codes: suppliers, stock items, chart of accounts. beres matches documents against these so entries arrive carrying the codes your accounting system expects. See Import your master data.

Master admin The role that manages every current and future organization in one organisation group. Master admins can create and rename companies, switch between them, and manage other master admins.

Needs review The document was read, but something needs a person — an unmatched item, a missing quantity, a total that doesn't reconcile.

Merged document Two or more uploads combined as pages of one document. beres normally detects and combines these automatically. The earliest received upload becomes page 1. Manual merge and unmerge correct missed or incorrect grouping. See Correct an automatic page merge.

Optional column An extra field your accounting system supports but doesn't require, such as Project or Area. Can be left off, set to a fixed value, or filled from a reference list.

Organization A company workspace inside beres. Holds one set of books, documents, master data, linked chats, team members, settings, and billing. Several organizations can belong to one organisation group.

Organisation group The set of companies managed by the same master admins. Company data remains separate inside the group.

Overflow price The per-document rate charged past your plan's included allowance. A plan with an overflow price keeps processing past the limit; a plan without one stops.

Processed The document has reached your accounting system. Separate from status — a document can be Extracted but not yet Processed.

Push Creating entries directly in your accounting system over its API, with no file to download or import. Needs a paid plan and saved credentials. Contrast with export.

Ready The readiness pill in the review workspace meaning a document has nothing outstanding and can be exported.

Reference list A code-to-value lookup backing an optional column — for example a list of project codes.

Counterparty The other party on a document — a supplier on a purchase invoice, a customer on a sales document. Duplicate matching and code resolution work on the counterparty, whichever side it is.

Reviewer The role that can do the whole daily job — receive, review, export, and manage master data — but not change organization settings, channels, export target, or billing.

Resolution Matching what was read on a document against your master data to produce actual codes.

Status Where a document is in the pipeline: Received, Processing, Extracted, Needs review, Blocked, Failed, or Invalid. Note that Processed and Duplicate are not statuses.

Stock item A line-level product code used by SQL Account (eStream). beres sends the item code; SQL Account gets its GL posting account from the maintained stock group or item setup.

Terms Payment terms for a supplier, such as 30 days. Carried onto the entry where the export target uses it.