PVARA's Documentation Standards for NOC Submissions

An NOC application can be substantively correct and still create friction at the review stage if the documents behind it are formatted the wrong way. Regulation 8A of the PVARA No Objection Certificate Regulations 2025 sets five specific documentation standards that apply to everything an applicant submits, separately from the substance of the AML/CFT framework itself.

This article reads Regulation 8A as published and sets out exactly what each of the five standards requires.

What is Regulation 8A of the NOC Regulations?

Regulation 8A, titled “Documentation Standards,” is a short provision sitting immediately after Regulation 8’s list of the nine required AML/CFT framework components. Where Regulation 8 governs what an applicant’s documents must say, Regulation 8A governs how those documents must be prepared and presented before they reach PVARA. The provision applies to “all documents submitted to the Authority” — not only the AML/CFT policy set, but the full body of material an applicant files as part of its No Objection Certificate application.

The Regulation states:

All documents submitted to the Authority must: (a) be written in English or Urdu; (b) include version control; (c) be paginated and indexed; (d) be submitted in a searchable electronic format; and (e) include written evidence of Board approval where required.

What are the five documentation standards, in detail?

Five requirements, each addressing a distinct risk in how a large regulatory submission can go wrong if left unstructured.

1. Language. Documents must be written in English or Urdu. A policy drafted in another language for a foreign parent’s global compliance suite must be translated before submission — the Regulation does not provide for submission in the original language with a translation appended, only that the document itself “be written in” one of the two accepted languages.
2. Version control. Every document must include version control. For a submission built from documents that were drafted, revised and re-approved multiple times before filing, this means each document needs a visible version number or revision history showing which draft is the final, board-approved version — a live concern given that Form A4’s declaration requires the CEO and MLRO to certify that submitted documents are “final versions, approved by the Board and operationally implemented.”
3. Pagination and indexing. Documents must be paginated and indexed. This is a practical requirement rather than a substantive one, but it is stated as a hard rule, not a preference — an unpaginated or unindexed submission does not meet the standard as drafted.
4. Searchable electronic format. Documents must be submitted in a searchable electronic format. A scanned image of a printed and signed document, without an accompanying searchable version, does not satisfy this requirement on its own — the Regulation requires the format itself to be searchable, which a flat image file typically is not.
5. Written evidence of Board approval, where required. Documents must include written evidence of Board approval where required. Regulation 8.2(a) requires the AML/CFT Policy specifically to be “approved by the Applicant Board,” and Form A4’s Section 3 separately requires “a Board resolution evidencing such approval” to be attached to the application — so for at least the AML/CFT Policy, this fifth standard is not optional.

Standard	What it requires	Where it bites hardest
(a) Language	English or Urdu	Foreign-parent policy documents drafted in another language
(b) Version control	Visible version number or revision history	Documents revised multiple times before final board sign-off
(c) Pagination and indexing	Numbered pages, indexed structure	Long, multi-part submissions such as the AML/CFT framework set
(d) Searchable electronic format	Text-searchable file, not a flat scan	Scanned and signed paper documents
(e) Written evidence of Board approval	Attached board resolution	The AML/CFT Policy under Regulation 8.2(a) and any document “where required”

Why does “where required” in item (e) matter?

Because it makes item (e) conditional rather than universal, unlike items (a) through (d), which apply to “all documents submitted to the Authority” without qualification. The Regulation does not itself define which documents fall within “where required” beyond the AML/CFT Policy’s explicit board-approval requirement at Regulation 8.2(a). Our reading is that any other document the Regulations separately describe as needing board approval — for example, the outsourcing policy referenced in Form A4’s Section 1 confirmation table, which is listed there as part of the board-approved framework set — would also trigger item (e). Where a document’s own governing provision does not mention board approval, item (e) does not appear to impose one by itself; it is a formatting instruction that follows the substantive requirement rather than creating a new one.

How does Regulation 8A connect to the rest of the application process?

It sits underneath the entire Annex A form set. Form A1 — the Application for AML Registration — is the primary submission document and, per Regulation 15.1, must be accompanied by “all required documentation.” Every one of those accompanying documents, from the AML/CFT Policy to the Outsourcing Register at Form A5, is subject to Regulation 8A’s five standards regardless of which specific form or policy it is. Regulation 15.2 separately allows the Authority to specify electronic submission requirements from time to time, which our reading takes as PVARA retaining the ability to add further technical detail — file formats, size limits, submission portals — on top of the baseline standards Regulation 8A already fixes.

The connection to assessment is direct. Regulation 16.1 lists the matters PVARA evaluates during the NOC review, including “adequacy and operational readiness of the AML/CFT Framework” and “governance and internal control arrangements.” A framework that is substantively strong but arrives without version control, pagination, or a searchable format is harder for PVARA’s assessors to work through in the sixty-calendar-day decision window that Regulation 17.1 sets for the Authority — and Regulation 15.1’s language that “incomplete applications may be delayed or returned” gives the Authority room to treat a poorly formatted submission the same way it treats a substantively incomplete one.

What should an applicant do before filing?

Four checks, applied to the full document set rather than to any single form:

• Run a language check across every document, including any policy inherited from a foreign parent, and translate into English or Urdu before submission rather than after a query from PVARA.
• Assign a version number and revision date to every document, and retain the version history internally so the “final, Board-approved version” referenced in Form A4 is traceable back through its drafts.
• Paginate and index the full submission as a single package, not document by document in isolation, so a reviewer working through a cross-referenced AML/CFT framework can move between the policy, the CDD procedures and the risk assessment without losing their place.
• Convert every signed document to a searchable electronic format, keeping the signed paper or wet-ink version as a separate evidentiary record rather than as the only file submitted.

Getting Regulation 8A right does not, on its own, secure an NOC — the substance still has to satisfy Regulation 8’s nine components and the fitness-and-propriety standard applied to Key Individuals. But a submission that fails Regulation 8A’s formatting standards risks slowing an otherwise strong application down before its substance is even reached, inside a review window PVARA is bound by a fixed number of days to complete.

Related reading

• PVARA Exchange License: Capital, Rules & Obligations 2026
• PVARA Transfer & Settlement License: Crypto Payments 2026
• The PVARA Licensing Gold Rush: Pakistan’s Crypto Frontier

About this analysis

This analysis was prepared by the CoinConnect research desk from Regulations 8.2(a), 8A.1, 15.1, 15.2, 16.1 and 17.1 of the PVARA No Objection Certificate Regulations 2025, together with Form A1 and Form A4 at Annex A, read as published. Where practice is not yet settled or guidance has not been issued, that is stated in the text above.

Regulatory positions change and specific requirements should be verified against the current position published by the relevant authority before you act on them. This is information and analysis, not legal advice, and it does not create an advisory relationship. Take professional advice on your own circumstances.