Splitting Account Preparation Between Roles: Who Does Which Step

Editorial team Spend Ledger

Treat preparation as a controlled workflow

Preparing an advertising account involves more than filling in settings. The team must establish which business is responsible for the activity, confirm that payment arrangements are appropriate, configure the account consistently with the business’s plans, and check that the finished setup is accurate and permitted. Dividing this work among roles makes responsibilities visible and reduces the chance that an assumption will pass unnoticed from one step to the next.

An account is a work tool, not a shortcut around a platform’s rules. Whether a business prepares its own account or receives access through an agency arrangement or an acquisition, the team should confirm that the account’s ownership, access, payment method, and intended use are allowed under the platform’s current terms. Any transfer or change in control should follow the platform’s official process where one applies. A handoff inside the team cannot make an otherwise impermissible arrangement acceptable.

A practical workflow separates four responsibilities:

• Business-details coordinator: gathers and checks the information about the business.
• Payment lead: handles billing arrangements and payment setup.
• Account configurator: applies approved settings in the account.
• Reviewer: independently checks the setup and records whether it is ready, needs correction, or requires platform guidance.

One person may hold more than one operational role in a small team, but the review should remain independent of the work being approved. If there is no suitable independent reviewer, the team should identify that as a control gap rather than treating self-approval as equivalent.

The business-details coordinator: establish what is being represented

The business-details coordinator gathers the information the account setup will rely on. This role should not guess, embellish, or make details fit a desired outcome. The information should come from the business’s responsible representatives and records, and it should be consistent with the platform’s current requirements.

The coordinator should assemble the business identity and relevant operating details, clarify who has authority to act for the business, and describe the intended advertising activity in plain language. Depending on the platform and the business, the account may ask for information or documentation to verify identity, business status, website ownership, or other claims. The coordinator’s responsibility is to identify what is needed and provide accurate material through the proper process, not to manufacture evidence or decide that a check can be skipped.

The handoff to the payment lead and account configurator should include a reviewed information pack, with the source and status of each item made clear. It should distinguish confirmed information from items that remain uncertain or are awaiting an official decision. Sensitive records should be shared only through approved, appropriately restricted channels.

The coordinator should also note any relevant account history or existing restriction that the team knows about. That context must not be concealed to secure access or avoid a review. If the business cannot establish that it is entitled to use an account, or if the platform has restricted the account, the next step is to seek clarification through official support or appeal channels—not to reassign the task as a way to bypass the issue.

The payment lead: set up billing transparently

The payment lead handles the financial side of preparation. The role is to confirm that the payment method is authorized for the business and that the billing details match the actual arrangement. The lead should understand who is responsible for charges, who can manage the payment method, and how billing records will be reviewed. These points should be agreed internally before the details are entered.

Payment setup should use truthful information and a method permitted by the platform. The lead should not borrow another party’s payment details without clear authorization, disguise who is paying, or use payment changes to get around a restriction. If a payment method is declined, a balance is disputed, or billing access is limited, the responsible person should investigate the cause through official billing support. Creating another setup to avoid resolving the issue can create further account and business risk.

The payment lead’s handoff should state which billing arrangement was approved, who authorized it, whether setup is complete, and what remains unresolved. It should not expose full payment credentials in an ordinary task note. The configurator needs enough information to select the approved arrangement in the platform, not unrestricted access to financial details.

Current payment requirements, available methods, and billing policies can change. The team should check the platform’s own help and policy pages for current values and requirements rather than relying on an old internal note. If the platform requests additional confirmation, the payment lead should coordinate the response with the business-details coordinator and the person authorized to submit it.

The account configurator: apply the approved plan

The account configurator turns the accepted business and payment information into account settings. This role should work from the documented handoffs, not from informal assumptions or unapproved requests. Before changing anything, the configurator should confirm that the account is the correct one, that the assigned access is legitimate, and that its intended use is consistent with the platform’s terms.

Configuration may include account identity fields, access permissions, billing selection, business relationships, and the structure needed to manage advertising activity. The exact options depend on the platform. The configurator should use only settings that correspond to the actual business arrangement and the team’s approved plan. If a setting is unclear, the proper response is to pause and ask for clarification or consult official guidance—not to select whatever seems most likely to pass review.

Access should be limited to people who need it for their role. The configurator should avoid making broad or permanent access changes for convenience, and should document material changes so that the reviewer can compare the final state with the approved plan. If the account is supplied through an agency or another legitimate business relationship, responsibilities, ownership, access, billing, and support arrangements should be clear in writing and consistent with platform rules.

The configurator’s handoff is a record of what was actually done, not merely what was intended. It should identify the settings applied, any differences from the approved plan, outstanding platform prompts, and any step that could not be completed. The reviewer needs a reliable description of the final state and a way to inspect it without relying solely on the configurator’s summary.

