The product

It does the typing. Your team does the deciding.

LegacyBridge sits in front of your AS/400 (IBM i) system, prepares the entry from the document, and hands the final say to one of your people.

Book a demo
Data extraction and entry into AS/400 (IBM i)–□✕FileEditViewActionsHelpWork with Document EntrySystem:LEGBRDGDocument file:ORDENT01Library:QGPLPosition to:INV-104882Document IDType options, press Enter.2=Change 5=Display details 6=PrintOpt Document Type Status_INV-104871InvoicePosted_ORD-558904OrderPostedMore...===>F3=Exit F5=Refresh F12=CancelReadySession: LEGBRDGCaps: OffStatementsOrdersRX claimsInvoices

Step by step

From the inbox to an approved entry

Seven steps. The sixth one is a person.

Your AS/400 (IBM i) screen
The AS/400 (IBM i) entry screen as it looks today
Unchanged. Nobody types into it.
What your team sees
The clean review screen, filled in and waiting for approval
Filled in, side by side with the document, waiting for a yes.
  1. Step 1The document arrivesThrough email, SFTP, cloud storage, an API or another agreed source.
  2. Step 2LegacyBridge reads the informationCustomer and supplier numbers, invoice and order numbers, product codes, quantities, prices, dates, tax codes, claim and policy numbers, shipping references and account information.
  3. Step 3The data is checkedMissing information, incorrect formats, unexpected values and your other business rules.
  4. Step 4The correct AS/400 (IBM i) screens openThe same menu path and screen sequence an employee would follow.
  5. Step 5The fields are preparedThe information is placed into the required AS/400 (IBM i) fields.
  6. Step 6A person can review the transactionYour employee compares the prepared transaction with the original document and decides whether to approve it.
  7. Step 7The result is recordedWhat was read, what was entered, what was flagged and who approved the transaction.

What it handles

Built for the documents you actually get

Any readable document

Emailed PDFs, scans, spreadsheets, printed paperwork — or a photo taken on a phone.

Reading that fits your senders

Every supplier lays out an invoice differently. Reading is tuned to the documents you receive.

Your business rules applied

Totals, tolerances, required fields and account codes checked before entry.

The screens you already use

The same menus and fields your team knows. Nothing new to learn.

Entry in the right order

Fields are filled the way an experienced clerk would fill them.

A stop before submission

The entry is completed and then waits for a person to approve it.

A clear record

What was entered, by whom, and when — kept and reviewable.

Your system

Nothing changes in your systems

No replacement, no rewrite, no new connection to open up. If your team can enter it on a screen, it can be prepared the same way — including in-house programs written decades ago and still running the business.

ORDER ENTRY AS/400
CUST . . . . . . 004182
ITEM . . . . . . AX-7741__
QTY . . . . . . 0024
PRICE. . . . . . 000184.50

AS/400 (IBM i) is the same system historically known as AS400 and iSeries, after two rebrandings.

Where documents come from

However it arrives, it can be read

Emailed

A supplier PDF in the inbox.

Scanned

A batch off the office scanner.

Spreadsheet

A file someone exported.

Phone photo

Snapped on the warehouse floor.

Portal download

Pulled from a customer portal.

Questions

Product questions, answered plainly

Yes. UiPath and other broad RPA platforms can automate AS/400 (IBM i) terminal screens. The difference is that UiPath provides a platform for building many kinds of automation, while LegacyBridge is a focused product for moving information from documents into AS/400 (IBM i).

No. LegacyBridge is designed to work with your existing AS/400 (IBM i) application and screen-based process.

No. LegacyBridge can follow the same AS/400 (IBM i) screen workflow your employees use today. A direct API integration may still suit some processes, but it is not required to test or use LegacyBridge.

Yes. AS/400 (IBM i) is the same system historically known as AS400 and iSeries. If your team calls it any of those names, this is for you.

Yes. The controlled proof can use one of your real documents, your actual workflow and an access setup approved by your team.

It does not have to. LegacyBridge can prepare the transaction and stop before final submission. Your employee checks the result and decides whether to approve it.

Yes. The environment, account permissions, accessible screens, approval point and allowed actions can be agreed before the proof begins.

LegacyBridge can flag missing or uncertain information and send the item to a person for review. It does not need to guess.

Known validation messages can be handled as part of the workflow. Unexpected responses can stop the transaction and send it for review.

Yes. You can begin with approval required for every transaction. Later, you may choose to automate only simple and high-confidence cases.

No. Your existing process remains available throughout the proof. You can test selected documents while the rest continue through the normal process.

It can work with custom applications when the required process is available through supported AS/400 (IBM i) terminal screens.

Common examples include invoices, sales orders, purchase orders, insurance claims, work orders, receiving documents, shipping documents, inventory forms and customer or account forms — in any readable format, including a photo taken on a phone.

Your team shows the current document and AS/400 (IBM i) workflow, explains the business rules and reviews the prepared transaction. LegacyBridge handles the workflow configuration with you.

The company behind LegacyBridge is certified to ISO 9001 for quality management, ISO/IEC 27001 for information security management and ISO/IEC 27017 for cloud security controls. LegacyBridge also uses PCI DSS-compliant infrastructure.

Yes. The team behind LegacyBridge has delivered and supported systems for Fortune 500 companies and organizations such as PUMA, The New York Times, The Met, Boy Scouts of America and the University of Michigan.

You decide whether to stop, test more documents or move the workflow into wider use. There is no required company-wide rollout.