What happens to a case number when a case has several parts

One matter, several records, several numbers

People reasonably expect a matter to have a number in the way a person has a name. What actually happens is that a matter generates records, and records generate identifiers, so a single situation can easily acquire four or five numbers that all legitimately refer to parts of it.

A relationship may have an account number. A request within it gets a case reference. A document produced along the way carries its own identifier. A payment has a transaction reference. Correspondence may be numbered separately again. None of these is the real one; each addresses a different object, and the object it addresses determines what quoting it can achieve.

Identifiers follow the thing that has a lifecycle

The rule underneath this is that anything with its own beginning, middle and end tends to get its own identifier. A case opens, is worked and closes, so it needs a handle. A payment either succeeds or fails, so it needs one too. The account persists across all of it, so it has a stable identifier of its own that does not change when individual cases come and go.

This is why an account number cannot tell anybody what stage your request has reached. It identifies the wrong object. It points to the durable relationship rather than to the piece of work, and the piece of work is where status, ownership and progress actually live.

Parent and child references, and the suffix that means something

When one matter has several strands, the usual pattern is a parent reference with children hanging beneath it. You see this in the suffixes: a base number with a dash and a sequence, or a letter appended, each identifying one component of a larger whole.

The important consequence is that the parts can be in different states at the same time. One strand is closed while another is under review; one has been decided and another is waiting on a third party. Being told your case is closed can therefore be accurate about a child reference and quite wrong about the matter as a whole, and this genuinely confuses conversations unless somebody establishes which level is being discussed.

Linked is not the same as merged

Two related records can be connected in more than one way, and the difference is significant. A link is a cross-reference: both records continue to exist, each keeps its own status and its own owner, and the link tells a reader that the other one is relevant. A merge is a consolidation: one record survives, the other is closed with a pointer to it, and future activity happens in a single place.

Merging is used sparingly because it is difficult to reverse and because it can bury history. Linking is cheap and leaves both trails intact, so it is the default, and it produces the familiar situation where two teams each hold a live reference for what you regard as one problem. Both are correct. They are working on different records that happen to be about the same thing.

Duplicates arise for a mundane reason

A second reference for the same matter usually appears because a new contact arrived through a channel that could not see the existing case: a form submitted while a call was open, an email that generated its own ticket, a visit to a different office. Systems open a record when something arrives, because failing to record an arrival is the worse error.

Duplicates aren’t harmful in themselves; they become harmful when work happens twice, or when two people reach different conclusions on the same facts and both are recorded. Flagging that you already have a reference, early in any new contact, is the cheapest available way to prevent that, and it is a piece of information staff are usually pleased to receive.

Which number to quote, and when

The practical approach is to keep all of them, labelled with what each was given for and by whom, and to lead with the one that matches the question. For progress on a request, quote the case reference. For anything about money, quote the transaction or invoice reference. For anything about the underlying relationship, quote the account.

And when a number does not produce a result, the useful next question is which type of reference the person can search on, because many systems can only look up one kind. A reference that fails is often the right reference offered to the wrong search box, which is a much easier problem to fix than a record that has gone missing.