# Project-change-to-invoice metadata packet | SourceX

Canonical: https://refer.sourcex.si/guides/chain-project-change-to-invoice
Last updated: 2026-11-04

A partner can note, without opening anything, which tools hold each step from scope change to accepted file to revised invoice (here monday.com, Dropbox and QuickBooks Online), the years and rough volumes each covers, who administers each one, how long each keeps its change history, and which links between the steps are recorded or only remembered. The case to flag is an invoice built from an outdated scope version. Whether the records can be licensed is decided later, after SourceX's review.

## The business task the packet describes

Agencies change scope constantly. A client asks for an extra feature, the account lead agrees a new fee, the team delivers the work, the client accepts it, and finance bills for it. Each step is a small decision made by a different person in a different tool, and the money only comes out right when all of them line up.

Across hundreds of projects, that history records how an agency prices change, proves delivery and catches its own billing mistakes. The packet does not try to capture any of that. Its job is to tell SourceX where each step lives, how far back it goes, how long each tool keeps its change history, and how confidently the steps can be joined. That is enough for SourceX to judge whether a conversation is worth having.

## What each system can tell you without opening it

Fill in the packet from one conversation with the operations lead and the finance lead. The history limits come from the vendors' published help pages; everything else is the company's own description.

- **monday.com.** Ask how projects and scope changes are tracked: one board per client, one per project, or a shared pipeline board, and since when. monday.com keeps an item-level Activity Log that can be filtered by person, date or column and records items created, archived or restored, and item and board logs can be exported to Excel. Ask the admin how far back the logs go on the agency's plan rather than assuming.
- **Dropbox.** Ask how project folders are named and whether accepted deliverables are moved, renamed or kept in place. Dropbox keeps earlier file versions for 30, 180 or 365 days depending on plan, cannot restore permanently deleted files, and does not apply version history to web-based files such as Google Docs. So the plan tier is a packet fact worth writing down.
- **QuickBooks Online.** Ask roughly how many invoices and revisions the agency issues a year, and whether invoices reference a job number or scope version. The QuickBooks Online audit log records edits to transactions and customers, needs admin access to view, and keeps history for two years; a transaction's own audit history shows who changed it, when and what changed, but not why.

## Sample packet, filled in

Illustrative: a fictional 210-person brand and packaging design agency that runs client work on monday.com boards, keeps deliverables in Dropbox and invoices from QuickBooks Online.

| Packet field | monday.com | Dropbox | QuickBooks Online |
|---|---|---|---|
| Object types | Board items, status changes, Activity Log entries | Project folders, files and file versions | Invoices, credit memos, audit history entries |
| Date range | 2019 to today | 2017 to today | 2018 to today |
| Rough volume | About 600 projects a year; most have at least one scope item | One folder per project | About 7,000 invoices a year, invoiced monthly |
| History limit | Activity Log depth on their plan: to confirm | 180 days of versions on their plan | Audit log events kept for two years |
| Join to the next step | Job number on the item, used since 2021 | Folder named by job number, mostly | Scope reference in the memo, sometimes typed |
| Administrator | Operations lead | IT manager | Finance lead (company admin) |
| Known gap | Scope approvals agreed on calls, then logged | Client acceptance arrives by email | Invoices copied from the previous month |
| Unknown until review | Rights in client contracts | Which deliverables are client-owned | Personal data in customer records |

Keep amounts out of the packet. "About 600 projects a year, invoiced monthly" is the right level; the fee figures below exist only to show the pattern, not as something to collect. For fuller field lists, see the [QuickBooks inventory template](/resources/a-metadata-only-quickbooks-inventory-template-for-company-introductions), the [monday.com systems page](/systems/monday-com) and the [Dropbox export page](/systems/dropbox-business-export-all-data-admin).

## How the packet flags an invoice built from an old scope

The case to surface is a revised invoice that bills an outdated scope version. In the illustrative agency, a snack-food client adds four flavor variants to a packaging refresh. The account director logs "Scope v4: four extra variant dielines" on the board and marks it Approved, moving the fee from $31,200 to $36,800. The print-ready artwork lands in the job's Dropbox folder and the client's brand manager signs it off. At month end the billing coordinator duplicates the March invoice, still built on scope v3, and sends $31,200. Nobody outside the agency notices. The gap surfaces six weeks later in the agency's own work-in-progress review, when the job's logged hours sit well above what was billed, and finance raises a supplementary invoice for the $5,600 difference instead of crediting the original.

The partner does not need to find that project. The packet makes cases like it findable through three rows: the "Join to the next step" row shows the scope reference on invoices is only sometimes typed, the "Known gap" row shows invoices are copied from the previous month, and the "History limit" row shows how long each tool would still hold the evidence. Ask the finance lead one question: "When scope changes mid-project, how does the new figure reach the invoice?" If the answer depends on someone remembering, write that down.

Note the timing too. With 180 days of Dropbox versions and two years of QuickBooks audit history, the evidence for older projects is already partial. That is not a reason to avoid the introduction; it is a reason to describe the limits accurately.

## Client-owned work, and who can authorize the discussion

Agencies hold two kinds of record. Their own operating records, such as boards, timesheets, invoices and audit trails, normally belong to the agency. Deliverables made for a client may be governed by the client contract. The guide on [separating agency records from client-owned work](/guides/how-agencies-can-distinguish-their-own-operating-records-from-client-owned-work) explains the line, and the [customer implementation records page](/data-types/customer-implementation-project-records) shows a similar split in software services.

Introduce the person who can authorize a licensing discussion, the CEO, often the agency founder or managing director, with the COO as a possible sponsor, and name the finance lead and operations lead as the people who can answer the packet. Check the basics first: 50+ full-time employees at peak (contractors excluded, which matters in agencies that rely on freelancers), 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 the opportunity: demand for this record type, the rights review result, how client and personal data would be handled, the company's offer, and any reward. Partners never ask for or handle raw client records, invoices or files. Other system pages, including [Bill.com invoice history](/systems/bill-com-export-invoice-history), are collected in the [systems hub](/systems).

## Go deeper on project-change-to-invoice records

- [Project-change-to-invoice record linkage](/guides/project-change-to-invoice-record-linkage): the record chain, step by step, with the identifier that joins each hop and where it breaks.
- [Project-change-to-invoice completeness checklist](/resources/project-change-to-invoice-completeness-checklist): a pass, partial or fail scorecard for judging whether the billing trail is complete enough to discuss.
- [What a single-system project export loses](/guides/project-change-to-invoice-missing-context): a before-and-after reading of one project, with and without its surrounding records.

## 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 client can fill most of this packet and owns its boards, files and books outright, [register as a partner](/register), check it against [who qualifies](/who-qualifies), and keep the [program terms](/terms) on hand when you introduce its founder.

## Sources

- https://support.monday.com/hc/en-us/articles/115005310745-The-Activity-Log
- https://help.dropbox.com/delete-restore/recover-older-versions
- https://quickbooks.intuit.com/learn-support/en-us/help-article/audit-log/use-audit-log-quickbooks-online/L2WoVnW6I_US_en_US
- https://quickbooks.intuit.com/learn-support/en-us/help-article/audit-log/view-transaction-changes-audit-history/L7obVhic2_US_en_US
- https://refer.sourcex.si/terms
