Traceability: understanding how records and evidence connect

A customer disputes an invoice. The invoice alone shows what was billed, but it may not explain what was agreed, what was delivered, or why an additional charge was included. Resolving the dispute requires a connected account of the transaction.

Traceability is the ability to follow that account through related records and supporting evidence. It allows the business to explain where an amount came from, what happened to the goods or service, and how the resulting obligation was settled.

Relationships carry meaning

When a quotation leads to an order, the relationship connects the offer to the commitment. When a delivery relates to that order, it connects physical fulfilment to the agreement. When an invoice and payment follow, they explain billing and settlement.

DNA's Document Flow presents the predecessor, successor, and related-document links returned with the transaction. Related records can include allocations and reversal entries as well as the main commercial documents. The value is more than avoiding repeated typing: a recorded link explains how another document relates to the transaction.

Two documents with matching amounts are not thereby linked. Likewise, an empty Document Flow is not enough to prove that no related business event happened. It shows that no links were supplied for that view; the transaction and its supporting records still need to be understood.

Some values are inherited or restricted when documents come from an earlier source. This can preserve the agreed customer, lines, or commercial treatment. A restriction should therefore be understood in relation to the source agreement, rather than treated only as an inconvenience.

A practical example

A contractor orders 30 air-conditioning units. The supplier delivers 20, then 10. The first invoice covers the initial delivery. The second invoice covers the balance. The contractor pays an amount that is allocated partly to each invoice.

An investigation of the order requires both delivery records and both invoices. An investigation of the payment requires its allocations. Looking at only one invoice might incorrectly suggest that the customer was underbilled; looking at only the receipt amount might incorrectly suggest that one particular invoice was fully settled.

Traceability makes the connections explicit. It also makes exceptions visible, such as a delivery without corresponding billing or a payment that has not settled the invoice under discussion.

Supporting documents and conversations

Structured records describe the transaction, while supporting evidence explains its context. An accepted quotation, specification, delivery acknowledgement, or correspondence can explain a decision that a total cannot.

DNA supports attachments in relevant transactions and provides shared document storage. Its document facilities include folder permissions, previews of supported file types, and activity history. Internal folder roles distinguish owners, editors, and viewers. External file-sharing options serve a different purpose and require a deliberate audience decision.

The business value of a shared file is that the relevant people can use the same evidence. Multiple disconnected copies can create uncertainty about which version reflects the agreement. A renamed file is not necessarily a revised agreement, and a conversation does not automatically change a posted transaction.

Evidence should answer a specific question

A delivery acknowledgement supports the fact of receipt. It does not necessarily prove that an installation milestone was accepted. A bank confirmation supports a money movement, but its relationship to an invoice still needs to be established. A signed proposal supports agreed terms, but subsequent authorised changes may also matter.

Good traceability therefore combines references, dates, quantities, amounts, and the purpose of each piece of evidence. It avoids assuming that any attached document proves every aspect of the transaction.

Why this matters beyond disputes

The same connections support handovers, management reviews, and corrections. A colleague can understand the position without relying entirely on the memory of the person who entered the original record. A manager can distinguish a commercial delay from a warehouse delay. Finance can explain an outstanding balance with reference to the actual documents.

The aim is a business history that remains understandable after the immediate activity has finished.