Hestur AIHestur
    All work
    Finance AutomationFinance / Accounting

    Kontera to Topal Invoice Registration Pipeline for Fiechter

    Automated ingestion of supplier invoices from Kontera's document processing platform and registration into Topal — Switzerland's leading SME accounting software — handling both Accounts Payable and General Ledger entry types.

    2 min readJun 1, 2025
    fiechter-invoice-pipeline.com
    Kontera to Topal Invoice Registration Pipeline for Fiechter screenshot

    Key result

    2

    invoice types (AP & GL) handled in one automated pipeline

    Type

    Finance Automation

    Automation

    Industry

    Finance / Accounting

    2025

    Outcome

    Manual invoice entry eliminated

    The Problem

    Fiechter, a Swiss finance and accounting firm, processes a high volume of supplier invoices captured through Kontera — an intelligent document processing platform that extracts structured data from incoming PDFs and scanned documents. The bottleneck was getting those invoices into Topal, the firm's accounting system, without manual re-entry. The added complexity: invoices had to be handled differently depending on whether they were Accounts Payable entries or General Ledger postings, each with distinct Topal record structures.

    What We Built

    A GoFlow pipeline that picks up processed invoice data from Kontera and registers it in Topal automatically. The workflow handles authentication, data transformation, routing by invoice type, payment creation, and error recovery — with no manual steps in the happy path.

    Kontera Enrichment & Transformation

    The workflow enriches each incoming Kontera invoice with additional metadata, then transforms the record into Topal's invoice format — mapping supplier identifiers, cost centres, VAT codes, and posting dates.

    Topal Authentication with Auto Re-Login

    The workflow logs into Topal's API and extracts the session token. If the token expires mid-run, a conditional branch detects the auth failure and re-authenticates automatically before retrying — preventing a full batch failure from a routine session timeout.

    AP vs GL Routing

    A FlowSwitch node routes each invoice by type. Accounts Payable invoices create a creditor invoice and a corresponding payment record in Topal. General Ledger invoices follow a separate path with direct journal posting logic. Each route has its own error handling and fault recovery — including a dedicated path for invoices that carry no payment.

    Fault Recovery

    The workflow catches multiple failure modes — Topal API faults, transformation errors, and no-payment edge cases — and either retries automatically or routes to an error flow. No record is silently dropped.

    Stack

    • GoFlow — workflow orchestration
    • Kontera — intelligent document processing platform
    • Topal — Swiss SME accounting software
    • REST API integration (both platforms)

    Result

    Fiechter's invoice processing now runs without manual data entry. Kontera captures the document; GoFlow handles the rest — routing, creating, and posting into Topal based on entry type. The error-handling design means failed records are surfaced rather than lost, giving the accounting team full confidence in the pipeline.

    Portfolio

    See all our work

    All projects