Nexus reads every document in a transaction — purchase order, receipt, bill of lading, invoice, contract — and reconciles it against the rest of the file and against your ERP. Conflicts, duplicate payments, fraud signals and missed obligations surface with a dollar value, an owner and a deadline.
Drawn from internal pilots and reference implementations. Results vary with document quality, vendor mix and the state of your master data — we size it against your own history before you commit to anything.
Aurus.ai turns unstructured documents — invoices, receipts, bills of lading, scans, contracts and paper — into clean, ERP-grade structured data, then reconciles that data against the rest of the file and against your system of record, names every conflict, duplicate and missed obligation it finds, assigns an owner and a deadline, and tracks it until someone closes it.
Your team matches POs to invoices to receipts by hand. Mismatches stall payments, exceptions pile up, and staff spend the close chasing paperwork. Meanwhile Oracle says one thing, Ariba says another, and the spreadsheet says a third — so nobody can prove which is right.
The same invoice re-entered into three to five disconnected systems, each keystroke a chance to introduce the variance somebody will chase next month.
Finding the right documents, emailing the vendor, waiting, re-checking. The queue grows faster than the team clears it, and SLA debt compounds quietly.
Duplicate payments typically surface 60 to 90 days later, if they surface at all. By then the vendor relationship, not the control, is what recovers the money.
The record of who approved what, and on what evidence, lives in email threads. When an auditor asks, reconstructing it costs weeks of somebody senior.
A document arriving by email at 2am and an EDI 810 from a tier-one supplier follow the same path. Anything that fails a stage goes to a dead-letter queue for human review instead of blocking everything behind it.
Email attachments, EDI, cloud storage, ERP exports, API hooks and manual uploads normalise into one queue. No provider change, no second inbox.
500 docs/min peakDocument type, vendor, PO reference and schema identified automatically by a model registry that selects the right variant on confidence.
≥85% threshold27 or more fields per document. Fields below threshold are isolated and routed for review rather than written downstream on a guess.
93.2% avg confidenceSchema rules, business logic and cross-checks against the system of record run before the document is allowed near the matching queue.
Duplicate detectionInvoices matched to POs, receipts, bills of lading and payment records on a weighted score across 12 dimensions, anchored to the purchase order.
99% match accuracyEvery break gets a severity, a financial exposure, an owner and a deadline. It stays open and escalating until somebody closes it.
Tracked to closeMost AP tools anchor on the invoice, which is why a ghost invoice with a plausible vendor name gets paid. Nexus anchors on the purchase order and treats every downstream document as a leaf that must resolve back to a PO line item.
The data model enforces it structurally. A PO core layer is populated from Oracle or SAP and held as the immutable reference. Every transaction record — receipt, bill of lading, carrier invoice, customs declaration, AP invoice, payment — carries a mandatory link back to a PO line. Nothing orphaned can enter the system, which removes the single largest source of duplicate and fraudulent payment in one design decision rather than through a rules engine somebody has to maintain.
Each module deploys independently, but they share a single schema — so a contract clause, a goods receipt and a payment record are queryable against each other rather than sitting in separate products that integrate badly.
Matches invoices to purchase orders on a weighted score across twelve dimensions — vendor identity, amount, date, PO number, line items, tax, currency, payment terms and more — rather than a single fuzzy string comparison.
Extends the match beyond the invoice into physical movement: receipts against bills of lading, carrier invoices against contracted rates, free-time windows against actual gate-out.
Most document tools only read from your ERP. Nexus writes back — approved invoices published as validated AP vouchers into Oracle and SAP, with rollback if the write fails.
A visual approval-chain designer your admins use directly. Drag nodes, set the assigned role, the SLA in hours, what happens on breach, what happens on rejection. No code, no support ticket.
Reads the agreement package together — master agreement, amendments, exhibits, schedules — and holds the commercial terms as the reference that invoices and carrier charges are checked against.
An exception is not a flag with a confidence score attached. It is categorised, scored for financial exposure, assigned to a role, and measured on how long it took to clear.
The reconciliation logic does not change between these. What changes is which documents are the reference and which breaks matter — configured at deployment rather than rebuilt.
Your team stops matching POs to invoices to receipts by hand. Nexus reconciles automatically, names every break in plain terms, and assigns it to the person who can clear it — so the close is not spent chasing paperwork.
Demurrage applied incorrectly, detention billed past free time, rates that do not match the service contract. Nexus reads the bill of lading, the terminal record and the carrier invoice together and disputes what is not owed.
Incoming material arrives with a certificate of analysis, a packing list and a receipt that all have to reconcile against the purchase order and the specification before the lot is released.
Where a matter is a stack of documents that have to agree with each other, Nexus reads the whole file, surfaces where it contradicts itself, and holds the collaboration until the package is signed off.
Every document gets an overall confidence score weighted by field criticality — amount, vendor identity and PO number carry the most weight. The score determines who looks at it. It never determines whether something gets written to your ERP unchecked.
| Confidence band | Share of volume | What happens |
|---|---|---|
| ≥ 90% | 73% | Matched, validated and promoted automatically. No human review unless a business rule fires. |
| 75–89% | 18% | Partially matched. Only the uncertain fields are highlighted, so a reviewer checks three fields rather than re-reading the document. |
| < 75% | 9% | Quarantined in the exception queue with the model's annotation. Human review required before anything is written to a system of record. |
| Document type | Model | Fields extracted | Average confidence |
|---|---|---|---|
| Tax invoice | AURUS-AP-INV-v3 | 31 | 94.2% |
| Purchase order | AURUS-AP-PO-v2 | 28 | 96.1% |
| Goods receipt note | AURUS-SC-GRN-v2 | 22 | 93.8% |
| Bill of lading | AURUS-SC-BOL-v1 | 19 | 91.4% |
| EDI 810 invoice | AURUS-EDI-810-v4 | 38 | 99.1% |
| EDI 850 purchase order | AURUS-EDI-850-v4 | 34 | 99.3% |
| Credit note | AURUS-AP-CN-v2 | 24 | 92.7% |
| Remittance advice | AURUS-AP-REM-v1 | 18 | 90.2% |
| Proof of delivery | AURUS-SC-POD-v1 | 15 | 88.9% |
Confidence figures are rolling averages from production and pilot document volumes. New document types are trained against your own historical documents during onboarding.
Every connector is governed by a configuration-driven registry that holds the field mappings, sync frequency, authentication and retry policy. Adding a source is configuration, not a project.
| Source system | Connection |
|---|---|
| Oracle ERP · AP and finance | REST API · OAuth 2.0 · bi-directional · real time |
| SAP Ariba · procurement | REST API · API key · bi-directional · scheduled |
| Coupa · invoice management | Webhook · OAuth 2.0 · push events |
| NetSuite | SuiteQL REST · OAuth 1.0a · bi-directional |
| EDI Gateway | AS2 · EDI 810 / 850 / 856 / 997 · ANSI X12 |
| Email listener | IMAP/SMTP · attachment extraction · rule-based routing |
| Google Drive, SharePoint, Box, OneDrive | OAuth 2.0 · folder watch · delta sync |
| Custom API or webhook | Inbound REST · HMAC auth · JSON, XML or EDI payload |
| Set | Purpose | Direction | Acknowledgement |
|---|---|---|---|
| 810 | Invoice | Inbound from vendor | 997 functional ack |
| 850 | Purchase order | Outbound to vendor | 997 + 855 PO ack |
| 856 | Advance ship notice | Inbound from vendor | 997 |
| 820 | Payment remittance | Outbound to vendor | — |
| 855 | PO acknowledgement | Inbound | 997 |
| 997 | Functional acknowledgement | Bi-directional | — |
Pulling fields off a page is close to a commodity. What still costs you money is everything that happens after the fields come out — and that is where most tools hand the work back to your team.
| Capability | Typical AP automation | Nexus |
|---|---|---|
| Reads and classifies the document | Yes | Yes |
| Extracts structured fields | Yes | Yes |
| Delivers to a queue or system | Yes | Yes |
| Anchors every record to a purchase order | No | Yes |
| Reconciles against the system of record | No | Yes |
| Reads the contract package as the reference | No | Yes |
| Assigns an owner and an SLA per exception | No | Yes |
| Escalates when the SLA is breached | No | Yes |
| Writes golden records back to the ERP | No | Yes |
| Tracks to disposition, not just delivery | No | Yes |
The comparison describes the category as it is generally marketed. Individual products vary — verify against any specific tool you are evaluating.
Beyond the ingestion, matching and reconciliation workbenches that run the pipeline above, each role gets the console that fits what they do. Every one of them writes to the same audit log.
Identity, access, retention and security policy are all set at the organisation level from the admin console — no backend access and no support ticket. Every login, approval, rejection, configuration change, export and API call is written to an immutable log.
The savings come from eliminating manual keying, cutting exception overhead, preventing duplicate payments, reducing audit cost, and retiring the integration maintenance that custom ERP connections demand every year.
| Cost category | What drives it today | Typical reduction |
|---|---|---|
| Manual invoice processing | Keying the same invoice into three to five systems | 85% |
| Exception resolution overhead | Hours per break, spent finding documents and chasing vendors | 85% |
| Duplicate payment losses | Paid twice, surfaced 60 to 90 days later if at all | 83% |
| Audit and compliance | Reconstructing who approved what, and on what evidence | 89% |
| ERP integration maintenance | Custom connections rebuilt after every upgrade | 85% |
Payback typically lands inside the first year. What that is worth depends entirely on your document volume, vendor mix and loaded cost per invoice — so we build the model against your own figures rather than publishing someone else's. Bring one month of documents and we will show you the arithmetic, including what it costs.
Reduction percentages are drawn from internal pilots and reference implementations, measured against the manual baselines they replaced. They are not a guarantee of your result and will vary with document quality, vendor mix and the state of your master data. Beyond direct savings, implementations typically also see days payable outstanding fall by around eleven days.
The delivery model is deliberately low risk. Your existing process keeps running through the whole of phase one, and no ERP customisation is required at any stage. Commercial deployments on the platform typically stand up in weeks, not quarters.
Every implementation includes a named customer success manager and a ninety-day hypercare period after go-live, with a four-hour response SLA on P1 issues.
Nexus is where documents decide money. Lexara is where they decide risk. Both run on the reconciliation engine described above.
Contract review reads one document. Lexara reads the whole package — master agreement, SOWs, amendments, exhibits — and finds the terms that contradict each other.
Drop a contract, invoice package or scan straight into the browser and watch Aurus read it. No account, no card, nothing saved.
We will reconcile them against your purchase orders and your system of record, and show you exactly what broke, what it was worth, and who should have caught it.