Skip to content

EntiHub Documentation

Finance Payment Terms & Mandates

Finance / Treasury — Payment Terms & Banking Mandate Catalog

AP, Sales, and Treasury need shared payment terms and mandate types. Changes couple tightly to supplier-critical-change controls.

Why this is needed

Sales promises NET60 while Treasury expects NET30.
Mandate types must be explicit for SEPA/ACH processes.
Pairs with supplier fraud controls.

Proposed entities in EntiHub

Governance settings

Setting	Recommended value	Why
`approvalRequired`	`true`	Term changes need Treasury sign-off.
`historyEnabled`	`true`	History of term changes for disputes.
`allowSameAuthorApproval`	`false`	Maker/checker separation for sensitive changes.
`deletedRetentionDays`	`90` (or higher)	Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: payment_term
displayName: Payment term
domain: Treasury
description: Payment term
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: term_code
uniqueConstraints:
  - name: uq_payment_term_term_code
    columns: [term_code]
columns:
  - name: term_code
    dataType: string
    nullable: false
    maxLength: 32
  - name: name
    dataType: string
    nullable: false
    maxLength: 128
  - name: net_days
    dataType: int
    nullable: false
  - name: status
    dataType: string
    nullable: false
    maxLength: 16

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

term_code	name	net_days	status
NET30	Net 30	30	active
NET60	Net 60	60	active

Benefits for the company

One term catalog for Sales and AP.
Treasury controls sensitive changes.
Cleaner link to supplier change workflows.