rips/cloud
ESOpen RipsCloud →
RIPS operations

RIPS with and without an invoice

What changes between the two journeys and why RIPS should not be treated as a secondary billing feature.

RIPS with invoice

This journey has a health FEV that references and groups the RIPS support.

RIPS without invoice

Not every package requires an invoice created in the same tool. A RIPS-first flow lets you prepare and dispatch the set without inventing a prior billing record.

Why the two concepts should stay separate

When the product only orbits the invoice, RIPS is treated as a technical attachment.

How RipsCloud approaches it

RipsCloud works with RIPS with and without an invoice. It uses PahFacturar for issuance when the case needs it. Portal and API belong to one subscription.

See the intended journey.

Review the work cycle in the portal and production documentation.