Skip to content
XSIS
Talk to an engineer

Industries

Manufacturing and enterprise ERP

Your ERP at the centre, with plants, suppliers and finance connected to it

ERP extensions, MES and supplier integrations, EDI and planning data for manufacturers and multi-entity enterprises.

Talk to an engineer
An engineer monitors systems from a control room

Overview

In manufacturing and multi-entity enterprises the ERP is the system of record, but it is rarely the only system. Plants run MES and quality tools, suppliers and customers exchange EDI, banks hold the cash, and planners still work in spreadsheets.

We extend and connect the ERP so that orders, production, stock, quality data and finance flow between these systems without rekeying. We work with SAP S/4HANA, Microsoft Dynamics 365, Oracle NetSuite, Oracle Fusion Cloud ERP, Odoo and Sage, without implying a partnership with their vendors.

We also build the tools around the ERP that people use on the shop floor and in the office: mobile apps for stock and maintenance, supplier portals and planning dashboards.

What we build

ERP extensions

Custom modules, reports and workflows built with the ERP’s own extension tools, kept apart from the standard code so upgrades stay possible.

Shop-floor integration

Production orders, confirmations, scrap and quality results exchanged between MES, machines and the ERP.

Supplier and customer portals

Order confirmations, forecasts, delivery schedules and invoices shared with partners.

Mobile tools

Apps for stock movements, picking, maintenance and inspections, built for scanners and gloved hands.

Planning and reporting data

Data pipelines and dashboards for demand, capacity, inventory and margin.

Multi-entity finance

Intercompany postings, consolidation inputs and bank connectivity across entities and countries.

How it connects

The ERP at the centre, every connection monitoredBanks, stores, payment networks and third parties connect to the ERP through one integration layer. Anything that fails lands in a queue with an alert, never in silence.ERPERPSAP S/4HANA, OracleNetSuite, Dynamics365, Odoo, SageXSISIntegration layerAPIs, queues,mapping andvalidationBankBanksPayments, statusreports, statementsPOSPOS and storesSales, returns, stockand pricesGatewayPayment gatewayand acquirerCard authorisation andsettlementThird partyThird partiesCRM, logistics, tax,KYC and identityServiceMonitoring andexception queueRetries, alerts andreconciliation breaksPeopleYour operationsteam1REST/JSON · ODataIDoc2ISO 20022 pain.001SFTP H2H3camt.053MT9404REST/JSON5REST/JSON6ISO 85837SFTP8REST · SOAPwebhook910

The ERP at the centre, every connection monitored

Banks, stores, payment networks and third parties connect to the ERP through one integration layer. Anything that fails lands in a queue with an alert, never in silence.

  • Primary flow
  • Asynchronous
  • Exception path

The flow, step by step

  1. From ERP to Integration layer: Orders, invoices and payment runs, over REST/JSON · OData · IDoc (primary flow).
  2. From Integration layer to Banks: Payment files, over ISO 20022 pain.001 · SFTP H2H (primary flow).
  3. From Banks to Integration layer: Statements, over camt.053 · MT940 (asynchronous).
  4. From POS and stores to Integration layer: Sales and returns, through an event queue, over REST/JSON (asynchronous).
  5. From Integration layer to POS and stores: Prices and stock, over REST/JSON (primary flow).
  6. From POS and stores to Payment gateway and acquirer: Card authorisation, over ISO 8583 (primary flow).
  7. From Payment gateway and acquirer to Integration layer: Settlement files, over SFTP (asynchronous).
  8. From Integration layer to Third parties: Customers, shipments and tax documents, over REST · SOAP · webhook (primary flow).
  9. From Integration layer to Monitoring and exception queue: Failed messages, to a dead-letter queue (exception path).
  10. From Monitoring and exception queue to Your operations team: Alerts and breaks to resolve (exception path).
ERP to bank: payments out, statements inApproved payments leave the ERP as signed ISO 20022 files over a host-to-host channel. Status reports and statements come back the same way and are matched to open items. Rejections and unmatched lines go to your team with the reason attached.ERPERPPayment runs, openitems, general ledgerXSISIntegration layerMapping, validation,signing andschedulingGatewaySecure bankchannelHost-to-host SFTP,EBICS or bank APIBankBankPayments and cashmanagementServiceReconciliationengineMatching rules andtolerancesPeopleTreasury andfinance teamReviews rejectionsand breaks1REST/JSON · IDoc2ISO 20022 pain.001OpenPGP3SFTP H2H4pain.002 · camt.053MT9405SFTP H2H6camt.0537REST/JSON8pain.002RJCT910

