Automating Bexio Vendor Bill Exports into SIX pain.001.09 via SFTP, API, and Google Drive
Business Use Case & Requirements
Finance teams using Bexio need flexible ingestion pipelines—whether dropping Excel/CSV vendor sheets into an SFTP directory, syncing via Google Drive folders, or posting directly via REST API—to convert vendor bills into bank-ready SIX pain.001.09 XML.
Technical Architecture & Pipeline Execution
The pipeline monitors configured input channels (SFTP, Google Drive, email attachment parser, or direct API webhook), normalizes Bexio semicolon-delimited Excel/CSV exports, validates Swiss QR-bill reference numbers, and deposits ready-to-sign pain.001.001.09 XML files into designated outbound SFTP or e-banking folders.
Lieferant;IBAN;Betrag
Office Supply;CH48...;345.80
<Ref>210000...</Ref>
</CstmrCdtTrfInitn>
Standards & Compliance Highlights
- Swiss interbank clearing strictly mandates pain.001.001.09 formatting for supplier credit transfers.
- Structured creditor reference (SCOR) nodes preserve QR-bill reference strings without truncation.
- Multi-channel ingestion (SFTP, API, email, Google Drive) decouples ERP export timing from bank signing windows.
Industry Comparison & Perspective
While legacy desktop banking clients (such as Multiline or traditional EBICS software) require manual file transfer steps and lack cloud-native Google Drive or email intake hooks, this architecture operates as an event-driven omnichannel translation engine.