Overview
A Contract is planned with detailed activities / tasks, milestones and resources. A clearly and unambiguously structured Contract detail definition ensures successful planning, monitoring, and control. The purpose of this functionality is to ensure that Government acquisitions are executed efficiently, on time, and within budget.
General information surrounding the Managed Contract is necessary to effectively carry out all contract management processes.Contracts often require a number of Attachment files to be included.
Navigation
Contract Management ► Managed Contracts
Managed Contracts screen fields and Tabs
Fields | Description |
Code | Unique alphanumeric Identifier for the Contract, (i) Manujally entered by the user, or (ii) System auto-generated using a Customized Algorithm, depending on the value of the Generate Managed Contract ID parameter (see details in System Parameters > Contract Management in the Admin Module). |
Workflow Status | The default value is 'In Preparation'. This is workflow related and can have these possible values: ‘Approval Requested', 'Approved', 'Closed', 'In Execution' and 'Cancelled'. |
Reference Number | Refers to an internal number of the Contract used by the user. |
Contract Source | User must be able to select 'Original' or 'Amendment' from the Drop Down List.Original' by default |
Issue Date | System Date automatically issued at the beginning of Contract registry. |
Start Date | Date in which the Contract begins to be valid. |
End Date | Last date that the Contract is valid. |
Contract Currency | Currency which will be used for all the Contract amounts and transactions. It should be the Original Currency of the Contract or the Domestic Currency of the client. |
Contract | Reference from/to the Base Contract. |
Contract Type | The Contract Type associated to a Contract. For example: Consulting Services, Goods and Services, Small Works, etc. |
Payment Base | Reference to the Payment Base of the Contract such as Lump Sum, Time Base, etc. |
Vendor | Reference to the contracted Vendor. |
Institution | The Institution Unit that contracts the Vendor. |
Contract Manager | Employee in charge of the communications related to the Contract. This Employee must belong to the Institution. |
Inspection Manager | Employee in charge of performing Physical Inspections. This Employee must belong to the Institution. |
Document | Reference to the Procurement Document to which this Contract is associated. |
Original Currency | Original Currency of the Contract. Default value is the Domestic Currency of the client. |
Institution Signing Date | Date when the Institution signs the Contract. |
Vendor Signing Date | Date when the Vendor signs the Contract. |
Total Amount | Total amount of the Contract. |
Taxes Amount | Total amount of Contract Taxes. |
Other Charges Amount | Total amount related with Other Charges of the Contract. |
Net Total Amount | This attribute is calculated automatically by the System with the following formula: Contract Total Amount – Taxes Amount – Other Charges Amount. |
Original Total Amount | Total amount of the Contract in its original currency. |
Physical Current Progress | Current Physical Progress of the Contract which is updated depending on Line Items Physical Progresses. |
Payment Current Progress | Current Payment Progress of the Contract which is updated depending on Line Items Payment Progresses. |
Language | Language Used. |
Abbreviation | Provide the short form of the Contract. |
Description | Short Description of the Contract. |
Reason For Cancelling | The user must explain the reasons behind the cancelling of a Contract. It is mandatory when the contract reaches the Cancelled status. |
Reason For EarlyClosure | The user must explain th reasons behind an early closure of the Contract. |
Initial Execution Fiscal Year | Filter criteria to filter the report by Initial Execution Fiscal Year. |
Overview
Since Managed Contracts can cover multiple years, Contract Planning must be done through Line Item Drops. Drops allow planning Contract deliverables in different fiscal years by registering drops with delivery dates in different fiscal years.
Each Drop can be associated with one or more Goods/Services Receive Notes (GSRN) which is registered in the Assets and Inventory System. Also, each Drop can have associated one or more Inspections. With these GSRN and Inspections, Contract Management System can validate Drops Receptions, Acceptances, and Payments.
Drops have a status which reflects the different stages of the Drop flow. Setting Drops as Received status depends on Drop Physical Current Progress must be equal to 100%.
Drop status of Acceptance is a requirement to authorize Contract Payments. However, the complete behavior of Drop Change Status is defined in Drop Workflow Configuration.
When a Drop (or Work Item) is finished, the public employee should officially receive that Drop registering this action in the system. Only is possible to receive drops for contracts with status equal to In Execution.
Navigation
Contract Management ► Contract Line Item Drops
Line Item screen fields and Tabs
Field | Description |
Managed Contract | Managed Contract related to the Line Item Drop. |
Line Item | Line Item associated with the Managed Contract, the list of Line Items to select from will be generated based on the Managed Contract. |
Drop ID | Unique automatically generated identifier for the Drop |
Delivery Date | Delivery Date of the Line Item Drop, last day for receiving the goods, services or works |
Status | Status of the Status Line Item Drop, may be: Planned, Ready for Execution, In Execution, Received, Approval for Acceptance Requested, Accepted, or Cancelled |
Fiscal Year | Fiscal Year of the Line Item Drop |
Amount | Monetary Amount of the Line Item Drop |
Prorated Cost | Prorated Cost of the Line Item Amount. Automatically calculated with the following formula: Drop Amount/Line Item Amount. |
Quantity | Quantity of items for the drop |
Current Physical Progress | Percentage representing the current physical progress/reception of the Drop. Progression ranges from 0% to 100%. |
Current Payment Progress | Current progress of the payment for the Line Item Drop. |
Language | Language used to register information |
Abbreviation | Short name given for the Line Item Drop |
Description | Short Description of the Line Item Drop. |
Comments | Any comments or related information about the Line Item Drop |
Inspection Tab | Collection of one or many Physical Inspections for the drop. Inspections include advances or percentages of progress of each Drop (or Work Item). |
Receive Return Note Detail Tab | Collection of one or more Receive Note Details related with this Drop. |
Overview
Contracts may be created with stipulated guarantees. Details surrounding a Guarantee will be entered and attached to a Contract. Guarantee Types include: Advance Payment Bond and Performance Bond.
Guarantee screen fields and Tabs
Fieds | Description |
Reference Number | Reference Number of the Guarantee. |
Guarantee Type | Reference to the Guarantee Type such as Bid Bond, Advance Payment Bond, Performance Bond, etc. |
Status | Possible values: Active, In Use, or Expired. The default value is Active. This attribute is manually entered by the user, but it can be automatically updated by the System. |
End Date | Date when the Guarantee Period ends. |
Maximum Amount | Represents the Maximum Guaranteed Amount. This attribute must be entered in the currency of the Contract in the Managed Contract screen. The System must show the currency symbol in the screen. |
Language | Language used. |
Abbreviation | Short form of the Guarantee. |
Description | Brief description of the Guarantee. |
Comments | Brief comments related to the Guarantee. |
Overview
System allows to attach files to support the guarantee process.
Attachments screen Fields
Field | Description |
ID | Consecutive number auto generated by the system. It will be unique within the system. |
Language | Country specific language for the title and description. |
Title | Title of the Attachments. |
Description | Description of the attachments. |
Attachment | System allow to selete and upload supporting file. File type can be: pdf, doc, xls, jpg, etc. |
Date Time | Date and Time of the last operation performed on the attachment document. Visible for the user. Automatically assigned by the system. |
User | Last user who uploaded or updated the document. Visible for the user. Automatically assigned by the system. |
Language | Mandatory field, language of the document. The system will suggest the default language; however the user can change such language. |
Overview
This entity contains the collection of Coding Blocks used in Guarantee entity used for Contracts. It is a collection because Coding Blocks are registered per Fiscal Year and Contracts can be multi-year.
Guarantee Coding Block screen fields
Field | Description |
Fiscal Year | Fiscal Year which the Coding Block is active |
Coding Block | Ledger Coding Block. This Coding Block it is used in FA to register the Guarantee. Search function to the COA Group with attribute ‘Budget Execution’ equal to ‘True’. |
Overview
Managed Contracts supports attaching documents to a Contract. The Final Assembled Attachment is a collection of attached files to a particular Contract. When a Final Assembled Attachment is under Original status, the user can add, change, or remove files from the collection of attachments. So long as the Contract status has not been set to In Execution and the Final Assembled Attachment status is set to Original, modifications can be made to the collection of Attachments.
After the Contract has been set to In Execution, the Final Assembled Attachment can only be changed through Amendments. When a file Attachment has been removed from the collection of Final Assembled Attachments, the file will have Removed status. When a new file is attached, it will hold New status. When a file Attachment is updated, the old version will remain with Replaced status and the new version will have Replacement status.
Final Assembled Attachment screen fields
Field | Description |
ID | Consecutive number auto generated by the system. It will be unique within the system. |
Order | Defines the order of how the attached file should be assembled or printed. |
Status | This field can have the following values: Original, New, Replaced, Replacement, and Removed. The default value will be Original. |
Language | Language used. |
Title | Name of the Attachment. |
Description | Description of the Attachment. |
Date Time | Defines the Date and Time of the Attachment. |
User | Represents the user who uploaded the Attachment |
Attachment language | Language of the document. |
Overview
Each Contract can have a collection of one or many Sections related, including the order of such Sections. Such information will be inherited from the Contract Type selected, however the user can change the order, discard some Sections and add more Sections from the catalogue.
Field | Description |
Order | The order number will be inherited from the Contract Type; however the user can change it. The System will ensure that no two sections within the same Contract have the same number. |
Inherited | Defines whether the Contract Section was inherited or not. |
Completed | This value is false (unchecked) by default. Every time, the user changes this value to true (checked). The System will record the time stamp in the field Completion Date. If the user changes this value to false (unchecked), in order to make changes, the System will assign blank to the field Completion Date. |
Document Section | Reference to the Section Catalogue. |
Completion Date | Automatically populated by the System with the date and time when the Completed field changes its value to true (checked).This field is visible to the user. The default value will be blank. |
The Contract can have zero or more Vendor Validation Rules which can be used as requirements of the contract. Also, additional requirements can be defined as Contract Sections.
Vendor Validation Rules may already exist as part of the Procurement Document for FreeBalance customers using (PEM) Public Expenditures Management, or (PEGP) Public Electronic Government Procurement.
Managed Contract Requirement screen fields
Fields | Description |
Vendor Rule | The validation rules or requirements that Vendors must comply to sign a Contract. It represents the criteria set up to manage the Vendors of the contracts. |
Overview
One or more Funding Sources can be associated with a Contract, for instance: Donators, Financial Organizations, Government, etc.
Contract Founding Source screen fields
Fields | Description |
Funding Source | Reference to the Funding Source base entity such as Federal Government, World Bank, International Monetary Fund, etc. |
Amount | Amount given by the Funding Source organization for the Contract. This attribute must be entered in the currency of the Contract. The System will show the Currency symbol in the screen. The sum of amounts of all the Funding Sources must be less or equal to the Total Amount in the referenced Contract. The attribute is not mandatory because some Funding Sources could provide materials, products, etc. not necessarily money. |
Language | Language used. |
Funding Detail | Provides details of the Funding. For example, details of the materials, products, or any other Funding Source. This attribute is mandatory if the Amount field is empty. |
Overview
Creating a new Managed Contract may be based on a previous Base Contract existing in the system. Most of the Base Contracts are associated with assets contracts; for instance, contracts surrounding maintenance or leasing of an asset. Within the system, only Base Contracts can be associated to Asset Items.
This process will start when creating a new Managed Contract. If a valid 'Document' is selected when creating a new Managed Contract, the system automatically will copy the information from the existing Base Contract to the current Managed Contract. Changes to any of the copied values may be made.
An existing Base Contract only can be referred once. When the referred Base Contract, the system must validate this condition.
To CREATE a Managed Contract based on a Base Contract, follow the steps below:
Navigation
By default, you will be in Search Mode.
1. Click on the New icon (you will then be in Insert Mode).
2. Find the Base Contract you want to base a Managed Contract on.
Click on the Look up Icon located next to the Document Field. .
3. Select the Base Contract you want to base a Managed Contract on.
Note: An existing Base Contract can only generate one Managed Contract.
Note: The system will automatically copy the information from the existing Base Contract to the current Managed Contract.
4. If required, Enter Managed Contract Fields with an asterisk , which are mandatory fields that must be filled in.
5. Make necessary Modification to the new Managed Contract, refer to Modify a Managed Contract for more information.
Note: Modifications can be made on any value copied from a Base Contract.
6. Click on the Save icon at the bottom of the Managed Contracts page to save your new Managed Contract information. A window will appear to confirm.
Overview
Creating a new Base Contract may be based on a previous Managed Contract existing in the system. Most of the Base Contracts are associated with assets contracts; for instance, contracts surrounding maintenance or leasing of an asset. Within the system, only Base Contracts can be associated to Assets.
This process will start when creating a new Managed Contract by clicking the 'Create Base Contract' icon. This button only will appear after the Managed Contract has been created and if the Managed Contract is not associated with an existing Base Contract. When a Base Contract is created, the system will save the new Base Contract with the information saved in the existing Managed Contract.
An existing Managed Contract can generate only one Base Contract. The button 'Generate Base Contract' only will be enabled if the existing Managed Contract hasn't generated a Base Contract until that moment.
To CREATE a Base Contract based on a Managed Contract, follow the steps below:
Navigation
By default, you will be in Search Mode.
1. Find the Managed Contract you want to base a Base Contract on.
Enter the information to be used as retrieval criteria in the appropriate field(s). If you prefer to see all Managed Contracts, leave all fields blank.
Click Find .
2. Select the Managed Contract you want to base a Base Contract on.
Note: An existing Managed Contract can only generate one Base Contract.
3. Select the Create a Base Contract Button at the bottom of the Managed Contract Screen.
Note: The Create a Base Contract Button will appear only after the Managed Contract has been created and if the Managed Contract is not associated with an existing Base Contract.
4. The system will display the following confirmation message.
5. Click Okay to Confirm the Creation of a Base Contract based on this Managed Contract or click Cancel to cancel the creation of a Base Contract based on this Managed Contract.
Note: If the user confirmed the action, attributes will be copied from the Managed Contract to the Base Contract.
Note: If the process is successful the system will assign a Contract ID for a Base Contract, which will appear on in the Contract field of the Managed Contract screen.
6. Click the Update Icon at the bottom of the screen to save your new Base Contract.
7. The following message will be displayed to the user indicating the process was successful, select Okay.
Navigation (By default, you will be in Search Mode.) Overview The Managed Contracts screen contains the general information for a Managed Contract. Managed Contracts have a specific workflow that enables a managed contract to move from the In Preparation stage to the Closed stage. Illustrated below is the Managed Contracts Workflow: The following workflow transitions are manual. Listed below is the list of Manual Workflow Transitions illustrated above. This table indicates the transition name, previous status required, and the next status of a managed contract.
|
Navigation (By default, you will be in Search Mode.) Overview In order to approve a Contract, all mandatory information in Managed Contract entity and Line Item entity is required. This means, all the information for an Approved Contract is located in these both entities. Before approving, users can add additionally Contract information such as Drops, Planned Inspections, Planned Payments, etc. but they are optional in that moment. Also, this additional information can be added after Contract approving. A Contract in Approval Requested status is available to be set to Approved status. To REQUEST APPROVAL for a Managed Contract, follow the steps below:
Note: In order to Request Approval for a Managed Contract, the Managed Contract status must be Created. Note: Once approval is requested, changes to the Managed Contract are no longer permitted. Note: After approval is requested the next step for the Managed Contract maybe: Approved or Rejected by Supervisor, or Cancelled (refer to Workflow Transitions for Managed Contracts for more information).
To verify that the Managed Contract status is set to Approval Requested
|
Navigation (By default, you will be in Search Mode.) Overview In order to Approve a Contract, all mandatory information in Managed Contract entity and Line Item entity is required. All the information for an approved Contract is located in both the Managed Contract and Line Item. Before approving, users can add additionally Contract information such as Drops, Planned Inspections and Planned Payments. Additional information can be added after Contract approving. An Approved Contract is available to be set to In Execution status, where its conditions will take effect. To APPROVE an Approval Request for a Managed Contract, follow the steps below: To OPEN a Managed Contract you wish to Approve, follow the steps below: Note: By default, users defined to approve Managed Contracts will receive an Internal Message. The System automatically generates this internal message because another user has Requested Approval to a Managed Contract:
Or, you can navigate to the module and search for the Managed Contract you wish to Approve. To do this Go to Step 3 below.
Note: In order to Approve a Managed Contract, its status must be Approval Requested. Note: Once Managed Contract request for approval is Approved, no further modifications can be made to a Contract (refer to Workflow Transitions for Managed Contracts for more information).
To verify that the Managed Contract status is set to Approved
|
Navigation (By default, you will be in Search Mode.) Overview The Managed Contracts screen contains the general information for a Managed Contract. A contract can be set to In Execution from the Approved status by a user with the proper authority. Also, a Contract may not reach the In Execution status unless all Contract Planning information consisting of: Line Items, Drops, Planned Inspections, and Planned Payments are entered. Refer to Contract Planning Validation for more information. To Set a Contract as IN EXECUTION, follow the steps below: To OPEN a Contract you wish to set as In Execution, follow the steps below: Note: By default, users defined to oversee setting Contracts In Execution will receive an Internal Message:
Or, you can navigate to the module and search for the Contract you wish to set to In Execution. To do this Go to Step 3 below.
Note: In order to Set a contract as In Execution, Contract status must be Approved. Note: Once Managed Contract is In Execution, the next Status for the Managed Contract may be Closed or Cancelled refer to Workflow Transitions for Managed Contracts for more information.
|
Navigation (By default, you will be in Search Mode.) Overview Contract Closure process changes the Contract Status to Closed. Refer to Contract Closure Conditions for more Information. To CLOSE a Contract, follow the steps below: 1. OPEN the Contract you wish to Close. Note: By default, users defined to close Contracts will receive an Internal Message:
Or, you can navigate to the module and search for the Managed Contract you wish to Close. To do this, go to Step 3 below.
Note: In order to Close a Contract, Contract status must be In Execution. Note: For a Contract, Closed is the last status (refer to Workflow Transitions for Managed Contracts for more information).
|
Contract Closure process changes the Contract Status to Closed (refer to Workflow Transitions for Managed Contracts for more information). In order to Change Contract Status to Closed, Contract must accomplish with the following conditions:
For Early Termination of a Contract, the Contract must accomplish the following conditions:
|
Navigation (By default, you will be in Search Mode.) A Contract can be Cancelled from the In Preparation, Approval Requested, or In Execution status. When a user cancels a Contract a Reason(s) for Cancelling must be explained. The conditions of a Cancelled Contract no longer take effect. To CANCEL a Contract, follow the steps below:
Note: By default, users defined to close Contracts will receive an Internal Message:
Or, you can navigate to the module and search for the Managed Contract you wish to Cancel. To do this, go to Step 3 below.
Note: In order to Cancel a Contract, Contract status may be: In Preparation, Approval Requested, and In Execution (refer to Workflow Transitions for Managed Contracts for more information). Note: Once Cancelled the System will allow the creation of a new contract with the same Procurement Document and Vendor.
|
Navigation (By default, you will be in Search Mode.) Rejecting a Contract will prevent it from being included in the System as Approved. The conditions of a Rejected Contract do not take effect. To REJECT an Approval Request for a Managed Contract, follow the steps below:
Note: By default, users with authority to Reject a Contract will receive an Internal Message:
Or, you can navigate to the module and search for the Managed Contract you wish to Reject. To do this, go to Step 3 below.
Note: In order to Reject a Managed Contract, Managed Contract status must be Approval Requested. Note: Once Contract has been Rejected, the Contract status will change to In Preparation (refer to Workflow Transitions for Managed Contracts for more information).
|
Navigation (By default, you will be in Search Mode.) To PLAN a Managed Contract, follow the steps below:
Note: Once Line Items, Line Item Drops, and Inspections information has been entered the Managed Contract screen will display this information in View Mode.
|