e-Tax Declaration (e-Beyanname)
Prepare VAT, withholding, advance tax and stamp duty declaration data from SAP; validate with control reports and file in e-Declaration format.
What problem does it solve?
In most companies tax declarations are prepared by rearranging SAP extracts in Excel. This work, repeated every period, carries both a reconciliation burden between the company and its accountant and the risk of an unexplained gap between the declared amount and the books.
How does the solution work?
The solution compiles data for VAT 1/2, withholding and premium service, advance tax and stamp duty declarations directly from SAP documents, fills declaration lines automatically through account and tax code mappings, and runs control reports comparing declared amounts with the ledger. Output is produced in the format the e-Declaration system accepts.
What changes in practice?
Declaration preparation starts from a validated list rather than an extract. Gaps between declaration and books are visible at source, and during an inspection every line traces back to an SAP document.
Benefits
- Declaration data is compiled directly from SAP documents
- Differences between the declared amount and the books are seen before filing
- Every declaration line can be traced to SAP documents
Where it sits in SAP
Integrated with FI tax postings and tax codes; covers filling the declaration lines through account and tax-code mappings, control reports and producing the output to be uploaded to the e-Declaration system. Filing is done with the company's or its accountant's own e-Declaration access.
Who it is for: Tax and Finance teams, external accountants
Frequently asked questions
Once the declaration data leaves SAP, who submits it to GİB, and does our accountant's role change?
The solution compiles the declaration lines from SAP, runs the control reports and produces the file to be uploaded to the e-Declaration system; the submission itself is done with the company's or its accountant's e-Declaration credentials, which the solution does not take over. The accountant's role shifts from building declarations out of extracts to approving a prepared and validated list. Reconciliation between the declared amount and the books is therefore completed in-house before submission.
How are tax code and account mappings updated when regulation changes, and what do we do when a new line is added to a declaration?
The mapping between declaration lines and SAP tax codes and G/L accounts is kept in a rule table that a key user can maintain. When a new tax code is created or a line is added to a declaration, an entry is added to the mapping table without changing program code. Movements on tax codes or accounts with no mapping are listed separately in the control report, so an amount left out of the declaration is noticed before submission. When the declaration format itself changes, the output template is updated at package level.
What exactly do the control reports compare, and are declarations prepared separately for each company code?
The control reports compare the amounts on the declaration lines with the period movements of the related tax accounts and, for VAT, with tax code totals from sales and purchase documents; where there is a difference, the documents behind it are listed. On the withholding side, the consistency of payroll-sourced and withheld payment postings with FI is checked with the same logic. Declarations are prepared per taxpayer, that is per company code, and for companies filing separately for branches the breakdown can be defined per business place.