Project-change-to-invoice record linkage: the keys that tie a scope change to its corrected invoice

Short answer

A company connects project-change-to-invoice records by naming the identifier that carries across each hand-off, usually a job number typed on the board item, the project folder and the invoice memo, and by pointing to each tool's own history: the Activity Log, file versions, the transaction audit history and credit memos. Where no identifier carries, the join is inferred from dates and should be labeled that way. The weakest link sits between the accepted file and the scope version it delivered.

Visual briefFull-size diagram
Six records from scope item to corrected invoice click together as chain links keyed by job number; the link between the delivered file and the approved scope version glows as a weak, inferred join and then turns solid once acceptance is recorded on the item.
Illustrative chain for a fictional agency job. The weak link is the one agencies often infer from dates rather than record.

This record chain is part of the project-change-to-invoice records guide. The guide covers the metadata packet; this page covers only the keys, link by link.

The chain in six records

One scope change, from request to corrected bill, leaves six records behind. Illustrative: a fictional 140-person digital agency, job J-2417, where the client asks for an extra checkout feature halfway through the build.

  1. Scope item. A board item for the change, with a status column and the job number typed into a text column.
  2. Scope approval. The status moves to "Scope v3 approved". The board's item-level Activity Log stores the change with the person and date, and item and board logs can be exported to Excel.
  3. Delivered file. The feature build saved in the project folder named for J-2417, with earlier versions kept for 30, 180 or 365 days depending on the file plan.
  4. Client acceptance. An email from the client approving the build. It sits in the account lead's inbox, outside every tool the agency administers.
  5. Invoice. An invoice for $18,400, duplicated from last month's and still priced on scope v2. Its memo may or may not carry J-2417.
  6. Correction. A credit memo applied against the first invoice and a reissued invoice for $22,900. Each transaction's audit history shows who changed it, when and what changed.

Taken as one chain, the job is easy to follow. Taken as six unconnected records, nothing proves the $4,500 difference belongs to the checkout change. Each link needs a key, and the keys are not equally strong.

Step, record, key and system

The table is the evidence asset: for each link, what record sits on either side, which key joins them, and whether that join is written down or reconstructed.

StepRecordJoin key to the next stepSystemRecorded or inferred
1 to 2Scope item to its approvalItem ID, inside the Activity LogProject boardRecorded
2 to 3Approved scope to delivered fileJob number in the folder nameBoard and file storeRecorded if naming is consistent
3 to 4Delivered file to client acceptanceFile version date near an email dateFile store and emailInferred from timing
4 to 5Acceptance to invoiceJob number or scope reference on the invoiceAccountingRecorded only if finance types it
5 to 6Invoice to credit and reissueCredit applied to the invoice; audit historyAccountingRecorded, with one caution
6 to 2Reissued invoice back to scope v3Scope version named on the new invoiceAccounting and boardUsually inferred

The last row closes the loop. Without it, a reader can see that an invoice was corrected but not that the correction was caused by billing an outdated scope version.

Five breaks come up again and again. Each is a question the company can answer from memory.

  • The job number arrived late. If boards adopted job numbers in 2021, every earlier join between board, folder and invoice rests on client names and dates.
  • Acceptance lives in inboxes. Step 3 to 4 is often the weak link. A file version saved two days before an approval email does not prove that file was the one approved. The company should call this join inferred.
  • Invoices are copied forward. When finance duplicates last month's invoice, the memo carries last month's scope reference, or none. That is how the outdated-scope case enters the books.
  • Credits can land on the wrong invoice. QuickBooks Online creates a credit memo and then applies it to an open invoice; with automatic application turned on, it applies credits to the oldest open invoices first. A credit meant for the J-2417 invoice can attach to an older one, so ask whether auto-apply is on.
  • History windows close. Dropbox version history depends on plan and does not cover web-based files such as Google Docs. If an accepted deliverable was a Google Doc, step 3 may have no version trail at all.

The weak link can be repaired going forward and, sometimes, reconstructed backward.

Going forward. The cleanest fix is a status on the monday.com item, such as "Client accepted", set by the account lead with a link to the Dropbox file version. The Activity Log then records the acceptance with a person and date, and step 3 to 4 moves from inferred to recorded. Some agencies add a scope version column so the invoice memo can name it.

Backward. For older jobs, the company can search email for the job number around each delivery date. That is work the company does under an agreement, not something a partner asks for. What a partner can note is the year the forward fix started, because that is the year the chain becomes reliable.

In J-2417, the repaired chain reads: scope v3 approved in week 3, feature build delivered in week 5, client acceptance logged on the item in week 5, invoice at $18,400 in week 6, credit and reissue at $22,900 in week 9. The $4,500 gap now has a recorded cause. For the same job read from each export on its own, see the sibling before-and-after reading; to mark a whole archive, use the completeness scorecard.

What the company describes, and who authorizes it

The company describes the chain; it does not hand it over. For each link, a partner records three facts: the key, whether it is recorded or inferred, and from which year. If nobody has checked what a tool's export contains, the field is marked unknown rather than guessed. This page does not imply that SourceX has a connector for monday.com, Dropbox or QuickBooks; how records would move is settled after review. Partners never ask for or handle raw boards, files or invoices.

The operations lead and finance lead can answer the link 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, 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 it: which deliverables are client-owned under client contracts, how personal data in customer records would be handled, and whether a buyer wants this record type. Tool-specific export notes are on the monday.com page, the Dropbox admin export guide and the Bill.com invoice history page; why cross-system records carry more value explains why a joined chain matters.

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 its six links are recorded and from which year, register as a partner, confirm the basics on who qualifies, and read the program terms before introducing its founder.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does the agency need to join the records before an introduction?

No. The company only describes which identifier carries across each hand-off and whether that join is recorded or inferred. Any actual joining happens later, under the company's own agreement, after SourceX's review.

What if the agency never used job numbers?

Then most joins are inferred from client names and dates. Say so. A chain described as mostly inferred is still useful to a reviewer, as long as nobody claims it is recorded.

Does SourceX connect to monday.com, Dropbox or QuickBooks?

This page names the tools only to show where records usually sit. It does not describe a SourceX connector. How any records would move is settled after review and agreement.

Sources

  1. support.monday.com/hc/en-us/articles/115005310745-The-Activity-Log
  2. help.dropbox.com/delete-restore/recover-older-versions
  3. quickbooks.intuit.com/learn-support/en-us/help-article/audit-log/v…
  4. quickbooks.intuit.com/learn-support/en-us/help-article/customer-re…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment