Correct data from the first save
Polish NIP, REGON and PESEL numbers checked by check digit. A three-line name, customer kind (customer, bank, tax office, employee), supplier and recipient flags, sales agent with commission, forwarder.
Registration data, trade terms, limits, bank accounts, accounting settings, addresses, contacts, consents, attributes, notes and attachments. Sales, purchasing and accounting work on the same record — each on their own tab.
Polish NIP, REGON and PESEL numbers checked by check digit. A three-line name, customer kind (customer, bank, tax office, employee), supplier and recipient flags, sales agent with commission, forwarder.
“Transactions on hold” and “orders on hold” flags sit on the record and on the customer list — nobody misses that this company needs care.
Payment method and term separately for sales and purchasing, maximum term, delivery method, discount, currency. Parent company (head office) and payer — terms can be taken from the payer's record.
A limit amount and an overdue limit for chosen dates and currencies. The system won't let periods in the same currency overlap. Plus the number of days a payment may be overdue.
NRB/IBAN numbers verified by checksum, the bank recognised from the account number, one default account per currency. Split payment (MPP) and foreign-currency settlement marked on the record.
Domestic, EU or non-EU customer (checked against the country), cash accounting, reverse charge, related entity, VAT registration dates, JPK procedures and KSeF settings for sales and purchases.
Changing the main address closes the current version and creates a new one — the old one stays with its validity dates. A typo can be fixed without creating a version. Additional addresses — correspondence, delivery — alongside.
Contact persons in a set order, with the invoice recipient marked. GDPR and marketing consents with version, grant and withdrawal dates, and a “valid on date” filter.
The fictional customer “Przykładowa Hurtownia Spożywcza” on demo data.










Click a screenshot to see it at full resolution. All data in the screenshots is fictional. The application interface is in Polish.
The same customer entered twice means double receivables and two different limits for one company. HQSFlow checks whether a tax ID is already in the database — including archived records. Whether a duplicate is blocked or only flagged with a warning is the administrator’s choice in the system settings. Customer codes are unique.
A customer that isn’t referenced anywhere can simply be deleted. If it is already linked — as an item’s manufacturer, another company’s payer, the owner of a barcode — HQSFlow moves it to the archive instead. The data stays, the list stays clean, and a mistake is undone with one click.
Fields the standard doesn’t cover can be added by the administrator as attributes — without programming. Contracts and other files go on the Attachments tab.
Tell us how many companies, customers and items you have and what you use today. We will show HQSFlow on examples close to yours and tell you honestly what it already handles — and what it doesn't yet.
We answer every request personally, usually within one working day.