Phyto Nex AI for SAP Concur

SAP Concur already enforces header-level limits through audit rules, but those rules evaluate the amount and expense type an employee typed, not what is printed on the receipt. A $612.47 entry coded as Hotel passes a $650 nightly cap even when the attached Marriott folio shows $86.40 of minibar and a $38 in-room movie. Phyto Nex AI pulls the receipt image for every entry through the Receipts v4 API, reads the folio line by line, and compares what was charged with what was claimed.

The connection is authorized once by a Concur administrator from the App Center listing. Concur issues a company-level refresh token to Phyto Nex AI; no individual user credentials are stored, and the grant can be revoked from Concur's connected apps page at any time. Because the scopes are read-only, Phyto Nex AI cannot approve, reject, or edit a report inside Concur. Findings appear in the Phyto Nex AI AP queue and, optionally, as a comment your processor sees when the report lands in their queue.

Concur environments are rarely uniform. Phyto Nex AI reads policy groups per entity, so the US sales policy and the UK services policy are evaluated against their own limits and currencies. Itemizations created in Concur (for example, splitting a hotel bill into lodging, room tax and breakfast) are respected; Phyto Nex AI only flags itemizations that disagree with the folio, such as a breakfast line that is actually room service with two cocktails.

Company card transactions imported from the card feed are matched against out-of-pocket entries across every report in the trailing 120 days. That is how a $3,200 fare paid on the corporate Amex and resubmitted as a personal reimbursement two weeks later gets caught before the payment batch runs.