From document to structured fields.
Supplier, identifiers, dates, line items, VAT and totals are extracted into a reviewable schema. Unsupported or ambiguous documents are not forced into an invoice result.
Foldline extracts invoice fields, verifies what it can prove, and keeps source evidence next to anything that needs a human review. If extraction is uncertain, Foldline withholds the risk result instead of guessing.
BIN 123456789012
Invoice # INV-2048
Add a PDF or image privately.
Foldline turns the invoice into structured fields.
Extraction must be reliable before risk is calculated.
You see verified checks, evidence, or a clear needs-review state.
Extraction is only the first step. Foldline separates extraction uncertainty from business exceptions, keeps the original evidence beside the result, and refuses to turn parser uncertainty into a fake risk score.
Subtotal + VAT does not match the invoice total.
Shown only after the required values passed the extraction gate.The same supplier and invoice number already exist in the workspace.
Invoice number alone is not enough to call something a duplicate.The current product is intentionally narrow while the first real workflows are being validated.
Supplier, identifiers, dates, line items, VAT and totals are extracted into a reviewable schema. Unsupported or ambiguous documents are not forced into an invoice result.
Foldline checks invoice math and same-supplier duplicate invoice numbers. Optional fields such as PO references are not treated as errors unless a future workspace rule requires them.
Uploads move through explicit processing states. A document is either reliably checked, needs human review, unsupported, or failed.
Foldline uses private storage, short-lived signed access and database policies to keep document access scoped to the right account and workflow.
Read the security architecturePractical answers about what the current MVP does, where documents go, and what still requires human judgment.
No. Document conversion is only the parsing layer. Foldline adds structured fields, source evidence, a reliability gate, deterministic invoice checks and human review.
It does not turn extraction uncertainty into a business-risk score. The document is marked as needing review, the uncertain fields remain editable beside the original, and risk stays uncalculated until the extraction is reliable enough or a person confirms the data.
Not when the extraction passes the reliability gate. Proofline focuses attention on verified exceptions. If extraction itself is uncertain, Foldline makes that clear and asks for a human review instead of pretending the result is reliable.
No. A PO reference is informational by default because not every invoice requires one. A future workspace rule can make it mandatory for a specific workflow.
Foldline does not flag an invoice as a duplicate from the invoice number alone. The current check also requires the same supplier identity in the workspace.
Original documents are stored in a private Supabase Storage bucket. Browser access uses short-lived signed URLs rather than permanent public file links.
No. Foldline structures and checks document data. A person remains responsible for reviewing the result before relying on it.
Yes, but uncertain extraction must be reviewed first. Unsupported documents are not exported as invoices.
Invoice review is the current MVP path. Related documents can be stored in a review packet, while broader cross-document checks are still being tested and are not presented as a finished capability.
Tell me what your team reviews today and we can see whether Foldline is a reasonable fit.