[
https://issues.apache.org/jira/browse/OFBIZ-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358339#comment-15358339 ]
Swapnil Shah commented on OFBIZ-7682:
-------------------------------------
I feel checkbook number is also one kind of recurring information (like check#) although with lesser frequency. i.e., As soon as all check leafs are consumed then it is definitely bound to lose its existence physically and would no longer be in use. Not too sure but it might be better fit for payment reference.
Apart from this i think all other field mapping makes sense and are in sync with ticket description.
> Define and add new entity for 'Check' as Payment Method
> -------------------------------------------------------
>
> Key: OFBIZ-7682
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7682> Project: OFBiz
> Issue Type: New Feature
> Components: accounting
> Affects Versions: 14.12.01, 15.12.01
> Reporter: Swapnil Shah
> Assignee: Swapnil Shah
>
> Based on the concluded requirement on OFBIZ-6899. Let's define Check as new entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store all relevant details related to Check used as payment method for any party.
> PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
> BANK_NAME
> ROUTING_NUMBER
> ACCOUNT_TYPE
> ACCOUNT_NUMBER
> NAME_ON_ACCOUNT
> COMPANY_NAME_ON_ACCOUNT
> CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
> LAST_UPDATED_STAMP
> LAST_UPDATED_TX_STAMP
> CREATED_STAMP
> CREATED_TX_STAMP
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
