Basware applies AI to the work around supplier invoices

Basware applies AI to accounts payable, where an invoice must be understood, coded, approved and reconciled with business records before it can proceed. Its useful contribution is broader than extracting text from a document. The company connects invoice handling with the exceptions, accounting choices and enterprise integrations that determine whether finance teams can rely on the result.

01 / ProductAI supports a financial process with several distinct decisions

Basware’s AP Automation page describes invoice handling, matching, routing and coding across purchase-order and non-PO workflows. These activities should be distinguished. Extracting the correct amount does not establish the correct account code, and an accurate code does not establish that the expense has been approved.

InvoiceAI is the company’s umbrella for AI across the invoice lifecycle. The page describes several AI techniques and evolving agent capabilities. This Blueprint concentrates on the more concrete SmartCoding and AP workflow descriptions rather than assuming every agentic ambition is a generally available, separately usable product.

SmartCoding uses invoice history and multiple accounting dimensions to suggest coding for non-PO invoices. Basware describes showing five alternative coding combinations and allowing teams to set confidence thresholds. That gives reviewers an actionable starting point, but historical frequency should not become the sole reason to charge a new invoice to a particular business unit.

Basware completed its acquisition of Trustpair on 5 October 2026. The announcement says Trustpair continues with its own platform, contracts and support. Payment assurance is therefore relevant company context, but buyers should not assume that the acquisition automatically bundles those capabilities into an AP subscription.

02 / AudienceUseful where invoice exceptions consume finance capacity

Basware is most relevant to finance organizations with a substantial flow of supplier invoices, multiple operating units or several ERP environments. Its company overview presents an established invoice lifecycle business, while the current AP offer targets the work between invoice arrival and financial processing. This makes the AI relationship central to an existing operating problem.

A good sponsor includes accounts payable, accounting-policy owners and ERP integration staff. AP reviewers understand recurring supplier patterns; controllers determine whether the accounting treatment is appropriate; system owners ensure that approved data reaches the correct ledger. An evaluation that includes only document capture will miss the disagreements that occur later.

A small business with a limited invoice flow may have a simpler starting point in its existing accounting system. An enterprise with inconsistent supplier identifiers or unclear cost ownership may need cleanup before automation expands. The volume of invoices matters less than the combination of repeatability, exception burden and the organization’s ability to define a correct result.

03 / WorkflowPropose a non-PO coding pilot with meaningful exceptions

Consider a proposed pilot for recurring facilities invoices that arrive without a purchase order. This is an evaluation design, not a test of Basware. Select a reviewed historical sample and identify the supplier, legal entity, cost center, account and approver for each invoice. Preserve the original invoice and the reason for any correction made during the historical review.

Include ordinary recurring charges as well as a new location, a one-off repair and an invoice covering more than one department. These examples test whether a suggestion follows the actual business context or merely repeats the supplier’s most common accounting treatment. Keep a separate set of invoices for evaluation rather than assessing only examples used to prepare the workflow.

Ask SmartCoding to present its suggestions and alternatives. The reviewer should compare the proposed dimensions with the invoice and the relevant accounting policy. Record accepted suggestions, edited fields and cases that need clarification from the business. The goal is not to maximize acceptance at any cost; it is to reduce avoidable work while retaining a defensible explanation.

Treat an automatic-processing threshold as a policy choice to evaluate. Begin with human review, inspect the errors that remain and only then decide whether a narrow class of invoices is suitable for less intervention. An incorrectly coded invoice that appears confident can be more troublesome than an uncertain invoice routed to the right person.

Finally, follow approved data into the ERP and reconcile the result. Include a closed accounting period, an inactive cost center and a duplicate invoice in the test design. Check who receives each exception, how it is corrected and whether a retry creates another record. Measure accounting corrections and reconciliation effort separately from text-extraction accuracy and processing speed.

04 / PricingCommercial scope follows functionality and business volume

Basware’s pricing page describes subscriptions tailored to selected modules and organizational requirements. The pricing FAQ on its AP Automation page specifies functionality, business volume and commitment as commercial factors. The reviewed sources do not publish a cash tariff that supports a universal price per invoice or per employee.

A useful proposal should identify the invoice population, selected modules, expected volumes, ERP connections and implementation responsibilities. Ask how the supplier treats volume changes, additional legal entities and custom requirements. Confirm which InvoiceAI or SmartCoding capabilities belong to the proposed package rather than assuming the umbrella name guarantees every feature.

Separate the planned automated route from the exception route when comparing costs. The buyer may still need staff to resolve missing supplier information, disputed charges and invalid accounting allocations. Those are operational planning considerations, not claimed Basware charges. A low unit price is not sufficient if the remaining exceptions become harder to investigate.

Request a pilot scope with representative invoices and explicit acceptance criteria. It should be possible to compare the proposal with the actual outcome: which work was automated, which decisions remained with finance and how much reconciliation effort was required. Avoid extrapolating a supplier’s general efficiency claim into a forecast for a different invoice mix.

05 / DistinctionsThe accounting handoff is part of the product question

Basware’s ERP integration overview describes standard, advanced and partner-led approaches, with APIs and connectors. The practical distinction is the ability to fit invoice processes around existing financial systems. It does not establish that every custom ERP workflow is ready to use without configuration.

That integration scope matters because accounts payable often needs information from several places: supplier status, purchase orders, receipts, cost allocations and approval ownership. An AI suggestion becomes more useful when it can be checked against those records. Conversely, a suggestion based on stale master data may be plausible while still failing when the approved invoice reaches the ledger.

SAP’s Blueprint is relevant when the organization’s procurement and finance processes revolve around an ERP estate. Workday’s Blueprint provides another view of AI close to financial and organizational records. Compare Basware against the concrete invoice problem and existing system capabilities, rather than assuming a dedicated AP layer or an ERP-native approach is always preferable.

06 / QuestionsHistory, thresholds and approvals deserve close inspection

Ask how the proposed workflow handles a supplier whose invoices belong to several departments. Review the evidence behind a coding suggestion and what happens when the pattern changes. Historical data can be helpful, but it can also contain old accounting choices, temporary exceptions and mistakes that should not be repeated.

Request a clear explanation of confidence thresholds and the consequences of crossing them. Does a threshold determine a suggestion, a routing step or an automatic action? Which fields must be reliable together? The answer should be demonstrated with the actual package and configuration, including invoices that fall just outside the intended automatic path.

Approval and payment authority should remain explicit throughout the evaluation. A coding recommendation is not evidence that the business accepted the goods or authorized payment. Establish the responsible approver, the source of that authority and the record retained when a decision changes. This is especially important when a recurring invoice looks familiar but includes a new charge.

The InvoiceAI page mixes current product descriptions with forward-looking discussion of agents. Ask the supplier to distinguish generally available capabilities, customer-specific configuration and roadmap items. Build the initial acceptance criteria around demonstrable functionality. Future features can inform a longer-term discussion without becoming a dependency for the first useful result.

07 / DecisionChoose one invoice class and inspect the complete outcome

Basware deserves a closer look when finance teams want to reduce repetitive invoice work while retaining a clear exception and reconciliation process. Start with a coherent invoice class whose correct accounting treatment can be reviewed independently. Include enough variation to expose the limits of historical suggestions.

The decision to expand should depend on the complete process: accurate capture, appropriate coding, valid approval, successful ERP recording and manageable exceptions. If the pilot only improves the first stage, document that narrower benefit. If it exposes inconsistent master data or unclear cost ownership, use those findings to improve the process before increasing automatic handling.