How records reach the Office
Every inbound record — a contract, a payment, a project, a company's ownership — reaches the Office one of three ways, and is checked the same way whichever it was.
A contract value typed from an award letter is validated exactly as hard as one that arrived over a connection. If the figure is not an amount, it is held back; if the project is not on the register, it is held back; if a payment exceeds its commitment, it is held back. Typing it does not make it true.
What differs between the three
One line against the record. It names which system the record is about, which route it came down, and — for anything that did not come from an interface — the officer who entered it and what they were reading from. That line appears wherever the figure appears, so a reviewer weighing a price against a benchmark can see whether they are looking at something GHANEPS said or something a colleague attested to. Both are usable. The difference matters when two figures disagree, or when somebody asks a year later how the Office knew.
| Route | What it needs | What the record carries |
|---|---|---|
| Live interface | An agreed interface and a credential | Source, extraction time, schema version |
| Controlled file drop | An extract the institution agrees to send | The above, plus the officer who loaded it and what the file was |
| Entered by an officer | A letter, schedule or statement | The above, plus the officer’s name and the document reference |