Your data model
One shared data model for your financial processes.
Ocost connects invoices, documents, contracts, suppliers, line items, deadlines and payments into a source-linked model. Connections become visible that otherwise stay separate across PDFs, emails, ERP exports and spreadsheets.
Sound familiar?
Your data scattered across PDFs, emails and spreadsheets?
Without a shared model every analysis stays manual and every question stays open. Ocost connects scattered documents into a searchable, source-linked picture — the basis for analysis, checking and downstream processes.
How Ocost turns individual data into a model
More than OCR: Ocost doesn't just read text — it connects data points with source, context and meaning. Behind the scenes there is an ontology — a connected data model for documents, suppliers, items, contracts, payments and deadlines.
- Invoice
- Document / attachment
- Contract
- ERP export
- Delivery note
- Payment
- Supplier
- Item / service
- Line item
- Contract
- Payment term
- Discount
- Cost centre
- Payment
What Ocost connects
Suppliers
Name variants, customer numbers, bank data and document sources are merged.
Line items
Items, services, quantities, prices and descriptions are structured and made comparable.
Categories
Line items can be classified by eCl@ss or customer-specific logic.
Contracts & deadlines
Contracts, terms, payment deadlines, discounts and inspection deadlines are linked with documents.
Sources
Every statement stays traceable to the underlying document or line item.
How it works
In four steps
- 1
Upload documents
Via drag & drop, email or interface — a PDF is enough.
- 2
Read to the line item
Text recognition reads every line, eClass classifies consistently.
- 3
Connect
Suppliers, items, contracts and documents — linked automatically.
- 4
Ask questions
Every answer comes with its source from the model.
What Ocost does for you
Three outcomes, measurable
Items are unified automatically — so prices and suppliers become comparable. Technical basis: eClass.
- 1
Everything connected
Suppliers, items, contracts and documents are linked — one question, one source-linked answer.
- 2
Down to the line item
Read down to the individual line; classification by eClass or setup logic instead of coarse header data.
- 3
Grows with the documents
New documents extend the model; uncertain cases can be reviewed depending on setup.
- Reading
- to the line item
- Answer
- with its source
- Classification
- eClass / setup
Suppliers, items, contracts and documents — source-linked into one model.
Concrete result
What you see after 24 hours
Connected documents
Suppliers, items, contracts and documents are linked — no longer scattered.
Sourced answers
Every analysis comes with source and line item.
Unified items
The same items made comparable across suppliers.
Up-to-date model
Every new document extends the picture automatically.
Why this matters
Better analyses
Metrics come from connected data, not from isolated PDFs.
Faster review
Invoices, line items, suppliers and deadlines are visible in context.
Less manual clean-up
Inconsistent spellings, categories and tables don't have to be re-sorted every time.
Foundation for automation
Approval, 3-way matching, discount logic and analyses need a shared data model.
A simple example
A supplier appears in documents as „Müller GmbH“, „Mueller GmbH“ and with different customer numbers. Ocost can merge these signals, assign documents and line items and make discrepancies visible — with a source reference to the respective invoice or line item.
A maintenance service appears in several invoices with different item descriptions. Ocost structures the line items, makes price discrepancies visible and links them with contract, deadline or cost centre, provided this information is available.
What the data model does — and what it doesn't
- connects data points with sources
- normalises suppliers and line items
- classifies by eCl@ss or setup logic
- makes relationships and discrepancies visible
- creates a foundation for analysis and automation
What it isn’t:
- not an ERP replacement
- no mandatory manual master-data consulting
- no guarantee of perfect classification
- not a replacement for expert approval in uncertain cases
- not a black box without source reference
Frequently asked questions
What does ontology mean at Ocost?
At Ocost, an ontology is a connected data model. It links documents, suppliers, line items, contracts, payments and deadlines so that relationships become visible and verifiable.
Does our master data have to be perfect?
No. Ocost can also start with incomplete or inconsistent documents. The quality of the results, however, depends on the data situation and setup.
Does Ocost classify automatically by eCl@ss?
Ocost can classify line items by eCl@ss or customer-specific logic. Uncertain cases should be reviewed or confirmed depending on the setup.
Can you trace where a statement comes from?
Yes. Results are meant to stay source-linked — down to the document or line item they are based on.
Why do I need this in addition to ERP or BI?
ERP and BI often show data that is already structured. Ocost also connects unstructured documents, receipts and exports and makes them usable for analysis and downstream processes.
Built for
These roles benefit directly
Ready in minutes
Send Ocost a month of documents
Sign up with your work email. Ocost reads your website and the register, fills in your company and starts reading what you send.
No card needed · the trial has the limits of S