Backlog
28Under consideration
Easier Purchase Order Summary Download from Documents Tab
Customers want an easier way to download a summary of purchase orders for a specific date range directly from the Documents tab, as the current export options are not functional and require a less intuitive workaround. We are working on adding a direct "Download Summary" option to the Documents tab for filtered purchase orders, similar to the existing functionality for timesheets. This will streamline the process and allow users to export data in CSV/Excel format.
Variations pull through line by line into Payment Application
Rather than pulling the entire variation as one line item into AfP’s, variations should pull into payment applications as the sections in the bill of quantities do.
Fix empty email bodies showing on invoices synced to Xero
Some invoices synced to Xero show an empty email body instead of the attachment. Update the attachment order so the PDF/attachment takes priority.
Inherit supplier when creating a document from another document
When creating a document from another document, automatically inherit the supplier and link back to the source document.
Show % of PO remaining on hover
Show the percentage of a purchase order left when hovering over the invoiced amount.
Add manual reverse charge notes to invoices
Allow a manual note to be added to invoices for reverse charge VAT.
Exclude materials on site from the summary view
Exclude 'materials on site' entries from the summary view but keep them included in payment applications.
Variations - chat to CorePIlot
Why Variations (change orders) significantly impact project budgets and timelines. Users need to chat with CorePilot about variation status, approvals, financial impacts, and relationships to payment applications. Questions like "What's the total value of approved variations?" or "Show unapproved variations affecting margin" require variation context. What Index all variation-related data and enable conversational queries about: Variation orders (VO numbers, descriptions, values) Approval status and workflows (internal, client approvals) Financial impact (added/removed amounts, margin effects) Relationships to payment applications and certifications Line item details (BoQ items affected, quantities, rates) How Data indexing (coreloops-ai) Vector DB seeding: Extract variation data from main DB Structure context documents: Variation header: VO number, description, supplier, total value Approval status: internal/client approval states, dates, approvers Line items: BoQ references, quantities, rates, subtotals Payment links: which payment applications include this VO Financial impact: effect on budget, margin, forecast Generate embeddings for semantic search Update on variation creation/modification Query capabilities: Filter by: status (approved/pending/rejected), value ranges, dates Aggregate: total variation value, approved vs pending Join: variations → payment applications, variations → suppliers Calculate: impact on budget utilisation, margin erosion Chat prompts Sample queries to support: "Show all pending variations awaiting client approval" "What's the total value of variations this month?" "List variations for [supplier name]" "Which variations are in payment application #5?" "Show proceed-at-risk variations" "What's the impact of approved variations on our margin?" Dependencies COR-1267: Parent chat interface COR-1398: Tenant data guardrails Variation data model and approval workflows Payment application linkage Acceptance Criteria [ ] All variation orders indexed with full details [ ] Approval status and workflow state available in chat [ ] Users can query variations by status, supplier, value, date [ ] Chat calculates total variation impact on budget and margin [ ] Variation-to-payment-application relationships surfaced [ ] Line item details accessible through chat [ ] Proceed-at-risk variations flagged in responses [ ] Queries scoped to user's tenant and project permissions [ ] Context updates when variations created/approved/modified
Integrate Coreloops with Sage 200
Why Implement integration between Coreloops and Sage 200 for seamless accounting synchronisation via Membrane and Zynk. Export approved documents from Coreloops into Sage 200. What Implement one-way data export from Coreloops to Sage 200 for invoices, bills, and related financial documents. How See child issues for detailed implementation tasks. Integration approach: Use Membrane as the integration platform Leverage Zynk connectors for Sage 200 connectivity Export approved documents from Coreloops to Sage 200 Key features: CIS mapping to Sage 200 Export invoices and bills to Sage 200 Tracking categories/cost centres mapping Automatic sync via webhooks Attachment handling Dependencies Membrane configuration with Zynk for Sage 200 Sage 200 API access and credentials Zynk documentation: https://docs.zynk.com/workflow/documentation/sage-200/index.html Acceptance Criteria All child issues completed Documents export successfully from Coreloops to Sage 200 CIS settings sync correctly Error handling and logging implemented Users can view sync status from Coreloops
Payment Application - chat to CorePIlot
Why Payment applications (valuations) are critical monthly snapshots of project financial status. Users need to chat about certification gaps, retention, historical trends, and supplier claims. Questions like "What's the gap between applied and certified this period?" or "Show payment application history for cost code 02" require detailed valuation context. What Index payment application data to enable queries about: Valuation summaries (numbers, dates, total values) Line item details (BoQ items, claimed vs certified amounts) Retention calculations and release status Variations included in each application Period-over-period trends Supplier-specific applications How Data indexing (coreloops-ai) Vector DB seeding: Extract payment application data from DB Structure context documents: Application header: valuation number, date, supplier, total applied/certified Line items: BoQ references, quantities, rates, applied %, certified % Retention: amount held, cumulative retention, release dates Variations: VOs included, amounts Summary metrics: total applied, certified, gap, retention Historical comparison: vs previous application, cumulative totals Generate embeddings for search Update on application submission/certification Query capabilities: Filter by: application number, supplier, date, status Aggregate: total applied, certified, gaps, retention held Trend: period-over-period changes, cumulative progression Drill-down: specific cost codes, BoQ items within applications Chat prompts Sample queries to support: "Show the latest payment application status" "What's the certification gap in valuation #8?" "List all payment applications from [supplier]" "Show retention held across all applications" "Compare this month's application to last month" "Which line items were reduced in certification?" "What's the total uncertified work in progress?" Dependencies COR-1267: Parent chat interface COR-1398: Tenant data guardrails Payment application data model Variation linkage Retention calculation logic Acceptance Criteria [ ] All payment applications indexed with line item detail [ ] Users can query applications by number, supplier, date [ ] Chat calculates certification gaps (applied vs certified) [ ] Retention amounts surfaced in responses [ ] Variations included in applications shown [ ] Period-over-period comparisons available [ ] Drill-down to specific cost codes and BoQ items [ ] Uncertified WIP calculated correctly [ ] Historical application data accessible [ ] Queries scoped to tenant and project permissions [ ] Context updates on new applications and certifications
Next up
2Committed and queued
Sales Invoices should show DRC
Generated Sales invoices created within Coreloops, where we have to charge a domestic reverse charge, should show the amount without affecting the total amount in the document
Supervisor view
Why Supervisors have direct oversight of operative work and schedules but currently cannot input or manage timesheet data. This creates dependency on office staff and delays in timesheet processing, whilst reducing accuracy as supervisors cannot verify work performed. What A supervisor-specific interface for managing operative timesheets, including the ability to schedule shifts, update hours worked, and submit timesheets for payroll processing. How Create supervisor dashboard showing all operatives under their supervision Build timesheet creation interface for scheduling operative shifts Implement timesheet editing capabilities (hours, breaks, job details) Add bulk submission functionality for multiple operative timesheets Display timesheet status (draft, submitted, approved) Show validation errors and warnings before submission Implement mobile-responsive design for field use Dependencies User role management (supervisor identification) Supervisor-operative relationship data Timesheet data model Authentication system COR-1478 (parent feature) Acceptance Criteria [ ] Supervisors can view list of all their operatives [ ] Supervisors can create new timesheet entries for operatives [ ] Supervisors can schedule shifts with start/end times, breaks, and job codes [ ] Supervisors can edit draft and submitted (but not approved) timesheets [ ] Supervisors can submit individual or multiple timesheets at once [ ] Clear validation messages shown for incomplete or invalid timesheet data [ ] Timesheet status clearly displayed (draft, submitted, approved, rejected) [ ] Interface is mobile-responsive for use on tablets/phones in the field [ ] Supervisors can only access timesheets for their assigned operatives
In Progress
2Actively being built
Link uploaded cost elements to tags or cost codes
Allow uploaded cost elements to be linked to tags or cost codes.
Enhance Cost Element Upload with Tagging for Reporting
Many of our users need a better way to categorize their uploaded cost elements for accurate financial reporting. They find it challenging when these costs aren't automatically linked to existing tags or cost codes, leading to difficulties in getting a consolidated view of their expenses. We are working on an update that will allow users to easily link uploaded cost elements to their existing tags or cost codes during the upload process. This will ensure all costs are correctly categorized and reflected accurately in their reports, providing more precise financial insights.
Done
12Recently shipped
Credit Notes in Transaction Reports and Cost Forecasts
Customers need to see credit notes accurately reflected in their transaction reports. This is essential for precise financial oversight and to ensure that final cost forecasts are complete and correct. We propose an enhancement to include credit notes as a distinct line item within transaction reports, ensuring their values are properly incorporated into all final cost forecast calculations.
Enhance Duplicate Invoice Detection Reliability with Robust Testing
Customers need to be confident that duplicate invoices are always accurately identified to prevent errors and ensure precise financial management. Ensuring the integrity of financial data is paramount for operational efficiency and cost control. We are improving the reliability of our duplicate invoice detection system. This initiative will involve implementing comprehensive testing to guarantee that our AI-powered matching consistently and accurately flags potential duplicates, thereby strengthening financial security and operational trust.
Customise the branding on outbound document emails
When Coreloops sends documents (like invoices) by email, the template currently shows Coreloops' own branding. Let customers apply their own company branding (e.g. logo) to the outbound email template instead, so documents feel like they're coming from the customer's business.
Allow linking credit notes to invoices
Why Credit notes need to be linked to invoices so actual costs are reduced in all reports where that cost was previously allocated. What Users can now link credit notes to specific invoices. This updates the amount invoiced against that PO and updates the transaction report at the same time. After linking a credit note, you’ll be prompted to link line items in the credit note to specific line items on the invoice.
Include credit notes in transaction reports and cost forecasts
Include credit notes in the transaction report and final cost forecast calculation.
Automated sequential job numbers
Automate generation of job numbers with configurable sequential numbering.
Seamless WhatsApp Document Transfer to Accounting Software
When financial documents like invoices and receipts are uploaded through specific channels, customers have noted that sometimes the associated attachments or project details are not fully carried over to their accounting software. This can create additional manual steps and potential inconsistencies in their financial records. We are developing an enhancement to guarantee that all documents, including their attachments and assigned project information, are consistently and accurately transferred from Coreloops AI to integrated accounting platforms, irrespective of the initial upload method. This will ensure complete data integrity and further streamline financial reconciliation processes.
Choose which section a variation is published to
Allow the user to choose which section a variation is published to. In the Modal allow the user to create a new section. Default the name to variations.
Bulk supplier update for documents
Why The AI can incorrectly assign documents to similar but wrong suppliers (e.g., "Travis Perkins Hire" instead of "Travis Perkins"). Whilst improved matching logic will reduce this (COR-1479), when it does occur, users must manually update each document individually. This is inefficient when multiple documents need the same supplier correction. What Enable bulk supplier updates in the documents view: Allow users to select multiple documents Provide option to change supplier for all selected documents at once Update supplier field across all selected documents in a single action How Add "Change supplier" bulk action to documents page when multiple documents selected When clicked, open supplier selection dropdown/modal Upon confirming new supplier, update all selected documents Show confirmation message with count of documents updated Ensure action is available in the bulk actions toolbar alongside existing Delete/Approve actions Dependencies COR-1479 - Improved supplier matching should reduce frequency of this issue Acceptance Criteria Users can select multiple documents in documents view "Change supplier" option appears in bulk actions when documents are selected Clicking action opens supplier selection interface All selected documents update to new supplier when confirmed Action works regardless of current supplier assignments Confirmation message shows number of documents updated Works consistently with existing bulk actions (Delete, Approve)
Operative view
Why Operatives are best positioned to provide accurate information about their work hours, breaks, and job activities. Currently, they cannot input this data directly, leading to inaccuracies, delays, and dependence on supervisors or office staff to manually enter timesheet information. What A self-service interface for operatives to view, update and submit their own timesheets. The system respects configurable review workflows, routing submissions to either supervisors or office staff based on organisational settings. How Create operative-specific timesheet view showing their scheduled and actual hours Build interface for operatives to update their timesheet entries (hours worked, breaks, job details) Implement timesheet submission workflow Add validation to prevent submission of incomplete timesheets Display timesheet status and review workflow Route submissions based on settings (supervisor review vs office review) Implement mobile-first design for field access Add read-only view for approved timesheets Dependencies Operative user authentication Timesheet settings configuration (review workflow) Timesheet data model Notification system for submission confirmations COR-1478 (parent feature) Acceptance Criteria [ ] Operatives can view their own timesheets (scheduled and actual) [ ] Operatives can update hours worked, breaks, and job details [ ] Operatives can submit timesheets when complete [ ] Clear validation prevents submission of incomplete data [ ] Timesheet status visible to operative (draft, submitted, approved, rejected) [ ] Submissions route correctly based on review settings (supervisor or office) [ ] Operatives receive confirmation when timesheet is submitted [ ] Approved timesheets are read-only [ ] Rejected timesheets can be edited and resubmitted [ ] Interface is mobile-responsive for use on phones in the field [ ] Operatives can only access their own timesheets