Data warehouse integration

Documents to Amazon Redshift tables

Holofin reads PDFs and scans and writes every field into Redshift, provisioned or Serverless, in the AWS region you run in.

Try Holofin free Book a demo

Harbourline Insurance plc

CERTIFICATE OF EMPLOYERS' LIABILITY INSURANCE

Policy No. HL-EL-0048213

Name of policy holderFenwick & Shaw Builders Ltd

Date of commencement01 November 2026

Date of expiry31 October 2027

Limit of indemnity£10,000,000

Signed on behalf of the insurerR. Okafor

SELECT field, value, confidence, page, needs_reviewFROM holofin.extracted.document_fieldsWHERE document_id = 'doc_2RB7NE'ORDER BY page, field;

	field	value	confidence	page	needs_review
1	insurer	Harbourline Insurance plc	0.99	1	false
2	policy_number	HL-EL-0048213	0.98	1	false
3	insured_name	Fenwick & Shaw Builders Ltd	0.97	1	false
4	cover_type	employers_liability	0.96	1	false
5	period_start	2026-11-01	0.97	1	false
6	period_end	2027-10-31	0.62	1	true
7	limit_of_indemnity	10000000.00 GBP	0.95	1	false

✓7 fields loaded

!1 flagged for review

A certificate of insurance read by Holofin and loaded into Amazon Redshift. Sample document; every name and number on it is invented.

How it works

1
Connect Amazon Redshift 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 Amazon Redshift is visible to it.
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
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 Amazon Redshift like any other source.

How the Amazon Redshift connector writes

Holofin writes through the Redshift Data API, so no inbound network path to your cluster or workgroup is needed. It assumes an IAM role you create in your account, mapped to a database user that can insert into one schema.

The only grant Holofin needs:

-- IAM role for the Redshift Data API: holofin-loader
CREATE USER "IAMR:holofin-loader" PASSWORD DISABLE;
GRANT USAGE ON SCHEMA extracted TO "IAMR:holofin-loader";
GRANT INSERT, SELECT ON ALL TABLES IN SCHEMA extracted TO "IAMR: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 Amazon Redshift's own names.

holofin.extracted.document_fields
document_id	STRING	Holofin's identifier for the document, stable across reloads.
document_type	STRING	The class Holofin gave the document: supplier_invoice, payslip, bank_statement, and so on.
field	STRING	The field name, in snake_case, as defined in your extraction schema.
value	STRING	The value as normalized text: ISO dates, dot decimals, IBANs without spaces.
confidence	FLOAT	Between 0 and 1. How sure Holofin is of the value.
page	INTEGER	The page of the source file the value was read on.
bbox	ARRAY<FLOAT>	Where on that page: x, y, width, height, as fractions of the page.
needs_review	BOOLEAN	True when the confidence is low or a rule failed, such as a balance that does not add up.
reviewed_by	STRING	Who confirmed or corrected the value in Holofin, once someone has.
loaded_at	TIMESTAMP	When the row was written. Corrections write a new row; the latest wins.

Query it in Amazon Redshift

List the insurance certificates that expire in the next 30 days, with DATEADD:

-- Insurance certificates that expire in the next 30 days
SELECT document_id, value::date AS period_end
FROM holofin.extracted.document_fields
WHERE document_type = 'insurance_certificate'
  AND field = 'period_end'
  AND NOT needs_review
  AND value::date BETWEEN CURRENT_DATE
                      AND DATEADD(day, 30, CURRENT_DATE)
ORDER BY period_end;

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.

Frequently asked questions

Does it work with Redshift Serverless?

Yes. Point Holofin at a Serverless workgroup or at a provisioned cluster; the Data API works the same way with both.

Do I need to open my VPC?

No. The Data API is called over AWS's HTTPS endpoint with the IAM role you grant. Your cluster can stay private.

How quickly do fields appear in Amazon Redshift?

Within seconds of the document being read. Most documents are read in under a minute, so a file sent by email is usually queryable in Amazon Redshift a minute later.

What happens when a reviewer corrects a value?

Holofin writes a new row for that field with the corrected value, needs_review set to false and reviewed_by filled in. Keep the latest row per document and field to get the current state, or keep every row for a full audit trail.

Can I choose which fields are loaded?

Yes. Each document type has an extraction schema in Holofin. Add, rename or remove fields there and the next documents load with the new names. Nothing in the table structure changes.

Which documents does Holofin read?

Any business document sent as a PDF, a scan or a photo: invoices, payslips, bank statements, tax notices, company extracts, IDs, certificates. Holofin also checks each file for tampering and can flag a suspicious document before its fields are trusted.