MSAMM
Back to course

Implementing Cloud Financials: From Empty Pod to Go-Live · Module 6 · Banks, Branches and Cash Management

Account use and business unit access

Lesson 59 of 153 · 9 min

Assign the account uses — payables, receivables, payroll — then assign business unit access per use: the wholesale business unit gets payables access, the shared services business unit gets receivables access. Then show the consequence by opening a payment setup screen and looking at which accounts appear, and show what a missing assignment looks like from the user's side. This is the top cause of "my bank account does not appear." Not a permissions issue and not a setup issue — an account use assignment issue, which is a different place to look entirely. Account uses can be added later without pain, so assign only what is needed now. And this ties straight back to the business unit design from the previous module. If that design was wrong, this is where it starts to hurt.

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 6 · Banks, Branches and Cash Management

  1. 1The cash management model
  2. 2Banks, branches, accounts
  3. 3Account use and business unit access
  4. 4Bank statement formats and transaction codes
  5. 5Loading a bank statement
  6. 6Reconciliation rules and tolerances
  7. 7Cash position and external transactions
  8. 8What breaks
  9. 9Lab: configure, load, reconcile