What a VIES statement reports
VIES enables tax authorities to exchange information about relevant intra-EU transactions. For a Cyprus supplier, the practical task is to identify reportable supplies, allocate them to the correct customer VAT number and category, and place them in the correct month. It is not a list of every overseas invoice or every receipt from abroad.
Keep three tasks separate: checking a customer’s VAT number, submitting the monthly recapitulative statement and filing the VAT return. A successful number validation does not submit a statement. Filing a VAT return does not complete VIES. The records can draw on the same transactions, but each task answers a different question.
The Tax Department’s general VIES guidance explains the monthly reporting obligation. Build the process around a complete sales population and documented classification. Starting only from last month’s customer list can miss a new reportable customer or preserve one whose circumstances have changed.
Decide which transactions belong in the statement
Review relevant intra-Community supplies of goods and services against the applicable rules. The customer’s EU address alone is insufficient. For services, examine customer status, place of supply and the relevant tax treatment; not every service to an EU business belongs in the same category. Keep goods, services and any applicable triangular-transaction reporting distinct.
Domestic sales and ordinary non-EU service sales should not be added merely because they are business transactions. Purchases from EU suppliers are not the supplier’s outgoing-sales statement. The reverse-charge services guide explains the related tax decision, while the VIES working paper records the reportable sales resulting from that assessment.
Special territories need deliberate treatment. The Tax Department’s Northern Ireland notice distinguishes qualifying goods transactions using the XI identifier from services. Do not treat all UK transactions as ordinary EU supplies or apply a goods rule to services simply because the customer has an XI number.
Validate and preserve customer details
Confirm the contracting entity, country and VAT identifier before the first relevant supply. The official VIES validation guidance explains that the tool checks information from national systems. Retain the result and date. A validation failure should be investigated rather than replaced with an invented number or treated automatically as proof of fraud.
Check whether the number belongs to the legal customer on the invoice. A group may have several companies and registrations. The entity paying the bill may not be the recipient of the supply. Keep the agreement and customer confirmation with the master-data record, and route unresolved identity differences to review before final reporting.
Review changes during an ongoing relationship. Save evidence when the customer changes registration, legal name or establishment. Do not overwrite historical details so that prior-period reports become impossible to reconstruct. A controlled customer record should show which identifier was used for the relevant supply and why.
Build a monthly preparation file
| Stage | Working record | Check |
|---|---|---|
| Extract sales | Invoice and credit-note population | All billing systems included |
| Classify | Reportable and excluded transactions | Reason for each unusual treatment |
| Validate customer data | Country and VAT identifier evidence | Correct legal recipient |
| Allocate month and category | Tax-point and transaction schedule | No blanket bank-date assumption |
| Reconcile and review | Ledger and VAT bridge | Customer detail agrees with totals |
| Submit and retain | Filed version and acknowledgement | Correct entity and period |
Use invoice-level detail as the preparation base, then aggregate according to the reporting requirements. Keep the link from each reported customer total back to its underlying documents. If the accounting software stores country and VAT number in separate fields, test how the export combines them and handles spaces or punctuation.
Include a clear exclusion column for transactions examined but not reportable. That makes review easier than deleting them from the file with no explanation. Preserve the original extract and the adjusted working version. A reviewer should be able to see what changed after extraction and which person approved each material adjustment.
Assign the correct reporting month
Determine the applicable transaction timing rather than selecting the month from the bank statement. Invoice, delivery, service completion and payment dates can differ. Goods and services do not necessarily follow the same timing rule. Keep the dates needed for the assessment and document unusual cases, such as advance payments or continuous services.
A late invoice discovered after preparation may belong to an earlier period. Do not place it in the current month merely because that month is still open. Identify the original event and establish whether an earlier statement requires amendment. The monthly-close process should include a review for late billing and missing documents.
For foreign-currency supplies, retain the conversion basis used for the report and reconcile it to the invoice record. The multi-currency guide distinguishes original amounts and later exchange differences. A customer payment at a different rate should not automatically replace the value previously determined for reporting the supply.
Worked example: reconcile customer totals, not only the grand total
Assume a month contains €8,000 of reportable services to Customer A and €3,000 to Customer B. A properly supported €1,000 reduction relating to Customer A belongs in that same reporting month under the applicable rules. All amounts are in euros; the example assumes no other reportable categories or transactions.
| Customer | Initial reportable services | Supported adjustment | Final service value |
|---|---|---|---|
| Customer A | €8,000 | −€1,000 | €7,000 |
| Customer B | €3,000 | €0 | €3,000 |
| Total | €11,000 | −€1,000 | €10,000 |
The correct total is €10,000, but that is not enough. Reporting €8,000 for A and €2,000 for B would produce the same total and still be wrong. Review the allocation by VAT number and category. Likewise, a correct customer allocation in the wrong month does not become correct because the annual total agrees.
The example does not establish that every credit belongs in its issue month. Before using a negative adjustment, determine whether it is a later commercial change or an error in an earlier submission. Keep the supporting credit-note analysis with the working paper so the treatment can be checked.
Reconcile VIES to the VAT and accounting records
Prepare a bridge from the sales ledger to the relevant VAT records and monthly VIES totals. The periods may differ: do not compare one monthly statement with a full VAT period and assume the difference is an error. Group the appropriate months and separate timing, category and currency differences with evidence.
Check that reportable services, goods and other relevant categories are not mixed. A ledger’s broad “EU sales” account may contain transactions needing different reporting. The invoice checklist helps ensure the source documents carry the identity and supply details required to support the classification.
Do not force totals to agree by adding an unexplained balancing row. Investigate missing invoices, duplicates, credits, wrong identifiers or incorrect periods. Retain a reconciliation explaining legitimate differences as well as corrections. A statement that agrees to a flawed export can still be incomplete if one billing platform was omitted.
Use the monthly deadline and review nil periods
The ordinary filing deadline is the 15th day of the following month, subject to an official extension for the relevant period. For example, September reporting ordinarily points to 15 October. The Tax Department’s guidance also describes a €50 late-filing charge. Check current official notices rather than assuming an old temporary extension continues.
For a business with an ongoing VIES filing obligation, no reportable transactions does not automatically remove the monthly task. Cyprus guidance addresses nil statements. Confirm the period and obligation in the account, and follow the current nil-filing instructions. Do not invent a zero-valued customer transaction simply to make an empty month look populated.
Set an internal review date before the statutory deadline, allowing time to resolve customer-number queries and late documents. Assign a backup preparer or representative. A monthly calendar should distinguish data collection, approval and actual submission; completion of a spreadsheet is not completion of the filing obligation.
Submit through Tax For All and check the result
Use the current Tax For All support guidance and the correct taxpayer account or authorised representation. Before entering data, verify the company and period displayed. Similar company names or several client accounts can make a technically successful submission belong to the wrong taxpayer.
Review the entered or imported data against the approved working paper. Where XML is used, validate the current format and inspect the resulting rows, not only the file-generation message. Confirm categories, identifiers, signs and totals. Follow the portal’s current instructions for nil statements rather than copying ordinary transaction rows with zero values.
After submission, save the acknowledgement and the filed version. Reconcile the final displayed amounts to the approved schedule. A saved draft is not a filed statement. If an error message occurs, retain the details, resolve the cause and confirm the final status; repeatedly pressing submit without checking status can create uncertainty about what was accepted.
Correct earlier errors in the appropriate statement
The Tax Department’s VIES FAQ describes amendments through TFA and distinguishes returned goods from replacement of an original invoice. It also gives the correction deadline as the end of the following month and describes a €15 late-correction charge. Identify the specific period and event before applying that guidance.
If a customer number or reported amount was wrong, retain the original filed version, the corrected figures and the reason. Do not disguise an old omission as a new current-month sale. Record who approved the amendment and save the new submission evidence. The reconciliation should show which version is now the operative one.
Separate an actual reporting error from a later commercial adjustment. A genuine return can have a different reporting path from replacement of an incorrectly issued invoice. Review the supporting documents and the applicable guidance. Correcting the customer ledger alone does not necessarily update a statement already submitted through the portal.
Check exports for silent data changes
Before uploading or copying figures, inspect how the working file handles VAT identifiers. Spreadsheet software can remove leading zeros, change long strings into scientific notation or interpret a country prefix incorrectly. Store identifiers as text and compare the final exported value with the validated customer record. Do not alter the actual identifier to satisfy a spreadsheet format.
Check decimal separators, negative signs and duplicate customer rows. An import accepted by the portal can still contain the wrong value if the source file used a different convention. Keep a small control summary by category and customer count, then compare it with the imported result. Document and review any manual correction made after the export.
Keep a file that can survive a handover
Retain the sales extract, classification notes, validation evidence, period decisions, adjustment calculations, reconciliation, approval, filed statement and acknowledgement. Record open queries and responsibility for follow-up. Connect amendments to the original period rather than storing them in an unrelated folder named only by the day they were prepared.
When changing accountant or software, agree which months were filed, which remain drafts and which corrections are outstanding. Test one ordinary customer, one credit and one nil period in the new workflow. A clear handover prevents duplicate filings, missed months and reuse of outdated customer details, while preserving the evidence behind the reported amounts.
Keep access responsibilities current. Confirm that the authorised representative can view the relevant period before a deadline approaches, and remove obsolete access through the proper process when responsibility changes.