Skip to content

Build3 publishers3 min readPublished

SAP schedules its new finance Joule Assistants for early adopters in the first quarter of 2027

SAP unveiled Joule Assistants for five business areas at Connect, with most due via early adopter and GA releases by the first quarter of 2027. Controllers get a pilot calendar, while SAP Pay already moves money in the US and UK.

The Engineer · Build desk

Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

Photograph accompanying SAP schedules its new finance Joule Assistants for early adopters in the first quarter of 2027
Photo: thenextweb.com

What happened

  • SAP's new Revenue Recognition Assistant explains how revenue is configured, calculated and posted, and classifies transactions under IFRS 15 and US GAAP.
  • A new Disclosure Assistant gathers and tags data for external financial reports, drafts the narrative and checks the result before it is published.
  • SAP Pay, built on the newly formed Tereina subsidiary, sends payment once an invoice is approved in SAP Cloud ERP and matches it to the invoice or purchase order.
  • SAP plans to buy TechWolf, a Belgian company that maps work and skills inside organizations, on undisclosed terms, with closing expected in the fourth quarter.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • exposure Because SAP Pay pays on approval, the people who can approve invoices in SAP Cloud ERP are, in effect, the people who can pay them, and approval rights need review on that basis.
  • constraint Agents built as extensions of configured processes inherit whatever revenue and cost-allocation rules a customer already has, errors included, so cleaning up configuration comes before any pilot.
  • decision Trade teams need their own baseline for manual classification time before SAP's 'as much as half' figure can go into a business case.

Eric van Rossum, SAP's head of product marketing for applications and suite, described an agent as something that "to a certain degree is actually just an extension of the process in the back end" [16]. I think he has the design right for this work. SAP has spent five decades writing each country's localization and regulatory requirements into its core applications, among them Brazil's Nota Fiscal electronic invoicing rules and AI regulations that are not the same in Europe as in the US [17]. An agent that calls those processes inherits their rules. It does not have to rediscover Brazilian invoicing law from a prompt.

The exposure sits in the steps where an assistant produces something the configured process did not already decide. Explaining how revenue is configured and posted is a read over existing rules [7]. Classification under IFRS 15 or US GAAP is a judgment [7]. The narrative in an external report is generated text, and the pre-publication check runs inside the same assistant that drafted it [8]. A draft and its review from one tool amount to one control. The Overhead Accounting Assistant makes bulk changes to cost and profit centers [9], so a wrong instruction lands on many records in one pass. "If you're going to do a financial close or if you're going to do statutory reporting or many of these items," van Rossum said, "there is just not a room for error" [13].

The trade figure gets the treatment any vendor benchmark gets. SAP says the International Trade Assistant cut classification work by as much as half in early deployments [20]. The phrase "as much as" puts that at the top of the range. SAP did not say how many deployments there were or what baseline they were measured against [20]. For the figure to transfer, a buyer's classification would have to be mostly manual today, on a product catalog that looks like those early customers' catalogs.

SAP Pay has the cleanest design in the set. Matching happens at payment time inside the ERP [14]. The payment and the document it settles share one system of record. Cross-border payments can also settle in stablecoins [15].

At Sapphire earlier this year, SAP outlined an "Autonomous Enterprise" run in large part by AI agents [1]. Connect is aimed at the line-of-business staff who run finance, procurement, HR and supply chain day to day [2]. "Connect is all about making it real," van Rossum told The New Stack. "We set the strategy at Sapphire. Now we need to come with the proof points, what that means for our customers, what it means when we have the products in our hands and so on." [3] The new finance assistants open early adopter programs in the first quarter of 2027 [11]. The finance assistants launched at Sapphire are due to gain six dedicated agents, for close, treasury, tax, billing, planning and receivables [10] [19]. In Las Vegas this week, the hands-on part is more than 20 labs where attendees build their own agents [4].

What to watch

  • Whether SAP publishes deployment counts and a baseline behind the International Trade Assistant's classification figure.
  • Which of the new finance assistants move from early adopter programs to general availability after the first quarter of 2027, and on what dates.
  • SAP Pay's expansion beyond the US and UK, and regulatory approval of the TechWolf deal ahead of a fourth-quarter close.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories