Business Central for Payments: ERP for ISOs, PayFacs, and Growth-Stage Processors

Payments companies have a specific ERP trajectory. Early-stage (pre-Series A) often runs on QuickBooks — which cannot handle residual revenue recognition, interchange fee pass-through accounting, or the multi-entity structure most ISOs and PayFacs use. Growth-stage companies outgrow QuickBooks and face the ERP decision — NetSuite (dominant for mid-market payments), Sage Intacct, or enterprise platforms (SAP, Oracle). Business Central fits a specific niche: payments companies deep in Microsoft 365 where the CRM is Dynamics 365, companies that want integration with Power Platform for residual reporting to sales partners, and companies that find NetSuite priced too high for their current scale. At that niche, BC delivers in 5-7 months at a cost point the company's CFO can justify.

Payments BC done right configures for payments reality. Dimensional accounting for residual revenue by merchant, sales partner, and scheme. Revenue recognition for processing revenue (pass-through interchange, scheme fees, processor markup) under ASC 606 with the gross vs net presentation decision. Residual calculation for sales partners with the complex commission structures ISO relationships involve. Multi-entity for the common PayFac / acquirer / ISO structure. Integration with the processor platform for transaction data feeding the GL. AP for scheme fees, processor costs, and vendor payments. With the audit trail the external auditor and eventual SOC 2 Type II examination expect. Done with this discipline, BC delivers. Done as generic ERP, it doesn't handle residual revenue — which is the work that actually defines payments company finance.