Dynamics 365 for Payments: F&O for Payments Companies at Scale

D365 F&O is the wrong answer for the processor platform (Stripe, Adyen, FIS, Fiserv, TSYS, proprietary) — those run payment processing at latency and scale F&O isn't designed for. F&O is the right answer for the financial backbone of a mid-to-large payments company — GL with the dimensional structure payments revenue analytics require (merchant, sales partner, scheme, MCC, product), revenue recognition for processing revenue (pass-through interchange, scheme fees, processor markup) under ASC 606 with the gross vs net presentation decision that defines payments company financial statements, residual revenue calculation for sales partners with the commission structure complexity ISO and PayFac relationships involve, multi-entity consolidation across the common PayFac + acquirer + ISO + technology subsidiary structure, and AP at scheme fee and processor cost volume.

Payments F&O done right configures the GL for payments reality. Dimensional accounting for merchant-level, sales partner-level, scheme-level, MCC-level, and product-level revenue and cost visibility. ASC 606 revenue recognition for processing revenue with gross vs net decision documented (gross presentation where payments company is primary obligor in scheme relationships, net where payments company acts as agent). Residual calculation for sales partners across the commission structures ISO agreements involve. Multi-entity consolidation with intercompany accounting. Integration with the processor platform for transaction data feeding GL at summary or detail level. Integration with CTRM where applicable (FX-heavy cross-border payments). Audit trail supporting SOC 2 Type II and SEC if public. Done with this discipline, F&O delivers in 15-24 months for payments at scale. Done as generic ERP, it doesn't handle the residual or gross/net decisions that define payments company finance.