SoftTech AI Registry
SAP · Joule

Create Single Payment

Joule transactional capability for SAP S/4HANA Cloud Private Edition in which a user asks Joule, in natural language, to create a single supplier payment - either by selecting an open vendor line item (initiating clearing of that single open item) or, where no open-item reference exists, by supplying all mandatory payment fields. SAP documents the capability as calling API FAP_CREATE_SINGLE_PAYMENT through semantic object-action AccountingDocument - createSinglePayment, and also offers a button to navigate to the Create Single Payment Fiori application. SAP defines transactional capabilities as allowing users to create, display, update or delete business data without leaving the chat window.

Recorded characteristics

Function
Documented function: (a) create a single payment by selecting an open vendor line item and providing minimum input such as offsetting account number and posting date - SAP states that after the list of open items of a supplier account is displayed, the user can initiate clearing of a single open item by clicking the Create Single Payment option, or use a direct prompt instead; (b) create a single payment by providing vendor account number, company code, amount and other details, where a vendor payment without an open-item reference requires all mandatory fields; (c) navigate to the Create Single Payment Fiori application with a click of a button. For the no-open-item path SAP lists mandatory fields: Tax Code, House Bank, Posting Date, House Bank Account, Payment Method, Bank Sub-account, Document Date, Value Date, Amount, Company Code, Fiscal Year. SAP sample direct prompt: "Create single payment for Supplier Account 10300002, company code 1010, document 5100000017, item 001, fiscal year 2026". SAP does not document which fields Joule may default, infer or retrieve rather than collect from the user. Persistent state: SAP identifies the invoked action as AccountingDocument - createSinglePayment (API FAP_CREATE_SINGLE_PAYMENT) and describes the open-item path as initiating clearing of a single open item. Beyond the named semantic object and the word clearing, SAP does not enumerate the resulting document types, general-ledger postings, supplier balance effects or cash/bank clearing account effects, and these are recorded as not established. No reversal, cancellation, payment edit or reset-clearing function is documented for this capability. Boundaries: Post Outgoing Payments (FAP_PAYMENT_POST_SRV, Supplier - postPayment, post and clear a single outgoing payment in one step) and Manage Supplier Line Items (FAP_VENDOR_LINE_ITEMS_SRV, retrieval and payment blocks) are separate documented Joule capabilities and are not part of this record.
Data access
Documented context for the open-item path is the supplier account open line-item list already displayed in the conversation, from which a single open item can be selected; SAP identifies a payment by supplier account, company code, document number, item and fiscal year. Retrieval of supplier or vendor line items is documented as the separate Manage Supplier Line Items capability (supplier account, company code, item type, key date, clearing status, supplier name or ID). No broader access to finance records is documented for Create Single Payment.
Actions
Can take actions
External actions
Unknown
Human confirmation
Not established
Permission basis
Not established
Administrative control
Business AI activation through the AI Activation Dashboard in SAP for Me and Central Business Configuration (package activation, user counts, AI Unit SKU); assignment of the SAP_BR_AP_ACCOUNTANT business role; the underlying technical catalog SAP_TC_FIN_FO_COMMON for the semantic object-action; SAP S/4HANA Cloud Private Edition release level. No capability-specific on/off switch, usage restriction or capability-level audit control is documented on the capability page.
Default state
Conditional
Availability
SAP S/4HANA Cloud Private Edition only; SAP does not document Public Edition support for this capability. SAP states two different minimum releases in current documentation: the capability page technical table gives 2023 FPS01+, while the Release-Specific Capabilities list gives Create Single Payment 2025 FPS01+. Both are recorded; the discrepancy is unresolved in SAP current documentation. No GA/preview label, region list or language list is documented for this capability.
Licensing
Requires SAP S/4HANA Cloud Private Edition and Joule/Business AI entitlement. SAP activation documentation references an AI Unit SKU (8019164, released 20 May 2025) and a legacy AI Unit SKU (8018592), with package activation via SAP for Me. No price, no per-request consumption and no capability-specific entitlement are documented.
External model or provider
Not established
Limitations and uncertainty
Not established: whether Joule presents a summary or requires an explicit confirmation before executing (no confirmation step is documented, and a conversational prompt is not treated as confirmation); the runtime identity under which the backend action executes (SAP documents only that the user must hold SAP_BR_AP_ACCOUNTANT, and that Joule business users authenticate through SAP BTP AppRouter/XSUAA OAuth authorization code flow - a required business role does not by itself establish that execution carries the invoking user authorizations, and no separate agent identity is documented either); the exact SAP document objects and accounting postings created; whether the supplier item is cleared by this action or clearing is merely initiated; any downstream payment medium, bank communication, automatic payment program, payment run or external funds transfer (no bank transmission is documented, so external action is unknown rather than no); which mandatory fields may be defaulted or inferred; model or provider; any AI-specific execution logging distinct from ordinary SAP document audit data; supported payment methods, currencies, partial or residual items, withholding tax, special G/L, cross-company payments, amount limits or approval workflow.

Evidence