Kolena AI Agent
Vendor Invoice Processing
Turn any vendor invoice into a clean, coded, and validated AP record - header and line items extracted, cost allocated across properties, arithmetic footed, terms and tax reviewed, duplicates and PO match flagged, and a Post / Hold / Reject recommendation.
Impact
Every AP control - footing, duplicate detection, tax review, PO-match readiness, terms and discount math, and GL coding - runs on every invoice in the queue instead of the few an analyst has time to check before payment, and multi-property invoices are split automatically instead of re-keyed by hand
per invoice
Volume fit
Works best for
AP teams processing hundreds to thousands of vendor invoices a month across a property portfolio, especially where many invoices bill work across multiple sites
Too small for
a team paying only a handful of invoices a month, where manual keying is faster than setup
Typical inputs
Documents
- Vendor invoice (single-property or multi-property)
- Vendor statement (rollup of prior invoices)
- Credit memo / credit note
- Purchase order (for three-way or two-way match)
- Receiving report / goods receipt or work-order completion
- Prior invoices from the same vendor (for duplicate detection)
Systems
- AP inbox / email
- Vendor portal
- ERP / accounting system
- Purchasing / PO system
- Property management system
Output
A validated AP record per invoice: canonical header, coded line items, per-property cost allocation, footing and tax checks, payment-terms and early-payment-discount analysis, PO-match and approval routing, a duplicate flag, a ranked exceptions list, and a one-line Post / Hold / Reject recommendation
Delivered to
- ERP / accounting system as an approved payable
- Approval workflow (PO owner or property manager)
- Return-to-vendor correction request
- Payment run / treasury schedule
What it extracts
· 16 fields
- Form
Invoice Summary
A one-look roll-up of the vendor, invoice number, dates, PO, bill-to entity, and the subtotal / tax / total so a reviewer can orient before reading the detail.
- Classification
Document Type
The intake bucket - single-property invoice, multi-property invoice, vendor statement, credit memo, or duplicate / resubmission - which routes every downstream check and protects the organization from paying the same obligation twice.
- Form
Invoice Header
The canonical header record - vendor legal name and remit-to, vendor tax ID, bill-to entity, invoice number and dates, payment terms, PO and receiver references, currency, and the subtotal / tax / total that feed every validation.
- Table
Line Items
One row per billable line, read with enhanced vision for scanned and handwritten trade invoices, with a spend category, a property or unit reference, and a suggested GL account bucket.
- Table
Cost Allocation
For a multi-property invoice, the dollar split across each property or cost center - by explicit allocation table, by percentage, or summed from the line items - reconciled to the invoice subtotal with a residual row if it does not tie.
- Number
Computed Line-Item Total
An independent recomputation of the sum of every line amount, so the AP team never relies on the vendor's own arithmetic for the subtotal.
- True/False
Invoice Totals Reconciliation
The core footing control - true only when the line items sum to the subtotal and the subtotal plus tax equals the total, both within tolerance.
- Form
Payment Terms and Discount Analysis
Parses the payment terms and computes the discount deadline, discount amount, net due date, annualized discount return, and a recommended pay-by date so a 2/10-type early-payment discount is never missed.
- Form
Tax Review
Recomputes the effective tax rate, checks it against the stated rate and the place of supply, and flags a possible overcharge to recover or missing tax that may trigger a buyer-side use-tax accrual.
- True/False
Vendor Tax ID Well-Formed
Confirms a vendor tax registration or taxpayer ID is present and plausibly formatted - a prerequisite for input-tax recovery and information reporting, and a common gate before onboarding a new vendor.
- True/False
PO Match Readiness
True when the invoice carries a usable purchase-order reference, signaling it can enter a two- or three-way match rather than routing through non-PO approval.
- Form
Approval Routing
Recommends the match type (three-way, two-way, or non-PO), the approval path, and a qualitative approval tier by dollar band, leaving the organization's approval matrix authoritative on the final threshold.
- Classification
Capex vs Opex Classification
Classifies the invoice as operating expense, capital expenditure, mixed, or ambiguous using GAAP improvement-vs-repair cues, so property improvements are capitalized and routine repairs are expensed.
- True/False
Duplicate or Resubmission Flag
Surfaces on-document duplicate signals - a DUPLICATE / COPY / RESUBMITTED stamp or a re-issue reference - that a key-field fingerprint match against AP history would miss, caught before approval.
- Table
Exceptions and Findings
The master exception report - every genuine issue from all checks, one row each, ranked Hold-first then by dollar impact, with the category, the finding, the dollar at stake, and a recommended action.
- Text
AP Recommendation
A single Post / Hold for review / Reject sentence naming the vendor, invoice number, amount, and the one most important reason, applying the reject and hold rules in order.
Prerequisites
- Your chart of accounts and GL coding rules (the agent suggests; the AP team confirms)
- Your capitalization threshold policy (capex vs opex)
- Your approval-authority matrix and dollar thresholds
- The matching PO and receiving report where a PO-based purchase is expected
Human review
An AP analyst reviews the flagged exceptions and the cited invoice fields before the invoice posts; the organization's own GL mapping, capitalization threshold, and approval-authority matrix govern the final coding and sign-off.
Where it fits
Accounts payable / vendor invoice processing
A vendor submits an invoice (single-property, multi-property, statement, or credit memo) by email, AP inbox, or vendor portal; a purchase order and a receiving report may already exist in the purchasing system
This step
Invoice capture, coding, validation, and approval routing
After
Who uses it
Grounded in
- Three-way match (purchase order / receiving report / vendor invoice) - accounts payable internal controlverified as of 2026-07-22
- Duplicate invoice detection - key-field fingerprint (vendor, invoice number, invoice date, total amount)verified as of 2026-07-22
- Early-payment discount / trade-credit terms (e.g., 2/10 Net 30)verified as of 2026-07-22
- US GAAP ASC 360 (Property, Plant, and Equipment) and IRS tangible property regulations - Treas. Reg. Sec. 1.263(a)-3 (improvements) and Sec. 1.263(a)-1(f) (de minimis safe harbor)verified as of 2026-07-22
- Sales and use tax - buyer-side use-tax self-assessment and place-of-supplyverified as of 2026-07-22
- Vendor tax identification and information reporting - IRS Form W-9 / 1099 (US) and VAT/GST input-tax recovery (non-US)verified as of 2026-07-22
Related agents
Browse all agents →Utility Bill Extraction (AP)
Turn any utility bill - electric, gas, water, sewer, stormwater, or trash - into a clean, cited, footed AP record: usage recomputed from the meter reads, charges reconciled to the total, duplicates screened, master-metered costs allocated across units, and the bill GL-coded and exception-flagged.
CAM Reconciliation
Reconcile a landlord's CAM statement against the lease and catch every over- or under-billing, with each finding cited to the controlling clause.
CRE Market Research
Turn a pile of market reports, broker commentary, and news into a normalized, cited, filterable research database - one row per document, with every figure cross-checked against current public benchmarks.
See Vendor Invoice Processing on your documents
We'll run it against a file of yours and walk through every cited field.