Turn business documents into verified, actionable records.
MetryxAI reads your invoices, matches them line by line against purchase orders from your ERP, flags every discrepancy, and routes exceptions to the right reviewer — so your AP team approves with evidence, not guesswork.
-
Live today
- AI invoice extraction
- Odoo purchase-order sync
- Line-level PO matching
- Reviewer → approver workflow
Extracted recordINR · 3 lines
- vendor
- Northwind Packaging Pvt. Ltd.
- gstin
- 29ABCDE1234F1ZW ✓ checksum valid
- invoice_no
- NWP/26-27/0417
- po_reference
- PO-00418 ↔ Odoo PO
- total
- ₹1,35,700.00
Line match · invoice vs PO-004182 / 3
Extraction is the easy part. Trusting what happens next is the hard part.
- 01
Documents arrive unstructured
PDFs and scans in inboxes, in every vendor's own layout, keyed into the ERP by hand.
- 02
The truth lives in the ERP
Purchase orders and receipts sit in a different system from the invoice, so checking them is slow and gets skipped.
- 03
Exceptions disappear into email
Variances get settled in threads with no record of who decided what, or why.
Understand. Validate. Act.
One controlled pipeline from source document to approved record. Every step keeps its evidence, so any result can be traced back to the document and data behind it.
Turn documents into data
Extract structured fields from invoices and pull the matching business records from your ERP.
- AI invoice extraction Available
Vendor, GSTIN, invoice number, PO reference, line items, tax and totals.
- Configurable extraction profiles Available
Tune extraction per document type for each organisation.
- ERP purchase-order sync Available
Full and incremental loads from Odoo.
- Source preservation Available
Original payloads kept with checksums for replay and audit.
Check it against the truth
Compare every invoice with its purchase order and surface what doesn't agree.
- Line-level PO matching Available
Quantity, rate and line-total variances, plus lines missing from the PO.
- Variance and risk scoring Available
Variance % per line and a risk level per invoice.
- Vendor identity checks In progress
GSTIN checksum validation. Ambiguous vendors are never auto-merged.
- GRN three-way matching In progress
Bring goods receipts into the same match run.
Move it forward, with control
Route exceptions to people, record each decision, and hand approved records downstream.
- Review & approval stages Available
Reviewer and approver stages, configurable per organisation.
- Role-based permissions Available
Financial exceptions limited to authorised roles.
- Decision history Available
Every status change, comment and approval, with who and when.
- Controlled ERP writeback Pilot
Proposal → approval → source check → one idempotent execution.
Built as an operational system, not a demo.
Each layer has one job, so financial records stay consistent, isolated and replayable.
Operational ledger
Postgres is the system of record for AP data, with tenant row-level security.
Source & provenance
Original files in object storage. Raw-ingest metadata and lineage are kept immutable.
Background workers
Connector sync, extraction, matching and writeback run as queued, retryable jobs.
One connector contract
Every ERP adapter implements the same AP interface, so new systems plug into the same controls.
Every invoice checked. Only exceptions need people.
MetryxAI sits between your inbox and your ERP. Invoices that agree with their purchase order move ahead with a full record. Invoices that don't arrive in front of a reviewer, already explained.
Less manual keying
Fields and line items are extracted for review instead of typed in.
See where every invoice is
Extracted, matched, in review, approved — each status is visible.
Cleaner vendor data
Invalid GSTINs become data-quality exceptions instead of silent matches.
Controlled operations
AI prepares the evidence. Authorised people make the decision.
Exceptions MetryxAI surfaces
ExamplesQuantity, rate or line total differs from the purchase order line.
An invoiced line has no matching line on the referenced PO.
Invoice total doesn't match the purchase order total.
The PO reference on the invoice doesn't exist in the synced ERP data.
GSTIN fails format or checksum checks, so it is never used to match a vendor.
Runs the queue
Manages matching, exceptions and the team's workload.
Resolves exceptions
Sees the variance, the document and the PO side by side.
Signs off with context
Approves knowing what was checked and what was flagged.
Keeps control
Sets the approval stages, roles and connector settings.
From a vendor PDF to an approved record, one invoice at a time.
Follow the sample invoice from the top of the page through each stage.
-
Ingest
The invoice is uploaded. The original file is stored as received, with a checksum, so it can always be replayed.
# intake file NWP-0417.pdf checksum sha256:9f3c…e21a status stored
-
Extract
AI turns the document into structured fields and line items, using the extraction profile for that document type.
# extracted fields vendor, gstin, invoice_no, date, po_reference, lines[3], igst, total -
Validate
The extracted data is checked: is the GSTIN well-formed, do the lines add up, does the PO reference exist?
gstin ✓ checksum valid line totals ✓ sum to taxable value po_reference ✓ PO-00418 found
-
Match
Each invoice line is compared with the purchase order synced from your ERP. Goods-receipt matching is being added to the same run.
PO-00418 (Odoo) lines matched 2 / 3 grn three-way match — in progress
-
Surface
Discrepancies become specific, explained exceptions with a variance and a risk level, not a vague "needs attention".
LINE_MISMATCH line 2 · rate invoice 1,240.00 · po 1,180.00 variance +5.08% · risk MEDIUM
-
Review
The exception goes to a reviewer, then an approver. Comments and decisions are recorded against the invoice.
reviewer comment added approver pending history every event · actor · time
-
Accept
Once approved, the record is ready for the downstream ERP process. Direct ERP writeback runs only as a controlled pilot.
status APPROVED writeback controlled pilot proposal → approval → execute once
Controls built into the design.
Finance data needs guarantees, not promises. These are the rules the platform is built around.
Tenant isolation
Every AP request runs under a validated tenant scope, backed by row-level security in the database.
Role-based access
Admin, AP manager, approver and viewer roles. Resolving financial exceptions takes explicit permission.
AI is advisory
Models extract and explain. They cannot approve an invoice, send anything, or write to your ERP.
Review, not blind trust
Uncertain or conflicting results go to a person instead of moving ahead on their own.
Exact money handling
Decimal arithmetic, never floats. Matching stays within one currency. INR conversion keeps the rate, date and source.
Immutable match history
Match runs are versioned by their inputs, policy and engine. New data supersedes a run but never deletes it.
Source preservation
Original documents and raw payloads are kept with checksums, for replay and audit.
Safe ERP writes
Writeback is idempotent. If an outcome is unknown, it is reconciled, never blindly retried.
We don't put certification badges on this page. During evaluation we'll walk your security and IT teams through our current posture, data handling and deployment, and answer your questionnaire directly.
Starting with the ERPs Indian finance teams run.
Connectors ship one at a time, each with full controls. Here's where each one stands.
Odoo
Purchase-order sync with full and incremental loads. Our first production connector.
Zoho Books
The next AP connector, built on the same connector contract.
Tally
Planned after Zoho Books, for teams running Tally as their book of record.
Tell us how invoices move through your team today.
A few details help us come prepared. No sales script.
- 01You share your workflowVolume, systems and where things get stuck.
- 02We map it with youA working session on your documents and your ERP setup.
- 03We agree what to evaluateA scoped evaluation, with clear criteria for what we'll measure.