Native IBM i EDI — no front-end servers, no middleware.

IPLS TBT400 / TBT EDI runs entirely within IBM i. All major EDI standards. highgrove is a UK IPLS partner — deployed live at Magna Specialist Confectioners.

Most EDI solutions sit in front of IBM i. IPLS TBT EDI runs inside it — native, no additional servers, no middleware dependency. If you're on IBM i and want EDI that stays on IBM i, this is it. highgrove is a UK IPLS partner with a live deployment at Magna.

NativeIBM i — no servers
AllMajor EDI standards
LiveAt Magna
Products

The IPLS product range

TBT400

Multi-protocol comms & file transfer

IBM i native multi-protocol communications and managed file transfer — AS2, SFTP, FTP, FTPS and more. No front-end servers.

TBT EDI

Any-to-any EDI translation

Native IBM i EDI mapping and translation. EDIFACT, ANSI X12, TRADACOMS, XML and all major standards. Direct integration with IBM i applications.

TBT AES

Combined comms + EDI

TBT400 and TBT EDI combined — a single native IBM i solution covering file transfer, communications and EDI translation end to end.

EDI standards supported
EDIFACTANSI X12TRADACOMSXMLEANCOMVDAODETTERosettaNet
Live deployment

IPLS TBT EDI is live at Magna Specialist Confectioners.

Magna runs native IBM i EDI through IPLS — managed and supported by highgrove. No front-end servers, no middleware. Direct integration with Mangrove ERP and IBM i production systems.

Read the Magna story Talk to our EDI team
Native

Runs inside IBM i

No additional servers. No middleware. No external dependencies. IPLS lives entirely within the IBM i environment.

Integrated

Direct ERP connectivity

Direct integration with IBM i applications and ERP — no import/export cycles or file-based hand-offs.

Supported

UK partner — highgrove

highgrove provides UK-based implementation, integration and ongoing 1st-line support for IPLS.

Common questions

Things IBM i EDI specialists ask us

What does "native IBM i" actually mean?

It means TBT EDI runs as a native IBM i application — no Windows servers, no Linux containers, no external middleware. It integrates directly with IBM i data and applications at the OS level.

Can it handle our trading partner requirements?

Yes. TBT EDI supports all major EDI standards (EDIFACT, ANSI X12, TRADACOMS, XML and others) and all major transport protocols (AS2, SFTP, FTP, FTPS). Speak to highgrove about specific partner requirements.

What's the difference between TBT400, TBT EDI and TBT AES?

TBT400 handles communications and managed file transfer. TBT EDI handles EDI mapping and translation. TBT AES is the combined solution — both in one. highgrove will recommend the right configuration for your environment.

Do you provide implementation as well as licences?

Yes. highgrove handles implementation, integration with your IBM i applications, trading partner setup and ongoing UK-based 1st-line support.

Talk to our IBM i EDI team