Purchase orders #897
Labels
Extensions - Drafted
Relating to a drafted extension
Focus - Extensions
Relating to new or proposed extensions, or the governance and maintenance of extensions
Splitting from #396 and copying questions in issue description:
Yes. They can provide important details on the fulfillment/implementation of the contract.
contract.implementation.transactions
or do they represent a contract in themselves?Semantically, purchase orders are not transactions.
@georgneu wrote:
@chrisalexsmith wrote:
Indeed, the acceptance of a purchase order forms a legal contract. However, per #896, they do not belong in the
contracts
array. The proposal is instead to author a purchase orders extension, e.g.contracts.implementation.purchaseOrders
, and to include guidance on how to model the contract under which the purchase orders are issued, per the discussion in #896.@georgneu wrote:
@chrisalexsmith had indicated the integration of both types of data in some systems. However, as is often the case, this is not how e-GP systems are universally implemented.
The text was updated successfully, but these errors were encountered: