1. Treasury Management
  2. Implementation
Reference

How a Treasury Management rollout works

Set up a small treasury cycle before broader use.

  1. Prepare records

    Agree organizations, fiscal periods, GL accounts, counterparties, remitters and team ownership.

  2. Load a pilot

    Enter open payment requests and receivable invoices with their line detail and source documents.

  3. Rehearse decisions

    Run a pending-request approval, a scheduled-payment release and a draft-invoice send. Inspect each result.

  4. Check cash

    Follow a released payment to its bank reference and compare an inbound receipt with its invoice balance.

  5. Expand carefully

    Review the pilot evidence with the responsible roles before adding more transaction volume.

What the customer provides

Provide legal-entity details, account codes, an accounting calendar, counterparty and remitter identifiers, open obligations, invoice documents and bank evidence. Name the people who prepare, approve, release and review. Decide which bank and delivery systems supply external outcomes.

Changing it afterwards

Rehearse status and permission changes on a real case before changing the team process. Retain the original decision and operation result when an exception is corrected. Recheck reports and saved views after changing source fields or imported identifiers.

Set up Treasury Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started