Advanced orders Payment rule relationship to trading agreements (Business Edition)

Event-driven payment rules can coexist with trading agreements and associated terms and conditions.

A trading agreement can be a contract, a business account, an RFQ, or an auction. Trading agreements can have terms and conditions associated with them. A trading agreement can specify which payment methods should be used for a store through terms and conditions and related business policies. Payment terms and conditions are typically payment methods with or without payment instruction information. Payment terms and conditions can also specify (through related business policies) account information to be used on a user or store basis, and also any amount restrictions for a payment method.

Purchase order and line of credit are related terms and conditions, but they do not have the same model as the other payment terms and conditions. A line of credit is modeled as a policy by itself.

Payment methods are associated with stores through entries in the POLICY database table. If an entry is made in this table with a policy type of "Payment," the entry is considered to be a payment method. For a list of payment policies associated with event-driven payments, and a description of the policy property that uniquely identifies the policy as an event-driven payments policy for advanced orders, see Payment business policies for event-driven payments.

Contracts cannot specify which payment actions need to be taken for a particular business event, such as order capture or release to fulfillment. This is the responsibility of the event-driven payments subcomponent.

Once event-driven payment rules are invoked, the event-driven payments subcomponent does not rely on any trading agreement, terms and conditions, or business policy to calculate and execute payment actions.

Feedback