Data warehouse integration
Documents to BigQuery rows, ready to join
Holofin reads PDFs and scans and writes every field into a BigQuery table in your project, in the EU region you pick.
| field | value | confidence | page | needs_review | |
|---|---|---|---|---|---|
| 1 | employer_name | Lumen Logistique SAS | 0.99 | 1 | false |
| 2 | employee_name | Camille Martin | 0.98 | 1 | false |
| 3 | pay_period | 2026-09 | 0.99 | 1 | false |
| 4 | contract_type | CDI | 0.95 | 1 | false |
| 5 | gross_salary | 3450.00 | 0.98 | 1 | false |
| 6 | net_before_tax | 2689.12 | 0.96 | 1 | false |
| 7 | net_paid | 2451.37 | 0.66 | 1 | true |
✓7 fields loaded
!1 flagged for review
How it works
- 1
Connect BigQuery 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 BigQuery 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 BigQuery like any other source.
How the BigQuery connector writes
Holofin writes through the BigQuery Storage Write API in committed mode, so each row is queryable as soon as it is written and never loaded twice. It uses a service account that holds BigQuery Data Editor on one dataset, in the location of your choice (EU by default).
The only grant Holofin needs:
-- Service account: [email protected] GRANT `roles/bigquery.dataEditor` ON SCHEMA `holofin-analytics.extracted` TO "serviceAccount:[email protected]";
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 BigQuery's own names.
| 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 BigQuery
Average net pay per employer on this week's payslips, leaving out values still waiting for review:
-- Net pay declared on payslips this week, per employer, -- keeping only fields nobody needs to look at again SELECT employer.value AS employer, COUNT(*) AS payslips, ROUND(AVG(SAFE_CAST(net.value AS NUMERIC)), 2) AS avg_net_paid FROM `holofin-analytics.extracted.document_fields` AS net JOIN `holofin-analytics.extracted.document_fields` AS employer USING (document_id) WHERE net.field = 'net_paid' AND employer.field = 'employer_name' AND NOT net.needs_review AND net.loaded_at >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 7 DAY) GROUP BY employer ORDER BY payslips DESC
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
Is the table partitioned?
Yes. Holofin creates it partitioned by day on loaded_at and clustered on document_type and field, so queries filtered on recent documents scan little data.
Can the data stay in the EU?
Yes. The dataset lives in your project and in the location you set when you create it, such as EU or europe-west9 (Paris). Holofin itself processes the documents in France.
How quickly do fields appear in BigQuery?
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 BigQuery 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.
Put Holofin on your own documents.
Every value linked to the page it came from, every PDF checked for tampering, rules checked across the whole file.