For accounting practices
Every client's month, on one calendar.
VAT, VIES, PAYE, social insurance, SDC, provisional tax, annual returns, and UBO register windows, tracked per client, with the prep datasets and files generated ahead of each deadline, ready for you to check before anything goes out.
A ten-client practice runs ten VAT calendars, ten sets of SDC and provisional-tax dates, and at least one annual return and UBO window each, usually split across spreadsheets, sticky notes, and whoever remembers first. The obligations do not thin out for a busy quarter, and a missed SDC withholding date or VIES filing is not a delay, it is a compliance failure with a client's name on it.
Pileform tracks every client's Cyprus obligations on one calendar and assembles the dataset behind each deadline ahead of time, so review, not remembering, is the job.
How it works
The month laid out before the dates arrive.
Deadlines populate per client as soon as their VAT regime and filing profile are set up. Behind each date, Pileform assembles the numbers a return or a withholding form needs from the client's posted books, so a reviewable draft is waiting, not a blank form on the day.
One calendar, every client, every obligation.
VAT returns, VIES declarations, PAYE, social insurance, SDC, provisional-tax instalments, annual returns, and UBO register windows, tracked per client with reminders ahead of the due date. One screen replaces the spreadsheet a practice usually keeps for this.
The dataset behind the date, ready before it's due.
SDC withholding prep builds the TD603 and TD601 datasets from a client's posted books. Provisional-tax decision support shows where this year's figures sit against the 75% safe-harbor threshold, so the instalment decision is made against real numbers, not last year's guess.
VIES declarations, XML ready to check.
The VIES declaration XML is generated from posted intra-community supplies for the period. You review it and file it yourself through TAXISnet; Pileform prepares the file, it does not submit it.
Payment batches, one file per run.
A SEPA payment-batch file is generated from the payables you have approved, ready to upload to your own bank's portal. Pileform builds the file; your bank moves the money, on your instruction.
An audit-season packet, not five tabs stitched by hand.
The auditor export workbook carries the general ledger with links back to each source document, a movements schedule, AP/AR aging, and anomaly annexes, the packet an auditor asks for, generated instead of assembled every year under deadline.
Categorisation that remembers each client, separately.
Per-client categorisation learning keeps one client's confirmed rules and chart of accounts apart from the next. Twenty clients means twenty rule sets, not one blended guess.
Where you stay in charge
Generated for review. Nothing filed without you.
Every file waits for a look.
The VIES XML, the SEPA batch, the SDC withholding datasets, each lands in your queue as a file to check, not a submission already made. Filing and uploading stay actions you take, through TAXISnet and your own bank.
Decision support, not advice.
The provisional-tax check shows where a client sits against the 75% safe-harbor line, in numbers pulled from their posted books. What that means for the instalment, and any advice you give the client, is your judgement, not the system's.
Posting still needs your yes.
Reviewed entries post to Xero, QuickBooks Online, QuickBooks Desktop, or BTMS on your confirmation; Esoft clients get a ready-to-import Excel file instead. Nothing reaches a client's ledger unreviewed.
Questions practices ask.
Cyprus VAT returns, VIES declarations, PAYE, social insurance, SDC, provisional-tax instalments, annual returns, and UBO register windows, tracked per client with reminders ahead of each due date. Obligations are set from each client's registered regime, so the calendar reflects who actually owes what, not a generic filing list.
No. Every file it prepares, the VIES declaration XML, the SEPA payment batch, the SDC withholding datasets, is generated for your review. You file it through TAXISnet, upload it to your bank, or hand it to the client yourself. Nothing is submitted automatically.
It shows where a client's current-year figures sit against the 75% safe-harbor threshold, calculated from their posted books. That is a number, not a recommendation: the instalment decision, and any advice you give the client about it, stays yours.
No. Learning is scoped per client. Corrections you confirm for one client's chart of accounts do not carry over into another client's rules, even inside the same practice login.
A general ledger with links back to each source document, a movements schedule, AP/AR aging, and anomaly annexes, built as one workbook instead of five tabs assembled by hand every audit season.
Run one client's month through, start to finish.
Sign up free, no card. Try the calendar and the prep files against a real client before the next deadline lands.