BrightFlag Connector: Sync All Matters and Invoices (Remove Invoice Status Filtering)
AnsweredWhich connector?:
Brightflag
Additional details:
1. [Higher Priority] Matters — Full Sync Regardless of Invoice Status
Currently, only matters that have an approved invoice appear to be synced. We assign budgets to matters across our full portfolio, so we need all matters represented — including those without any approved invoice. This gap means a significant portion of our matter data is missing from our downstream reporting today.
2. [Lower Priority] Invoices — Full History, Not Only Post-Approval
We've observed that only invoices after the first approved invoice on a matter are synced. Ideally, all invoices would be included regardless of approval status, as we track invoice activity (approved or not) across all matters for spend analysis purposes.
Neither request requires changes to existing tables — we are simply asking for the sync logic to reflect the full dataset available in BrightFlag.
-
Official comment
Hi Brandon,
Thank you for this detailed request! We've added this to our feature improvements backlog. We're currently reviewing the technical feasibility of removing the invoice approval filter — the Brightflag API's filtering options aren't fully publicly documented, so we're investigating whether the sync logic change is straightforward.
Could you tell us more about your use case? Specifically, are you primarily blocked by missing matters without approved invoices, or is the pre-approval invoice history equally important? That context will help us prioritize. We'll keep you updated on this thread. -
Hi Unnikrishnan,
This is great to hear -- thank you! This reply is actually great timing since I just met internally regarding this data yesterday.
- We do see retrieving all invoicing activity as important, especially those that have no approved invoice but one is pending. However, the clear winner in priority (and primary blocker) would be retrieving all matters.
- With backlog requests like this one, how long does it normally take to be completed? I am sure it varies on other workload and size of lift for each request, just need to know how to communicate back to my internal stakeholders. They are debating on getting our internal Data Engineering team involved or waiting for this feature request.
-
Hi Brandon,
Thanks again for the timely inputs.
We typically prioritise basis the demand. For this, I have bumped up the priority. An actual timeline will depend on the engg analysis and few more aspects like how quickly we are able to get access, how well documented the APIs are etc. We will reach out to you for access and notify you of progress.
Please sign in to leave a comment.
Comments
3 comments