Progress Billing & Draw Applications (AIA-style)
Monthly draw applications against a schedule of values, with retention, change orders and G702/G703-style continuation sheets
Progress Billing & Draw Applications (AIA-style) Contractors bill construction projects in monthly draws against a Schedule of Values (SoV), the way AIA G702/G703 forms work. This app models the continuation sheet math directly: scheduled value, previously billed work, this-period work completed, stored materials, retention held, balance to finish. Change orders revise the contract sum and flow straight into the schedule of values. A contractor -> architect -> owner certification workflow keeps every draw auditable, and retention accrued during billing can later be released through dedicated retention-release documents. A work-in-progress reconciliation flags any draw where stored materials are driving billed-to-date ahead of certified work completed, the classic source of over/under-billing disputes.
Key Features
Change Order
Change Order. Tracks Change Order No., Project, Date, Description, Reason / Scope Narrative. One-click submit, approve, reject, reset to reset to draft.
Draw Application (G702)
Draw Application (G702). Tracks Project, Application No., Reference, Period From, Period To. One-click load sov, submit, certify, approve, mark paid.
Progress Billing Project
Progress Billing Project. Tracks Project, Project No., Owner, Architect, Contractor. One-click view sov, view change orders, view draws.
Retention Release
Retention Release. Tracks Reference, Project, Date, Lines, Total Released. One-click approve, mark paid, reset to reset to draft.
Progress Billing & Draw Applications
Progress Billing & Draw Applications (AIA-style) Contractors bill construction projects in monthly draws against a Schedule of Values (SoV), the way AIA G702/G703 forms work.
This app models the continuation
This app models the continuation sheet math directly: scheduled value, previously billed work, this-period work completed, stored materials, retention held, balance to finish.
Change orders revise the contract
Change orders revise the contract sum and flow straight into the schedule of values.
A contractor -> architect ->
A contractor -> architect -> owner certification workflow keeps every draw auditable, and retention accrued during billing can later be released through dedicated retention-release documents.
Use Cases
Screenshots
Change Orders
Draw Applications
Projects
Retention Releases
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Pokutsoft
- Dependencies: base, mail
- Support: support@pokutsoft.com
- Update date: 2026-07-18
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1178 |
| Technical Name |
construction_progress_billing_aia |
| License | OPL-1 |
| Website | https://pokutsoft.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module