Separate the client boundary first

Create one organisation for each company whose books are being maintained. The organisation owns its document email, linked Telegram senders, master data, accounting target, credentials, members and billing context. This is the boundary that prevents one client’s supplier mapping from influencing another client.

A firm-level administrator may need visibility across organisations, but reviewers should receive only the company access required for their work.

Give clients a forwarding habit, not an accounting login

A person can send documents by email or Telegram without receiving review access. Likewise, a bookkeeper can review without being a sender. Separate these roles so client staff do not need to learn the accounting workspace simply to hand over a PDF.

For clients whose invoices already arrive by email, forwarding to the private address is the lowest-friction route. Telegram is useful for staff photographing paper documents in the field.

Load the right master data before live processing

For SQL Account eStream, import or sync suppliers and stock items. For SQL Account ARAP and AutoCount Cloud, import or sync suppliers and chart-of-account data. Confirm the export target before importing because master data is kept per target.

Human corrections teach mappings inside the organisation. They never cross into another client’s data.

Make review ownership explicit

Choose who clears document fields, who approves accounting codes, and who delivers the final batch. A small firm may use one person for all three. A larger team can separate reviewers and admins while preserving an audit-friendly status trail.

Batch work can include up to 100 documents. Use smaller batches when one reviewer is new to the client or the supplier set contains many exceptions.

Deliver according to each client’s system

AutoCount desktop is not currently supported. beres also does not provide MyInvois submission or e-Invoice compliance functions.

Measure the firm benefit honestly

Report total human minutes per document, review-required rate, accounting-delivery success and the number of client follow-ups for missing or unusable files. Do not turn a best-case clean PDF into a claim about the entire client portfolio.

No client case study is published here yet. A real case study should include verified volume, before-and-after time, document mix and measurement dates. Until those inputs are supplied, this page remains a workflow guide.

Map a client workflow