Invoice 20816
PostedEverything matches.
Invoice, purchase order, and receipt agree. Terms and client policy allow automatic processing.
✓ Receipt matched✓ Terms checked
Posted straight throughNo analyst handoff required.
Invoice exceptions, cleared line by line.
Clear more invoice exceptions for straight-through processing. Across reconciles records and applies your rules, leaving your team the complex cases, with the evidence and next step ready.
Request a demoIllustrative invoice processing
Across
Check each invoice. Clear what matches. Prepare the exceptions.
Sample invoice · 20817
Needs reviewOnly 400 of 500 cases received.
- Received and matched400 of 500 cases · PO pricePay $9,600
- Not yet receivedRule R-07 · 100 cases to followHold $2,400
- Freight, not priceRule R-18 · prepaid over $10,000Dispute $310
Sent to the AP lead for review
Your AP lead approves this split payment first (R-24).
Review queue · evidence and rules attachedInspect the supporting rules
- R-07Partial receipt: pay what arrived, hold the restAP policy, section 3
- R-18Freight is prepaid on orders over $10,000Merovyn Packaging terms, clause 4
- R-24Split payments: AP lead approves firstApproval matrix, row 2
These are sample invoices. The second invoice waits for approval.
Where invoice processing breaks today.
Invoices that fail automated checks create a manual review queue. Analysts spend time finding the cause before they can decide what to pay. In this example, the PO lists 500 cases, the receipt confirms 400, and the invoice adds freight.
Three-way match for sample invoice 20817
Field Purchase orderPO7730Goods receiptReceiptGR-5521InvoiceInvoice20817 Match result
Cases 500400500 does not match
Unit price $24.00$24.00 matches
Freight $310 does not match
Total $12,000$12,310 does not match
An AP analyst must resolve each mismatch. One-off rules are costly to build and maintain across clients.
Clear more exceptions. Process more invoices.
Across applies your rules as an analyst would. It checks the records, explains the discrepancy, and decides the next step. Resolved cases can continue; decisions needing sign-off arrive ready for review.
Pay only for what arrived.
400cases received
of 500 ordered
of 500 ordered
400 received100 still outstanding
400 cases×$24 per case=$9,600
The unit price matches the purchase order. The quantity and freight explain the exception.
Cleared for payment, pending split-payment approval$9,600
400 received cases at the purchase-order price.
Hold the remaining 100 cases
$2,400Release this amount when the receipt is confirmed.
Dispute the freight
$310Vendor terms say freight is prepaid on this order.
Built from how you clear exceptions.
Much of how exceptions get cleared lives with your AP team, not in the ERP. The Architect reads your policies, vendor terms, and resolved exceptions, then asks your AP team about the gaps.
-
Policies, vendor terms, resolved exceptions, and your AP team’s answers.
- AP policy
- Approval matrix
- Vendor terms
- Resolved exceptions
- Expert interviews and transcripts
- Architect asks:Only $9,600 arrived. Does the $10,000 freight rule apply? AP lead answers:Yes, the order total counts. Dispute the freight.
-
The Architect drafts it in plain language. Your AP lead reviews it.
- R-07 AP policy, section 3 Partial receipt: pay what arrived, hold the rest
- R-18 Merovyn Packaging terms, clause 4 Freight is prepaid on orders over $10,000
- R-24 Approval matrix, row 2 Split payments: AP lead approves first
- R-31 Client rulebook No auto-rejection without review
-
A versioned graph that links each check to a decision and a sign-off.
- Check Invoice lines · Receipts · Vendor terms
- Decide Pay · Hold · Dispute
- Review AP lead approves · Agent-tagged write · Logged reason
-
The Operator catches rule changes. Past invoices re-run before a person approves the change.
- Kit billed as parts Matched
- Payment with a misread invoice number Matched by PO
- Short payment on three invoices Deduction case
- Approval threshold:
was $25,000, now $15,000
How we’ll measure the pilot.
Targets we agree with you before the build, scored on synthetic invoices with a known right answer.
Pay-or-hold decisions are checked against invoices with a known right answer.
The reason for each exception, checked line by line.
Apply a real rule change, then re-run the pilot invoices without engineering work.
Questions to askCheck the answer against your own cases
Questions to ask any invoice AI.
-
Does it find the cause, or only the stop?
Why it matters: A code like “price variance” still sends a person digging.
Across: It names the cause line by line, with the record and rule behind it.
-
Does it carry each client’s rules?
Why it matters: Every new client or entity arrives with its own exception set.
Across: Each client keeps its own rules and routing, such as no auto-rejection without review.
-
What happens when a rule changes?
Why it matters: Hand-coding each exception rarely pays back the effort.
Across: Describe it in plain language. It’s tested on past invoices and approved first.
-
Can you trace every pay or hold?
Why it matters: Auditors and your clients need the reason behind each payment and each hold.
Across: Every decision is logged with its rule and source. Agent writes are tagged as the agent’s.
Start with your hardest exceptions.
A three-week pilot on synthetic invoices built from your rules, scoped to one client or entity.
- Week 1
- AP policy, tolerances, and approval rules
- Your exception types, with resolved examples
- Vendor terms for the scenarios in scope
- Week 2
- Writes the rulebook in plain language
- Your AP lead reviews it
- Builds synthetic invoices for each scenario
- Week 3
- Tested on held-out invoices
- Causes and misses reviewed
- Results against the agreed targets
- Your decision
Use the results to decide whether to connect your ERP and your AP channels.
What we need to start.
- AP policy Matching, tolerance, and payment rules
- Approval matrix Who approves what, at which thresholds
- Vendor terms Pricing, freight, and payment terms
- Exception types Where automation stops today
- Resolved examples How your team cleared each one
- Time with your AP leads To answer the gaps the Architect finds
How it connectsPermissions, approvals, and your systems of record
Across runs where the work happens.
Your systems trigger the process and remain the source of truth. Across returns the result to the operational workflow, with a review package when a person needs to decide. The integration and review interface are configured for your use case and existing systems.
Work arrives
Invoice received or updated
- Coupa
- NetSuite
- SAP
- Oracle
Across
Context.
Rules.
Decision.
Routine work
Post the invoice, within the configured controls.
Ready for review
Prepared exception for the AP lead, with the reasoning and evidence ready.