English
+ Banking

From CAMT import to open item, prepared by the assistant.

Hegyon reads CAMT.053 and CAMT.054, assigns each entry to the right transaction, flags differences and shows your liquidity, you give the green light. Swiss banking, without the click-marathon.

01 · The problem

CAMT reconciliation isn't banking, it's detective work.

Every day CAMT.053 and CAMT.054 files arrive from two or three bank accounts. 250 entries a month, each one has to be assigned to the right transaction: incoming QR payment to a sales invoice, outgoing supplier payment to an AP invoice, salary run to employees, bank fee to expense, VAT advance payment to the VAT return. Doing this by hand takes two hours a day, and still misses the early-payment discount the customer subtracted.

02 · Under the hood

What Swiss banking actually requires.

Behind the simple reconciliation sits the full ISO 20022 universe, these five points are standard, not extras.

  • CAMT.053 / 054 / 052 complete, End-of-day, advisings, intraday movements, all three Swiss standard formats are read.
  • Auto-matching via QR reference, Swiss structured reference, ESR, and free-text purpose, the assistant recognises all three.
  • Multi-bank, multi-currency, Multiple bank accounts, CHF and EUR, with daily rate converted for the books.
  • Discount and difference detection, If the customer takes 2 % discount, the difference posts to expense automatically, not to an open dunning case.
  • Liquidity overview and cash forecast, Balance today, due receivables, planned payments, liquidity for the next 30 days at a glance.
03 · What you get back

3 bank accounts, 250 entries per month, how much time you reclaim.

An average Swiss SME with three bank accounts and 250 monthly entries traditionally spends around 12 hours a month on CAMT import, manual matching and clarification, usually in the hands of the bookkeeper, with peaks at month-end. With the assistant that drops to around 2 hours, because 95 % of entries are already matched via QR reference and purpose field. That's 120 hours a year, at a Swiss hourly rate of CHF 50 that's recovered capacity of CHF 6'000 per year, in bank reconciliation alone. The most valuable effect: you see every morning what your liquidity actually looks like, not only at month-end when the fiduciary delivers the numbers.

04 · Who it is for

Who bank reconciliation saves real work for.

This is built for Swiss SMEs that keep their books in-house and run their payments through one to four bank accounts: trades and construction, technical services, distribution, consulting. Typically invoices with a QR reference, a supplier payment run every one or two weeks, a fiduciary for the year-end close, and one person who has been ticking off the bank statement line by line.

It pays off most where incoming payments meet open invoices regularly and someone matches them by hand today. The more entries there are on a statement, the bigger the difference between matching and checking — and the sooner management sees what has actually been paid.

05 · Switching

The move starts at your bank, not with a project plan.

First you enable the daily camt.053 delivery in e-banking; at most Swiss banks that is a setting, at a few it is a short request to your relationship manager. Then you upload a closed previous month as a file and run it against your open items, without posting anything. That way you see, before the first productive day, which payments land cleanly through the structured reference and which need a hand. Nothing is posted until you approve.

After that, bank reconciliation is a short morning routine: read in the file or have it fetched automatically, decide the few unclear cases, approve. What you do not have to bring along is your history — old bank statements stay with your previous system or with your fiduciary, hegyon starts with the open items as at the cut-off date. An EBICS connection is not a prerequisite either: the file route is enough, and anyone who wants to connect directly later does so without rebuilding.

06 · The platform

Banking is one module — here is the rest.

07 · Frequently asked

What managing directors and bookkeepers ask first.

Which files do you need from our bank?

The bank statement as camt.053, the details behind batch credits as camt.054 and, if you want to see the day as it unfolds, camt.052. Your bank delivers all three through e-banking, usually as a daily file; some institutions require a one-off activation for it. Nothing more is needed: no separate contract, no interface programming, and existing payment orders carry on as before.

What about payments where the customer gives no reference?

hegyon matches those on amount, name of the ordering party and the text in the payment purpose, and puts the hit forward as a proposal, with the reason next to it. If nothing fits unambiguously, the entry stays in the list of open cases instead of slipping in somewhere. That is the part that needs your attention, which is exactly why it sits separately and not in the middle of the rest.

How are partial payments and batch credits handled?

A batch credit arrives on the statement as a single amount; the individual items behind it are in the camt.054. hegyon breaks the batch entry down into its single payments and settles each one against the invoice its structured reference belongs to. If someone pays only part, the remainder stays as an open item and carries on through dunning, with nobody having to add anything afterwards.

Can we also initiate payments, or only read them in?

Initiate as well. The approved invoices in accounts payable become a payment order as a pain.001 file, which you submit in e-banking; your bank's response comes back as pain.002 and shows, item by item, what was accepted and what was rejected. The signature rules stay where they belong: with your bank. hegyon prepares the order, people sign it.

Bank statements are sensitive. Where are they, and what does an AI model see of them?

Your data is hosted in Switzerland. Before anything is sent to an external AI model, our Sensitive Data Guard masks or blocks personal, contract and financial data, only the released, non-identifying content is forwarded, under no-training agreements. The matching itself, that is reference, amount and open item, runs as a calculation rule inside the application and needs no language model for it.

What happens if an entry was matched to the wrong invoice?

You undo the match and assign the entry to the right invoice. Nothing is deleted in the process: the original match, the correction, the person and the time are in the audit chain, as the GeBüV requires for traceable bookkeeping. For recurring entries without a reference, such as a bank fee, rent or a leasing instalment, you set up a rule once.

How does our fiduciary carry on working with this?

They get their own access with their own role and see what they are meant to see, or they pull the data out as an export for their closing software. Because every entry carries its document, its match and its approval with it, the round of queries about individual items falls away. The difference to today is mostly one of timing: at month-end the bank statement is already reconciled, rather than only then becoming a topic.

How reliable is the liquidity forecast?

As reliable as what is already recorded: receivables falling due, approved accounts payable, salaries, recurring direct debits. That produces a picture for the coming weeks which holds as long as nothing unrecorded comes along. What it cannot do is predict new business, or judge whether a late-paying customer will pay this time. It is a projection from your own figures, not a prediction.

See your bank reconciliation in the assistant, in 30 minutes.

We'll show you a CAMT.053 import that assigns 95 % in seconds, discount detection without a manual click, and a 30-day liquidity overview. No contract, no preparation.