← Blog
Perfex CRME-InvoicingCompliance

Perfex CRM myDATA: Send Invoices to AADE From Your CRM

Perfex CRM myDATA transmission without a monthly bill: how invoices reach AADE on payment, why the manual-payment path matters, and where the module stops.

A small Greek agency raises forty service invoices a month in Perfex CRM. Every one of them is already complete: client, ΑΦΜ, description, net amount, VAT. Then somebody opens a second browser tab, signs into a myDATA provider, and enters those same forty invoices a second time. Two minutes each when nothing goes wrong, and something goes wrong often enough - a transposed VAT number, an invoice raised on the 31st that only gets transmitted on the 3rd, a document nobody notices was never sent at all until the accountant asks in February.

Perfex CRM myDATA transmission is the fix for that second tab. The invoice already exists in the CRM with every field the platform needs. The only real questions are what triggers it to leave, and what it costs you per document to send it.

Disclosure: we build and sell the AADE myDATA Connector module for Perfex CRM, so weigh this article accordingly. The mechanics below apply whether you buy a module, hire a developer, or write your own client against the ΑΑΔΕ API - the design decisions are identical.

Why Perfex CRM myDATA transmission belongs in the CRM, not a second portal

Double entry between a CRM and a compliance portal is not a workload problem. It is a consistency problem, and consistency is exactly what software exists to solve.

Three things break when a human is the transport layer:

  • Transcription. One wrong digit in a client’s ΑΦΜ across forty documents is invisible until it becomes a correction.
  • Lag. The books are only as current as the last data-entry session. If that session happens weekly, your transmission cadence is weekly, regardless of when the invoice was actually issued.
  • Omission. The invoice that gets skipped is flagged by nothing, because neither system knows the other one exists.

Stated in Greek search terms, this is the ηλεκτρονική τιμολόγηση problem in its plainest form: the document is already correct, it simply has to reach the ΑΑΔΕ without a person carrying it there. The AADE myDATA Connector module for Perfex CRM transmits service invoices to the myDATA platform straight from the CRM, which removes the human leg entirely.

The two transmission moments that actually matter

Most of the engineering interest in a myDATA AADE Perfex integration sits in one question: when does the document go out? Get this wrong and you have a system that works beautifully for a third of your invoices and silently ignores the rest.

Two moments carry the real traffic, plus a third that catches the automated tail.

1. Automatic capture through a payment gateway

When a client pays online, the gateway callback creates the payment record in Perfex and the document is transmitted automatically and immediately. This path works with all Perfex payment methods, and it also works with custom payment modules - which matters more than it sounds, because plenty of Greek installs run a bespoke gateway for a local bank or a niche processor.

This is the path everyone builds first, and it is the path that flatters a demo. It is not the path that carries most Greek B2B invoicing.

2. Manual application of a payment by a staff member

Bank transfer remains the default settlement method for a great many Greek service businesses. The money arrives, someone on your team opens the invoice in Perfex and applies the payment by hand. If an integration only hooks the gateway callback, every one of those invoices never transmits, and nobody finds out for a month.

The module transmits on manual payment application as well, specifically for invoices settled outside an online gateway. In practice this is the more important of the two moments for most firms, and it is the one to check explicitly against any product you evaluate, ours included. Ask the vendor a single question: what happens when an accountant marks an invoice paid from a bank statement?

3. Cron, for recurring and automated payments

Recurring charges - Stripe Subscriptions being the obvious case - are transmitted through a CronJob. That gives you a third path for money arriving without anybody touching Perfex at all.

The dependency deserves naming. This path is only as reliable as your Perfex cron. If php /path/to/perfex/crons/cron.php is not firing on schedule, recurring documents queue up quietly. Confirm the cron actually runs before you rely on it for anything with a deadline attached.

MARK numbers, QR codes and a history you can audit

A transmission you cannot verify is not much better than no transmission at all. Two things make the outcome checkable.

The MARK number. Every accepted submission comes back with one, and the module keeps a full history of each invoice alongside its corresponding MARK. That gives you the report that matters at month end: which invoices have a MARK and which do not. In a portal-based workflow, answering that question means eyeballing two lists side by side and hoping.

