myDATA, ΔΙΑΣ and IBAN direct debit
Greek providers need three things that most ISP platforms treat as add-ons: ΑΑΔΕ myDATA submission, ΔΙΑΣ payment codes, and IBAN direct debit. In Veloxiom all three are produced from the invoice itself, so a compliance failure is visible next to the document instead of inside someone else's connector.
ΑΑΔΕ myDATA
- Submission of service invoices, retail receipts and credit notes with the income classification and VAT rate per line.
- The returned MARK and UID are stored on the invoice, with the submission state visible on the customer record.
- Failed submissions go to a retry queue with the exact ΑΑΔΕ error, so nothing is silently lost when the service is unavailable.
- Submitted invoices are locked against edits; corrections are made with a credit note that references the original document.
ΔΙΑΣ payment codes (RF) and reconciliation
Each invoice carries an RF payment code, so a subscriber paying through e-banking produces a transaction that matches its invoice automatically. Interbank payment files from the banks are imported with a preview before commit, with a full audit trail of what was settled.
For account movements, CAMT.053 and MT940 statements are supported, delivered by host-to-host SFTP, uploaded manually, or pulled through an open-banking aggregator. Payments without an RF code are matched in stages — invoice number, VAT number, name and amount, unique open invoice — and anything left over is paired manually.
Real-time ΔΙΑΣ online payments
Besides the collections file, ΔΙΑΣ can notify Veloxiom the moment a subscriber pays. A dedicated REST endpoint validates the RF code before the payment is taken — returning the customer name and the amount due, or rejecting an unknown or already settled code — then records the payment, settles the invoice and reactivates a suspended connection in seconds instead of hours. Partial payments stay open, reversals return the invoice to unpaid, and a notification delivered twice is never posted twice.
Requests are authenticated with an HMAC-SHA256 signature or a static secret, with an optional IP allowlist, and every event is logged. The scheduled SFTP/FTP file import keeps running underneath as the reconciliation check.
Direct debit on IBAN
SEPA Direct Debit mandates are stored per customer, so recurring invoices can be collected without card details. Card auto-pay and IBAN mandates run in the same collection cycle, and a failed collection follows the normal dunning rules rather than disconnecting anyone immediately.
Frequently asked questions
Do I need a certified e-invoicing provider?
Not necessarily — submission can be made directly to the ΑΑΔΕ API with the company's own credentials. If you use a provider, make sure the MARK is returned and stored on your invoices.
What if myDATA is unavailable during the monthly run?
Invoices are issued normally and queued. Submission completes when the service returns; billing and subscriber service are not affected.
Can I test without creating real submissions?
Yes — the ΑΑΔΕ test environment can be configured separately from production.
Does an unpaid invoice disconnect a subscriber automatically?
Only if you enable dunning rules, which are independent from submission and take grace periods into account. A submission error never disconnects anyone.