The reviewer: verify independently and record the outcome

The reviewer checks the finished setup against the source information and the approved plan. The reviewer is not there to rubber-stamp the work or to redo every task without context. The purpose is to spot discrepancies, missing approvals, unclear ownership, unsuitable access, inconsistent billing details, and settings that do not match the stated business activity.

A useful review asks whether the account represents the correct business; whether the people with access have an appropriate role; whether the payment arrangement is authorized and accurately represented; whether the account’s structure matches the intended use; and whether any platform notice or verification request remains unresolved. The reviewer should also check that the team has not treated a pending review as approval or interpreted the absence of a visible warning as permission to ignore a known issue.

The reviewer records a clear outcome: ready for the next permitted business step, correction required, or paused pending official guidance. “Ready” means the reviewed setup matches the evidence and applicable instructions available to the team; it is not a promise that the platform will approve the account, accept an advertisement, or leave settings unchanged. If the reviewer finds a discrepancy, the work returns to the relevant owner with a specific correction request.

Where the platform’s own process requires an appeal, identity check, business verification, or support contact, the reviewer should direct the issue to the official channel. The team should preserve relevant records and answer accurately. No internal sign-off can replace a platform decision.

Why preparation and approval should be separate

When one person prepares and approves the same account, a mistake can become hard to see. The person may unconsciously interpret missing information in favor of the work already done, overlook a mismatch, or approve an exception without a second view. Separation creates a useful pause between configuration and use, when errors are less costly to correct.

Independence does not require a large compliance department. In a small team, the business owner or another responsible colleague can review the setup, provided they did not make the configuration decisions being checked and have enough information to challenge them. If staffing makes full separation impossible, use a compensating control: document the reason, have another authorized person review the records as soon as practical, and keep the account inactive for any step that depends on an unresolved approval or policy question.

The reviewer should have access to evidence sufficient to verify the setup, but need not receive unnecessary sensitive information. Access can be read-only where the platform supports it. The team should also record who prepared, who reviewed, what was checked, and what remains open. This creates accountability without turning the process into a claim that every risk has been eliminated.

A disagreement should not be settled by silently changing the record or by asking the configurator to approve their own work. Escalate it to the person responsible for the business relationship or consult the platform’s official guidance. If a restriction or verification requirement is involved, address its cause through the designated support or appeal route.

Make handoffs explicit and easy to trace

A handoff is a transfer of responsibility, not just a message saying that a task is done. Each handoff should identify the sender and recipient by role, the item being transferred, its status, the evidence or source behind it, and any decision the recipient is expected to make. It should also identify unresolved questions and who owns the next action.

For example, the business-details coordinator can pass a verified information pack to the payment lead, noting which details are confirmed and which require follow-up. The payment lead can then pass an approved billing arrangement to the configurator, without sharing credentials through an unsuitable channel. The configurator can return a change record and account view to the reviewer. The reviewer can then return either a correction list or a documented decision to the accountable business representative.

Use a shared record that is access-controlled and maintained as the work progresses. Keep the current version of the plan, evidence references, approvals, and open questions together. Avoid parallel copies that can drift apart. If information changes after configuration, the change should be sent to the relevant roles and the reviewer should decide whether the account needs another check.

A handoff should never imply that the recipient has inherited authority to override a platform requirement. If the account’s status is unclear, pause the dependent work until the team has a reliable answer. Current requirements and values should be checked on the platform’s help and policy pages, since internal records can become outdated.

Draw the split as a responsibility chart

A simple responsibility chart makes the process visible. Put the preparation steps in rows and the roles in columns. Mark who performs the work, who provides necessary information, and who independently reviews or authorizes it. Use role labels rather than personal names so the chart remains useful when staffing changes.

| Preparation step | Business-details coordinator | Payment lead | Account configurator | Reviewer | |---|---|---|---|---| | Gather and confirm business information | Responsible | Informed | Informed | Checks evidence | | Confirm billing arrangement | Provides business context | Responsible | Receives approved details | Checks consistency | | Apply account settings | Answers questions | Confirms billing handoff | Responsible | Reviews final state | | Check readiness and open issues | Clarifies business facts | Clarifies billing facts | Provides change record | Responsible |

The chart is a map, not a substitute for written approval or platform policy. Add a note for the person accountable for resolving exceptions, especially when the account is provided by an agency or another party. Record whether that party controls access, billing, support, or account ownership, and confirm that the arrangement is permitted and documented. If a required responsibility has no owner, or the same person is shown as both preparer and independent approver, the chart has exposed a gap that should be fixed before the team proceeds.

Review the chart whenever the business arrangement, account access, payment responsibility, or platform requirements change. A clear division of work cannot guarantee approval or prevent every problem, but it can help the team notice unsupported claims, resolve uncertainty through the proper channels, and make account preparation more accountable.