Grant Application Document Checklist: Cross-Checking Tax and Social Security Certificates

A grant application document checklist works when every certificate in the file is compared with something else: the legal name and company number on the tax certificate against the company register, the issue date against the scheme's cut-off date, and the contribution status against the applicant's own declaration. Collecting a tax certificate and a social security certificate is the easy part. The review work is lining up one field on one document against one field on another document or an official register, and deciding what happens when they disagree. This guide sets out those comparisons for a UK-based grant team, with notes on EU-funded schemes.

This article is for informational purposes only and does not constitute legal, financial, or regulatory advice. Regulatory references are accurate as of the publication date. Consult a qualified professional for guidance specific to your situation.

What should a grant file contain before any cross-check starts?

A reviewable grant file has four document families: identity of the applicant, proof the entity exists, tax and social security standing, and the funding documents themselves. Without the first two, the certificates have nothing to be compared against. The UK government's Find a grant service lists central government schemes, and each scheme sets its own evidence list, so treat the list below as a baseline, not a rule.

Scheme rules decide which tax and contribution evidence is mandatory. The UK has no single document that every grant body accepts as proof of good standing, so the checklist must name the exact evidence the scheme asks for. If a scheme only asks for a signed declaration, say so on the checklist and compare the declaration with what the registers show.

Which fields must agree between the tax certificate and the rest of the file?

The name, the tax identifier and the date on the tax document must each match a second source. These are the comparisons we use as a baseline.

The reviewer rarely rejects on a first mismatch. The usual outcome is a query to the applicant with the two conflicting values side by side, a deadline to answer, and a note on the file recording who replied and when.

How do you compare the social security or contribution evidence?

Contribution evidence answers a different question from the tax document: it shows whether employer and worker contributions are being declared and paid, not whether the company is solvent. In a UK file this evidence is usually payroll-based, so the comparison is between headcount and the scale of the funded project.

• Headcount on the application against the number of employees implied by payroll or contribution evidence. A project budget with eight full-time posts and evidence for two employees needs an explanation.
• Employer name on the evidence against the legal name on the register. Group structures often put payroll in a different company from the one applying.
• Period covered against the scheme's look-back period. A statement ending before the look-back window starts proves nothing about the window.
• Payment arrangements. A document showing an agreed instalment plan is not the same as one showing no arrears. Record which one the scheme accepts.

When the scheme is funded from EU money, a further layer exists. The European Commission runs the Early Detection and Exclusion System (EDES), which backs exclusion decisions under the Financial Regulation. Only public exclusion decisions are visible to outsiders; full access is reserved to EU bodies and people involved in budget implementation. An applicant who does not appear in the public list has not been cleared by EDES. Absence from a public list proves only that no public decision is published.

What does a clean check look like, step by step?

1. Fix the anchors first: legal name, company number, registered address, signatory, from the register, not from the applicant's own documents.
2. Compare each anchor against every certificate and against the form. Record each result as match, mismatch, or not present.
3. Check each date against the scheme window, and note how long each certificate stays usable under the scheme's rules.
4. Check the entity status on the register on the day of review, and again just before payment if weeks have passed.
5. Write the query for any mismatch in one message with both values quoted, and log the reply.
6. Keep the checklist result with the file. A later audit asks what was compared, on what date, and who decided.

A rule that saves time: do not compare documents in the order they arrived. Compare them in the order of trust. Register data first, then documents issued by authorities, then documents prepared by the applicant or their adviser.

What do applicants and reviewers ask on forums?

Practitioners on grant and accounting forums keep returning to a handful of questions. Here are the three most common, answered.

"The certificate says one name and the application says another. Is that a rejection?" Not by itself. A trading name, a recent change of name or a subsidiary in a group all produce this. The reviewer asks for the register extract showing the link and records it. If no link can be shown, the file cannot move forward.

"My certificate is two months old. Will they accept it?" It depends on the scheme, not on a general rule. Some schemes ask for a document dated within a stated number of days of submission, others only for a current declaration. Read the guidance for the scheme, and ask the grant officer in writing if it is silent.

"We owe a small amount and have a payment plan. Are we out?" A plan agreed with the tax authority is a different status from unpaid arrears. Whether it qualifies is a scheme rule. The reviewer's job is to see that the document says what the applicant claims it says.

Where do automated checks help, and where do they stop?

A document validation tool compares fields: names, identifiers, dates, amounts, and where available the registers behind them. It flags that the company number on the certificate differs from the application, or that a date falls outside the window. It does not prove a certificate is genuine, and it does not decide eligibility. That decision stays with the grant officer. The value is speed and consistency on the repetitive comparisons, so the reviewer spends time on the exceptions.

For grant teams processing many applications, CheckFile's funding and financing solution runs these comparisons on the whole file, and the pricing page lists plans. The approach is the same one described in our guide on energy renovation grant documents, and the wider sector method sits in the industry verification guide. For supplier-side certificates, see vendor compliance certificate verification. Our security page describes how documents are handled.

FAQ

What is a grant application document checklist?

It is the list of documents a funder requires, plus the comparisons the reviewer runs between them. A list of documents alone only tells you what to collect; the comparisons tell you whether the file is consistent.

Which documents prove an applicant is up to date with tax and social security?

It depends on the scheme and the country. Some funders require a certificate from the tax authority and one from the social security body, others accept a declaration and check registers. The scheme guidance is the only authority on which applies.

Does a clean EDES search clear an applicant?

No. Only public exclusion decisions are visible, so a clean search shows that no public decision exists. Full access is limited to EU bodies and those involved in budget implementation.

How often should a certificate be re-checked?

At least at submission and before payment. If the award is paid in instalments, repeat the register check at each payment milestone and record the date.

Can software replace the grant officer's judgement?

No. Software compares fields and flags differences. The officer decides whether a difference is an error, an explanation or a reason to refuse.