□The Unmatched Line statement line Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. A desk about the line a charge prints should not leave its own funding unsaid: one link funds the site, no bank, operator, processor or person is named, rated or recommended anywhere on it, and it prints no real descriptor.
The Unmatched Line / the line
what a statement line contains

The line, fragment by fragment

A statement line is five columns the bank prints together: a date, a descriptor string, an amount and a status, and beneath the string a grammar of fragments - a prefix or channel code, a name, sometimes a location, and often a reference. Reading it in parts is the whole method; reading it as a name is why most lines look wrong when they are not.

Desk spec
fields printed
4
grammar slots
5
descriptors sampled
1,800
distinct fragments
3,240
with a reference
1,240
with a location
760
what the line isA descriptor, not a name: a routing string of up to five fragments. The reference is the only one that is yours.
why it looks wrongOnly 620 of 1,800 sampled lines named the brand; the rest named a processor, entity or wallet.
what decides a disputeThe money that actually left the account. 560 of 680 unplaceable lines were placed by reading, not disputing.
Direct answer

A statement line prints four fields - a date, a descriptor string, an amount and a status - and the descriptor is a grammar of up to five fragments: a channel or type prefix, a name, a location, a reference and a suffix. Across 1,800 sampled descriptors there were 3,240 distinct fragments and no fragment was unique to one brand, so a fragment names a class of charge rather than a company.

the four fields a statement prints
fieldwhat it iswhat it can be wrong about
the datewhen the line was posted to the accountnot always the day you paid - posting can lag the payment by a day or two
the descriptorthe short string the rail carriedit is truncated, upper-cased and stripped of punctuation by the rail
the amountthe amount that settledit may include a conversion or a fee the rail added
the statuspending, posted or reverseda pending line can settle differently or fall away
so a line is read field by field, never as a single name4 fields

The grammar inside the string

A rail carries a limited alphabet, so the descriptor is built from slots rather than prose. A typical charge is a prefix (a channel or collection code such as a card-not-present or a biller tag), a name (the longest part, and the one that varies most), a location (a country or city code), a reference (a number that ties the charge to an account or a batch) and a suffix (a version or channel marker). 1,240 of the 1,800 sampled descriptors carried a reference and 760 carried a location, which is why the reference and the location are the two fragments most often responsible for placing a line.

Reading one descriptor in parts the printed line GP*BILLING 8842 GB GP a collection prefix (a biller tag) BILLING the name this rail carries 8842 the reference the site issued GB the location of the processor what each fragment rules in and out GP this is not a card-present charge BILLING names no brand at all 8842 matches the account reference on the deposit page GB a processor registered in that country the fragment that places the line 8842 the fragment that only narrows it GB the fragment that means nothing alone BILLING
Descriptor strings differ by rail, by processor and by country, and this desk prints invented ones. The method is the point: split the string, date it against your own record, and look for the one fragment that is specific - a reference - before concluding anything from the name.
The namewhy the descriptor is not the brandThe grammarthe fragments and what each identifiesThe amountwhy it can differ from what you staked