Turkey e-Fatura and e-Arsiv Compliance

The compliance gap

Turkish taxpayers above the revenue threshold cannot legally issue a paper invoice to another registered taxpayer. Every sales document has to leave the business as a structured UBL-TR envelope, signed and routed either through the Revenue Administration (GIB) portal or through a private integrator, and every inbound e-Fatura has to be answered with an application response inside the statutory window. Delivery notes follow the same path as e-Irsaliye, and sales to unregistered buyers become e-Arsiv with its own reporting obligations.

SAP Business One ships no Turkish e-invoicing localisation. The usual result is a second, disconnected workflow: the accounting team keys the invoice into SAP B1 for the Journal Entry and the customer balance, then re-keys the same document into a portal or a spreadsheet template so it can be transmitted. Two systems drift apart. An invoice cancelled in SAP B1 stays live at GIB. A customer VKN typed correctly in one place is wrong in the other. Nobody can answer "which of last month's invoices actually reached the recipient" without opening a browser and counting.

ECOSIRE builds an add-on that removes the second workflow entirely. The invoice you post in SAP Business One is the invoice that reaches the buyer.

What ECOSIRE builds

The add-on is delivered as a SAP Business One extension package that talks to your company database through the Service Layer for document reads and writes, and through the DI API where a transaction has to be committed inside the same unit of work as a B1 posting. Nothing is written by direct SQL, so your database stays supportable.

Document generation from real B1 objects

A/R Invoices (Invoices), A/R Credit Memos (CreditNotes), A/R Down Payment Invoices and Deliveries (DeliveryNotes) are mapped field by field into UBL-TR. Business Partner master data supplies the VKN/TCKN, tax office, MERSIS and address block; the item lines supply GTIP codes, unit of measure mapping and line-level KDV, tevkifat and OTV amounts. Where SAP B1 has no home for a Turkish field, we add UDFs on the marketing document header and rows rather than overloading unrelated columns, and we add UDTs for the mapping tables (tax office register, exemption code list, unit-of-measure crosswalk).

Routing, status and the mailbox

A scheduled service polls the buyer register so the add-on knows, at the moment of posting, whether a Business Partner is an e-Fatura user (temel or ticari scenario) or an e-Arsiv recipient. That decision is stamped on the document and drives which envelope is produced. Outbound documents move through a queue you can see: draft, signed, sent, accepted, rejected, cancelled. Inbound e-Fatura and e-Irsaliye land in a mailbox screen where a purchasing user can accept or reject with a reason, and an accepted inbound invoice can be turned into an A/P Invoice with the supplier's own lines carried across.

Approval, numbering and cancellation

Turkish document numbering is series-driven and gapless. The add-on manages its own numbering series, tied to your SAP B1 document series, and refuses to reuse a consumed number. Cancellation and the e-Arsiv cancellation window are handled explicitly: a cancellation in SAP B1 raises the corresponding action outbound rather than silently diverging. Where your finance team wants a second pair of eyes before a document is transmitted, we wire the queue into SAP B1 approval procedures so transmission waits on the approval decision.

Reporting

Crystal Reports layouts are produced for the human-readable rendition of e-Fatura and e-Arsiv documents, matching the visual layout your customers expect, plus reconciliation reports: posted-but-not-transmitted, transmitted-but-not-accepted, and a period summary that ties the transmitted set back to the KDV figures in your Journal Entries.

Who it is for

Companies running SAP Business One in Turkey, and international groups whose Turkish subsidiary runs on SAP B1 while the rest of the group runs elsewhere. It suits businesses that already issue enough invoices that manual portal entry has become a job in itself, and those that need the audit trail from posting to transmission to sit in one place.

Compatibility

The add-on targets SAP Business One 10.0 on both Microsoft SQL Server and SAP HANA, on-premise or cloud-hosted. Connectivity to GIB is implemented either directly against the portal interface or against the private integrator you already hold a contract with — that choice is made in scoping, because it determines the transport and signing path.

How delivery works

1. Scoping call. We walk your invoice types, your tax scenarios (tevkifat, istisna, ihracat, OTV), your integrator or portal arrangement, and your document series. You show us three real invoices; those become the acceptance tests. 2. Fixed quote. You receive a written scope with the field mapping, the screens, the reports and the acceptance criteria, at a fixed price. Nothing starts until you approve it. 3. Build. Typical lead time is 2 to 4 weeks from approval. This app is built for you — it is not sitting on a shelf waiting to be downloaded. 4. Install into test. We install into your test company database first, run your real documents through it end to end against the test environment of your integrator or GIB, and hand you a written test script to work through with your own finance staff. 5. Install into production. Once you sign off on test, we schedule the production installation, migrate the configuration, and stand by for the first live transmission day. 6. Support. A support window is included from go-live, covering defects, GIB schema changes published in that window, and questions from your team.

What we do not claim

This is not a certified product and ECOSIRE is not an authorised integrator. If Turkish law requires you to transmit through a licensed private integrator, you keep that contract and we integrate with it. We build the SAP Business One side, and we build it against your actual documents.