ERP OperationsFree worksheetPDF, Excel, Word exportDiscrete ManufacturingEurope

ERP Interface Inventory and Register Worksheet

Interfaces are where ERP projects lose weeks. They are often undocumented, owned by someone who left, and discovered during testing. An interface register lists every connection so the team can decide what to keep, rebuild, replace by standard functionality or retire.

Download:
Interface IDInterface nameSource systemTarget systemProtocolDirectionRuns per dayMessages per runMessages per dayBusiness criticalOwnerPlan
360
2
3,840
480
20
Total messages per day
4,702
Number of interfaces
5
Average runs per day
34.8
Average messages per interface per day
940

Cover every system: shop floor machines, scanners, labelling, bank, tax authority portals, EDI providers, BI tools, spreadsheets with macros and manual file drops.

Document legacy integrations faster

See how private AI can read legacy scripts and describe interfaces for your register.

Optional. The tool and every export work without this. No spam.

How to use the register

Give each interface an ID, name the source and target and record the protocol and direction. Estimate runs per day and messages per run to get daily volume, which tells you whether a simple file drop is enough or an API with retry handling is needed. Mark business-critical interfaces and name an owner. Finally, record the plan for the new ERP and update it as design decisions are made.

  • Interview each department, do not rely only on IT records
  • Include spreadsheets that are loaded or exported by hand
  • Record the owner on the business side as well
  • Revisit after each design workshop

Where to find interfaces

Check scheduled jobs and batch scripts on the ERP server, database links, middleware or integration platform logs, EDI provider portals, bank connection settings, file shares with regular drops, and the licence list of third-party tools. In European plants, also look for tax and customs connections, such as e-invoicing networks, Intrastat reporting and SEPA bank formats.

Using the volume numbers

Daily message volume guides technical choices. A few hundred messages a day can go through scheduled files, while thousands of small confirmations from the shop floor suit an API or queue with monitoring. Peaks matter more than averages, so note month-end or shift-change spikes in the comments.

Common mistakes

The most common failure is an incomplete inventory that misses the small, forgotten integrations, such as a label printer fed by a script. Another is listing interfaces without a business owner, which makes testing and sign-off slow. Finally, avoid copying all interfaces one-for-one; many exist only to work around old system limits.

Frequently Asked Questions

How many interfaces does a typical plant have?

A mid-size manufacturer often has between 15 and 60 interfaces once banks, EDI, carriers, MES, PLM, BI and tax connections are included. Counts higher than expected are normal when the inventory is done properly.

What do Keep, Rebuild, Replace and Retire mean?

Keep means it works unchanged. Rebuild means the function is needed but must be re-implemented for the new ERP. Replace by standard means the new system or a vendor connector covers it. Retire means the need has gone.

Should manual file uploads be listed?

Yes. Manual uploads are interfaces that depend on a person and a spreadsheet. They are fragile and often high risk at cutover because the knowledge sits with one user. Record them and decide whether to automate.

How do I treat interfaces to government systems?

List them as critical, with the owner in finance or compliance, and note the legal deadline and format version. Formats and portals change, so confirm requirements with your tax adviser or the vendor's current documentation.

If you want help reading old integration scripts and documenting what they do, AI tools running on your own servers can summarise them for you. We can show how. Optional.