KYEASY support

Help centre

Find the key steps for getting started, protecting an account, reporting an incident and operating a till module in France.

Operational guide · 17 August 2026 editionRegulatory information reviewed 17 August 2026

This guide does not replace advice from an accountant, tax adviser or lawyer based on your actual business and payment flows.

1. Contact support

Email admin@kyeasy.com, the recommended channel, or call +33 6 25 82 33 91. Availability, on-call and response commitments in your quote, SLA or maintenance agreement always take precedence.

  • General request: state your organisation, the service or project and the outcome you need.
  • Incident: include the account or store, version, date and time, steps, observed result and expected result.
  • Critical incident: start the subject with “URGENT”, state the business impact and provide a callback number.
  • Never send a password, API key, payment-card security code or more personal data than troubleshooting requires.

2. Before going live

  • Confirm scope, modules, integrations, capacity, environments and acceptance criteria in the order.
  • Appoint a customer administrator, use one named account per user and grant least privilege.
  • Test sales, cancellations, corrections, refunds, taxes, payment methods, daily/monthly/annual closures, exports, backups and recovery.
  • Document the accepted configuration and train operators before recording real transactions.

3. Check whether French cash-register duties apply

Article 286 I-3° bis of the French General Tax Code generally concerns a person liable for French VAT who makes supplies not invoiced under Article 289 and records the payments in software or a till system. Exemptions and special cases exist.

  • Are you liable for VAT in France and outside an express exemption?
  • Do you take consumer payments or record transactions that are not always invoiced?
  • Does the system record and retain payments, even if it also manages invoices or accounts?
  • Does an administrative exception apply to the real payment flow, such as certain payments fully intermediated by a French or EU bank?
  • Has your accountant or tax adviser confirmed the result against the real process?

4. Apply the four ISCA requirements

Inalterability

  • Never overwrite or delete a recorded sale; use the documented cancellation, correction or refund action.
  • Keep the original operation, new entry, reason, operator and timestamp in the audit trail.

Security

  • Use named accounts, least privilege and protected administrator access.
  • Do not bypass the application to alter databases, logs, integrity controls or the system clock.

Retention

  • Run and reconcile the required daily, monthly and annual closures and retain detailed and cumulative data.
  • Agree tax and accounting retention with your adviser; ordinary backup is not a frozen statutory archive. French tax records are commonly retained for at least six years.

Archiving

  • Generate archives at the documented interval, no longer than annual or each financial year, and verify integrity and readability.
  • Keep archives and verification material in a controlled location and test restoration and reading.

5. Certificate or individual publisher statement

Since 21 February 2026, current French law accepts either a certificate from an accredited body or an individual publisher statement matching the tax-authority template. Evidence is useful only if it exactly covers the product in use.

  • Match the product, version, modules, options, date, customer and issuer to the installed system.
  • Keep the evidence, validity conditions, user documentation and configuration record.
  • Before a major upgrade, check that the target remains covered and archive the previous evidence.
  • KYEASY claims no NF525, LNE or other third-party certification without supplying the matching valid document.

6. Receipts and supporting documents

Since 1 August 2023, many French till and payment-card receipts are supplied at the consumer’s request rather than printed automatically. A consumer may still ask for paper without giving an email address. Exceptions require automatic supply or another note for certain warranty goods, card events, weighed goods and regulated services.

  • Configure the checkout for your sector and applicable exceptions.
  • Collect an email or phone for an electronic receipt only after notice and on an appropriate legal ground; do not reuse it automatically for marketing.
  • A professional invoice and a till receipt follow different rules; validate required content and workflows.

7. Troubleshoot without damaging evidence

Sync or display issue

  • Record the time, store, terminal and transaction; check connectivity and service state before retrying.
  • Search for an existing transaction identifier or receipt before entering it again.

Till difference or inconsistent transaction

  • Do not edit the database or delete logs.
  • Preserve identifiers, export what is available, record the difference and contact support.

Unreadable archive or export

  • Keep the original file and hash if available; do not save it in a different format.
  • Record the producing version, covered period and error before asking for help.

Account access

  • Ask your organisation administrator to verify role, status and recovery first.
  • KYEASY never asks for your password and limits identity checks to what is necessary.

8. Data-subject requests

If you are a consumer, member, recipient or employee whose data was entered by a merchant, contact that merchant first. It is normally the controller. KYEASY assists with searching, exporting, correcting, restricting or deleting under its instructions while preserving records the law prevents it from deleting. For KYEASY’s own relationship data, email admin@kyeasy.com.

9. Report a security incident

  • Revoke the suspected session, account or key if this can be done without destroying evidence.
  • Preserve logs, times, screenshots and identifiers; do not discuss the event in a public channel.
  • Email admin@kyeasy.com immediately with “URGENT — security”, impact, known time range and an available contact.
  • A customer controller must also start its own risk and breach process; KYEASY cannot replace that responsibility.

10. Subscription, storage and billing

  • The public €1.00 per GB per month is indicative and excludes bespoke work; the order sets price, VAT and capacity.
  • To change capacity, request an invoice or give non-renewal notice, write from an authorised contact and identify the organisation and account.
  • Termination takes effect under the order and Terms. Export required data before access ends.
  • Never send card data to support; use only the payment method stated on the invoice or agreed secure flow.

11. Migration, integrations and cloud switching

  • Use a minimised, pseudonymised sample before a full migration and validate formats, tax rules, duplicates, time zones and control totals.
  • Assign responsibility for source backup, acceptance, rollback and transfer-file deletion.
  • For a switch to another provider or on-premises environment, give written notice of the target and desired date; KYEASY provides exportable data, formats and known limits under the order and EU Data Act.
  • Unless technically unfeasible with reasons given, the initiation notice period is no more than two months, transition normally takes 30 days, and retrieval remains available for at least 30 days after completion.

12. Official resources

Need an answer for your circumstances?

Tell us your organisation, the service concerned and the outcome you need. Do not include passwords, secrets or payment-card data.

Contact KYEASY