Your needs

Produce and distribute my documents,
without rewriting my programs

Invoices, delivery notes, statements: your IBM i output becomes polished PDFs that are sent, archived and ready for e-invoicing. Depending on your starting point, we either take your spool files as they are or design new documents.

Questions from IT managers

What you ask us about your printed output

Flip a card to read the answer and see the product that addresses it.

Distribution

My invoices still go out on paper. Can we e-mail them as PDFs without touching the programs?

See the answer

Yes. PHL Spool starts from the spool file your application already produces, adds a page background and e-mails it. Recipients can come from an SQL query. Not a single line of code to write.

PHL Spool →

E-invoicing

How can we produce Factur-X invoices from the IBM i?

See the answer

PHL Spool generates the XML from the spool file’s fields and embeds it in the PDF, as PDF/A-3 compliant with the EN 16931 standard, in the BASIC, BASIC WL and MINIMUM profiles.

PHL Spool →

Archiving

Can we find all of a customer’s invoices in a few seconds?

See the answer

Each document is indexed in DB2 from its own fields (customer, date, number). Searches are run from the web interface, and the PDFs are stored in the IFS or on a remote server.

PHL Spool →

Printing

Workshops and warehouses still need to print. Can we keep our printers?

See the answer

Yes. PHL Spool prints automatically to an output queue or in PostScript 3 via SFTP, with conditional printing and a set number of copies per template.

PHL Spool →

Design

I want to redo my documents: logo, colours, barcodes, a polished layout.

See the answer

PHL Print turns your PRTFs into graphical documents designed to the pixel in PHL Studio: page backgrounds, dynamic images, barcodes, conditional colours. The RPG that produces the data does not change.

PHL Print →

Web application

Can we display an invoice or a delivery note on screen, straight from the application?

See the answer

With PHL Print, the document is displayed on screen in PHL Web, sent by e-mail, or split by keyword so each recipient gets their part.

PHL Print →

Two solutions

Reuse what exists or design something new

The two work together: PHL Spool to distribute what already comes out right away, PHL Print for the documents that deserve a redesign.

PHL Spool

Reuse your existing spool files, with no development

We start from the SCS spool file your application already produces. A template adds a page background, then indexes, archives and distributes it: printing, e-mail, storage, web portal, Factur-X. Templates are configured in a graphical interface, without touching the programs.

Who it’s for

IT departments that want to go paperless quickly for invoices, delivery notes and statements, and move to e-invoicing without opening the code.

PHL Print

Design graphical documents, to the pixel

Your printer files become real graphical documents, designed in the PHL Studio WYSIWYG editor. The document is compiled into native RPG: it is displayed in PHL Web, sent by e-mail, and supports barcodes, dynamic images and text entered at run time.

Who it’s for

Teams that want a polished layout, new documents, or their printed output displayed in the web application.

How to get started

Start with one document, not a project

01

A first document, on a real spool file

Together we choose the document that matters most, often the invoice. We build its template on one of your real spool files, not on a mock-up.

02

The distribution rules

For this document, we decide where it goes: printer, e-mail, indexed archive, Factur-X. Your other output keeps coming out as before.

03

Document by document

We extend to delivery notes, statements and other output at your teams’ pace, and move to PHL Print for the documents that deserve a redesign.