Industries / Technology / Software and SaaS / ERP and CRM software
Finance
The ledger and the work that feeds it: recording sales and purchases, checking and paying supplier invoices, collecting from customers, and keeping the controls that stop errors and fraud.
5
Milestones achieved, from 1973 to 2016.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1973
Postings made as they happen
SAP's first product was a financial accounting system it named RF, the "R" standing for real time. It processed entries when they were needed instead of in batches overnight, and became the base of the modular system later called SAP R/1. The software was written and tested on customers' mainframes at night and on weekends, and after two and a half years SAP had 40 reference customers.
Credit
SAP
1975
Invoices checked against purchases
SAP's materials management system, RM, joined purchasing, stock records and invoice verification, the check that a supplier's invoice matches what was ordered and received. Amounts flowed from it straight into financial accounting, so an invoice could be verified and posted in one step. SAP calls this, all of a company's applications sharing data stored in one place, the feature that set it apart.
Credit
SAP
2004
Finance software in court
The US Justice Department and ten states sued to stop Oracle buying PeopleSoft, arguing that only Oracle, PeopleSoft and SAP could supply finance and human resources software to large, complex organizations. On 9 September 2004 Judge Vaughn R. Walker ruled for Oracle: the plaintiffs had not proved that Lawson, AMS, Microsoft and other vendors did not compete with the three. The court also found that 90% of ERP sales are bundles of several modules, rarely one alone. Oracle completed the purchase on 7 January 2005, at a preliminary total price of $11.1 billion.
Credit
US District Court for the Northern District of California; Oracle
2015
One table for every posting
In SAP S/4HANA, released in 2015, every business transaction in the general ledger, management accounting (called controlling), asset accounting and the material ledger writes a single journal entry to one table, the universal journal. Before, each area kept its own records and they had to be reconciled. An SAPinsider article called the delayed, manual reconciliation of controlling with the general ledger one of "the most painful aspects" of implementing SAP finance, and said it was now "instantaneous and automatic".
Credit
SAP
2016
Old flaws in live systems
US-CERT, the US government's computer emergency team, warned that at least 36 organizations worldwide showed signs that attackers had exploited a flaw in SAP's Java platform, which runs SAP ERP among other products. SAP had patched the flaw in 2010; exploiting it gave attackers who had not logged in full control of the business data and processes. In April 2025 a new flaw in SAP NetWeaver, which let anyone upload programs without logging in, was added to the US list of exploited vulnerabilities five days after it was published.
LessonERP systems are often left unpatched for years, and attackers look for them.
Credit
Onapsis, whose researchers found the 2016 attacks; US-CERT
Watch for
Invoices matched by an agent
Oracle says the Payables Agent in its Fusion Cloud ERP takes in invoices from email, supplier portals, e-invoicing networks and PDFs, and matches them to purchase orders and goods receipts. It then applies tax, policy and fraud checks and routes each invoice for approval and payment, so that more invoices pass with no person touching them. Oracle gives no figure. In June 2026 Version 1, a consulting firm that implements Oracle, wrote that the agent was not yet generally available and was still in an early adoption program.
Achieved whena customer or auditor publishes the share of invoices processed without a person, the error rate and the share passed to people, over a stated period and volume.
Claimed by
Oracle, October 2025
Collections ranked by agents
Nestlé, which is moving its finance and operations systems in 140 countries to SAP S/4HANA, says SAP's Joule Accounts Receivable Assistant can rank overdue invoices by risk and business context and recommend the next step to collectors. SAP says the assistant, four of whose agents handle collections, speeds up payment and lowers days sales outstanding, the average number of days a company waits to be paid. PYMNTS reported that SAP gave no figures and no release date.
Achieved whenNestlé or another named customer reports days sales outstanding and collectors' workload before and after, over at least two quarters, measured by someone other than SAP.
Claimed by
Nestlé and SAP, October 2026
Open
01
A public three-way match test
A public set of made-up purchase orders, goods receipts and supplier invoices, loaded into an open-source ERP, in which some invoices carry planted problems: a wrong price, a short delivery, a duplicate, the wrong unit of measure, goods never received. It scores how often the ERP's own matching rules, and AI agents, pass the good invoices and stop the bad ones. Matching an invoice to its order and its receipt is called three-way matching.
The briefCredit · unclaimed02
Duty conflicts in open ERPs
An open-source checker that reads who holds which roles and permissions in ERPNext or Odoo and lists every user who can do two jobs that internal controls say must be split, such as setting up a supplier and paying it, or raising a purchase order and approving it, together with a seeded test that scores any such checker. The conflicts come from a published rule set that anyone can extend. Splitting such jobs between people is called segregation of duties.
The briefCredit · unclaimed
Open 01 · the brief
A public three-way match test
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public set of made-up purchase orders, goods receipts and supplier invoices, loaded into an open-source ERP, in which some invoices carry planted problems: a wrong price, a short delivery, a duplicate, the wrong unit of measure, goods never received. It scores how often the ERP's own matching rules, and AI agents, pass the good invoices and stop the bad ones. Matching an invoice to its order and its receipt is called three-way matching.
Why it is still open
Oracle's Payables Agent, which does this matching, was still in early adoption in June 2026 with no published rates. The public material found is a set of 50 procurement questions and answers, which tests knowledge rather than documents, an open-source invoice-to-pay agent whose own evaluation file gives "smoke-level scenario coverage", and another open-source payables agent whose labeled test data holds 12 invoices. A search found no public scored test with documents and an answer key.
Built with what exists
ERPNext or Odoo Community, open-source ERPs that hold purchase orders, receipts and supplier invoices; Python with the Faker library to make up suppliers and orders, and a PDF library such as ReportLab to print the invoices, so the data behind each PDF is the answer key; AI agents built on models such as Claude, Gemini and GPT, each run several times (see the Note "All twenty times"), with the cost per invoice recorded (see the Note "The jobs agents repeat").
First step
Generate 50 orders, receipts and invoices with ten planted problems in ERPNext, and record which problems its standard checks catch.
Done looks like
2,000 invoices from 100 made-up suppliers, a fifth of them with planted problems of eight kinds; for each method, the share of bad invoices stopped, the share of good invoices wrongly held and the cost per invoice, over three runs, with data and scoring code under an open license.
Open 02 · the brief
Duty conflicts in open ERPs
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An open-source checker that reads who holds which roles and permissions in ERPNext or Odoo and lists every user who can do two jobs that internal controls say must be split, such as setting up a supplier and paying it, or raising a purchase order and approving it, together with a seeded test that scores any such checker. The conflicts come from a published rule set that anyone can extend. Splitting such jobs between people is called segregation of duties.
Why it is still open
For Odoo 18 to 20, the developer Pokutsoft sells two modules, at about $79 and $97 under Odoo's proprietary license, that scan users against conflict rules; neither publishes a test of how many conflicts it finds, and the rules are not open. On the ERPNext forum in 2020, a user asked how a client's accountant could check before go-live "that the shipping receiver can't also create and approve POs"; the replies suggested redesigning the roles or writing a custom report over the table that maps users to roles. In a thread from October 2025 to August 2026, users comparing ERPNext and Odoo permissions with SAP's access control product were pointed to permission hooks, code they would write themselves. Searches of GitHub and the web found no open-license checker or shared rule set for either system.
apps.odoo.comapps.odoo.comdiscuss.frappe.iodiscuss.frappe.io
Built with what exists
Python; ERPNext's user, role and permission records read through its REST API, or Odoo's groups and access rules read through its XML-RPC interface; a test company set up in each system; optionally an AI model to suggest which duties a custom role covers, with every suggestion checked by hand.
First step
Write ten conflict rules for ERPNext's buying and accounts modules and run them against a test company with five deliberately over-permitted users.
Done looks like
A rule set of at least 30 conflicts across purchasing, payables, receivables and the general ledger, tested on 100 seeded role setups holding 300 planted conflicts, with every conflict found or missed and every false alarm reported, for the new checker and for any other checker run on the same setups; code and rules under an open license.