2026.1 Bill Capture: OCI Document Understanding LMM and currency sourcing preference

The 2026.1 release notes for Vendors, Purchasing, and Receiving are thin on technical detail — there are no record/field IDs, no SuiteScript module changes, and no SuiteTalk schema updates called out. The substantive changes are all in Bill Capture. Here is what an admin or integrator actually needs to know.

What changed

1. Intelligent Bill Capture (OCI Document Understanding LMM)

Bill Capture's extraction backend now uses Oracle Cloud Infrastructure's Document Understanding Custom Generative Model V2.0 — a large multimodal model (LMM) — to pull header and line values from vendor bills. Oracle claims improved accuracy on multi-column layouts, mixed content, and unstructured/free-text invoices.

• Rollout is gated: select accounts hosted in US data centers only. There is no documented opt-in toggle.
• When active, a "Built with Llama" badge appears on the Review Scanned Bill page — that's your only in-app signal that the new model is running.
• The release notes do not specify whether extracted field shape, confidence scoring, or the scannedvendorbill record schema changes. Assume downstream automations that read parsed values may see different content quality (more fields populated, possibly different formatting) even though the record structure is unchanged.

2. New currency-sourcing preference

Previously, the currency on a scanned bill was always inherited from the vendor record. You can now source it from the scanned file itself, and file-sourced currency is the new default.

• Setting lives at Bill Capture Preferences > Review Page Field Sourcing > Currency.
• This is a behavior change on upgrade — accounts that relied on vendor-record currency for multi-currency vendors will see the bill currency populated from OCR results going forward unless the preference is flipped back.

3. Open scanned documents from the list

On the Scanned Vendor Bills list, the file name is now a clickable link that previews the source document in-browser and allows download. No API or workflow impact — pure UI convenience.

What's not in the release note

The page does not mention any of the following, and you should verify them yourself if they matter to you:

• Whether the SuiteScript N/record type for scanned vendor bills (or the related staging records) gained or changed any fields.
• Whether SuiteTalk REST (/services/rest/record/v1/vendorBill) or SOAP WSDL surfaces any new fields tied to the LMM extraction.
• Governance cost or rate-limit changes when invoking Bill Capture programmatically.
• Data residency implications of routing bill images through OCI Document Understanding — relevant if you have non-US vendors but a US-hosted account.

What to do

1. Audit the currency preference before upgrade. Go to Setup > Accounting > Bill Capture Preferences > Review Page Field Sourcing and decide whether file-sourced or vendor-sourced currency is correct for your AP workflow. If you have multi-currency vendors and have been depending on the vendor record as the source of truth, set Currency back to the vendor record after upgrade.
2. Check for the "Built with Llama" badge on the Review Scanned Bill page in a sandbox refreshed to 2026.1. Its presence tells you whether your account is in the LMM rollout.
3. Re-test any SuiteScript or workflow that consumes scanned bill output (user event scripts on bill creation, approval routing, GL impact lines). Even without schema changes, different extraction quality can cause previously-empty fields to populate, which may trigger field-change logic that didn't fire before.
4. Re-test integrations that POST or GET vendor bills via REST/SuiteTalk against a 2026.1 sandbox to confirm no silent payload differences on bills originating from Bill Capture.
5. Review data residency and privacy with your compliance team if vendor invoices contain regulated data — extraction now flows through an OCI generative AI service.
6. Communicate the list-page preview to AP users; it eliminates the need to drill into a record just to check the source PDF.

Bottom line

No code-breaking changes are documented, but the currency-sourcing default flip is a real behavior change, and the LMM extraction can change which fields come back populated on scanned bills. Treat this as a functional regression-test item for any AP automation, not a no-op upgrade.