ERP to bank: payments out, statements in

Approved payments leave the ERP as signed ISO 20022 files over a host-to-host channel. Status reports and statements come back the same way and are matched to open items. Rejections and unmatched lines go to your team with the reason attached.

  • Primary flow
  • Asynchronous
  • Exception path

The flow, step by step

  1. From ERP to Integration layer: Approved payment run, over REST/JSON · IDoc (primary flow).
  2. From Integration layer to Secure bank channel: Signed and encrypted payment file, over ISO 20022 pain.001 · OpenPGP (primary flow).
  3. From Secure bank channel to Bank: Delivered to the bank, over SFTP H2H (primary flow).
  4. From Bank to Secure bank channel: Status reports and statements, over pain.002 · camt.053 · MT940 (asynchronous).
  5. From Secure bank channel to Integration layer: Collected and validated, over SFTP H2H (asynchronous).
  6. From Integration layer to Reconciliation engine: Statement lines, over camt.053 (asynchronous).
  7. From Reconciliation engine to ERP: Matched entries posted, over REST/JSON (primary flow).
  8. From Integration layer to Treasury and finance team: Rejected payments, with the reason code, over pain.002 RJCT (exception path).
  9. From Reconciliation engine to Treasury and finance team: Unmatched lines: a reconciliation break (exception path).
  10. From Treasury and finance team to ERP: Corrected and resubmitted (exception path).

Typical integrations

EDI with partners

Orders, despatch advice and invoices in EDIFACT or ANSI X12.

Banks

Payments and statements for every entity, in ISO 20022 and MT formats.

MES and plant systems

Manufacturing execution, quality and maintenance systems, through APIs, OPC UA gateways or files.

CRM and commerce

Customers, quotes and orders from CRM and e-commerce platforms.

Engineering for the rules

Traceability

Batch and serial numbers are carried through every integration, so a recall or an audit can follow a part from supplier to customer.

E-invoicing and tax

We connect the e-invoicing and tax reporting platforms each country requires, and keep the records they ask for.

Segregation of duties

Integrations run under named technical users with only the rights they need, and every posting can be traced to its source.

Questions and answers

Will custom work block our ERP upgrades?

Not if it is built the right way. We use the ERP’s supported extension points, such as APIs, events and extension frameworks, and keep custom code apart from the standard product. Each extension is documented and tested, so it can be checked against a new release before you upgrade.

Link to this question
Which ERP systems do you work with?

We work with SAP S/4HANA and SAP Business One, Microsoft Dynamics 365 Finance and Supply Chain Management and Business Central, Oracle NetSuite, Oracle Fusion Cloud ERP, Odoo, and Sage Intacct and Sage X3. Naming a product does not mean a partnership with its vendor. Tell us your version and modules, because they decide the integration options.

Link to this question
Do you implement ERP systems?

Our focus is extending and integrating ERP systems rather than running full implementations. We often work alongside your implementation partner and take on the integrations, data migration, custom extensions and the apps around the ERP, so the core project can stay on its plan.

Link to this question
Can you migrate our data to a new ERP?

Yes. We profile and clean the data, map it to the new structures, and run trial migrations until the results reconcile with the old system. The cut-over is rehearsed, and after go-live open items, balances and stock are checked against agreed totals.

Link to this question
Can one integration serve several companies and countries?

Yes. We design integrations to handle several legal entities, currencies, banks and tax rules from one platform, with the settings for each entity held as configuration rather than code. Adding an entity then means adding configuration and tests, not a new integration.

Link to this question
What drives the cost of ERP integration work?

The number of systems and partners, how many message types each one needs, the quality of the data, the extension options of your ERP version, and how much testing your partners require. We estimate per flow after discovery, so you can start with the flows that save the most effort.

Link to this question

Tell us what you need to build or connect.

Describe the systems, the timeline and the constraints. The right engineers take it from there.

Talk to an engineerSee how we work
  • Our team will call you within 24 hours during your preferred time slot
  • Our team is available 24/7