The QR code. Each document carries a QR code following ΑΑΔΕ compliance guidelines, so the customer can verify the invoice electronically and download the PDF from the Perfex CRM Customer Portal. The practical benefit is fewer “can you resend the invoice” emails, because the client has a self-service route to a verified document.

Customers outside Greece are covered too - the module works for client companies inside and outside Greece and the EU, which matters if you bill international clients from a Greek entity and would rather not maintain two invoicing workflows.

What unlimited documents on a one-time purchase does to your cost base

Greek e-invoicing for Perfex CRM is mostly sold on one of three meters, and each of them prices something you would rather not be punished for.

Pricing modelTypical market rate12 months at 40 invoices/month36 months
Per month€10 - €30€120 - €360€360 - €1,080
Per document€0.10 - €0.50€48 - €240€144 - €720
Per customerScales with your client listUnpredictableUnpredictable
One-time modulePaid once€0 recurring€0 recurring

The subscription totals are the boring part. The meter itself is the interesting part.

Per-document pricing taxes growth. Every invoice becomes a small variable cost on a compliance step that produces no revenue. That is a rounding error at forty documents a month and a real line item at four hundred. Worse, it creates a quiet incentive to batch or consolidate documents for reasons that have nothing to do with how you actually want to bill.

Per-customer pricing bills your CRM twice. You already run Perfex to hold that client list. Paying a second vendor in proportion to the same list means your growth arrives on two invoices instead of one.

The module removes the meter: a small one-time fee, then unlimited invoices, unlimited customers, and no hidden charges. For a firm issuing 500 documents a year, three years of even a mid-range subscription is money spent transporting data that a hook could have moved. Lifetime updates come with that one-time purchase, which matters because the myDATA API is not frozen - an integration that stops being maintained eventually stops being compliant.

Where this module stops

The honest section, and the one to read before buying anything in this category.

  • Services only. The module covers sales of services. Sales of physical goods also require a POS terminal, which puts retail and product-based businesses out of scope entirely. If you sell goods, this is the wrong tool and no configuration changes that.
  • One line item per invoice. The module supports a single line item per invoice. Before anything else, open your last fifty Perfex invoices and count how many carry two or more lines. If most of them do, you either restructure how you bill or you look elsewhere.
  • Transmission is tied to payment, not issue. All three paths above fire when money is recorded. If you invoice on 30 or 60 day terms, the gap between issuing and transmitting is the length of your payment terms. Ask your accountant which deadline applies to your document types before assuming that gap is acceptable.

None of these are defects. They are the boundaries of a tool built to do one job cheaply rather than every job expensively, and knowing them in advance is worth more than any feature list.

Bridging to an ERP or custom software

Plenty of firms do not keep everything in the CRM. Where the invoicing flow starts in an ERP, a booking system, or in-house software, the sensible pattern is to keep Perfex as the invoicing and transmission layer and feed it from outside, rather than building a second myDATA client that also has to be maintained.

The module connects to those systems through the GraphQL Module for Perfex, which gives you one query interface over the CRM’s data instead of a pile of bespoke endpoints. The compliance logic stays in one place, and the upstream system only needs to know how to create an invoice.

Before you install anything, run these six checks

  1. Count line items. Pull your last fifty invoices from Perfex. If more than a handful carry two or more lines, fix the billing structure first or stop here.
  2. Confirm you sell services. Any physical goods in the mix means a POS requirement this does not address.
  3. Map how payments are actually recorded. Gateway callback, manual application by staff, or recurring cron - write down the percentage split. All three are covered, but your split tells you which path to test hardest.
  4. Verify the cron end to end. Log a recurring payment and watch it transmit. Confirming that a crontab entry exists is not the same test.
  5. Add up 36 months of your current provider’s bill. That is the real comparison figure, not the monthly one.
  6. Ask your accountant about deadlines. Payment-triggered transmission has to fit the rules that apply to your document types, and only they can confirm it does.

If checks one, two and six clear, the rest is an afternoon.