Vendor directory
Maintain supported vendor information in one canonical record.
Vendors and payments
Keep supported vendor and payment activity beside the expense.
Maintain canonical vendor records, attach payment evidence and record supported partial or final payment activity with explicit confirmation.
The payment handoff
A payment state is unclear when the expense and evidence are elsewhere.
Small teams need to know the vendor, related expense, amount already recorded and what remains due without pretending the product executes banking or accounting.
A clear path from capture to responsible action.
Each step keeps the record, its context and the next responsibility visible.
- 01
Maintain the vendor
Use the existing canonical vendor record.
- 02
Open the expense
Keep the related site, amount, evidence and approval context visible.
- 03
Record payment activity
Attach supported evidence and record a partial or final amount.
- 04
Confirm state
Prevent duplicate, overpayment and invalid-state operations.
What vendor payments covers.
Focused capabilities for the complete workflow, described within their supported operating boundaries.
Payments due
See supported due-state information in Finance Inbox.
Partial and final records
Record supported payment activity with validation.
Payment evidence
Retain supported source evidence beside the record.
Clear payment state
Vendors and payments due remain visible in Finance Inbox.
Current product evidence shows the compact Finance Inbox sections and the decision centre used by supported release actions.
- Canonical vendor records
- Partial and final payment state
- Duplicate and overpayment protection
A useful record has a responsible next person.
The feature supports the handoff without blurring who records, reviews or receives the information.
Accountant
Maintain supported vendor, evidence and payment records.
Owner
Confirm permitted money-changing actions with context.
Project manager
See the supported project expense and payment state when permitted.
Payment boundary
NIYAM records supported activity; it does not execute a bank transfer.
Payment release and mark-paid actions require explicit authorised confirmation. Tax accounting and bank settlement remain outside the product claim.
- Explicit confirmation
- No bank-execution claim
- Evidence and history retained
Questions about vendor payments.
Straight answers about scope, review and responsibility.
Can NIYAM record partial payments?
Supported partial and final payment activity can be recorded with the current validations and evidence.
Does NIYAM prevent overpayment?
The current contract validates duplicate and overpayment attempts and protects invalid state transitions.
Does NIYAM send money to the vendor?
No. It records supported operational payment state; it is not represented as bank execution.