Implementing Cloud Financials: From Empty Pod to Go-Live · Module 10 · Expenses
Corporate cards
Lesson 102 of 153 · 1 min
The card issuer sends a transaction feed. Transactions land in the employee's expense workspace. The employee categorises them and submits. Company-pay versus individual-pay is the design decision in card programmes, and the difference between them is an accounting difference rather than a policy one. Then matching card transactions to receipts, which is where most of the employee's effort actually goes. Then the integration reality, which nobody puts in a sales deck: each card provider's file format differs, feeds break, and reconciliation of the card liability account is a monthly job. Set that expectation before go-live rather than after the first month it is missed. And the one that goes wrong six months in: unsubmitted card transactions sit in limbo and nobody owns them. Recommend an aging report and a named owner. It is a control problem rather than a technical one, which is exactly why no configuration screen will prompt…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Cloud Financials: From Empty Pod to Go-Live, with a certificate on completion and a fourteen-day refund window.