rips/cloud
ESOpen RipsCloud →
Documents that accompany RIPS · Available according to provider configuration

The invoice accompanies. RIPS stays at the center.

Create health invoices, credit notes and debit notes from RipsCloud through PahFacturar. Prepare and send the related RIPS as a separate process.

AudienceProviders who need a health document with the RIPS
InputPatient, payer, services and a configured resolution
OutcomeHealth document and related RIPS package
Product scope

Tools for your process.

See product functions and process requirements.

01

Health invoice

Prepare the invoice with patients, services and provider configuration.

02

Credit notes

See the source document and available values before issuing the note.

03

Debit notes

Record additional services and their RIPS without leaving the portal.

04

Related RIPS

After document acceptance, prepare, validate and send the related package.

05

Document evidence

See the status and files offered by each document type.

06

PahFacturar integration

RipsCloud manages communication with the issuance provider.

Work journey

Every step keeps its context.

Prepare data, review the result and keep evidence.

01

Check configuration

Confirm company, certificate, resolution and issuance environment.

02

Prepare the document

Record patient, payer and services or the reason for the note.

03

See acceptance

Verify the document result before preparing its RIPS.

04

Send its RIPS

Validate and send the related package. Keep both evidence sets.

Limits

What this product does not promise.

  • Health invoices and notes only; it is not a general accounting system.
  • DIAN acceptance and RIPS acceptance are different results.
  • The provider must have the configuration needed to issue.
  • Not every RIPS package needs an invoice.

Work with RipsCloud.

Read the documentation or talk with the team about your organization setup.