E-Invoice Integration

Your order or sales document is converted into a UBL-TR XML document and sent to your integrator's API. The integrator delivers an e-Fatura to the buyer through the Revenue Administration (GİB) and reports an e-Arşiv invoice to GİB, and we write the returned status back into your system.

An e-Fatura is issued between a seller and a buyer who are both registered in GİB's e-Fatura system, and it reaches the buyer electronically through GİB. If the buyer isn't registered, a consumer for example, an e-Arşiv invoice is issued instead; it is sent electronically or on paper and its details are reported to GİB. The integration makes that choice for each invoice by checking the buyer.

On the GİB portal invoices are issued one by one by hand, and there is no official API for sending them from your own software. Direct integration with GİB needs a separate approval, infrastructure and information security process, so most companies that want to invoice automatically from their software work with a private integrator. We connect to your current integrator's API, and if you switch integrators only the connection layer changes.

We aren't tied to any one integrator and can work with GİB-authorised private integrators that offer an API. If you don't have one yet, the choice is yours; we help you assess the technical side.

Not always. If invoices come from an ERP such as Logo, Mikro, Netsis or SAP, the right route is often to bring e-commerce and marketplace orders into the ERP and invoice from there. We build a direct e-invoice integration when invoices need to be issued from a system outside the ERP.

It depends on the document types, the number of channels that issue invoices and your integrator's API. After a discovery call we share a clear timeline and a transparent quote as a fixed project price or a monthly retainer; your integrator's own fees are separate. You can also outline your needs in our project planner.