A database of your business, built from its documents.
Relations turn separate tables into one connected model: an invoice knows its supplier, its order and its lines; a supplier knows every document that mentions it.
Relations, line items and hierarchies
- 1
Relate two tables
Single or multiple links, with the reverse column created for you.
- 2
Break down into lines
Line items live in their own sub-table — and one sub-table can serve invoices, quotes and orders at once.
- 3
Build hierarchies
Parent and child records for projects, cost centres or properties, shown as a tree.
What you get
Link invoices to suppliers, orders to deliveries and lines to their documents: two-way relations, shared line items and trees, like a real database.
Filled by extraction
Relations fill themselves as documents are read: matched to existing records, or created when new.
Up to five levels
Lines within lines: an order, its lines, their deliveries.
Merge duplicates
Two rows for the same supplier? Merge them column by column — and undo if needed.
Four ways to work
Chips in the cell, a picker, an inline sub-table and a panel with the full record.
An invoice is linked to its supplier, its order and the payments that settle it; rollups add up what is linked. A workflow status then reads where each record stands — To Pay, Partially Paid, Settled — from the data, never typed by hand.
Used in
Frequently asked questions
How is this different from a spreadsheet?
Links are real relations: rename a supplier once and every invoice shows the new name.
Can one table have several parents?
Yes. A single lines table can belong to invoices, quotes and orders at the same time.
What if I remove a link by mistake?
Undo it. Every change can be undone for 30 minutes.
