SAP
SupportedSAP S/4HANA / SAP ERP
Master data · Finance · Purchasing · Inventory · Orders
OData and SOAP APIs for purchasing and logistics processes.
Talk about SAP integration ERP & existing systems
You do not have to replace your ERPto run on INVO.
SAP, Oracle, Microsoft Dynamics or an in-house solution can remain your central ERP. INVO integrates with the environment you have and can run as a specialized operating layer for planning, purchasing, inventory and production.
Your ERP
SAP / Oracle / Dynamics
- Finance
- Accounting
- Master data
- Controlling
Integration layer
INVO
Drone production operations
- Planning
- Purchasing
- Inventory
- Production
- MES
- Quality
- Plant operations
Works with your current stack
INVO can work with the systems already running in your organization.
Integration statuses reflect the actual state on the INVO side. We do not mark an ERP as integrated without a real, deployed integration.
Oracle
SupportedOracle Fusion Cloud ERP / SCM
Finance · Purchasing · Supply chain · Inventory
REST APIs for Financials, Procurement and Supply Chain Management.
Talk about Oracle integrationMicrosoft Dynamics
SupportedDynamics 365 / Business Central
Finance · Operations · Inventory · Master data
Data entities over OData, REST APIs and Dataverse synchronization.
Talk about Microsoft integrationOther ERP / legacy systems
Custom buildREST · SOAP · OData · Files · Middleware
Scope defined per system
If your organization runs its own ERP, an industry solution or a legacy system, we design the right data-exchange model for it.
Talk about your ERPWe start from what the systems need to exchange, not from a vendor logo.
One owner per data domain
For every type of data, we define a single source of truth.
The most important part of a good integration is not the number of endpoints. It is settling which system owns each piece of information.
- SupplierSource of truthSAP
INVO consumes the supplier record.
- BOMSource of truthINVO
The ERP can receive the resulting data it needs.
- Purchase orderSource of truthDepends on the architecture
INVO → SAP or SAP → INVO.
- Production consumptionSource of truthINVO
Actual consumption can be passed into the financial processes.
One record can appear in several systems. Only one of them should own it.
System responsibilities
Each system should be responsible for what it does best.
This is an example split. The final division of responsibility between systems is defined during Solution Design for each customer.
| Area | Your current ERP | INVO |
|---|---|---|
| General ledger | Owner | — |
| Accounting | Owner | — |
| Corporate finance | Owner | — |
| Cost centers | Owner | Consumes |
| Supplier master data | Shared | Consumes |
| Customer master data | Shared | Consumes |
| Components | Shared | Operates |
| BOMs | — | Owner |
| Demand forecasting | — | Owner |
| Production scheduling | — | Owner |
| Purchase planning | — | Owner |
| Warehouse operations | Shared | Operates |
| Production execution | — | Owner |
| MES | — | Owner |
| Quality | — | Owner |
| Actual costs | Financially | Operates |
We are not building a second ERP next to your ERP. We are splitting responsibility between systems.
Data exchange with the ERP
We sync the data needed to run the process end to end.
Not all of these flows are required. The direction and scope of each synchronization are designed per customer.
Master data
- Suppliers
- Customers
- Products
- Components
- Units of measure
- Locations
- Cost centers
- Employees / users
Purchasing
- Purchase requirements
- Purchase orders
- Supplier data
- Prices
- Confirmations
- Receiving
Inventory
- Inventory levels
- Movements
- Receiving
- Consumption
- Adjustments
Production
- Production orders
- Component requirements
- Produced quantities
- Actual consumption
- Production status
Finance
- Actual costs
- Accounting references
- Cost centers
- Invoices
- Financial documents
Sales and contracts
- Sales orders
- Demand
- Customer contracts
- Locations
ERP → INVO
- Master data
- Customers
- Suppliers
- Cost centers
- Sales orders
INVO → ERP
- Production actuals
- Consumption
- Receiving
- Operating costs
- Purchase orders
The plan comes from business data. The actuals come back from production.
Vendor ecosystems
What INVO looks like next to SAP, Oracle and Dynamics.
Every major ERP exposes its own integration surface. We design around the one you actually run.
INVO alongside SAP
SAP S/4HANA
SAP → INVO
- Customers
- Suppliers
- Selected material data
- Cost centers
- Sales demand
INVO → SAP
- Receiving information
- Component consumption
- Produced quantities
- Operating costs
- Purchasing documents
Example scope, defined individually. SAP exposes integration APIs through OData and SOAP, including communication with external systems and EDI.
Oracle
Financials · Procurement · SCM · Inventory
- Planning
- BOMs
- Purchasing operations
- MES
- Quality
Oracle Fusion Cloud exposes REST APIs for Financials, Procurement and Supply Chain Management, so the integration architecture can be designed around specific business domains.
Microsoft Dynamics
Finance & Operations · Business Central · Dataverse
- Planning
- Purchasing
- Inventory
- MES
- Production
Dynamics 365 Finance & Operations exposes public data entities over OData, Business Central recommends REST APIs as the primary web-service integration, and data can sync with Dataverse in both directions.
Your system does not have to be SAP or Oracle.
Many drone manufacturers run in-house tools, local ERPs or systems that grew with the company. INVO can be integrated with that environment too.
- REST API
- SOAP
- OData
- SFTP
- XML
- CSV
- Database integration
- Middleware
- Dedicated connectors
We do not start by asking which ERP you use. We start by asking which data has to flow between systems.
The right integration for the right process
Not all data has to sync the same way.
We match the synchronization model to the business process, not the other way round.
Real time
- Critical operational changes
- Statuses
- Data needed immediately
Near real time
- Inventory
- Operational orders
- Selected master data
Batch
- Selected financial data
- Reporting
- Large data sets
Designed during the rollout, not bolted on afterwards.
We do not connect systems blind. The integration architecture is designed during Discovery and Solution Design.
- 01System landscapeWhich systems exist today?
- 02Process mappingWhich system takes part in which process?
- 03Data ownershipWhich system is the source of truth?
- 04Data mappingHow do the data models correspond?
- 05DirectionWhich data flows which way?
- 06FrequencyReal time, near real time or batch?
- 07Error handlingWhat happens when something fails?
- 08MonitoringHow do we confirm the sync is correct?
Enterprise-grade integration
An integration has to be operable, not just switched on.
Once it is live, someone has to be able to see what it did and put it right when it fails.
Monitoring
Visibility of the synchronization state.
Error handling
Handling of failed messages.
Retry
The ability to reprocess data.
Audit trail
What was sent, when, between which systems, and with what result.
You do not have to integrate everything on day one.
The rollout can run in phases. The target architecture can be complete from the start while the integrations go live in sequence.
- Phase 1Master data
- Phase 2Orders and demand
- Phase 3Inventory and purchasing
- Phase 4Production actuals
- Phase 5Finance and advanced analytics
Each phase is usable on its own — no stage waits on the one after it.
Why coexistence matters
Grow operations without rebuilding the whole enterprise stack.
Protect the current investment
You do not walk away from years of investment in your existing ERP.
Lower rollout risk
A smaller change footprint in the corporate systems.
Specialized capability
You add functionality built specifically for drone production.
Plan meets execution
You connect corporate data to what actually happens on the floor.
Finance processes stay put
Existing accounting processes can continue unchanged.
Phased rollout
INVO can be deployed module by module and site by site.
ERP & existing systems
Show us your current architecture.
During discovery we go through the systems already running in your organization, settle data ownership and design where INVO belongs. You do not have to start by replacing the ERP.