| Created: | 1/10/2022 12:02:22 PM |
| Modified: | 4/15/2022 10:31:34 AM |
Project: |
|
Advanced: |
|
| Attribute | ||
|
Public Money amount |
||
Details:
|
||
|
Public DateTime date |
||
Details:
|
||
|
Public String description |
||
Details:
|
||
|
Public String direction |
||
Details:
|
||
|
Public String ID |
||
Details:
|
||
|
Public Money remainingAmount |
||
Details:
|
||
|
Public String status |
||
Details:
|
| Element | Source Role | Target Role |
|
«TMF_ABE» Party Payment ABE ABE «TMF_ABEIsComposedByEntity» |
Name: |
Name: |
Details:
|
||
| Element | Source Role | Target Role |
|
«TMF_BusinessEntity» PartyRevShareReconciliationItem Business Entity |
Name: partyRevShareReconciliationItem |
Name: partyPayment |
Details:
|
||
|
«TMF_BusinessEntity» PaymentPlan Business Entity |
Name: _paymentPlan |
Name: _partyPayment |
Details:
|
||
|
«TMF_BusinessEntity» BankAccount Business Entity |
Name: bankAccount |
Name: partyPayment |
Details:
|
||
|
«TMF_BusinessEntity» PartyRole Business Entity |
Name: _partyRole |
Name: partyPayment |
Details:
A PartyPayment represents the transfer of wealth from one Party to another. So it is received from a PartyRole and made to a PartyRole.<br/><br/>The PartyPayment might be either inbound or outbound and always uses a PaymentMethod.<br/><br/>A PartyPayment might specify the BankAccount to which the payment is transferred.<br/><br/>The diagram below shows different types of PaymentMethods identified at the present time, currently allowed for paying due amounts such as CheckPM, DigitalWalletPM, LoyaltyBurnPM...<br/><br/>As all the PaymentMethod might not be yet described as a sub-class of PaymentMethod, a PaymentMethod might be described a PaymentMethodSpecification defining the characteristics.<br/><br/>ThirdPartyCollectionPM is an example of payment method, using which payment can be made through the third party, such as bank transfer, payment tool(like PayPal, Alipay).<br/><br/>A PaymentMethod is owned by a PartyRole.<br/><br/>A PaymentPlan may specify PaymentMethods to use for auto-pay. If several PaymentMethod are specified, a priority is given to each of them. Over time, PartyPayments are collected according to the PaymentPlan.<br/>
|
||
|
«TMF_BusinessEntity» PartyRevShareReconDiscrepancy Business Entity |
Name: partyRevShareReconDiscrepancy |
Name: partyPayment |
Details:
|
||
|
«TMF_BusinessEntity» PartyRevenueShare Business Entity |
Name: partyRevenueShare |
Name: partyPayment |
Details:
|
||
|
«TMF_BusinessEntity» PaymentMethod Business Entity |
Name: _paymentMethod |
Name: _partyPayment |
Details:
|
||
|
«TMF_BusinessEntity» PartyRole Business Entity |
Name: partyRole |
Name: partyPayment2 |
Details:
|
||
|
«TMF_BusinessEntity» PartySettlementPayment Business Entity |
Name: partySettlementPayment |
Name: partyPayment |
Details:
|
||
| Tag | Value |
| IsCoreEntity | False |
Details:
Values: true,false
Default: False |
|
| rsa_guid | _aifwaU4cEeO_XpEXs37Qew |
Details:
|
|
| Property | Value |
| isActive: | 0 |
| isFinalSpecialization: | 0 |
| Object | Type | Connection | Direction | Notes |
| «TMF_BusinessEntity» CustomerPayment | Business Entity | Generalization | From | |
| «TMF_BusinessEntity» BusinessPartnerPayment | Business Entity | Generalization | From |