This before-and-after reading is part of the project-change-to-invoice records guide. It uses one Illustrative agency job and reads it twice: once tool by tool, once joined.
Before: three exports, three partial stories
Illustrative. A fictional 140-person digital agency builds a retail website. Mid-project, the client asks for a store locator, and the fee rises from $18,400 to $22,900. Here is what a reader learns from each export, described at metadata level.
- The board on its own. An item reads "Scope v3: add store locator", moved to Approved in week 3. Its history shows who changed the status and when. A reader concludes: scope grew, someone signed off, work presumably followed. The amount, the delivery and the bill are absent.
- The file store on its own. The project folder holds a build saved in week 5, with earlier versions alongside it. A reader concludes: a feature was built. Nothing says it was requested as a scope change, accepted by the client or charged for.
- The books on their own. An invoice for $18,400 in week 6, a credit and a new invoice for $22,900 in week 9, and a trail showing who edited what. A reader concludes: the agency made a billing error and fixed it. Nothing says what the error was.
Each story is accurate as far as it goes, and each points the wrong way on its own. The board suggests the change was handled. The files suggest it was routine. The books suggest a typo.
After: one job line, joined
Join the three exports on the job number and the dates line up into a single account of what happened.
| Week | What happened | Where the record sits |
|---|---|---|
| 3 | Scope v3 approved on a client call; fee rises to $22,900 | Board status change and its history |
| 5 | Locator build delivered; client approves it by email | File version; account lead's inbox |
| 6 | Finance copies last month's invoice and bills $18,400 on scope v2 | Invoice in the books |
| 8 | Client queries the bill against the approved scope | Email thread |
| 9 | First invoice credited; reissued at $22,900 | Credit, reissue and edit trail |
| 10 | Client accepts and pays the revised invoice | Payment record |
Now the job has a labeled exception: billed $18,400 against an approved $22,900, a $4,500 gap caused by invoicing an outdated scope version and closed by a revised invoice. The outcome, the client accepting the revision, is part of the record too. That is a different fact from "the agency made a billing error", and it is the fact a reviewer cares about.
What each export loses, and where it lives
Each row is a question someone would ask about the job. The middle columns show what a single export can say; the last column shows where the missing answer lives.
| Question | monday.com alone | Dropbox alone | QuickBooks alone | Where the context lives |
|---|---|---|---|---|
| Was scope changed, and by whom? | Yes, with date and person | No | No | Board status and Activity Log |
| What was the change worth? | Only if typed on the item | No | Shows two amounts, not why | Board item joined to invoices |
| Was the work delivered? | Status only | File version and date | No | The job's project folder |
| Did the client accept it? | Rarely recorded | No | No | Email, outside all three tools |
| Which scope did the first bill use? | No | No | No | Invoice memo compared with board |
| Why was the invoice revised? | No | No | Edit trail only | All three, read in order |
| How did the client respond? | No | No | Payment received | QuickBooks plus the email thread |
Three rows have no single-system answer at all. That is the general pattern described in what data is missing from AI training: structured records survive, the reasoning between them does not. Finance teams will recognize the same shape from accounts payable exception handling, seen from the other side of the invoice.
Context that disappears on a schedule
Some of the missing context is not just separate; it expires. Two limits come from the vendors' own help pages.
- Dropbox file history. Earlier versions are kept for 30, 180 or 365 days depending on plan. Permanently deleted files cannot be restored, and version history does not cover web-based files such as Google Docs. An agency that keeps deliverables as Google Docs, or that closed an old Dropbox account, may have no delivery trail for older jobs.
- QuickBooks Online audit log. It records edits to transactions and customers, needs admin access to view, and keeps history for two years. The invoices remain; the record of who changed them, and when, ages out.
For monday.com, ask the agency's admin how far back the Activity Log goes rather than assuming. An agency that changes plans, closes a file account or switches accounting systems can lose part of the job line without noticing. A documented plan change or migration is a real reason to describe the records sooner. The export side of each tool is covered on the monday.com page and the Bill.com invoice history page.
Naming the gap in an introduction
A partner never needs to see the job above, or any job. What a partner can describe is which of the three contexts exists, for which years, and how they could be joined: by a job number on boards, folders and invoices, or only by client name and date. The record linkage page sets out the joins step by step, and the completeness scorecard turns them into pass, partial or fail marks.
The operations lead and finance lead can answer the questions. The person who can open a licensing discussion is the CEO, often the founder in an owner-run agency. Check the baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
What stays unknown until SourceX reviews it: which deliverables are client-owned, how customer contact details would be handled, which years a buyer would want and what the agency would be paid. Partners never ask for or handle boards, files or invoices.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If an agency can tell you which of the board, file and billing contexts it still holds, and for which years, register as a partner, check it against who qualifies, and read the program terms before introducing its founder.