PO invoices need matching; non-PO invoices need judgment. Most tools do one well. Finnoto runs both through the same capture and control pipeline - 3-way match where a PO exists, policy-driven coding and approvals where it doesn't.
Illustrative product behaviour - values shown are examples.
PO invoices at least have a reference to check. Non-PO invoices - rent, utilities, marketing, professional fees - arrive with nothing but a claim.
Which GL, which cost centre, whose budget? When coding lives in one accountant's head, month-end reclassification becomes a ritual.
Without an amount-and-category matrix, non-PO invoices get approved by whoever answers email fastest - and audit asks why.
Every non-PO invoice is spend that skipped procurement. Untracked, the share grows until contracts and budgets mean little.
Field-level extraction runs 96%+ on typical Indian invoice formats; low-confidence fields route to a human with the document side-by-side, so errors get caught at entry, not at audit.
From vendor history, description understanding and your chart-of-accounts rules - suggested automatically, confirmable in one click, learned from corrections.
Yes - price and quantity tolerances by category or vendor; within-band variances flow through, outside-band ones create exceptions with the delta highlighted.