These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Treasury Management
- Data model
The tables behind Treasury Management
Treasury Management ships with 17 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 17
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Organization
Organizations, team members, Counterparties and Remitters establish the legal entity, people and trading parties.
Outbound obligations
Payment requests and payment request lines hold the request and its accounting detail.
Cash
Payments relates movement to payment requests or receivable invoices.
Incoming obligations
Receivable invoices and receivable invoice lines retain the invoice and revenue detail.
Accounting
Fiscal periods, GL accounts, journal entries and journal lines provide period and account context.
Evidence
Review decisions, operation receipts and record attachments preserve decisions, action results and files.
Every table, by feature
- Payment requests7
- Payment execution4
- Receivables5
- Bank reconciliation5
- Accounting6
- Review evidence7
- Shared and settings1
- Payment requests
Outbound payment requests awaiting approval and scheduling, matched to the counterparty and organization that settles them.
Linked to Counterparties, Organizations, Fiscal periods - Payment request lines
Line detail behind each payment request: description, quantity, unit price and the GL account charged.
Linked to Payment requests, GL accounts - Counterparties
Counterparties treasury pays: payee master data with settlement terms, remit-to details and contact information.
Linked to Organizations - Fiscal periods
Accounting calendar with open and closed periods that gate journal posting.
- Organizations
Legal entities and business units whose books this app keeps; every document belongs to one organization.
- Review decisions
Approval trail: who approved, rejected or returned a bill, invoice, payment or journal entry, when and under what conditions.
Linked to Team members, Payment requests, Receivable invoices, Payments - Operation receipts
Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
Linked to Team members
- Payments
Money movement in and out of the business, matched to a bill or invoice and reconciled to the bank.
Linked to Counterparties, Remitters, Payment requests, Receivable invoices - Payment requests
Outbound payment requests awaiting approval and scheduling, matched to the counterparty and organization that settles them.
Linked to Counterparties, Organizations, Fiscal periods - Counterparties
Counterparties treasury pays: payee master data with settlement terms, remit-to details and contact information.
Linked to Organizations - Operation receipts
Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
Linked to Team members
- Receivable invoices
Incoming receivable invoices issued to a remitter, tracked from issue through collection.
Linked to Remitters, Organizations - Receivable invoice lines
Line detail behind each receivable invoice: description, quantity, unit price and revenue category.
Linked to Receivable invoices, GL accounts - Remitters
Remitters who fund incoming cash: the parties that owe treasury, with settlement terms, credit limit and billing details.
Linked to Organizations - Payments
Money movement in and out of the business, matched to a bill or invoice and reconciled to the bank.
Linked to Counterparties, Remitters, Payment requests, Receivable invoices - Operation receipts
Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
Linked to Team members
- Payments
Money movement in and out of the business, matched to a bill or invoice and reconciled to the bank.
Linked to Counterparties, Remitters, Payment requests, Receivable invoices - Operation receipts
Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
Linked to Team members - Record attachments
Parent-agnostic evidence files attached to any business record in this app.
Linked to Team members - Payment requests
Outbound payment requests awaiting approval and scheduling, matched to the counterparty and organization that settles them.
Linked to Counterparties, Organizations, Fiscal periods - Receivable invoices
Incoming receivable invoices issued to a remitter, tracked from issue through collection.
Linked to Remitters, Organizations
- Fiscal periods
Accounting calendar with open and closed periods that gate journal posting.
- GL accounts
Chart of accounts: the coded account structure every bill line, invoice line and journal line posts into.
- Journal entries
General ledger header balancing debits and credits for a period.
Linked to Fiscal periods, Organizations - Journal lines
Debit and credit lines that make up a journal entry.
Linked to Journal entries, GL accounts - Payment request lines
Line detail behind each payment request: description, quantity, unit price and the GL account charged.
Linked to Payment requests, GL accounts - Receivable invoice lines
Line detail behind each receivable invoice: description, quantity, unit price and revenue category.
Linked to Receivable invoices, GL accounts
- Review decisions
Approval trail: who approved, rejected or returned a bill, invoice, payment or journal entry, when and under what conditions.
Linked to Team members, Payment requests, Receivable invoices, Payments - Operation receipts
Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
Linked to Team members - Record attachments
Parent-agnostic evidence files attached to any business record in this app.
Linked to Team members - Team members
Finance staff who prepare, review and approve finance operations, with their role and approval limit.
Linked to Organizations - Payment requests
Outbound payment requests awaiting approval and scheduling, matched to the counterparty and organization that settles them.
Linked to Counterparties, Organizations, Fiscal periods - Payments
Money movement in and out of the business, matched to a bill or invoice and reconciled to the bank.
Linked to Counterparties, Remitters, Payment requests, Receivable invoices - Receivable invoices
Incoming receivable invoices issued to a remitter, tracked from issue through collection.
Linked to Remitters, Organizations
Keys and references
Keep business numbers stable during migration. Match payment requests.Counterparty to Counterparties and payment requests.Organization to Organizations. Match Payments.payment request or Payments.Invoice to the originating record. The record attachments parent table and parent record identifier should lead back to the exact business record.
Migration order
- Load Organizations, team members, Counterparties, Remitters, fiscal periods and GL accounts.
- Load payment requests and receivable invoices with their line detail.
- Load Payments, then the related review and operation evidence.
- Check links, totals, dates and statuses on a small pilot set.
Set up Treasury Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.