Plan an Abacus document integration before adding AI

Abacus describes AbaConnect as a component for transferring data to and from its applications. Its documentation is organised by application, version and interface. This does not establish that every installation can accept every document or operation. Check the intended import against the software you actually run. Official AbaConnect documentation, checked on 26 September 2026.

Describe the requirement more precisely than “PDF to Abacus”. For example: supplier invoices arriving in a designated mailbox are assigned to the correct company, checked for required fields and duplicates, approved and transferred to an agreed destination module. Your partner must confirm whether the result is an attached document, a prepared entry or another type of record.

Reading and writing are separate requirements. Matching may only require read access to supplier and cost-centre records. Creating or changing a transaction requires a supported write path. An available export does not prove an equivalent import exists. Automating the user interface also does not replace a documented agreement about a supported integration.

Before requesting an estimate, record the company, application, version, deployment arrangement, necessary options, responsible contacts and intended destination object. Identify who can approve changes to master data and access rights. This small inventory prevents technical and accounting assumptions from being buried in an implementation proposal.

These six questions settle an Abacus document integration with the support partner before an estimate:

Ask the partner to demonstrate both a successful import and a deliberate rejection. A polished demonstration with one clean invoice rarely explains missing fields, unknown references or partial success. Those cases usually determine how much manual work remains after launch.

Also establish a separate test environment or another approved test procedure. Synthetic records should be clearly identified, and the team should know how to remove or reverse them without mixing them into live accounting. Do not assume the same connection can safely serve development and production.

A mapping connects source information to the meaning of a destination field. Include provenance, format, transformation and behaviour when a value is absent. “Date” is insufficient: document date, receipt date and posting date have different purposes. A technically valid value can still be wrong for the accounting task.

The following is an illustrative internal mapping, not an AbaConnect schema:

The chosen interface documentation determines actual field names, required values and supported operations. Keeping that distinction explicit avoids a seemingly finished integration failing because its output does not contain the ERP references that the import expects.

Decide who owns transformations. The extraction service may identify a printed supplier name; the business mapping chooses a verified supplier record. Those are different decisions. Preserve the original value so that a reviewer can explain a match and correct it without rerunning the whole process.

A mapping example with several different dates

Suppose an invoice is dated 28 August, arrives on 2 September and is approved on 5 September. These are three separate facts in this synthetic example. Accounting may define another date or rule for the posting period. Do not collapse them into a generic timestamp.

Preserve invoice date, arrival and approval separately. Accounting determines the target field and period rule; implementation records and follows that approved mapping. The difference between document date and processing period can then be explained later.

Apply the same principle to money. The printed total, an independently calculated check total and any converted amount are different values. Retain calculation rule and currency. A discrepancy needs targeted review rather than silent rounding or repeated model calls until a plausible answer appears.

The situation. This is a synthetic planning example, not a completed client integration. A Swiss services company receives an invoice for CHF 2,450.00. The supplier exists in its master data. The accompanying message says “Alpine project”, but that phrase is not a valid cost-centre identifier.

What the workflow does. The intake process assigns an internal case identifier. Extraction stores the invoice number, date, amount, currency and source locations. Duplicate checking finds no existing case. Master-data matching identifies one supplier but cannot determine one cost centre. The workflow creates a review task and does not create a new cost centre from the free text.

Review and transfer. The responsible person selects an existing reference and records why it applies. Only the approved record is sent through the confirmed import path. The workflow stores the acknowledgement and destination identifier. Accounting then opens the result and checks the company, total, source attachment and processing state. This proves the transfer path. Payment remains a separate decision.

The acceptance record. A useful acceptance record contains both the expected and actual result. If the source is attached but the record is in the wrong company, the case fails even though the transport succeeded. If the document cannot be opened by the intended reviewer, that also remains an unresolved operational defect.

A connection failure after submission is especially important. The destination may have accepted the request even though its response never arrived. Repeating a create operation blindly could create another transaction. Agree how the workflow searches for or confirms an already submitted case using a stable reference. The actual interface must support the chosen method.

An Abacus transfer workflow should separate at least four states:

• Not yet submitted.
• Result uncertain: an uncertain result needs destination reconciliation first.
• Rejected for a business reason: a rejected record needs corrected data or mapping.
• Acknowledged.

Successfully uploading a file does not prove that every transaction within it was accepted.

Check multi-company handling as well. Identical supplier names or invoice numbers must not cause records to be merged across companies. The company identity belongs in the intake record and every subsequent matching key. Limit the connection to the companies and operations required for this workflow.

Synthetic test: a partially successful batch

The batch. A batch contains ten approved cases. Seven are acknowledged, two are rejected because references are unknown and one loses its response. The operator must distinguish all three groups. Batch submitted does not adequately describe the result.

Handling each group. Store destination identifiers for the seven confirmed cases. Keep the two rejected cases open with reasons and owners. For the uncertain case, inspect the destination using the agreed reference before another attempt. Resubmit only after establishing that creation did not occur and retry is appropriate.

Reconciliation. Reconciliation initially shows ten source cases, seven confirmed, two rejected and one uncertain. After resolution, it should show ten confirmed outcomes, never eleven. Include these expected counts in acceptance so operators can identify repeat-processing errors without interpreting lengthy technical logs.

Discuss three concrete Abacus transfer outcomes with the support partner:

1. Documents only: documents are made available while entry remains in the existing workspace.
2. Reviewed information: reviewed information is imported for further processing.
3. Approved transaction: a transaction already approved by the business is transferred.

Each has different requirements for permissions, acknowledgement and correction.

Assess them using the same questions: which manual activity disappears, which remains and which operational task is introduced? An existing import may already carry the required information. Conversely, missing source linkage or a required processing state must be resolved before implementation.

Record the chosen route and rationale. The partner should identify the interface and installed scope. A general statement that AbaConnect will handle it is insufficient: the interface family alone does not establish support for the required object, fields and operation.

Roles

Name the business owner, Abacus support partner and integration operator. Accounting approves mapping and corrections; the partner confirms supported interfaces and ERP changes; the operator monitors delivery, permissions and uncertain states. One person may hold several roles, but the responsibilities should remain explicit.

After an upgrade

Agree who reruns acceptance after an Abacus upgrade and authorises reconnection. Changes to required fields or master data should be discovered before the next month-end. A documented trial transfer provides a concrete checkpoint.

During an outage

For an outage, define which cases staff handle manually and how those actions are reconciled back into the integration record. Otherwise a correctly restarted import can recreate transactions already entered during the outage. Recovery therefore includes counts and business state, not simply restoring connectivity.

Acceptance testing for an Abacus document integration should include six cases:

• a normal document
• a repeated submission
• an unknown reference
• a missing required value
• a credit note
• an interrupted handoff

For each, record the expected destination state, responsible person and accessible source evidence. Test that an unauthorised user cannot access the file or accounting information.

Measure time to acknowledged completion, manual correction rate and unresolved transfers. High extraction accuracy is of limited value when the import requires daily repairs. Repeat the same compact acceptance set after a software or mapping change before resuming automatic processing.

Project cost includes existing licences, partner work, mapping, review and operation. Without knowing the installed scope, a universal Abacus price would be misleading. A useful quotation request therefore includes the intended transfer, representative documents and exception cases. The result should be a reviewable integration proposal with explicit prerequisites, supported operations and operating responsibilities.

These guides and service pages cover the decisions next to an Abacus document integration:

• AI document processing: capture, review and transfer
• Automate Swiss fiduciary document and client workflows
• Automate bexio document intake and review
• Connect n8n to ERP systems with supported interfaces
• Detect duplicate invoices with business keys and review

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