BLOG
E-Beyanname Scope: Declaration, Period, Channel
Saying that an e-Beyanname product “supports VAT, withholding, or corporate tax” is not a complete scope definition. The applicable filing channel for the same declaration can vary by tax period, the rollout date for the taxpayer’s province or tax office, taxpayer authorization, whether the filing is original or corrective, and GİB’s current rollout across test, pilot, and production.
Scope should therefore be managed as a traceable declaration–period–province/tax office–taxpayer–channel matrix, not as a permanent check mark in a product list.
Six dimensions of the scope decision
1. Declaration type and tax code
Use GİB’s exact declaration name and tax code, not only an internal product label. VAT 1, Stamp Duty, Corporate Provisional Tax, and Withholding and Payroll Tax have different fields, attachments, and business rules. GİB publishes separate developer sections for declarations including KDV1, Stamp Duty, Corporate Tax, Corporate Provisional Tax, and MUHSGK.
Published developer documentation does not by itself prove that production access is enabled for every taxpayer. Production scope must be confirmed separately.
2. Tax period and declaration version
In GİB’s API flows, the period is a primary input for selecting the applicable declaration version and validation rules. The documentation includes messages for a missing period version and, in some scenarios, instructions to use BDP for an earlier period.
SAP mappings should therefore be versioned with effective start and end dates. Do not assume that a correction for an earlier period uses the same channel as the current period.
3. Province, tax office, and phased rollout
GİB can enable declaration families in phases by province and tax period. For example, its 20 July 2026 announcement states that KDV1, KDV2, KDV2B, KDV4, and KDV9015 will expand to every province except Istanbul for the July 2026 tax period, effective 1 August 2026.
This timetable shows why declaration type and period alone are insufficient. Recheck GİB’s latest announcement for the taxpayer’s province or tax office before project decisions and production use.
4. Taxpayer and user authorization
An e-Beyan integration application requires declaration filing authority. Different checks can apply to a primary user, delegated user, tax professional, or a company filing on its own behalf. An API 401, 403, or an authorization-specific business message is not necessarily a connectivity defect; the taxpayer and contract context must also be checked.
5. Environment
GİB’s guide separates Pre-Prod, Pilot, and Prod. Approved IP addresses and API keys are environment-specific. A declaration that passes a test flow may not yet be enabled by GİB in production.
Record the environment in the scope matrix and do not treat test success as production authorization.
6. Filing scenario
Original filings, corrections, late filings, special approval, cancellation, and document retrieval do not share identical rules. GİB’s user documentation explains, for example, that a correction proceeds from the latest approved declaration, approved declarations cannot be deleted, and accrual documents are available only in applicable statuses.
Recommended scope matrix
Manage at least these fields for every row:
| Field | Decision record |
|---|---|
| Declaration | GİB name, tax code, and internal process owner |
| Period | Effective dates and declaration version |
| Province / tax office | Taxpayer’s registered unit and effective rollout date |
| Environment | Pre-Prod, Pilot, or Prod |
| Authorization | Taxpayer, user, contract, and approval conditions |
| Channel | REST API, BDP, or channel to be confirmed |
| Scenario | Original, correction, late/special approval, cancellation |
| Evidence | GİB announcement, API guide, and test result |
| Last review | Date and accountable reviewer |
Prepare this matrix at project start and review it whenever GİB changes an announcement or API version. A verifiable scope record is more useful for users and testing than a permanent claim that “all declarations are supported.”
Continue with the SAP E-Beyanname integration architecture and the implementation checklist. See how scope is expressed in the interactive simulation of the Fenikstech SAP E-Beyanname solution.
Official sources
- GİB e-Beyan Integration Guide
- GİB announcement of 20 July 2026 on the phased KDV e-Beyan rollout
- GİB KDV1 API documentation
- GİB Corporate Provisional Tax API documentation
- GİB declarations user documentation
This article was reviewed against the official sources on 23 July 2026.