Duplicate invoice records

Ticketclosed

Copperlane Payroll: documents · Duplicate invoice records

Ian reported invoice records appearing twice in the system, throwing off reporting counts. Support asked for examples to diagnose the cause.

Priority normal

made from

What happened

What this says

Current to 11 Oct 26

Ian reported invoice records appearing twice in the system, throwing off reporting counts. Support asked for examples to diagnose the cause.

Problem: Duplicate records are undermining reporting accuracy and eroding data trust. Handling: Support requested specific examples to trace root cause. Watch: Data quality issues, especially duplicates, damage confidence in the platform. This needs investigation to rule out connector misconfiguration or data-source issues on Copperlane's side.

AI · claude-haiku-4-5-20251001 · 11 Oct 2026

AImade from

Details

Updated 9 Oct 26

Prioritynormal

Statusclosed

Categorydata_quality

Channelemail

First response (min)137

Helpdeskmade from

Trail

created · Ian Brearley 30 Mar 2026 11:00
We're seeing some invoice records appearing twice in the system. It's throwing off our counts in reporting. Can you look into why this is happening?
public_reply · Bethan Lister 30 Mar 2026 13:17
Hi Ian, thanks for reporting that. Just so I've got this right, you're seeing duplicate invoice records. Can you share an example with me? That will help me track down the cause.
status_change · Bethan Lister 10 Apr 2026 14:22
status_change · 14 Apr 2026 23:59

Helpdeskmade from

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

Summary is the landing page: what happened this week, the calls just held and the calls coming up, the risks and the renewals due.
Organisations lists every customer. Open one to see its key facts, the AI assessment and next step, platform usage, the ARR journey, deals, documents, contacts and activity, and the lineage of every block.
Conversations, Commercial, People, News and Documents cut the same data by topic. System explains how the brain is built and where each figure comes from.
Every card ends with a small made from link: it opens the lineage explorer focused on that card, so you can walk from the figure down to the raw rows it came from.
Use the sun and moon button at the top right to choose dark or light. Choose your device's own mode again to go back to following the device.

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

Search the brain finds the organisations, people, calls, emails, tickets, documents and news that match your words, with links to their pages.
Ask Claude copies your question and opens the B-Brain Claude Project, where Claude answers from the same data using the B-Brain tools and cites the pages it used.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

Data	Records
Organisations	75
People at customers	290
BB-Demo staff	40
Calls	784
Email threads	1,169
Support tickets	449
Documents	477
Deals	117
Invoices	101
Events	49
News items	56

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Ask B