Filing monitoring
Company Filing Monitoring: How to Track New Official Filings After Onboarding
A practical guide to company filing monitoring after onboarding, including official filing alerts, filing-history APIs, routine versus material filings, source evidence, and review workflows.
Short answer
Company filing monitoring means watching official registries for new filings, notices, or filing-history updates tied to companies you already know. The goal is not to treat every filing as a risk event. It is to detect what changed, classify the filing, attach source evidence, and route material changes to review.
Filing history is one of the most useful official sources for post-onboarding company monitoring. It can show routine annual accounts, confirmation statements, officer appointments, registered office changes, capital changes, insolvency events, dissolution steps, mergers, demergers, and other registry activity.
The hard part is not noticing that a filing exists. It is matching the filing to the right company, deciding whether the filing matters, avoiding duplicate alerts, preserving the source evidence, and making the output usable for a risk, compliance, supplier, merchant, or customer operations workflow.
Why company filing monitoring matters after onboarding
A company can pass onboarding and then change in ways that are visible first through official filings. If your team only runs periodic review, those updates may sit unnoticed until the next scheduled check.
The volume is large enough that manual checking does not scale. In its 2024 to 2025 annual report, Companies House reported a UK register size of 5.43 million companies, 14.7 million total filings accepted, 13.5 million digital filings accepted, and 16.3 billion register accesses during the year.
Filing monitoring helps teams focus on the companies they already care about. Instead of reading a national filing feed by hand, the workflow starts from a known portfolio and turns relevant official activity into reviewable alerts.
What is company filing monitoring?
Company filing monitoring is the process of tracking new official filings, notices, and filing-history updates for a confirmed company record over time.
A useful workflow should:
- Start from known companies, such as customers, merchants, borrowers, suppliers, or vendors.
- Resolve each company to the correct official registry record.
- Ask for confirmation when a name-only match is uncertain.
- Monitor filing histories, registered notices, update feeds, or announcement services.
- Classify filings into reviewable signal types, not just raw registry codes.
- Attach source evidence so a reviewer can verify what happened.
For the API pattern behind this flow, see the company monitoring API guide.
Which company filings should teams monitor?
Filing names vary by country, but the practical categories are similar: routine compliance filings, legal-entity changes, governance updates, risk events, and source documents that support a deeper review.
Annual accounts and financial statements
Accounts and financial statements are often routine, but they still matter because they can refresh financial context and prove that a company has met a registry filing obligation. GOV.UK's accounts filing guidance says company officers are legally responsible for preparing and delivering accounts to Companies House on time.
A monitoring workflow should usually record accounts filings as source-backed activity, then let policy decide whether the filing needs human review.
Confirmation statements and annual returns
Confirmation statements can confirm or update important company details. GOV.UK's confirmation statement guidance says Companies House may issue a penalty and the company may be struck off the register if a confirmation statement is not filed.
For monitoring, the useful alert is not just "CS01 filed." It should tell the reviewer whether the filing appears routine or whether it coincides with a status, address, capital, officer, or control-context change.
Director, officer, and signatory filings
Officer changes are often more actionable than routine filings because they can change who controls, manages, or signs for the company. See the director change monitoring guide for a deeper workflow.
Registered office and identity filings
Address, name, domicile, and identity-detail filings can affect operational records and matching. See the registered office address change monitoring guide for how to review these changes without treating every address update as high risk.
Capital, merger, demerger, and structure filings
Capital and restructuring filings can indicate changes to a company's legal structure. They should usually trigger a review when the relationship depends on exposure limits, ownership context, credit policy, supplier criticality, or a previously approved company profile.
For capital-specific examples, see the share capital change monitoring guide.
Insolvency, liquidation, dissolution, and strike-off filings
These filings and notices are usually the highest-priority review triggers because they can affect whether a company is still active, solvent, or able to continue the relationship. See the company status change monitoring guide for status-focused handling.
Where official filing-monitoring data comes from
The strongest sources are official registries, filing histories, registered-notice APIs, announcement services, and registry update feeds. The exact shape depends on the country.
Companies House filing history and stream
Companies House exposes company filing history through its public data API. Its filing history stream returns filing history information such as form type, description, and dates.
The official API is powerful, but it still leaves teams to handle matching, polling or stream recovery, rate limits, classification, deduplication, and delivery. Companies House's rate-limit guidance says clients can make up to 600 requests within a five minute period.
PRH registered notifications in Finland
Finland's PRH publishes Trade Register public notices and open data for registered entries. PRH explains that its open data service lets users search, browse, and download data from the Trade Register's public notices in machine-readable format.
PRH's registered-matters statistics show why this source matters at scale: in 2025, PRH listed 191,940 changes to company or corporation details, 309,634 financial statements, and 57,635 notifications of beneficial owners among registered and processed Trade Register matters.
Brreg updates and announcements in Norway
Norway's Bronnoysund Register Centre publishes open data and announcement services. Its Enhetsregisteret API documentation describes update types for new, changed, deleted, and removed entities.
Brreg's announcement subscription page says users can subscribe to daily or weekly updates for specific organisation numbers, including changes of names and addresses, roles and capital, approved annual accounts, merger and demerger, dissolution, bankruptcy, compulsory liquidation, and debt settlement proceedings.
A filing alert is not the same as a filing review
A filing alert says that an official source changed. A filing review decides whether the change matters for a specific customer, merchant, supplier, borrower, or partner.
This distinction prevents alert fatigue. If every accounts filing, confirmation statement, and routine notice goes to the same urgent queue, reviewers stop trusting the feed. The better pattern is to classify the filing first and route it by policy.
| Filing type | Usual priority | Review question |
|---|---|---|
| Annual accounts filed | Low to medium | Does the filing change financial or credit context? |
| Confirmation statement filed | Low to medium | Did the company confirm details or update something material? |
| Director or officer change | Medium | Does the change affect approved control, signing, or relationship records? |
| Address or name change | Low to medium | Does the new identity detail conflict with onboarding records? |
| Capital or restructuring filing | Medium to high | Does the event affect exposure, ownership context, or structure? |
| Insolvency, liquidation, dissolution, strike-off | High | Does the company remain eligible for the relationship? |
What a useful company filing alert should include
A useful filing alert should let a reviewer understand and verify the change without repeating the registry search from scratch.
Useful alert fields include:
- internal customer, merchant, supplier, or vendor ID
- official company name, country, and company ID
- official source name
- filing type, notice type, or registry event type
- filing date, publication date, and detected date
- transaction ID, notice ID, barcode, or source reference
- source URL and document URL when available
- normalized signal type and severity
- plain-English summary of what changed
- previous and current values when the source provides them
If a source only proves that a filing happened, say that clearly. Do not invent values, risk scores, or conclusions that are not present in the source evidence.
How to operationalize company filing monitoring
The simplest filing-monitoring workflow starts with the companies your team already knows and turns official source changes into a clean review feed.
- Upload a known company list or send companies through an API.
- Match each company to an official registry record using the official company ID where possible.
- Confirm uncertain matches before creating a watch.
- Poll filing histories, read update feeds, or consume registry streams where available.
- Normalize raw filing types into signal categories that a reviewer understands.
- Deduplicate repeated source events so one filing does not create multiple noisy alerts.
- Attach source evidence and send the alert to the right queue, API feed, CSV export, or operational inbox.
Churnscan is built around this known-company workflow: resolve the company, confirm ambiguous matches, create a watch, poll official sources, and return matched signals with evidence.
Company filing monitoring vs periodic review
Periodic review asks "what does this company look like at the next scheduled checkpoint?" Filing monitoring asks "what official source activity happened since we approved it?"
| Question | Periodic review | Filing monitoring |
|---|---|---|
| When does it run? | On a fixed review cycle | Whenever official source activity is detected |
| What does it catch? | Known checklist items | New filings, notices, and registry updates |
| What is the source? | Questionnaires, documents, internal records | Official registry filings, notices, APIs, and feeds |
| What is the output? | A refreshed assessment | A source-backed review trigger |
| Best use | Broad reassessment | Keeping approved company records current |
Common mistakes in company filing monitoring
- Starting from names only: company names can be ambiguous. Use official IDs where possible and ask for confirmation when matching is weak.
- Alerting on every raw code: reviewers need plain signal categories, not untranslated filing codes.
- Ignoring routine filings: routine does not mean useless. Accounts and confirmation statements can still refresh the official record.
- Over-escalating routine filings: not every filing belongs in a high-priority queue.
- Losing source evidence: every alert should keep the official source URL, notice, filing reference, or document link when available.
- Confusing detection with decisioning: a filing alert should support review. It should not pretend to be a complete risk decision.
Frequently asked questions
What is company filing monitoring?
Company filing monitoring means tracking official registry filings, notices, or filing-history updates for companies that have already been approved, onboarded, or added to a portfolio.
Which company filings should teams monitor after onboarding?
Teams should monitor filings that can change the approved company record, including accounts, confirmation statements, officer changes, address changes, status changes, insolvency events, capital changes, mergers, demergers, and important registry notices.
Is every new filing a risk alert?
No. A new filing is a source-backed event, not an automatic risk decision. Routine filings may only need recordkeeping, while insolvency, dissolution, director, address, or capital filings may need review.
Can Companies House data be used for filing monitoring?
Yes. Companies House exposes filing history through its public data API and also provides a filing history stream that returns filing history information such as form type, description, and dates.
What should a filing alert include?
A useful filing alert should include the official company ID, filing or notice type, source, publication date, detected date, transaction or notice reference, source URL, document link when available, and a plain-English summary.
Source trail
This article was written from official registry documentation, government guidance, and Churnscan product context. Useful source starting points:
- Companies House annual report and accounts 2024 to 2025
- Companies House Public Data API filing history reference
- Companies House filing history stream reference
- Companies House API rate-limit guidance
- GOV.UK accounts filing guidance
- GOV.UK confirmation statement guidance
- PRH Trade Register public notices and open data
- PRH registered and processed Trade Register matters statistics
- Brreg Enhetsregisteret open-data API documentation
- Brreg subscription to announcements
Monitor new official filings after onboarding.
Use Churnscan to upload a company list or connect by API, resolve companies to official records, and monitor filing, status, governance, address, capital, liquidation, insolvency, and bankruptcy changes.