Automate Swiss fiduciary document and client workflows

An inbox is not a complete picture of an engagement. One message can concern several entities, periods and document types. A bank statement may be readable but cover the wrong month. Record the engagement, legal entity, period and document status separately.

Create an expected-document list for a selected client type. Include only the records actually needed, the responsible contact and accepted submission routes. Standardise receipt without hiding exceptions: a missing record, unreadable file and professionally unresolved transaction each require a different next action.

The following table shows five proposed document states for a fiduciary client process, what each state establishes and who owns the next step.

Do not derive completeness from file count. Ten uploaded documents might contain nine required records and one duplicate.

Rules first. Consistent filenames and structured exports can often be handled by straightforward rules. AI can assist when subject lines vary, document types need identifying or free-text client replies require routing. Its output remains a proposal with identifiable source material.

Three activities. Separate three activities: recognising text, extracting fields and making a professional decision. A date printed on an invoice is different from the appropriate accounting period. An extracted VAT figure is not a confirmed tax treatment. The reviewer therefore needs the original and the relevant passage, not just a polished summary.

Critical fields. Define critical fields such as client, amount, currency, supplier and payment details. An uncertain client match stops transmission. An unclear description may require only a manual addition. A high model confidence score alone is not a defensible substitute for these checks.

bexio. bexio offers an officially documented API. Its existence does not establish that every file can become a complete accounting record automatically. Check the required object type, permissions, client connection and acknowledgement for each individual operation.

Abacus. Abacus documents AbaConnect interfaces by application and version. The appropriate interface depends on the installed environment and enabled modules. Ask the responsible Abacus partner to confirm the precise import route.

Mapping table. Begin with a small mapping table: source, document, destination field, required value, permitted values and error owner. Do not confuse a successful file upload with creating a supplier bill or approving an accounting entry. Our guides to bexio documents and Abacus document workflows examine those checks in detail.

What arrives. A fictional fiduciary firm expects August bank records, supplier invoices and an explanation of a privately paid expense from a trading client. The client uploads three files: the July statement, an invoice for EUR840 and a phone photograph of the expense. The same invoice also arrives as an email attachment.

Duplicate and currency. The workflow flags the repeated invoice for review and preserves both incoming references. It does not treat the EUR invoice as a CHF document. Currency conversion must follow the source and method approved by the professional team; an assistant must not invent an exchange rate from memory.

Wrong period and unreadable photograph. The July statement is recorded as received but does not satisfy the August requirement. The amount on the photograph is unreadable. The follow-up is therefore specific: “Please upload the August bank statement and a readable photograph of the expense.” It does not request the already usable invoice again.

Outcome. After review, only the approved invoice case is passed onward. The expense remains professionally unresolved. This makes completed work visible while explaining why the monthly close as a whole is not ready for approval.

Current state. An automatic reminder may coincide with a new upload. Check the actual document state immediately before sending. A file that has arrived must not be requested again simply because an earlier list has not been refreshed.

Language and channel. Agree on a clear language and suitable contact channel. A French-speaking client needs the same underlying requirement as a German-speaking one. Translated terms, periods and amounts must agree. Language does not change the engagement or the evidence required.

Limits. Limit repeated reminders and assign unresolved cases to a person. After several unsuccessful messages, a telephone clarification may be more useful than another automatic copy. Measure avoidable follow-up work, not merely the number of reminders sent.

Audit trail. The Swiss Federal Tax Administration explains the audit trail as traceability from an individual document through the accounts to the VAT return and back. For workflow design, the original, correction, approval and transferred record must remain connected.

Corrections. An AI output should therefore be an editable preparation stage. If an amount is corrected, retain who changed it and the supporting source. Do not overwrite information in a way that makes the origin of an accounting entry incomprehensible later.

Retention. Set retention and deletion by record type and applicable obligation. A retention period for technical error logs is not a universal period for accounting documents. Conversely, temporary AI copies do not automatically need the same retention as the authoritative archive without a justified purpose.

Responsibility. The FDPIC’s guidance on outsourcing explains that responsibility for data protection remains with the outsourcing controller. Review instructions, subprocessors, processing locations, access and support for individuals’ rights. A Swiss data centre alone does not answer these questions.

Client separation. Technical separation between clients is especially important. A staff member authorised for client A must not retrieve client B’s records through an AI search. Test similar company names, shared contacts and permissions that have since been removed.

End of engagement. When an engagement ends, handle outstanding tasks, access and additional copies in an orderly way. Returning client documents and disabling a login are separate operations. Each needs a verifiable completion state and an owner who can explain any records that must remain under an applicable retention obligation.

Compare data entry, professional review, clarification and correction effort before and after the change. Faster intake is of limited value if review becomes more burdensome. A completed monthly case or professionally approved document provides a useful denominator, depending on the agreed scope.

Acceptance should include a wrong-client match, foreign-currency invoice, duplicate, late upload and a lost acknowledgement after a successful transfer. That final case must not automatically generate a second accounting entry. The workflow is operationally ready when these exceptions have accountable owners and traceable outcomes.

The following pages and articles cover related decisions for fiduciary and tax-firm workflows.

• AI automation: tasks, selection and implementation
• AI automation for tax firms
• Austria’s filing quota: deadlines and tax-firm workflows in 2026
• AI workflow approvals: who checks which action?
• Automate bexio document intake and review
• Plan an Abacus document integration before adding AI
• Request missing client documents from an explicit checklist

For a workflow review, start with the task, systems involved and typical exceptions. Discuss it with modernagents.