IBM i is one of the most reliable platforms ever built. It handles payroll, inventory, accounts payable, and core business operations for thousands of companies — and it does it without breaking a sweat.
But reliability in your core system doesn't always extend to the documents that flow around it. Reports get printed and filed in cabinets. Invoices sit in email inboxes. Approval processes happen over the phone. And somewhere, someone is manually re-entering data that already exists in DB2.
If any of that sounds familiar, your AS/400 document workflow is overdue for an upgrade. Here are five signs to watch for.
1. Your Team Is Still Printing IBM i Spool Files
Spool files are the lifeblood of IBM i reporting — invoices, statements, purchase orders, shipping documents. The problem is that most organizations still handle them the same way they did in 1995: print them, sort them, and file them in a cabinet.
Modern IBM i document management software captures spool files automatically the moment they're generated, converts them to searchable PDF, and indexes them against your DB2 data — no printing, no filing, no hunting. Any document is retrievable in seconds from any workstation.
If your team is still walking to a printer to retrieve an IBM i report, that's sign number one.
2. Document Retrieval Takes More Than 30 Seconds
How long does it take someone on your team to find a specific invoice from eight months ago? A customer's signed agreement from last year? A remittance advice tied to a payment?
If the answer involves walking to a filing cabinet, searching a shared drive, or calling someone in another department, that's a workflow problem — not a people problem. Each retrieval that takes two minutes instead of ten seconds adds up to hours of lost productivity per week across your organization.
Quick benchmark: In a well-implemented ECM system, any document should be retrievable in under 10 seconds by anyone with appropriate access, from any device, without leaving their desk.
The fix is full-text search tied to your existing index data. When documents are captured and indexed against your IBM i data — customer number, invoice number, date, document type — retrieval becomes a simple search, not a scavenger hunt.
3. Approvals Happen Over Email or Phone
Purchase order approvals. Invoice sign-offs. HR document reviews. Contract authorizations. If these processes live in email threads or happen verbally, you have no audit trail, no visibility into where something is stuck, and no way to enforce a consistent process.
This is especially common in IBM i shops where the core ERP handles transactions beautifully but has no native document routing capability. The documents end up outside the system — in email, on desks, in shared folders — where they're invisible to anyone trying to manage the business.
Workflow automation connects documents back to your AS/400 processes. When an invoice is captured, it routes automatically to the right approver, tracks where it is, sends reminders if it stalls, and records every action with a timestamp. No more "I never got that email."
4. New Employees Can't Find Anything Without Help
This is one of the most telling signs of a broken document workflow: institutional knowledge stored in people's heads rather than in systems.
When a new employee needs to find documents, do they need someone to show them which cabinet, which folder, which shared drive path, which naming convention? That means your document management depends on tribal knowledge that walks out the door every time someone leaves.
A proper enterprise content management system stores documents in a consistent, searchable repository with clear index fields. New employees find what they need the same way a ten-year veteran does — by searching.
5. You're Storing Documents on a Network Share
Shared drives feel like document management. They're not. A network share has no version control, no access audit trail, no retention policy enforcement, no full-text search, and no connection to your IBM i data.
When a document lives on a shared drive, you don't know who accessed it, whether it's the latest version, or whether it's been retained long enough to satisfy a compliance requirement. And when the server it lives on has a problem, those documents are at risk.
Moving documents out of shared drives and into a managed repository — with proper indexing, access controls, and retention rules — is one of the highest-impact changes an IBM i shop can make.
What to Do Next
If you recognized two or more of these signs, you're not alone. Most IBM i environments grew their document processes organically over decades, layering workarounds on top of workarounds. The good news is that modernizing doesn't require replacing your core system or retraining your entire team.
RVI is document management software built natively for IBM i — it integrates directly with your DB2 data, captures spool files automatically, and gives your team a single searchable repository for every document in your organization. It runs alongside your existing AS/400 environment without disruption.
See RVI Running on Your IBM i
Schedule a live demo and we'll show you exactly how RVI handles your specific document types and workflow — no generic slides, no pressure.
Schedule a Demo