API integration · Haravan → MeInvoice

Haravan → MeInvoice V2 AIO — one shop, multiple tax IDs

Haravan → MeInvoice V2 (AIO) uses the new MeInvoice API — draft → publish on one GenNova Dev platform. Key capability: one Haravan shop connects to multiple MeInvoice accounts (multiple tax IDs), each with its own draft / publish tokens and invoice templates.

Haravan → MeInvoice V2 (AIO) uses the new MeInvoice API — draft → publish on one GenNova Dev platform. Key capability: one Haravan shop connects to multiple MeInvoice accounts (multiple tax IDs), each with its own draft / publish tokens and invoice templates.

Set a default MST for orders outside sub-mapping; assign a dedicated MST per Haravan branch, sales channel, storefront or carrier when each warehouse belongs to a different legal entity. Task logs include a MeInvoice account prefix to distinguish MST. Shares the haravan_to_meinvoice license — no extra package for V2.

  • Multiple MeInvoice MST
  • MeInvoice AIO
  • Branch / channel mapping
  • Retry & logs

Sync process

Technical flow on GenNova Dev — from API connection to logging, based on the actual convert pipeline.

  1. 1 Connect APIs on both platforms and verify license / access rights
  2. 2 Add multiple MeInvoice V2 accounts (one MST per row), set default MST
  3. 3 Sync MeInvoice V2 templates and sub-mapping per branch / channel
  4. 4 Fetch source data via real-time webhooks, scheduled sync or manual runs
  5. 5 Filter orders and pick target MST per mapping layer
  6. 6 Create draft from Haravan order → publish MeInvoice V2
  7. 7 Update lookup code on Haravan; handle returns / adjustments
  8. 8 Write detailed sync logs for lookup and error handling

Synced data

E-invoices

Issue MeInvoice automatically when Haravan orders meet rules.

  • sync_orders

Status lookup

Refresh MeInvoice RefID and update lookup code on Haravan orders.

  • refresh_meinvoice_status

Products & customers

Sync catalog and buyers to MeInvoice (can reuse AMIS cache).

  • sync_products
  • sync_customers

Mapping configuration layers

  • MeInvoice invoice template
  • Issuance conditions by order status
  • Products / tax rates
  • Buyer info / tax ID
  • Multiple MeInvoice V2 accounts (MST)
  • Default MST & assignment per branch / channel / storefront

Business benefits

  • One Haravan shop → multiple MeInvoice accounts (MST) — no extra apps
  • Assign MST per branch, channel, storefront, carrier
  • MeInvoice V2 API — draft and publish on one AIO flow
  • Automatic lookup codes; logs tagged by MST
  • Retry and alerts on failure — accounting stays in control
  • Shares Haravan → MeInvoice license — deploy V2 without buying another plan

FAQ

Are MeInvoice e-invoices created automatically from Haravan orders?

Yes. When an order meets configured conditions, the system issues an e-invoice and updates the lookup code.

How are invoice issuance errors handled?

Detailed logs per order, manual or bulk retry support and alerts on failure.

How is MeInvoice V2 (AIO) different?

V2 uses the new MeInvoice API with draft → publish on one platform, better logs and retries.

Invoices for returns / refunds?

Configurable by order type; conditions set in the MeInvoice dashboard.

Is AMIS connection required?

Not required for e-invoice issuance; product/customer cache from AMIS can be used if connected.

Can one Haravan shop issue e-invoices for multiple tax IDs (MST)?

Yes — via Haravan → MeInvoice V2 (AIO). Add multiple MeInvoice accounts (one MST per row), set a default MST and assign MST per branch / channel / storefront through sub-mapping.

Start free Contact us About GenNova Dev