Integrations

Connect consumption data to the systems that bill for it

The Oeconomia API transfers structured EMIKO order records into the Partner's invoicing or accounting environment, reducing manual re-entry while preserving the link to the customer, equipment and measured usage.

Keep the source behind every figure

A completed service order carries the components that make the invoiced figure reconstructable.

EMIKO, ONE COMPLETED ORDER Order 48213 CUSTOMER Havnegade Marine ApS ASSET Pedestal A2, Vonge SERVICE Electricity QUANTITY 4.82 kWh PERIOD 14 Mar, 09:12 to 11:40 SETTLEMENT Prepaid in app OECONOMIA API PER BUSINESS, SEPARATELY YOUR FINANCE SYSTEM Ledger, period 03/2026 3110 ELECTRICITY SALES 15.42 HAVNEGADE MARINE APS, ORDER 48213 3120 WATER SALES 42.00 SANDVIG SHIPPING, ORDER 48219 3110 ELECTRICITY SALES 8.90 HAVNEGADE MARINE APS, ORDER 48224 EVERY LINE NAMES ITS ORDER

The exact payload and mappings are agreed during integration design.

What a transferred order can include

The agreed set is defined during integration design and follows your ledger structure.

  • Customer identity or account reference
  • Business and location
  • Connected asset or outlet
  • Service type
  • Start and finish time
  • Metered quantity and unit
  • Price or pricing reference
  • Settlement status
  • EMIKO order reference

Reduce manual work at period end

Accurate metering can still lead to inaccurate invoices when records are exported, adjusted in spreadsheets and keyed into another system by hand.

Less re-entry

Move agreed records electronically instead of recreating them manually.

Better traceability

Retain the source order, customer, asset, period and measured quantity behind the transferred figure.

Clear settlement treatment

Distinguish between orders paid in the customer application and orders that remain to be invoiced.

Separation by business

Where one EMIKO Partner account manages several legal entities, transfers can follow the approved business structure and ledger mapping.

An integration designed around your financial process

Every organisation has different customer references, nominal accounts, tax treatment, periods and approval rules. The integration scope should define the points listed here.

  • Which orders are transferred
  • When and how frequently records move
  • How EMIKO customers map to financial accounts
  • How services map to products or nominal accounts
  • How prepaid and invoiced orders are distinguished
  • How corrections, cancellations and exceptions are handled
  • Which references must appear on the final invoice

Reconcile before switching over

Run the integration alongside the existing process for an agreed period. Compare the order totals, settlement states and financial outputs before making it the primary transfer route.

This approach documents the mapping and gives the finance team a clear reconciliation record.

Suitable for structured procurement and audit requirements

Municipal, state and regulated Partners often need to demonstrate where a billed quantity originated and who had access to the record. EMIKO retains the operational components needed to reconstruct the order, while the integration passes the approved fields into the financial environment.

Discuss the integration scope

Bring your invoicing system, your ledger structure and the period process you follow today.

Book a demo Review security information