You accept a project this week, invoice part of it, and receive a smaller payment. Which amount belongs in the weekly report? All three can be useful, but they answer different questions. Reporting them under one label hides whether work is agreed, billed, or paid.
Build a small operational view with three clearly named sections. Keep the source record and currency beside each amount. This is a way to understand the team’s work and collections, not a substitute for your accounting or tax rules.
Decide what each number means
Booked work means the value of work actually accepted under your team’s defined agreement rule. An unaccepted proposal stays outside this number. If the scope changes, record the agreed change rather than silently replacing the original value.
Issued invoices means the invoices issued in the reporting period under the chosen operational definition. Keep invoice identifiers and adjustments traceable. Do not assume that an issued invoice is money in the bank.
Received cash means actual receipts evidenced by the relevant transaction records. Keep the receipt date and currency. A credit or other non-cash adjustment can reduce an outstanding invoice without adding a cash receipt.
Use the same reporting cutoff and explain which date selects each section. The agreement date, invoice date, and receipt date may fall in different weeks; that is a real difference, not a reason to force the totals to match.
Follow one fictional project through the report
The following example uses a single currency and ignores tax solely to keep the operational arithmetic visible. Adapt the definitions to your actual records before using the approach.
| Record | Amount | What it establishes |
|---|---|---|
| Accepted project JOB-021 | 1,200 | Agreed work |
| Issued invoice INV-041 | 800 | Amount billed on this invoice |
| Allocated payment PAY-009 | 300 | Cash received toward INV-041 |
| Credit CR-003 against INV-041 | 100 | Non-cash reduction of this invoice |
The report shows booked work of 1,200, issued invoice value of 800, and received cash of 300 for these records. The invoice’s remaining balance is 800 − 300 − 100 = 400. The credit reduces that balance; it does not turn the cash figure into 400.
The project value and invoice value also do not belong in a sum of 2,000. They describe related stages of the same work. The remaining project value is not automatically an overdue invoice.
Link the records before aggregating
Keep separate rows for agreements, invoices, and receipts, linked through stable project and invoice IDs. For a payment covering several invoices, record the actual allocations. For an unallocated receipt, show an exception rather than assigning it to the first matching client name.
At minimum, use these fields:
- Agreement: project ID, accepted date, agreed value, currency, and source reference.
- Invoice: invoice ID, project ID, issue date, amount, currency, and source reference.
- Receipt or adjustment: transaction ID, date, type, amount, currency, invoice allocation, and source reference.
Separate payment and credit types explicitly. Check a duplicate transaction ID before adding a second row. If a refund or reversal appears, preserve the linked record and treat it under your documented reporting definition rather than removing inconvenient history.
Keep exceptions visible
Do not add amounts in different currencies into one unlabeled total. Report them separately or use a documented conversion method with its date and rate source. Do not silently mix gross and net amounts, invoice dates and payment dates, or proposed and accepted work.
Keep a short exceptions list for missing references, disputed allocations, inconsistent currencies, and unexplained balances. A visible unresolved receipt is more useful than a tidy total based on a guess.
Publish a report someone can reconcile
Show the three figures with their definitions, period, currency, and links to the supporting records. Check the invoice balance separately from the cash total. Review an example with a partial payment and a credit before expanding the view to the full team.
The useful question then becomes clear: do you need more accepted work, more timely invoicing, or collection of existing invoices? Those are different actions. Keeping the numbers separate helps the team choose the action without mistaking one stage for another.