# Agency billing trail completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/project-change-to-invoice-completeness-checklist
Last updated: 2026-11-04

A project-change-to-invoice trail breaks when board items, folders and invoices share no job number, when Dropbox or QuickBooks history has aged out, when finance can invoice without checking the current scope, when client acceptance sits in personal inboxes, and when invoice errors are fixed by editing rather than crediting and reissuing. This scorecard turns those breaks into nine checks you can mark pass, partial or fail from the agency's own answers, without opening a board, a file or an invoice.

It belongs to the [project-change-to-invoice records guide](/guides/chain-project-change-to-invoice). If you have not yet seen what a gap looks like inside one job, the sibling [before-and-after reading](/guides/project-change-to-invoice-missing-context) shows it.

## How the scorecard reads: marks, core checks and bands

Every check gets one mark:

- **Pass:** recorded in a system for most years the agency wants to describe.
- **Partial:** recorded for some years, some clients or some people only.
- **Fail:** not recorded, or nobody can say. Unknown is a fail until confirmed.

Three checks are **core** because the chain cannot be joined without them: shared job number (check 2), client acceptance (check 5) and invoice-to-scope reference (check 6). The result is a band, not a score:

| Band | Rule | What to tell SourceX |
|---|---|---|
| Ready to describe | All three core checks pass, no more than two fails elsewhere | The chain is recorded end to end for the years stated |
| Describe with gaps | At least one core check partial, none failed | The chain holds for some years or clients; name which |
| Not yet describable | Any core check fails | Records exist, but joins would be inferred; say so plainly |

A band says how confidently the records could be joined. It says nothing about whether SourceX or a buyer will want them.

## The nine checks

| # | Check | Ask the agency | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1 | Coverage | Since which year do boards, project folders and invoices overlap? | Five or more years in all three | Shorter overlap, or a tool switch in between | One tool only, or unknown |
| 2 | Shared job number (core) | Do board items, folders and invoices carry the same job or scope number? | Yes, for all years described | From a given year, or for some clients | No shared number |
| 3 | Scope history | How far back does the board's Activity Log go on your plan? | Covers the years described | Shorter than the years described | Unknown, or logs not kept |
| 4 | File history | Which Dropbox plan, and are deliverables stored as files or as web documents? | Long version window; deliverables are files | Short window, or some web documents | Deleted folders or mostly web documents |
| 5 | Client acceptance (core) | Where is client acceptance recorded? | On the board item, with a date | Shared inbox or project folder | Personal inboxes only |
| 6 | Invoice-to-scope reference (core) | Does each invoice name the scope version it bills? | Always, in a memo or field | Sometimes, when finance types it | Never; invoices copied forward |
| 7 | Correction method | Are invoice errors fixed with a credit and reissue, or by editing the original? | Credit memo and reissue | Mixed | Edits to the original only |
| 8 | Credit application | Is automatic credit application turned on in QuickBooks? | Off, or credits checked by hand | On, but reviewed at month end | On and never reviewed |
| 9 | Exception awareness | Does the agency know invoices sometimes use an outdated scope, and how is it caught? | Yes, with a named catch point | Suspected, no routine catch | Not known |

The documented limits behind checks 3, 4, 7 and 8 come from the vendors. monday.com keeps an item-level Activity Log that can be exported to Excel. Dropbox keeps earlier versions for 30, 180 or 365 days depending on plan, cannot restore permanently deleted files, and does not version web-based files such as Google Docs. The QuickBooks Online audit log keeps edit history for two years, which is why a credit and reissue (check 7) leaves a clearer exception than an edit. QuickBooks applies a credit memo to an open invoice, and with automatic application on, to the oldest open invoices first, so a credit can attach to the wrong job (check 8).

## The outdated-scope question, asked three ways

Check 9 is the one that tells you most. Ask: "When scope changes mid-project, how does the new figure reach the invoice?" Answers usually fall into three groups.

1. **"Finance checks the board before every invoice."** Pass, if the board is where scope lives. Ask how long that has been true; the year it started is the year check 6 becomes reliable.
2. **"The client usually tells us."** Partial. The exception exists and is caught, but by the customer. The evidence sits in email threads and credit memos, not in a routine.
3. **"I don't think that happens."** Fail, unless someone confirms it. Agencies that copy invoices forward often have the case without having looked for it.

An agency that answers "yes, it happens, and here is how we catch it" is describing a known, labeled exception. That is worth more to a reviewer than a trail that looks clean because nobody checked.

## A scored agency (Illustrative)

A fictional 210-person brand and web agency, scored in one call with its operations lead and finance lead. Every answer is invented.

| # | Check | Answer heard | Mark |
|---|---|---|---|
| 1 | Coverage | Boards since 2019, folders since 2016, invoices since 2018 | Pass |
| 2 | Shared job number | Job number on items, folders and invoices since 2019 | Pass |
| 3 | Scope history | Admin unsure how far logs go back | Fail |
| 4 | File history | 180-day versions; most deliverables are files | Partial |
| 5 | Client acceptance | Acceptance emails filed to the project folder since 2022 | Partial |
| 6 | Invoice-to-scope reference | Scope version in the memo on every invoice | Pass |
| 7 | Correction method | Always credit and reissue | Pass |
| 8 | Credit application | Auto-apply on; reviewed at month end | Partial |
| 9 | Exception awareness | Happens a few times a year; caught at month-end review | Pass |

Core checks: 2 pass, 5 partial, 6 pass. Band: **Describe with gaps.** How a partner would put it: "Boards, folders and invoices joined on a job number since 2019; client acceptance recorded only since 2022; agency knows outdated-scope invoices happen and catches them at month end." For how a buyer-side reviewer thinks about quality, see [data quality due diligence](/resources/data-quality-due-diligence); for which tool counts as the authority for each fact, see [what a system of record is](/questions/what-is-a-system-of-record).

## Owners, the sponsor and what stays open

The checks point to the owners: the operations lead for checks 1 to 5, the finance lead for checks 6 to 9. The person who can open a licensing discussion is usually the founder, managing director or COO. A finance lead may also want to know how a new revenue line would be audited; [audit considerations for a new revenue stream](/resources/audit-considerations-new-revenue-stream) covers that.

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, as with [customer implementation project records](/data-types/customer-implementation-project-records); how customer details would be handled; which years a buyer wants; and what the agency would be paid. Partners never ask for or handle boards, files or invoices. The joins behind checks 2, 5 and 6 are set out step by step on the [record linkage page](/guides/project-change-to-invoice-record-linkage).

## 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.

When the scorecard gives you a band and one honest sentence about the agency's billing trail, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing the founder.

## Sources

- 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/customer-refunds-credits/create-apply-credit-memos-delayed-credits-online/L5kne9EiI_US_en_US
- https://support.monday.com/hc/en-us/articles/115005310745-The-Activity-Log
- https://refer.sourcex.si/terms
