Skip to main content

Have something to say?

Tell us how we could make the product more useful to you.

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.

Sandra Phillips3 months ago
1Oct 9

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.

Andy Cramp28 days ago

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.

Sandra Phillips3 months ago

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.

Andy Cramp3 months ago
Sep 11

Show % of PO remaining on hover

Show the percentage of a purchase order left when hovering over the invoiced amount.

Sandra Phillips3 months ago

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

Linear9 months ago
Feb 20

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

Linear10 months ago

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

Linear9 months ago
Planned

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

Andy Cramp2 months ago
1Nov 6

Being able to carry out bulk actions in bulk

As you can do in Xero, you should be able to make multiple changes to documents without having to wait for each one to be filled in before having to make the bulk action again

Jon Marsden2 months ago

Flagged timesheet entries to be shown at the top

When importing timesheet entries, the flagged entries should show up at the top of the list so that you do not need to scroll down to find them.

Ashraf Ahmed2 months ago

Consistent Xero Invoice Status Syncing Improvement

Customers need their invoices to consistently sync with the correct approval status when integrated with Xero. Currently, some invoices are incorrectly marked as "awaiting approval" instead of "awaiting payment" when they are approved in our system, requiring manual correction. This inconsistency can lead to extra work and potential delays in financial processing. To address this, we will investigate the underlying status-mapping logic to identify and resolve the cause of these inconsistencies. Our goal is to ensure all invoices accurately reflect their approval state in Xero without manual intervention, streamlining financial workflows for our users.

An Anonymous User3 months ago
Planned

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

Linear9 months ago

Show a running total in the PO matching view

In the PO matching view, show a running total of what has already been matched.

Show which invoice failed during batch approval

When batch-approving invoices, show which specific invoice failed to sync.

Sep 30Documents

Prompt to link a tracking category on new projects

When tracking categories are connected, prompt users to link a tracking category when creating a new project.

Save a default setting for suppliers on first use

When a setting like payment terms, VAT, cost code, account, or CIS rate is used for a new supplier, prompt to save it as the default.

Flag documents that don't match the supplier's default VAT or CIS rate

Flag a document when its VAT or CIS rate doesn't match the supplier's recorded default.