|
|
This data entry is used to enter collections from clients for construction services rendered. The billing to be collected must be entered first in the Billing to Client per Contract so that it can be marked as paid here.
Step-by-step instructions:
1. Open Cenral Menu. Your Central Menu maybe different from the screenshot below as each user can have different menu and access rights.
2. Select Systems ->Construction Contract Management
3. Double-click Transactions -> Collection per Project Contract. You will be redirected to Collection tab window.
4.Select Book where you want to encode the collection. This data grid is non-editable. If you want to update or add new cash receip book, open the Books Of Accounts Setup-Collection and make the necessary update and refresh the app after updating the master file.
5. Enter Collection Header data. Fill up the columns properly, read the data definition below for details.
6. Enter Collection Details. Click the dropdown arrow to view unpaid billings from the customer (EntityCode) in #5 above. Fill up the columns properly, read the data definition below for details.
7. TransactionID must be filled up for the genration of journal entries.
8. Amount column represents the amount collected.
9. Click Save to persist changes made to the database.
Data Definition for Collection Header
Database Table Name: gl_CollectionHeader
Primary Keys: CoID, Doctype, DocNo
|
Column Name
|
Sample Value
|
Description
|
|
CoID
|
T10
|
Hidden Column. The Company ID that the user is currently log-in
|
|
DocType
|
OR
|
Hidden Column. The value is taken parent table Cash/Receipt Book
|
|
DocNo
|
00010
|
The OR number
|
|
TransactionDate
|
|
The date of the DocNo or OR
|
|
EntityCode
|
|
Customer code
|
|
EntityName
|
|
Customer name
|
|
ContractNo
|
|
Optional only. The contract where the collection shall be applied. The system always follows the Collection Details info.
|
|
Particular
|
|
Payment particulars
|
|
Amount
|
|
Formula field. The, total amount collected based on Collection Details
|
|
*PaymentTypeID
|
|
Select from the dropdown list:
1. Bank Transfer
2. Bayad Center
3. BitCoin
4. Cash
5. Check
6. Credit Card
7. PayPal
|
|
*Bank, CheckNo, CheckDate, BankAccountNo, BankDate
|
|
Drawee bank and check data
|
|
*The system will use the Collection Header data if the Collection Details for payment type, drawee bank, check data are left blank.
|
|
Attachment
|
|
Optional only. You may scan docs and attach the same.
|
|
Remarks
|
|
Optional only.
|
|
VatableDP, WTaxDP, VatableRB, WTaxRB
|
|
Their value is used in computing the Prepaid VAT, Deferred VAT and WT. See Client Billing Types and Proforma Journal Entries for details.
|
|
Status
|
A
|
A=Active; I=InActive. You can mark inactive vendor category to remove them from the lookup table.
|
|
Createdby, DateCreated, Modifiedby, DateModified
|
|
These columns are called audit trails. Their values are auto-generated. One who created or modified the app. It is assumed that the current user is the one who created or modified the record.
|
:
Data Definition for Collection Details
Database Table Name: gl_CollectionDetail
Primary Keys: CoID, Doctype, DocNo, SeqNo
|
Column Name
|
Sample Value
|
Description
|
|
CoID
|
T10
|
Hidden and part of child key column. The Company ID that the user is currently log-in
|
|
DocType
|
OR
|
Hidden and part of child key column. The value is taken parent table Cash/Receipt Book
|
|
DocNo
|
00010
|
Hidden and part of child key column. The OR number
|
|
SeqNo
|
1
|
Hidden and part of child key column. Sequential number for details of collection.
|
|
DocGuidLink
|
|
Select from the lookup table the billing that you want to apply the collection
|
|
RefNo/InvNo
|
|
Optional only. You can use this as a reference number like the InvNo
|
|
SOANo
|
|
Optional only. Statement of Account reference number, if any.
|
|
GroupGuidLink / ContractNo
|
|
Select from the lookup table the ContractNo where you want to apply the details of collection
|
|
TransactionType
|
|
Hidden and obsolete already
|
|
DP
|
|
Check if the collection is a downpayment
|
|
Particular
|
|
Enter descriptive note about the collection. Ex: Collection of 20% progress billing
|
|
TransactionID
|
226
|
The transaction id to be used in creating the journal entry
|
|
TransactionDesc
|
Collection of PB
|
Transaction description of the TransactionID
|
|
VATATC
|
VB010
|
VAT ATC. The value will be taken based on the TransactionID
|
|
VATRate
|
12%
|
Rate in computing VAT
|
|
ATC
|
WC160
|
Alpha Tax Code to be used. The value will be taken based on the TransactionID
|
|
ATCRate
|
2%
|
ATC Rate.
|
|
Amount
|
|
The total amount collected.
|
|
VATAmount
|
|
Automatically computed based on the billing type setup
|
|
WTaxAmount
|
|
Automatically computed based on the billing type setup
|
|
FinalVAT
|
|
For government project, automatically computed based on the billing type setup
|
|
SC_PWD_Discount
|
|
Senior Citizen Discount, if any
|
|
NetAmount
|
|
Formula field column. The net amount to be collected.
|
|
*PaymentTypeID
|
|
Select from the dropdown list:
1. Bank Transfer
2. Bayad Center
3. BitCoin
4. Cash
5. Check
6. Credit Card
7. PayPal
|
|
*Bank, CheckNo, CheckDate, BankAccountNo, BankDate
|
|
Drawee bank and check data
|
|
*The system will use the Collection Header data if the Collection Details for payment type, drawee bank, check data are left blank.
|
|
VatSale
|
|
Vatable sales.
|
|
ExemptSale
|
|
Exempt sales, if any
|
|
ZeroRatedSale
|
|
Zero rated sales, if any
|
|
IsSaleToGov
|
|
Checked for government project
|
|
AccountCode, Account Title
|
|
Depreciated as the system is now using the TransactionID in generating journal entries.
|
|
Attachment
|
|
Optional only. You may scan docs and attach the same.
|
|
Status
|
A
|
A=Active; I=InActive. You can mark inactive vendor category to remove them from the lookup table.
|
|
Createdby, DateCreated, Modifiedby, DateModified
|
|
These columns are called audit trails. Their values are auto-generated. One who created or modified the app. It is assumed that the current user is the one who created or modified the record.
|
|
|
