Business management feature
Record the money you send your suppliers, bank-statement style — each payment then settles against that supplier's open purchase invoices.
It is the accounts-payable mirror of Customer Payments.
Use the documented operating model as a starting point, then adapt fields, approvals, reports, or connected areas when your process differs.
One connected record
The Supplier Payments feature keeps its source record, status, and downstream references inside BusinessIntents. Teams can work from the same operational context and open the detailed guide whenever they need field-level instructions.
A payment mirrors a line on your bank statement: Name (required) — a short label, e.g. "Payment for PI-0000001". Number — the bank's transaction reference from the payment order this went out on. Date (required) and Valor — the booking date and the value date, as the statement shows them. Amount (required) and Currency.
See the fields and stepsConnected work
Related features and workflows reuse the same business records instead of asking teams to rebuild the context.
A starting point, not a fixed package
BusinessIntents can tailor documents, fields, approval paths, reports, and connected business areas when the ready-made workflow is close but not exact.
Try BusinessIntentsDecision-stage answers
Record the money you send your suppliers, bank-statement style — each payment then settles against that supplier's open purchase invoices. It is the accounts-payable mirror of Customer Payments.
It connects with Customer Payments, Construction, Logistics, Retail, Wholesale, Purchase Invoices.
The detailed module guide documents the exact fields, statuses, actions, and connected records.
BusinessIntents can tailor documents, fields, approval paths, reports, and connected business areas when the ready-made workflow is close but not exact.
Review the real workflow
Use a real record or transaction to compare the documented flow with the way your team works today.
