The reconciliation department
A core banking, lending or insurance system that does not talk to the ledger grows a team whose job is to summarise the day into journals. Disbursements then leave through a bank portal that sits outside the audit trail. IFRS lives in a workbook with no posting date and no owner.
Client names appear only once signed off. The pattern is one we are asked to resolve in New York, Frankfurt and Johannesburg alike.
The hub posts under rules
AccountingFlow 365 sits on Finance & Operations. It receives sub-ledger activity from those core systems and posts it to the general ledger under controlled rules. Every source transaction keeps an audit trail. Consolidation is multi-entity. The hub does not change because the entity is in the United States, in Europe, in India or in Africa.
Business Central is the wrong container for this buyer. Sub-ledgers that must post under rules, and a group pack that is more than export-and-add, belong on Finance & Operations. A move between the two platforms is a project, not an upgrade.
Leases are data. Payments are a gateway.
IFRS 16 is a schedule, a liability, a right-of-use asset and a set of dated postings. LeasingFlow 365 does that on the standard Finance & Operations Asset Leasing module, including tax on the lease transactions. Test cases match worked examples. The lease is not a year-end spreadsheet.
IFRS 15 and IFRS 9 have to land the same way: the model may calculate, the posting hits the ledger. Vendor and employee payments go through DisbursementFlow 365. A new bank format is a mapping in Azure, not new X++. IBAN rules cover 89 countries. Maker-checker and an immutable status log are the control.
What to ask before you sign
Show a sub-ledger line that posts with its source key still on it. Show a lease that is not in Excel. Show a disbursement batch that a second person released. Show local statutory and IFRS from the same trial balance.
If any of those is a workbook, the hub has not been designed. It has been postponed to the close.