e-conomic integration
A e-conomic integration connects the accounting product with other systems. It can reuse supported data and reduce repeated entry. Direction, timing, posting and payment recording depend on the chosen connector and configuration.
Prepared with AIContent updated
Define the connector’s job
e-conomic is accounting software; the integration is the specific connection to another product. An API may expose capabilities a ready-made connector does not use. Choose based on supported workflows, not merely on both systems having an API.
e-conomic: transfer and reconciliation
Illustrative workflow to check against the selected connector’s actual capabilities.
- Source
Unique customer and invoice reference
- Mapping
Accounts, tax, currency and document type
- Transfer
Check response and store the target record ID
- Reconcile
Compare invoice, payment and accounting separately
A retried event must not create an extra invoice. MRR and accounting recognition need separate rules.
Customers, invoices and payments are different data
Agree which system owns customers, products, prices and account mappings. Check whether the connector creates a draft, issues an invoice, records a payment or only exports a document. These are different actions. A credit note is not by itself a cash refund.
An illustrative invoice workflow
A subscription in the source system provides the billing basis. If supported, the connector transfers agreed fields into the accounting product with a unique reference. A later payment must be matched separately. Errors need visibility and a retry process that does not create duplicates.
MRR is not accounting revenue
MRR normalises eligible recurring subscription prices to a month. Accounting revenue follows the applicable accounting policy, while bank movements record cash. Use subscription status and service intervals for metrics, and reconcile with invoices and accounting without assuming every amount must match.
Test and maintain the connection
Review accounts, tax, currency, customer identifiers and permissions. Use the actual testing options available and prevent test entries reaching live accounts. Check partial payments, credit notes, changed customers and retries where relevant and supported.
Measure the actual benefit
Measure time spent entering, reconciling and correcting data before and after implementation. Include operation, maintenance and licence costs when assessing the benefit. Freed capacity is not automatically a cash payroll saving, and real-time updates, recognition schedules or correct tax reporting require actual evidence.
Questions and answers
What is transferred automatically?
Only the fields and actions documented for the connector. Check direction, update frequency and error handling. The accounting product having an API does not make every function available in a chosen integration.
Can I calculate MRR from the accounts?
Invoice history may provide inputs, but you also need subscription intervals, status and normalisation. Cash and recognised revenue are not directly equal to MRR. Document the metric policy and reconcile differences.
Are partial payments and refunds supported?
Verify the actual connector. A credit note adjusts billing; a refund moves money. Choose a process that records both events and prevents duplicate entries.
How do I test safely?
Follow current access and testing documentation. Protect credentials and limit access to what is needed. Test selected cases and ensure fictitious data cannot become real charges or posted entries.
What should I do after a transfer error?
Find the source reference and error, check whether the target record already exists, and correct the cause before retrying. Reconcile systems and assign responsibility for exceptions that cannot be resolved automatically.
