How it works
From incoming document to completed AS/400 (IBM i) entry
Each document becomes a piece of work that can be tracked from the moment it arrives to the moment somebody approves it.
Book a demoInformation typically read
- Customer or supplier number
- Invoice or order number
- Product codes
- Quantities
- Prices
- Dates
- Tax codes
- Claim or policy numbers
- Shipping references
- Account information
The seven steps
Your screens, your business rules, your approval — nothing about the underlying application changes.
- Step 1The document arrivesThrough email, SFTP, cloud storage, an API or another agreed source.
- 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.
- Step 3The data is checkedMissing information, incorrect formats, unexpected values and your other business rules.
- Step 4The correct AS/400 (IBM i) screens openThe same menu path and screen sequence an employee would follow.
- Step 5The fields are preparedThe information is placed into the required AS/400 (IBM i) fields.
- Step 6A person can review the transactionYour employee compares the prepared transaction with the original document and decides whether to approve it.
- Step 7The result is recordedWhat was read, what was entered, what was flagged and who approved the transaction.
The old screen stays. Your team works from the clean one.
LegacyBridge follows the same menu path and screen sequence an employee would use. No new API is required.
Why the Proof Is Low Risk
See it work before giving it control
No automatic final submission
During the controlled proof, LegacyBridge can stop before the final AS/400 (IBM i) action. A person checks the document, extracted information and prepared fields before approving the transaction.
No forced cutover
There is no moment where the old process is switched off and the new one suddenly takes over. Your existing process remains available throughout the test. You can test LegacyBridge on one selected transaction while the rest of the team continues working normally.
No changes to the core application
LegacyBridge works with your existing AS/400 (IBM i) screens. The proof does not require changes to your RPG or COBOL application.
Start with one document
You do not need to provide a large dataset or open a full department to automation. Start with one invoice, one claim, one order or one work document.
Use your real business rules
The proof can follow the same checks, screen sequence and approval rules that your employees use today.
Keep a person in control
Every transaction can require human confirmation. LegacyBridge does not have to be allowed to complete work independently during the test.
Work within an approved security setup
Your technical and security teams can agree on the environment, access rights, permissions and data-handling rules before the proof begins.
Stop at any point
Testing one process does not commit you to a wider rollout. The proof exists to answer one practical question: Can LegacyBridge complete this real process correctly and safely?
Getting started
Seven steps from first call to a decision
Every one of them keeps your current process running.
