Zoho Books Consultant, Switzerland

QR references and automatic payment matching

The QR-bill solved one Swiss problem and created a design choice. Invoices can carry a structured QR reference, which requires a special QR-IBAN from your bank, or an international creditor reference used with a normal IBAN. Both let customers pay with the reference attached. The choice affects how your bank reports incoming payments and how Zoho Books can match them.

I settle this with finance and your bank before touching templates:

• which accounts receive customer payments, and whether a QR-IBAN is set up for them
• how the reference is built so each one points to a single invoice or customer
• whether the bank sends detailed credit notifications or only a statement
• how those files reach Zoho Books, by feed or by import

Matching rules then handle the everyday exceptions: a customer paying two invoices with one transfer, a payment short by a bank charge, a deduction for a credit note the customer already applied. Each exception has an owner and a standard treatment.

I test the loop end to end: issue invoices, pay them from a real banking app using the QR code, import the bank data and confirm the match. The QR-bill layout itself is covered on my Zoho consultant Switzerland page; here the focus is getting paid invoices closed without manual work.

Paying suppliers from QR-bills and bank files

Most Swiss supplier invoices arrive with a QR-bill too. That is useful: the payment part contains the creditor account, amount, currency and reference, so nobody needs to type them. The question is how that data gets from the paper or PDF into Zoho Books and then into a payment.

Options I compare with finance:

• Scan into Zoho. Check whether your edition or an add-on can read the QR code from a scanned supplier invoice and fill the bill and payment details.
• Scan in e-banking. Many teams scan QR-bills directly in their banking software and record the bill separately in Zoho, which works but splits the process.
• Pay from Zoho. Bills are approved in Zoho Books and exported as a payment file in the XML format your bank specifies, then uploaded to e-banking for release.

Whichever route you choose, the controls are the same: approval before payment, a second person releasing the file in e-banking, supplier bank details changed only through a controlled process, and payments matched back to bills after execution. I test the payment file with your bank, preferably with a small real payment, before the first full run. Suppliers paid in euros or other currencies need their own checks on bank charges and exchange differences.

Reviewing Swiss VAT figures before the fiduciary files

Your fiduciary decides how Swiss VAT applies to your company, including whether you use the effective method or a simplified method. Zoho Books has to follow that decision and produce figures the fiduciary can file without rebuilding them.

I set up a review routine for each VAT period:

• Report versus ledger. The Zoho VAT summary is compared with the balances of input and output tax accounts. Any difference is explained before the return is prepared.
• Revenue versus taxable turnover. Total revenue in the ledger is compared with turnover declared, with exports, exempt items and non-taxable income listed separately.
• Import VAT. Where goods are imported, import VAT documents from customs or the forwarder are booked consistently, so input tax claims match the paperwork.
• Foreign services. Services bought from abroad that may require you to declare tax yourself are flagged for the fiduciary's attention.
• Corrections. Adjustments from the previous period are recorded clearly rather than buried in regular entries.

The routine produces a short pack the fiduciary receives with the figures: summary, reconciliations and a list of open questions. Over a year, the same packs make the annual turnover reconciliation far easier. Product background sits on my Zoho Books consultant page.

Year-end handover and moving from a Swiss accounting package

At year end the fiduciary prepares statutory accounts and the tax return. They need a predictable set of information from Zoho Books, and the easiest way to provide it is a pack agreed in advance: trial balance, a list of unpaid customer and supplier invoices, bank reconciliations, a list of accruals and deferrals, fixed asset additions and stock values if relevant. I build the reports and a checklist so the pack looks the same every year.

Migration into Zoho Books usually comes from a Swiss accounting package, sometimes with a separate invoicing tool. The sequence I follow:

• agree the cutover date with the fiduciary, ideally at a year or quarter boundary
• load balances from the fiduciary's closing trial balance into the agreed accounts
• bring over unpaid customer and supplier invoices individually, with their references
• check bank details, payment terms and language of every customer and supplier first
• keep the old package accessible for lookups during the retention period

The first VAT period in Zoho Books acts as the migration test: if the review routine reconciles cleanly, the opening data was right. My ERP data migration service explains the wider method.

Swiss companies that should use something else

Zoho Books is a sound choice for many Swiss service firms and small traders. It is not the right ledger when:

• Payroll must sit inside the same system. Swiss payroll and its social insurance declarations need a specialist solution; if integration in one system matters, look at an ERP or a Swiss suite.
• Multi-entity consolidation with intercompany eliminations across francs and euros is required inside the books. Compare Odoo Accounting in Switzerland or Business Central in Switzerland.
• The fiduciary will not work with Zoho exports and insists on their own platform.
• Stock, landed costs and project accounting drive profitability analysis beyond what Zoho Books reports.

Platform selection more generally is covered under ERP consulting in Switzerland, and the Swiss hub page explains remote work. Multi-currency issues are discussed on ERP for multi-currency.