Separate the Preparer From the Approver: Acceptance Roles for Ad Accounts

Editorial team Spend Ledger

Why preparation and approval should be separate

An advertising account can look ready while still being unsuitable for work. Campaign settings may be in place, but the recovery contact could be missing, billing details could belong to the wrong entity, or nobody may be able to explain who owns and controls the account. If the same person prepares an account and declares it accepted, these gaps are easier to overlook.

Separating preparation from approval creates a basic check without turning account setup into a large compliance project. The preparer assembles the account and its supporting information. A reviewer who did not make those choices checks whether the account is understandable, usable for the intended work and consistent with platform rules and the team’s records.

This is a process safeguard, not a guarantee that an account will remain available, pass a platform review or deliver a particular result. Platforms may change their policies or request further information. The team remains responsible for using the account lawfully and following the platform’s current requirements.

Define the roles before work begins

The preparer may be an internal team member, an agency working under an agreement, or someone responsible for sourcing an account that the team plans to use. Their job is to gather the required information, make permitted setup changes and record anything the reviewer will need to understand. They should not certify their own work as independently checked.

The approver checks the record against the intended use and the evidence available. This person does not need to repeat every setup task. They should be able to ask questions, request corrections and decline acceptance when ownership, access, billing or recovery arrangements are unclear.

For a small team, roles can be assigned by task rather than by department. The reviewer might be a manager or another responsible colleague, provided they are not simply signing off on their own preparation. If the team cannot arrange an independent reviewer for a particular account, it should record that limitation and use an appropriate alternative control, such as a documented review by the person responsible for the business relationship. The review should not be represented as independent when it was not.

Establish what “ready” means

Acceptance should mean that the account is suitable to enter the team’s ordinary operating process—not that every campaign is approved, that the account is risk-free or that the platform has endorsed the business. Agreeing on this definition prevents a green status from being treated as a promise of future access or performance.

Before preparation starts, record the intended business use and the responsible business entity. Clarify who will control the account, who will administer it and who is responsible for advertising activity. The details should make sense together. For example, a business should be able to explain why the account’s ownership, billing arrangements and recovery contacts relate to the work being conducted.

If the account is sourced rather than prepared internally, check that the arrangement and any transfer or change of control are permitted by the platform’s current rules. Do not assume that possession of login details proves ownership or gives the team a right to operate the account. If the platform requires particular ownership, identity or business verification, follow its process and provide truthful information. Do not try to bypass a restriction, verification request or account decision.

Review access, recovery and ownership

The reviewer should confirm that the team understands who can access the account and why. Access should be limited to people with a legitimate work purpose, and the team should know who can manage permissions. A list of names alone is not enough if no one can explain their role or whether their access is still needed.

Recovery arrangements deserve a distinct check. Confirm that the account has appropriate recovery contacts or methods under the platform’s rules, that the responsible team can reach the people or channels involved, and that those arrangements are not dependent on an unknown former operator. A missing or inaccessible recovery route can turn a routine problem into a continuity issue.

Ownership should be clear in both the account setup and the team’s records. The reviewer should be able to identify the business responsible for the advertising, the party controlling the account and any agency or service provider involved. If those roles differ, document the relationship and the limits of each party’s authority. When ownership cannot be established, or a proposed arrangement conflicts with platform requirements, the account should not be accepted for use until the issue is resolved through legitimate channels.

Check billing details and supporting records

Billing is another area where a second reviewer can catch a mismatch. Compare the billing information available in the account with the business entity that is expected to pay. Check that the person responsible for payment understands the arrangement, that the relevant records are accessible to the business, and that any agency or third-party billing arrangement is documented.

The review is not an instruction to expose payment credentials more widely than necessary. The approver needs enough information to confirm that the arrangement is authorised and coherent, not unrestricted access to sensitive payment data. Follow the platform’s handling rules and the organisation’s own financial controls.

If billing details are incomplete, belong to an unexplained party or do not match the written agreement, pause acceptance. Ask the responsible party to correct the information through the platform’s permitted processes or provide a clear explanation supported by records. Do not change details simply to make them appear consistent, and do not submit information that is false or misleading.

Keep the evidence proportionate. The team might retain an internal note identifying the account, its responsible business, the relevant contacts and where supporting records are held. Avoid copying sensitive information into an informal form when a reference to an authorised record is sufficient.

Use a short acceptance form

A compact form makes the review repeatable without requiring a lengthy audit. It should capture the account identifier using the team’s approved internal method, the intended business use, the preparer, the reviewer and the outcome. It should also provide a place to note unresolved issues and the location of supporting documentation.

A practical acceptance form can ask:

• Is the intended use clear and allowed under the platform’s current rules?
• Is the responsible business and account-control arrangement documented?
• Are access roles understood and appropriate?
• Are recovery contacts or methods present and accessible to the responsible team?
• Do billing details and payment responsibility match the documented arrangement?
• Are any platform requests, restrictions or unresolved issues recorded?
• Is the account accepted, rejected or held pending clarification?

The reviewer should sign off only on what they actually checked. A signature or recorded approval means that the listed checks were completed based on the available information; it does not certify the account’s future status or replace platform review. If the team uses an electronic record, it should preserve who made the decision, what was reviewed and any conditions attached to acceptance.

Current platform requirements can change. Where the form depends on a specific policy, verification process or account feature, consult the platform’s official help and policy pages rather than relying on an old checklist.

Keep the review light for a small team

A useful review is focused, not exhaustive. The reviewer can concentrate on the issues most likely to cause confusion or interrupt work: unclear ownership, inaccessible recovery, mismatched billing and unexplained access. They do not need to re-create the preparer’s work or collect documents the business already keeps in an appropriate place.

Use one shared record and a consistent definition of acceptance. Avoid making the reviewer chase details across informal messages. The preparer can attach concise notes explaining unusual arrangements, while the reviewer records only what was checked, what remains open and who is responsible for resolving it.

The process should also fit the account’s circumstances. A straightforward internal setup may need little explanation. A sourced account or an agency-managed arrangement may need clearer written terms about control, permitted use, billing, access changes and responsibility for responding to platform requests. The review can stay brief while still asking for the information that matters.

Do not let speed turn into automatic approval. If a material fact is unknown, the form should show that the account is pending rather than accepted. This gives a small team a clear boundary without requiring an elaborate approval committee.

What to do when the reviewer rejects

A rejection is a work status, not a punishment. The reviewer should state the reason in practical terms: recovery is not established, billing does not match the documented arrangement, ownership is unclear, access cannot be explained, or the proposed use needs further policy review. The note should identify what information or correction is needed, without suggesting a workaround.

The preparer or responsible business contact can then address the cause through legitimate means. That may involve correcting an authorised billing record, clarifying an agency agreement, restoring access through the platform’s official process or asking the platform’s support or appeal channel for guidance. If the platform has restricted the account or requested verification, follow its stated process. Do not create replacement accounts to evade a restriction, disguise links between accounts or provide false documents.

After the issue is addressed, the account should return to review with the relevant update recorded. The reviewer can then make a fresh decision. If the concern cannot be resolved, keep the account out of active use and document the outstanding reason. An account is a work tool and, where lawfully and permissibly sourced, a purchased good; neither description removes the need for clear control, truthful records and compliance with platform rules.