Create a single source of truth across business systems

Decide which system controls each fact and how shared reports calculate their measures. Accounting can remain responsible for invoices while operations records completed visits. A connected view links the two and explains why their totals differ.

Putting everything in one database does not resolve a disagreement about what “September work” means.

Four completed visits and three invoices

In this fictional example, operations reports four completed visits in September. Finance reports three invoices issued in September. The owner wants to know why the numbers differ.

Start with the complete set of visits relevant to the comparison.

A

• Operations record: Completed September 12.
• Billing link: Invoice I-103, issued September 30.

B

• Operations record: Completed September 20.
• Billing link: Same invoice I-103.

C

• Operations record: Completed September 30.
• Billing link: Invoice I-104, issued October 1.

D

• Operations record: Canceled September 22; wrongly included in the completion export.
• Billing link: No invoice expected.

E

• Operations record: Completed August 26; excluded from September completions.
• Billing link: Invoice I-101, issued September 10.

F

• Operations record: Completed August 28; excluded from September completions.
• Billing link: Invoice I-102, issued September 18.

Now inspect all three September invoices and the later invoice for C.

I-101

• Issue date: September 10
• Linked visits: E
• Included in September invoice count: Yes

I-102

• Issue date: September 18
• Linked visits: F
• Included in September invoice count: Yes

I-103

• Issue date: September 30
• Linked visits: A and B
• Included in September invoice count: Yes

I-104

• Issue date: October 1
• Linked visits: C
• Included in September invoice count: No

Finance's count is three invoice records. Those invoices cover four visits, including two completed in August.

Operations has a genuine error: D is canceled. Excluding it reduces September's completed-visit count from four to three. The resulting counts happen to match, but they still describe different things. September completions are A, B, and C; September invoices are I-101, I-102, and I-103.

A useful shared view keeps both measures and their record links. It does not force invoices and visits into the same unit or period.

Follow the correction without losing the evidence

The operations reviewer opens D and confirms the cancellation. Until the source export is corrected, a reporting adjustment can identify D, reference the original export, and record the reviewer's approved exclusion from September completions.

The view can then show the original count of four, D's exclusion, and the corrected count of three.

When operations fixes the source, the adjustment must stop excluding D again. Otherwise, yesterday's correction creates tomorrow's undercount. Matching the correction to the source record makes that check possible.

This is why a spreadsheet adjustment needs its purpose, period, affected record, and approver. A typed number with no explanation cannot tell the next reviewer what to do when the source changes.

Assign authority and a person to resolve differences

Operations controls the approved completion event. Finance controls the invoice and payment records. A reviewer confirms links between customer identifiers and between visits and invoices.

A reporting discrepancy should go to the person responsible for the affected fact. Changing a dashboard total does not authorize rewriting the accounting ledger.

Source system and record ID stay attached to every imported item. Across acquired businesses, include the company too, since local invoice numbers may repeat.

Documents can also supply evidence. If a signed form and typed completion date disagree, keep the original file available for review. Extraction can check a clear job identifier automatically; an ambiguous identifier or disputed quantity needs someone to inspect it.

Make the shared calculation reusable

For completed visits, define the completion event, date, unit, cancellation exclusion, and treatment of approved corrections. Use that calculation in the dashboard and exports. An assistant explaining the total should obtain it from the same calculation.

The invoice measure needs its own issue date and inclusion rules. Users should be able to move from either total to the contributing records and then across the approved billing links.

Show source refresh times alongside the view. A failed accounting import should appear as missing information rather than zero invoices. Validate the relationships as well as the total: an invoice can have the right value and the wrong customer link.

Cass & York's AutoTakeoff work connected construction PDFs, measurement tools, and material records in an application. It is related published work involving documents and structured data.

Build the view around the disagreement

The proposed project brings together the operations reviewer, finance user, and manager reading the totals to confirm source records, measure definitions, invoice links, and corrections.

The proposed view shows both totals, the six relevant visits, four invoice records, and D's correction history. Testing covers A and B sharing one invoice, C's October billing, and removal of the temporary exclusion when the source is fixed.

Cass & York builds the connections and reporting views needed to make these answers traceable. Bring a total your departments cannot explain together.