Implementation guide · from order to e-invoice and e-archive

Who is this guide for? Finance, accounting, ecommerce and integration teams selling online in Turkey.

E-invoice or e-archive integration is not a PDF generator. It is a traceable route from an order with correct customer and tax data to a compliant document. Document type, provider response, cancellation and return should be designed together with the order lifecycle.

Validate document-driving data before the order closes

Customer type, tax identity, billing address, product tax, discounts, shipping and currency affect the document decision. Leaving missing data for post-payment correction damages both service and accounting. Apply the same validation rules in checkout and the administration workspace.

MarketOne NES and Nilvera electronic invoice integration settings — **A real screen from MarketOne.** Provider, scenario, automatic creation and connection options share one configuration area.

The event chain from order to document

Payment or a defined order state triggers the request. MarketOne sends the required data to a provider such as NES or Nilvera, stores the request identity and processes acceptance or rejection. A successful number, date and file link return to the order; delivery to the customer remains auditable.

Business rejection is not a network timeout

A rule-based rejection should not be resent until its data is corrected. After a timeout or temporary outage, the system should query the same request and avoid creating a second document. Users need an understandable cause, affected order and recommended action rather than a raw provider code.

Design cancellation and return from day one

Cancellation, partial return and full return create different financial outcomes. Confirm the required document path with current official sources and a qualified adviser. Preserve the link between original and correction documents and reconcile it with refund and inventory events.

Financial and technical acceptance tests

Test document-type decisions for individual and business customers.
Use orders with different tax, discount, shipping and currency data.
Run acceptance, rule rejection, timeout and duplicate-request cases.
Reconcile document, refund and inventory for partial and full returns.
Confirm current Turkish obligations with official sources and an adviser.

Responsibility by document stage

Stage	System responsibility	Human control
Prepare	Validate order and tax fields	Exceptional customer/tax data
Submit	Request, safe retry and response log	Correct a permanent rejection
Cancel/return	Relate documents and track state	Approve the financial scenario

Pilot one normal and four exceptional documents

Run business-customer, mixed-tax, rejection, partial-return and outage examples with accounting. Launch the MarketOne–provider connection only after document, payment and order records reconcile.

Explore the MarketOne product page · Request a tailored demonstration

Ecommerce with e-invoice and e-archive integration