Documents to PostgreSQL, in the database you already run

How it works

1. 1

   Connect PostgreSQL once

   Create a role with insert rights on one schema and paste its credentials into Holofin. Holofin creates the table on the first load; nothing else in PostgreSQL is visible to it.

2. 2

   Send documents the way you already do

   Upload in the app, forward by email, or post to the API. Holofin classifies each file, splits bundles into documents and reads the fields of each type.

3. 3

   Query the rows

   Each field lands as one row with its confidence, the page it came from and a needs_review flag. Join it to your own tables in PostgreSQL like any other source.

How the PostgreSQL connector writes

The only grant Holofin needs:

CREATE ROLE holofin_loader LOGIN PASSWORD '...';
GRANT USAGE ON SCHEMA extracted TO holofin_loader;
GRANT INSERT, SELECT ON extracted.document_fields TO holofin_loader;

The table Holofin writes

One row per field, so a new document type never changes the table. The same columns exist in every warehouse; types follow PostgreSQL's own names.

Query it in PostgreSQL

Bank details still waiting for a reviewer, one line per client file, with FILTER and bool_or:

-- Bank details still waiting for a reviewer, per client file
SELECT
  document_id,
  max(value) FILTER (WHERE field = 'iban') AS iban,
  bool_or(needs_review AND reviewed_by IS NULL) AS pending_review
FROM extracted.document_fields
WHERE document_type = 'bank_details'
GROUP BY document_id
HAVING bool_or(needs_review AND reviewed_by IS NULL)
ORDER BY document_id;

Security

• Documents are processed in Europe, on OVHcloud servers in France certified ISO 27001.
• Holofin only ever writes to the schema you grant. It cannot read your other tables.
• Retention of the source files in Holofin is set per organization, from zero data retention to indefinite. Rows in your warehouse follow your own policies.
• GDPR: Holofin acts as your processor. No document leaves the European Union.