Integrating In-House Systems with ERP: Data Integrity Rules You Can't Skip
Last updated: November 2026
Integrating in-house systems with an ERP such as SAP, Oracle, Microsoft Dynamics 365 or NetSuite is less about connectivity and more about data integrity. Master data ownership, identifiers, reference data, validation, transaction handling, reconciliation and auditability decide whether an integration supports finance and operations or quietly corrupts them. This article sets out ten data integrity rules for ERP integrations with internally built systems, explains how to connect systems without an API, and shows how no-code platforms such as ZigiOps can help.
ERP systems are unforgiving. A wrong cost center, a duplicated vendor or a missing tax code does not just look untidy; it affects financial statements, payments and compliance. That is why ERP teams are cautious about integrations, and why in-house systems are often kept at arm's length, exchanging data through manual entry or spreadsheets.
Yet in-house systems hold important operational data: production records, project hours, internal orders, field service jobs, asset details and procurement requests. Connecting them to the ERP removes manual work and delays, as long as data integrity is protected. The rules below make that possible.
The rules apply regardless of the ERP vendor or integration technology. They are written for integration architects, ERP teams and finance stakeholders who need to agree on how in-house data should enter the ERP, and how ERP results should flow back.
Why in-house systems and ERP are a delicate combination
- Different data standards. In-house systems often use free text where the ERP expects codes.
- Weaker validation. Internal tools may allow values the ERP would reject.
- Unclear ownership. Customer, vendor or product data may be maintained in both places.
- Limited interfaces. Many in-house systems lack APIs and expose only databases or files.
- Audit requirements. ERP transactions need traceability that in-house systems may not provide.
Rule 1: Define a system of record for every master data object
For each master data object, such as customers, vendors, materials, cost centers, projects and employees, decide which system owns it. In most cases the ERP owns financial master data, and in-house systems consume it. Where an in-house system creates master data, define how it is approved and created in the ERP.
Rule 2: Use stable identifiers on both sides
Every synchronized record needs a stable identifier known to both systems. Store the ERP's identifier, such as a vendor number or material number, in the in-house system, and store the in-house identifier in an ERP reference field where possible. Never match records only by name.
Rule 3: Synchronize reference data before transactions
Transactions depend on reference data: company codes, plants, cost centers, tax codes, units of measure and currencies. Synchronize this data from the ERP to in-house systems first, so in-house users can only select valid values. Most integration failures with ERP come from invalid reference values in transactions.
Rule 4: Validate before posting
Validate data in the integration layer before sending it to the ERP. Check mandatory fields, formats, value ranges and reference data. Reject or hold invalid records with a clear error, rather than letting the ERP reject them later or, worse, accepting incorrect data.
Rule 5: Respect ERP business logic
Post transactions through ERP-supported interfaces, such as APIs, BAPIs, IDocs, SOAP services or import programs, rather than writing directly to ERP tables. These interfaces apply the ERP's validation, authorization and posting logic. Direct table writes in an ERP can break consistency and support agreements.
Rule 6: Make transactions idempotent
Network issues and retries can cause the same transaction to be sent twice. Design integrations so that resending a transaction does not create a duplicate, for example by using the in-house ID as an external reference and checking for it before posting.
Rule 7: Handle partial failures explicitly
An order with ten lines may fail on one line. Decide whether to reject the whole transaction or post valid lines and flag the rest. Make the outcome visible in both systems.
Rule 8: Reconcile regularly
Even well-designed integrations drift over time. Schedule reconciliation reports that compare record counts and totals between the in-house system and the ERP, such as hours posted per project or orders per day, and investigate differences.
Rule 9: Keep a complete audit trail
Log every transfer with timestamps, identifiers, status and the user or service account involved. Auditors may need to trace an ERP posting back to its source. Integration logs are part of your financial control environment.
Rule 10: Control changes to mappings
Mapping changes, such as a new cost center rule or a changed account determination, can have financial impact. Treat them as controlled changes with approval and testing, just like ERP configuration changes.
| Rule | Prevents |
|---|---|
| System of record for master data | Conflicting and duplicate master records |
| Stable identifiers | Wrong matches and orphaned records |
| Reference data first | Invalid codes in transactions |
| Validate before posting | Rejected or incorrect postings |
| Respect ERP logic | Inconsistent data and support issues |
| Idempotent transactions | Duplicate postings after retries |
| Explicit partial failure handling | Hidden missing lines or amounts |
| Regular reconciliation | Undetected drift between systems |
| Complete audit trail | Audit findings and untraceable postings |
| Controlled mapping changes | Unapproved financial impact |
Connecting in-house systems that lack an API
The ERP side usually offers well-defined interfaces. The challenge is the in-house side. Many internal systems store data in a database without a service layer, or expose SOAP services, or provide a client library. Options include:
- Database views for reading in-house data and staging tables for writing ERP results back.
- SOAP services where the in-house system offers them.
- Libraries that encapsulate the in-house system's business logic.
- Files for batch flows where timing allows.
ZigiOps can integrate any system with any other through an API, SOAP, a database or a library. An in-house system therefore does not need an API to be integrated with the ERP. New connectors are typically built in about three days, and the integration is configured without code, including validation conditions, mapping tables and bi-directional status updates.
Example: project hours from an in-house tool to the ERP
An engineering services company records billable hours in an internally built project tool backed by an Oracle database. Hours must be posted to projects in the ERP for billing and cost accounting.
- Projects, work packages and activity types are synchronized from the ERP to the in-house tool daily, so engineers can only book against valid codes (Rules 1 and 3).
- Approved hours are read from a database view, each with a unique entry ID (Rule 2).
- The integration validates project status, activity type and hours before posting (Rule 4).
- Hours are posted through the ERP's standard time-recording interface (Rule 5), using the entry ID as an external reference to avoid duplicates (Rule 6).
- Rejected entries are written back to a staging table with the ERP error, and the engineer sees the reason in the in-house tool (Rule 7).
- A weekly report compares total hours per project in both systems (Rule 8), and every transfer is logged (Rule 9).
Typical in-house systems that feed the ERP
| In-house system | Data sent to ERP | Data returned from ERP |
|---|---|---|
| Project or time-tracking tool | Hours, expenses, project progress | Projects, activity types, billing status |
| Production or shop-floor system | Production confirmations, scrap, material usage | Production orders, materials, routings |
| Field service tool | Completed jobs, parts used, service charges | Customers, contracts, spare parts prices |
| Internal procurement portal | Purchase requisitions | Purchase order numbers, approval and delivery status |
| Asset register | New, moved and retired assets | Asset numbers, depreciation data, cost centers |
Each of these flows benefits from the same integrity rules. The specific ERP interfaces differ, but the principles of ownership, validation, idempotency and reconciliation stay constant.
Choosing the right integration platform for ERP flows
The integration platform should make the ten rules easy to follow rather than something every developer must remember. When evaluating options, check whether the platform supports:
- Conditions and validation rules configured without code
- Mapping tables for codes such as cost centers, tax codes and units of measure
- Correlation through external references to prevent duplicates
- Bi-directional status updates, so in-house users see ERP results and errors
- Detailed, exportable logs for audits
- Connectivity to in-house systems through databases, SOAP and libraries, not only APIs
- Deployment on-premises when ERP and in-house systems are both inside the corporate network
ZigiOps covers these requirements and can be deployed on-premises or in the cloud, which is useful when ERP systems and internal tools sit in different network zones.
Involving finance early
ERP integrations are often designed by IT teams and only reviewed by finance shortly before go-live. That is too late. Finance and controlling teams understand account determination, cost allocation and period-end processes, and they will be the ones explaining discrepancies to auditors. Involve them when defining mappings and reconciliation reports, and agree on how integration errors will be handled during month-end and year-end closing.
It is also worth agreeing on cut-off rules. If an in-house system records hours or production on the last day of a period, the integration must ensure they are posted in the correct period, or clearly flagged if they arrive late.
Testing ERP integrations
- Test with realistic volumes, including peak periods such as month-end.
- Test invalid data deliberately: missing reference values, closed projects, blocked vendors.
- Test retries and network failures to confirm no duplicates are created.
- Test partial failures in multi-line transactions.
- Run a reconciliation on test data and confirm totals match.
- Have finance users review postings in the ERP before go-live.
Security and compliance
- Use dedicated integration users in the ERP with only the authorizations needed for specific transactions.
- Maintain segregation of duties: the integration should not be able to approve what it posts.
- Encrypt all connections and protect credentials.
- Minimize stored data in the integration layer. ZigiOps does not store the data it transfers.
- Include integration logs and mappings in internal control reviews.
Frequently asked questions
What is ERP integration with in-house systems?
It is the process of connecting internally built applications with an ERP so that master data, transactions and status flow automatically between them, while preserving data integrity.
Why is data integrity so important in ERP integrations?
ERP data drives financial statements, payments and compliance. Errors introduced by integrations can have financial and regulatory consequences.
Should in-house systems write directly to ERP tables?
No. Use ERP-supported interfaces that apply validation and business logic. Direct table writes can cause inconsistency and may violate support agreements.
How do I avoid duplicate postings in ERP integrations?
Use unique external references from the source system and check them before posting, so retries do not create duplicates.
Can an in-house system without an API be integrated with SAP or Oracle?
Yes. The in-house side can be accessed through its database, SOAP services or libraries. Platforms such as ZigiOps support these methods without custom code.
How often should ERP integrations be reconciled?
It depends on volume and risk. Daily or weekly reconciliation is common for financial transactions; monthly may be enough for slow-changing master data.
Who should be involved in designing ERP integrations?
ERP and finance teams, the owners of the in-house system, the integration team and, for financial flows, internal audit or controls. Involving finance early prevents surprises at period-end.
What should happen when the ERP rejects a transaction?
The integration should log the error, keep the record in a visible error state and return the reason to the in-house system, so the right person can correct and resend it.
How do period-end closings affect ERP integrations?
Transactions must be posted in the correct period. Define cut-off rules, monitor late arrivals and agree with finance how corrections are handled after a period is closed.
Key takeaways
- ERP integrations with in-house systems are primarily a data integrity challenge.
- Define systems of record, use stable identifiers and synchronize reference data first.
- Validate before posting, respect ERP logic and design idempotent transactions.
- Reconcile regularly, keep a full audit trail and control mapping changes.
- ZigiOps connects in-house systems, even without an API, to ERP platforms through no-code configuration.
