AP-SETUP-020 · Master data · Legal entity
Define vendor methods of payment
Control how supplier payments are posted and generated for each approved instrument.
Where
| Menu path | Accounts payable > Payment setup > Methods of payment |
|---|---|
| Menu item | Display:VendPaymMode |
| Form | Not recordedUnverified |
| Tables affected | Not recordedUnverified |
| Data entity | VendorPaymentMethods |
| Scope | Legal entity |
| Country or region | Not recorded |
Value
| Recommended value | Not recordedUnverified |
|---|---|
| Rationale | Not recordedUnverified |
| Decision | Not recorded |
Dependencies and access
| Prerequisites | Not recorded |
|---|---|
| Required by | Not recorded |
| Security duty | Not recordedUnverified |
| Feature flag | Not recordedUnverified |
| Feature state | Not recordedUnverified |
Versions
| Introduced | Not recordedUnverified |
|---|---|
| Behaviour changed | Not recorded |
| Deprecated | Not recorded |
| Verified on version | Not recordedUnverified |
| Verified on date | Not recordedUnverified |
Risk and evidence
| Irreversibility | Hard to reverse — A payment method used in posted or transmitted payments must be changed through the customer's controlled payment design, not by rewriting history.Unverified |
|---|---|
| Common pitfall | Assuming a method's posting account also proves its electronic file format and bank approval are correct. |
| Test case | TC-AP-SETUP-01 · AP baseline defaults flow from setup to invoice and payment |
| Assets | Not recorded |
Verification
Partly verified
| Verified by | Microsoft Learn Accounts payable posting; July 2026 catalog deliverables rows 1451-1452; Fintrial MCP read and browser page walk 2026-09-30 |
|---|---|
| Environment | Fintrial MCP and browser, USMF |
| Note | Fintrial opened Methods of payment - vendors at menu item VendPaymMode through page search. Fintrial metadata identifies company-scoped VendorPaymentMethods with Name and dataAreaId keys; a fresh USMF read succeeded. No row data was copied. Intermediate menu nodes, bank, output format, posting account and effective payment behavior remain unverified. |
| Still to check | Form_name, Tables_affected, Recommended_value, Value_rationale, Security_duty, Feature_flag, Feature_state, Version_introduced, Verified_on_version, Verified_on_date, Irreversibility |
Cite this record
AP-SETUP-020 — Define vendor methods of payment. Beyond ERP Config Atlas, snapshot 2026-10-05, partly verified. https://www.beyonderp.cloud/atlas/step/AP-SETUP-020