From data to real outcome, step by step
Marginera is a decision-support desk: its rules are deterministic, its decisions are human and its outcomes are evidence-based. Every step of the flow is traceable.
From an invoice to an evidenced outcome
Click through Marginera’s real flow step by step. The documents and amounts shown are synthetic example data; the calculation comes from the rule engine in the kit.
Step 1 · Upload documents
Supplier invoices and order/delivery records arrive as CSV, XLSX or PDF. Column mapping is done once.
- INV-9001.pdf · INV-9001-A.pdf4 rowsUploaded
- siparis_teslim_eylul.xlsx5 rowsUploaded
Visit and fit check
A three-question check tells you whether your business is in scope; you see the synthetic demo analysis straight away.
Sign-up and verification
Identity is verified through SET Core; no separate password store is kept.
Setup wizard
Organisation, locations, roles and approval policy are defined in a few steps.
First data
CSV, XLSX or PDF is uploaded; documents are virus-scanned and column mapping is done once.
Reconciliation
The rule set is versioned: the same input always produces the same findings.
First discrepancy
A finding arrives with its source line and explanation; if the source is missing, the document is requested.
Review
The finance team reviews the finding; the decision and note are written to the audit log.
Case
Only sourced findings enter a case; the case owner and amount are fixed.
Approval
Requester, reviewer and approver are different people; if authority changes, the approval is re-evaluated.
Action file
The claim file is prepared as PDF and CSV; you do the sending.
Outcome
Expected, pending and realized are tracked separately; realized requires evidence.
Renewal
Contract obligations and renewal notices land in the calendar.
Screenshots and demo data are synthetic.
No outcome gets lost in a single total
The amount of an approved case is first “expected”. Once sent to the counterparty it is “pending”; when a credit note or proof of payment is added it becomes “realized”. Unevidenced user declarations are shown separately, in grey.
Approved case, not yet sent
Action file sent, awaiting a response
Evidence added: credit note, refund or offset
Want to see it on your own data?
Take the fit check, explore the synthetic demo analysis and request a place in the closed beta.