Standard Finance & Operations is not the Act
Standard Finance & Operations ships no preference-point scoring, no Central Supplier Database link, no B-BBEE tracking, and no GRAP or Modified Cash Standard reporting. The entity then keeps compliance in registers beside the system. The registers surface at audit, which is the most expensive time to discover them.
GovFlow 365 closes that gap on Finance & Operations, across demand to disposal. South Africa ships first. The rules engine is country-configurable. Kenya under PPADA 2015 and AGPO, and Nigeria, Ghana, Rwanda, Tanzania and Zambia, are on the roadmap. They are not live packs, and we will not pretend they are.
Four groups, one ledger
Procurement compliance: Bid Specification, Evaluation and Adjudication Committees with separation of duties enforced, a 21-day close, an 11:00 cutoff and 90-day validity.
Supplier verification: a live Central Supplier Database sync, a B-BBEE scorecard, a debarment check, and SBD forms including SBD9. A supplier is not awarded without those checks.
Reporting: GRAP or Modified Cash Standard from the system, not an IFRS-only chart wearing a public-sector name. Irregular expenditure sits in a register with a 10-day AG and Treasury reporting timer. Amounts over R1 million are flagged.
Contracts, assets and performance: Treasury Regulation 16A deviation bands, 30-day payment tracking, asset disposal and vendor penalties.
One toggle, not a second workflow
Preference scoring is PPPFA 80/20 and 90/10. The Public Procurement Act 28 of 2024 threshold model sits on a toggle. It is not a parallel process someone remembers to run in a spreadsheet.
Activation is phased. Compliance-blocking modules first, reporting second, SARS e-invoicing and PPA activation third. Compliance-blocking modules first is how audits are passed on time.
Statutes for other regions, including US and European procurement rules, are configuration on the same chart. A public entity with an oversight board in those regions still uses one chart. The statutory layer is configuration. Inventing a FAR article number to sound global would be a different kind of failure.
Payments still have to be seen
Thirty-day payment tracking is useless if salaries and vendors leave through a side portal. The DisbursementFlow 365 pays vendors and employees to any bank, with maker-checker, ISO 20022 pain.001, and IBAN rules for 89 countries. A new bank format is a mapping in Azure, not new X++. Payroll for Kenya, Nigeria and South Africa, where it is in scope, posts to the same books.
Ask whether a bid can be awarded without a CSD and debarment check. Ask whether the irregular-expenditure timer is in the system or in a diary. Ask whether GRAP comes from the trial balance. If the answer is a register beside Dynamics 365, the law is not in the ledger yet.