Swiss VAT effective method in software: from ESTV form boxes to eCH-0217
How a Swiss VAT return under the effective method travels from ledger accounts to ESTV form boxes to an eCH-0217 XML file: the data model, the pre-upload checks, a worked example with synthetic CHF figures, and the controls that belong outside the arithmetic.
- By
- Finray
- Published
- Updated
- Reading time
- 10 min
What does it take to get from ESTV form boxes to an eCH-0217 file?
Three things: a ledger in which every tax-relevant booking carries a tax code and a rate, a mapping from those codes to the numbered boxes (Ziffern) of the ESTV return, and an exporter that writes the figures into the XML structure defined by the eCH-0217 standard. The arithmetic is simple. Most of the engineering effort goes into the mapping, the checks before export, and the review that happens before anyone uploads the file.
This note follows one return under the effective method from the ledger to the file. It is not tax advice, and it describes the general mechanism rather than a particular product, except in the last section, which says what Corebanq Accounting does today.
Where does the effective method start in law?
The effective method is the basic rule. Article 36 of the Federal Act on Value Added Tax (MWSTG) says that, in principle, VAT is accounted for under the effective method, and defines the tax claim as the domestic tax owed, plus acquisition tax and any import tax declared under the deferral procedure, less the input tax credit of the settlement period. The simplified net tax rate method of Article 37 is an exception that has to be applied for. The net tax rate method replaces the input tax calculation with an approved rate, so its software requirements differ. For the full definition of the default method, see the entry on the VAT effective method.
Two choices come before any figure. The first is the type of accounting: agreed consideration, where the tax debt arises when the invoice is issued and the input tax claim when the invoice is received, or received consideration, where both arise on payment (Articles 39 and 40). Agreed consideration is the rule, and received consideration needs the ESTV’s approval. The second is the settlement period: Article 35 sets quarterly settlement as the rule; on application, settlement is monthly for a regular input tax surplus, or annual for turnover from taxable supplies of no more than CHF 5,005,000 a year (Art. 35 para. 1bis, since 1 January 2025). A system has to know both choices for each company, because they change which bookings fall into which return.
How do the form boxes translate into data?
The eCH-0217 standard states that its structure follows the existing paper forms of the ESTV, and for each XML element it names the Ziffer of the paper return. For the effective method, the mapping looks like this.
| Ziffer | Meaning in the return | eCH-0217 element |
|---|---|---|
| 200 | Total of agreed or received consideration | turnoverComputation / totalConsideration |
| 205 | Consideration from supplies excluded from tax, for which the option to tax was exercised | effectiveReportingMethod / opted |
| 220 | Exempt supplies, for example exports | suppliesToForeignCountries |
| 221 | Supplies provided abroad | suppliesAbroad |
| 225 | Transfers under the notification procedure | transferNotificationProcedure |
| 230 | Supplies excluded from tax, not opted for | suppliesExemptFromTax |
| 235 | Reductions of consideration such as discounts | reductionOfConsideration |
| 280 | Other deductions | variousDeduction |
| 300 to 379 | Taxable supplies per statutory rate | suppliesPerTaxRate |
| 38x | Acquisition tax | acquisitionTax |
| 399 | Total tax owed | not an element, derived |
| 400 | Input tax on material and services | inputTaxMaterialAndServices |
| 405 | Input tax on investments and other operating costs | inputTaxInvestments |
| 410 | Subsequent input tax deduction | subsequentInputTaxDeduction |
| 415 | Input tax corrections, for example mixed use | inputTaxCorrections |
| 420 | Reductions of input tax for subsidies and similar | inputTaxReductions |
| 500 or 510 | Amount payable or credit | payableTax |
The standard says explicitly that it dropped intermediate calculation steps of the paper form, and that Ziffer 399 is shown on the paper form but not represented in the schema. It also lists items it does not cover, such as the form for the subsequent input tax deduction and further documents that the ESTV can request on demand.
How is the file organised?
The root element is VATDeclaration. It holds general information (the taxable person’s UID and name, the generation time, the reporting period, the type of submission, the form of reporting, a business reference ID for the return, and the sending application), the turnover computation, one element for the accounting method, the payable tax, and optionally other flows of funds. There is no flag for the method; it follows from which method element is present. For the effective method this is effectiveReportingMethod, which also carries grossOrNet, telling the ESTV whether turnover is given net or gross. The standard notes that the ESTV recommends net values for the effective method where possible.
Version 2.0.0 is the approved version and replaces version 1.0.1. It is distributed with an XML schema named eCH-0217-2-0-0.xsd and with example files. The formatting rules are strict: UTF-8 without a byte order mark, no empty elements, times in coordinated universal time, and amounts with at least two decimal places.
What happens in a worked example?
The numbers below are synthetic. A fictitious company reports the third quarter of 2026 on agreed consideration with net values. Its ledger holds taxable supplies of CHF 120,000.00 at the standard rate and CHF 20,000.00 at the reduced rate. It has no exempt supplies and no other deductions, to keep the example short.
| Step | Calculation | CHF |
|---|---|---|
| Ziffer 200 total consideration | 120,000.00 + 20,000.00 | 140,000.00 |
| Tax at 8.1 percent | 120,000.00 x 0.081 | 9,720.00 |
| Tax at 2.6 percent | 20,000.00 x 0.026 | 520.00 |
| Ziffer 399 total tax owed | 9,720.00 + 520.00 | 10,240.00 |
| Ziffer 400 input tax, material and services | from approved purchase invoices | 3,100.00 |
| Ziffer 405 input tax, investments | from approved asset invoices | 1,150.00 |
| Ziffer 500 amount payable | 10,240.00 - 3,100.00 - 1,150.00 | 5,990.00 |
The standard’s formula for net values is tax rate divided by 100 times turnover, summed over the rate lines; acquisition tax is added the same way, input tax in elements 400, 405 and 410 is subtracted, and the corrections and reductions in 415 and 420 are added back. For gross values the formula divides by one plus the rate. Had the same turnover been reported gross, the standard-rate line would read CHF 129,720.00, and 129,720.00 x 0.081 / 1.081 again gives CHF 9,720.00.
Now suppose that in November the company finds that an asset invoice of CHF 600.00 input tax was left out of Ziffer 405 in the third quarter. The standard names three places where such a correction can go, according to accounting and tax principles: the first filing of a later period, a corrective return, or the annual reconciliation. A corrective return is a complete return that replaces the earlier one, so Ziffer 405 would read CHF 1,750.00 and the amount payable CHF 5,390.00. An annual reconciliation under Article 72, used for errors found while preparing the annual accounts of a closed tax period, contains only the difference, here a further CHF 600.00 of input tax, and complements the last return filed for the period. Software should therefore model submission types as separate workflows, because a corrective return and an annual reconciliation are not the same file with a different flag.
Which checks run before the ESTV accepts the file?
Section 7 of the standard lists plausibility checks that the vendor system has to run before sending, and says that the ESTV application performs the same checks after the upload and rejects a file that violates them. Examples include:
- the file must be valid against the XSD (error code MWST-0001);
- the accounting method must match the one registered with the ESTV (MWST-0002);
- the reporting period must match the registered period: for the effective method three months, one month or, with ESTV approval, one year (MWST-0003);
- only one first filing is allowed for a period (MWST-0004);
- the taxable turnover must equal the sum of the supplies by rate, to the centime (MWST-0005);
- payableTax must be computed without rounding of intermediate steps, with a final rounding either to two decimals or to five centimes in favour of the taxable person (MWST-0006);
- only rates published by the ESTV may be used (MWST-0007).
These checks catch format and arithmetic errors. They cannot tell whether a supplier invoice was a valid basis for input tax or whether a sale was classified at the right rate. That judgment belongs to the people who review the return.
What does the standard leave to the software vendor and the taxable person?
The standard fixes the file, not the process. It does not say how a company decides that a purchase invoice qualifies for input tax, how it classifies a sale at the right rate, or how it organises review. It also does not describe how the ESTV application handles a file after upload. Those parts sit in tax law, in the ESTV publications that the standard refers to, and in the company’s own procedures, so a green validation result is a necessary condition for upload and not evidence that the return is right.
What controls belong outside the arithmetic?
| Risk | Control kept outside the calculation | Owner |
|---|---|---|
| Tax code wrong on a booking | Tax codes validated at posting, with rates held with valid-from dates | Accounting |
| Return does not tie to the ledger | Every box reconciles to accounts, with drill-down from the figure to the lines and the source documents | Preparer |
| Input tax claimed on an invalid document | Check supplier details and amounts before deduction; keep the document | Accounts payable |
| Return prepared and filed by one person | Second-person review before export; the preparer cannot approve their own return | Finance lead |
| File changed after review | Export only the reviewed version, and record who exported it and when | Finance lead |
| Schema or rate drift when the ESTV updates | Re-run validation against the current XSD and rate list at each export | Software owner |
| Wrong submission type | Separate workflows for first filing, corrective return and annual reconciliation | Preparer |
| Late discovery of errors | Month-end close checklist that includes tax account reconciliation | Finance lead |
A hash-chained, append-only journal supports the audit trail around these controls, because the ledger behind the return can then be checked for later changes. It does not replace the review.
What does Corebanq Accounting do today, and what does it not do?
Corebanq Accounting from Finray supports this flow for the effective method on agreed consideration. Its figures are mapped to the ESTV form boxes. The return is prepared, then reviewed by an independent second person, then exported as an eCH-0217 XML file that is validated against the XSD, and finally the user uploads the file in the ESTV portal. The statements and the drill-down from a figure to accounts, lines, entry and source document sit in the same product.
It does not prepare returns under the net tax rate method, it does not support accounting on received payments, and it does not file directly with the ESTV. Companies in those situations need another route for the return. See Corebanq Accounting for the product description, and the eCH-0217 entry for the standard itself. The invoices that feed turnover are covered in the note From QR-bill to camt.054, and the glossary entry on the QR-bill describes the invoice format.
Frequently asked questions
- Do I need eCH-0217 to file a Swiss VAT return?
- No. The XML upload is one way to submit a return, and the standard exists so that accounting software can produce a file the ESTV application accepts. A return can also be entered by hand in the ESTV application. The standard is of interest to people who build or select software that exports the return.
- Does the effective method require agreed consideration?
- No, but agreed consideration is the default. Article 39 of the MWSTG says tax is accounted for on agreed consideration and allows received consideration on application to the ESTV. The eCH-0217 file carries the choice in the element formOfReporting, where 1 means agreed and 2 means received.
- What is an annual reconciliation?
- It is the corrective return under Article 72 of the MWSTG that is used when errors in the VAT returns of a closed tax period are found while preparing the annual accounts. In eCH-0217 it is submission type 3, and it contains only the differences from the full return of the period, not a complete new return.
- Which rates should software hold?
- Only rates that the ESTV publishes. The eCH-0217 standard says that only published rates may be used and that the ESTV application checks them. The ESTV lists 8.1, 2.6 and 3.8 percent as valid from 1 January 2024, and software should store each rate with its valid-from date.
- Can software file the return with the ESTV by itself?
- The eCH-0217 standard describes a manual upload of the exported file. It mentions a later machine-to-machine interface as a further step, and says that such an interface would mainly change the transport layer and the acknowledgement. This note does not rely on any such interface.
Sources
- Federal Act on Value Added Tax (MWSTG, SR 641.20) on fedlex.admin.ch: Art. 35, 36, 37, 39, 40, 72
- eCH-0217 Spezifikation E-MWST, version 2.0.0, status approved (German original)
- eCH-0217 Spezifikation E-MWST, version 1.0.1 (German, superseded)
- ESTV: Swiss VAT rates (page updated 5 November 2026)
- ESTV: Saldosteuersaetze und Pauschalsteuersaetze bei der Mehrwertsteuer
Discuss how this applies to your institution with the Finray team.
Book a briefing