Manage the path from order to e-Invoice or e-Archive with tax data, scenarios, status tracking, cancellation and retention rules.

Invoice integration is more than generating a document

Turning order data into XML or PDF is only one part of the process. Incorrect taxpayer status, tax number, address, VAT, discount, currency, scenario or issue time can make a technically generated document commercially wrong. The source order and electronic document need a durable reference and an immutable processing history.

Design the complete document lifecycle

After order approval, customer and line data are validated, the e-Invoice or e-Archive route is selected and an idempotent request is sent to the provider. Provider number and state are stored, while rejected or pending documents become actionable tasks. Cancellation, return and reissue require the same testing depth as the normal path.

MarketOne NES and Nilvera e-Invoice e-Archive integration screen Real screenshot from the MarketOne administration panel.

How MarketOne connects NES and Nilvera

MarketOne configures the NES or Nilvera provider, API key and company/taxpayer data separately. e-Invoice and e-Archive actions connected with the order lifecycle remain visible in one panel. If automatic creation is enabled, its trigger state must be explicit, and a failed document must not silently stop the order.

Select provider and process with real document samples

Review monthly volume, credit model, support response, API documentation, taxpayer lookup, service level, archive access and clarity of error messages. A pilot should include corporate and individual buyers, discounts, different VAT rates, foreign currency, partial returns and cancellations.

Go-live checklist

Tax ID, legal name and address validation
e-Invoice/e-Archive routing rule
Durable order-document reference
Idempotency for repeated requests
Reject, cancel, return and reissue tests
Document status and daily reconciliation

Which metrics should define success?

Before launch, measure manual minutes per order, failure-related cancellations, inventory mismatch, failed transfers, support volume and resolution time. Compare weekly during the first four weeks and monthly thereafter. Value is not limited to revenue growth: less rework, faster reconciliation and visible exceptions are equally important outcomes.

Common implementation mistakes

Activating every channel on the same day
Moving data before defining SKU and status dictionaries
Testing only the successful path
Leaving retry rules and exception ownership undefined
Trusting automation without a daily reconciliation report

Official sources and validation

GİB e-Belge

Continue with related guides

iyzico, PayTR and Bank Transfer Integration Guide · How to Plan ERP and CRM Integration

Explore the MarketOne product page. Discuss the right integration scope for your business.

NES and Nilvera e-Invoice/e-Archive Integration