<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>TILL blog</title>
    <link>https://tillbooks.ch/en/blog/</link>
    <atom:link href="https://tillbooks.ch/en/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Explainers on Swiss banking formats, agent-native accounting over MCP, and keeping Swiss books, from the team building TILL, the open-source ERP.</description>
    <language>en</language>
    <item>
      <title>EBICS explained: how a Swiss firm talks to its bank</title>
      <link>https://tillbooks.ch/en/blog/ebics-explained/</link>
      <guid isPermaLink="true">https://tillbooks.ch/en/blog/ebics-explained/</guid>
      <pubDate>Tue, 06 Oct 2026 08:00:00 GMT</pubDate>
      <category>Swiss banking</category>
      <description>EBICS (Electronic Banking Internet Communication Standard) is a standardised internet protocol for exchanging files between a company and its bank, used in Germany, France, Switzerland and Austria. The company registers three key pairs, for authentication, signature and encryption, and in Switzerland confirms them with a signed letter. It can then download statements such as camt.053 and, with a signing key, upload payment orders.</description>
    </item>
    <item>
      <title>MCP meets the ledger: can an AI agent keep the books?</title>
      <link>https://tillbooks.ch/en/blog/mcp-meets-the-ledger/</link>
      <guid isPermaLink="true">https://tillbooks.ch/en/blog/mcp-meets-the-ledger/</guid>
      <pubDate>Mon, 28 Sep 2026 08:00:00 GMT</pubDate>
      <category>Agents and MCP</category>
      <description>Yes, if the ledger enforces the rules rather than the agent. In TILL, an open-source Swiss ERP, an agent posts through the MCP verb post_entry. Every call carries an idempotency key, so a retry never double-counts. By default the write becomes a proposal a person approves. The engine refuses unbalanced entries and locked periods, and a posted entry is only ever reversed, never edited.</description>
    </item>
  </channel>
</rss>
