When transforming bank statements in Biatec.cz, you can choose between two output formats: the traditional GPC (ABO) and the modern SEPA XML (camt.053). Both formats have their advantages and limitations. In this article, we will compare them and help you choose the right one for your accounting system.
GPC (ABO Format)
GPC is a traditional Czech and Slovak banking format that has been in use for decades. Its official name is ABO format and it was originally designed for electronic banking in Czechoslovakia.
Technically, it is a text file with fixed-width fields - each line is exactly 128 characters long. The first line (header) contains information about the account and period, while the remaining lines represent individual transactions. The format is simple, reliable, and supported by virtually all accounting systems in the Czech Republic and Slovakia.
However, the limitations of the GPC format stem from its age:
- Variable symbol: maximum 10 digits, numeric characters only
- Transaction description: maximum 20 characters
- Account number: maximum 16 digits (Czech format, not IBAN)
- Encoding: Windows-1250 (limited character set)
SEPA XML (camt.053.001.02)
SEPA XML is an international ISO 20022 standard for bank statements. The camt.053 format (Cash Management - Bank to Customer Statement) is widely used throughout Europe and is gradually replacing national formats including GPC.
As an XML format, it has no fixed field length limitations and supports the full range of Unicode characters. This brings significant advantages:
- Variable symbol: no length limit, alphanumeric characters
- Transaction description: up to 140 characters
- Account number: full IBAN + bank BIC code
- Currency: ISO 4217 standard
- Encoding: UTF-8 (full support for diacritics and international characters)
Comparison Table
| Property | GPC (ABO) | SEPA XML (camt.053) |
|---|---|---|
| Variable symbol | Max 10 digits | No limit, alphanumeric |
| Transaction description | Max 20 characters | Up to 140 characters |
| Account number | Max 16 digits (CZ format) | Full IBAN |
| Currency | Numeric code | ISO 4217 (EUR, CZK...) |
| Encoding | Windows-1250 | UTF-8 |
| Structure | Fixed width (128 chars/line) | XML (tree structure) |
| Standard | National (CZ/SK) | International (ISO 20022) |
When to Choose GPC
The GPC format is the right choice if:
- You use an older accounting system that does not support SEPA XML import
- You are accustomed to the GPC workflow and do not want to change established processes
- You do not need long transaction descriptions - 20 characters are sufficient
- You work exclusively with Czech/Slovak accounts (not IBAN)
- Your accounting system has proven compatibility with GPC and you do not want to take risks
When to Choose SEPA XML
SEPA XML is a better choice if:
- You use a modern accounting system (POHODA 2024+, Money S3, FlexiBee)
- You need the full variable symbol with letters (e.g. PayPal Transaction ID)
- You need longer transaction descriptions (e.g. the full payment description from Stripe)
- You work with IBAN accounts and need bank BIC codes
- You want an international standard that will continue to be supported in the future
Special Settings for POHODA
If you use the POHODA accounting system, you have two versions of SEPA XML export available:
- SEPA XML CZ - generates Czech IBAN and BIC codes (suitable for Czech bank accounts)
- SEPA XML SK - generates Slovak IBAN and BIC codes (suitable for Slovak bank accounts)
POHODA from version 2024 fully supports SEPA XML statement import. If you are switching from GPC to SEPA XML, we recommend first importing test data and verifying that all fields are correctly mapped. A detailed guide can be found in the guide for importing into POHODA.
Conclusion
GPC remains a reliable choice for simple use cases with Czech and Slovak accounts. SEPA XML is a more modern alternative that removes the limitations of the GPC format and is better suited for international transactions and services like PayPal, Stripe, or Wise. The best strategy is to try both formats and choose the one that best suits your accounting system and workflow.