# Microsoft Ads Setup: Ownership, Access, Billing and Verification

> Prepare owned accounts, least-privilege access, advertiser verification and billing controls before advertising.

Source: https://mentionx.ai/learn/microsoft-ads/microsoft-ads-account-access-billing-verification  
Author: Dipuck Jones, founder of MentionX  
Updated: 8 November 2026  
Level: Practitioner

**A safe Microsoft Advertising setup keeps account ownership, user permissions, advertiser identity and payment responsibility explicit. A campaign can be technically editable while its operator still lacks authority over billing, verification or the merchant's assets.**

> **Key takeaways**
> - Give people individual access and the least privilege required for their work.
> - Distinguish account roles from bill-to-party ownership and manager relationships.
> - Follow the account's current verification notice rather than assuming one global deadline.
> - Reconcile billing documents separately from campaign performance and budget pacing.

*Checked 8 November 2026 (CET) against Microsoft's access, verification and billing documentation. Operating recommendations are editorial judgement. Ledgerline and all example arrangements and figures are fictional and illustrative.*

## Who should own the account and its relationships?

The merchant should know which legal entity advertises, which account contains delivery history and which organisation pays. Record the account identifier, account name, manager relationship, primary contact, business domain and accountable internal owner. Do not put passwords, recovery codes or payment-card details in this register.

An agency relationship should use authorised account or manager access rather than a shared employee login. Individual identities make role removal, incident investigation and change ownership easier. The agency's operational convenience does not justify making the advertiser dependent on one external person's credentials.

Distinguish ownership of the advertising account from ownership of connected assets. A Merchant Center store, website, tag-management container, commerce integration and CRM connection can each have separate administrators. A campaign owner who cannot identify the UET implementation owner has an incomplete setup even if ads can be created.

The [Google Ads account setup checklist](https://mentionx.ai/learn/google-ads/google-ads-account-setup-checklist) provides a transferable governance perspective. Do not copy its role names or billing permissions into Microsoft procedures. The destination platform's current permission table and bill-to relationship govern what an operator can actually do.

## Which role fits each job?

Microsoft documents Super Admin, Standard User, Advertiser Campaign Manager and Viewer roles. The role and the accounts assigned to the person both matter. A powerful role on the wrong account does not authorise work on the intended merchant.

| Role | Suitable responsibility | Important restriction to review |
| --- | --- | --- |
| Super Admin | Account-wide administration and critical ownership tasks | Reserve for accountable people, not every collaborator |
| Standard User | Campaign work and selected administrative or billing visibility | Cannot manage payment methods or Super Admin users |
| Advertiser Campaign Manager | Campaign operations on assigned accounts | Billing management is outside the role |
| Viewer | Audits, reporting and independent review | Read access does not permit campaign edits |

Microsoft's detailed guidance allows Standard Users to invite or remove certain non-Super-Admin roles. Therefore, “only Super Admins can ever manage users” is too broad. Conversely, being able to invite a campaign collaborator does not mean a Standard User can appoint a new Super Admin.

Use a job-based access request: named person, named accounts, role, reason, expiry or review date and approver. For an analyst who only reconciles reports, Viewer may be sufficient. For a campaign operator, a campaign-focused role may avoid unnecessary administrative exposure. Require stronger access only when the specific task needs it.

## How should manager access and handovers work?

A manager link is a formal relationship, not a substitute for understanding ownership. Document who requested and accepted it, which accounts it covers, who can unlink it and whether billing responsibility changes. Microsoft requires appropriate administrative authority for manager-link requests; do not assume any campaign editor can establish them.

Before an agency transition, inventory scheduled imports, automated rules, reporting recipients, audience sharing, conversion-goal scope and integrations. Removing a user's login does not necessarily remove automation configured while that person worked on the account. A surviving import schedule can continue overwriting local decisions after the contract ends.

Agree the handover evidence before removing access. It should include the current campaign map, measurement contract, outstanding verification issues, payment ownership and change log. Keep secrets in the approved credential system, not in the handover document. A screenshot showing a role is useful only if the account and date are visible and personal details are appropriately redacted.

For emergency continuity, make sure the organisation has a documented recovery route and more than one appropriately authorised internal contact where its policy permits. This is not a recommendation to create spare unauthorised identities. It is a reminder that access continuity belongs to the advertiser, not to a departing contractor's inbox.

## What does advertiser verification require?

Microsoft's advertiser identity verification process depends on the account, location and whether the advertiser is an individual or business. Use the notice and workflow shown for the actual advertiser. The course cannot provide a universal document checklist or promise a review time that applies to every market.

Prepare consistent legal information: the business name, address, domain relationship and other evidence requested in the current process. A trading name on the website and a different legal name on documents can require explanation. Do not improvise a substitute entity or alter facts to get through review.

Appropriately authorised Super Admin or Standard User owners, or eligible linked partners, may submit through the documented process. Identity documents should go only through the approved official workflow. Never request that a colleague paste identity scans into a general campaign brief or public support thread.

Verification can affect serving. Microsoft's documentation identifies EEA serving consequences and cases where particular payment methods require verification before ads run anywhere. Special sectors or jurisdictions can add requirements. Treat a notified restriction as a launch blocker, not as an inconvenience to evade with another account.

Changes to business information can affect verification status. Include legal-name, address and ownership changes in the operating change process. Record the current status, required action, responsible person and actual notice deadline. Do not rely on a generic historical deadline copied from an onboarding article.

## How do billing arrangements differ from budgets?

Microsoft's Billing Summary distinguishes prepay balances, postpay threshold amounts and monthly-invoice activity. These are payment arrangements, not interchangeable campaign-spend controls. Availability depends on the advertiser and billing setup; monthly invoicing is not an entitlement simply because it appears in documentation.

A postpay billing threshold determines when a charge can be initiated. It is not the maximum amount campaigns may spend. Prepay requires attention to available funds and interruptions, while an invoiced account needs invoice reconciliation and payment ownership. None removes the need for campaign budgets and monitoring.

Role permissions and bill-to-party ownership interact. A user can have a suitable role yet still lack access to particular billing tasks or documents because another customer is responsible for payment. Escalate to the actual bill-to owner rather than granting broad campaign permissions in the hope that invoices become available.

In an illustrative Ledgerline arrangement, the merchant pays Microsoft directly and an agency manages campaigns. The agency's performance report is not proof that the merchant's card charge matches the reported media cost. Finance should reconcile platform documents, taxes, credits, adjustments and the relevant service period independently.

## What should finance reconcile?

Use the correct account, currency, date range and document type. Campaign spend, an amount currently due, a payment received and an invoice total answer different questions. Taxes, credits, billing timing and unbilled activity can create legitimate differences.

Microsoft notes that filtering the billing table does not change the header summaries. This is a practical source of false discrepancies: an operator filters one account or document group, then compares that subtotal with a summary still covering a broader set. Record the scope of both numbers before concluding that something is wrong.

Allow for reporting and processing delays without treating every mismatch as harmless. Define an internal reconciliation cadence and an escalation threshold based on the business's exposure, not an invented platform guarantee. Preserve document identifiers and the relevant account context for support.

Do not attempt to solve a payment problem by repeatedly replacing cards, creating duplicate accounts or making unapproved payments. The responsible finance or account owner should investigate the official billing status and available resolution route. Campaign operators should know when to pause expansion while that investigation is open.

## Which account settings need early decisions?

Review currency, time-zone conventions, legal identity and primary contacts before launch or import. Microsoft's import guidance notes that changing account currency requires a new account, so a casual setup choice can create avoidable migration work. Do not promise that every foundational field is freely editable later.

Document how the advertising time zone relates to finance and analytics reporting. For a Berlin-based review, convert timestamps into the agreed Europe/Berlin zone and account for daylight-saving changes when comparing periods. A billing document's own service dates should not be silently reinterpreted as campaign event dates.

Choose notification recipients who will act on them. Verification, billing and serving notices are operational signals, not newsletter subscriptions. The primary contact must remain appropriate when a team changes. Test the internal escalation route with a hypothetical notice so responsibility is clear before an actual interruption.

> **Pro move:** Keep an access-and-obligation map, not merely a user list. For each critical task, identify the person with authority, the person who performs it and the evidence that confirms completion.

## Worked example: Ledgerline

Ledgerline inherits an account where a former agency contact is the primary operational contact, finance cannot locate invoices and the new analyst has been offered a shared login. No actual account changes occur in this illustrative exercise.

The team first separates three issues: access, payment responsibility and notification ownership. It requests individual Viewer access for the analyst, confirms the internal Super Admin and identifies the bill-to party. It also checks the current verification notice instead of assuming the previous agency completed every requirement.

### Walkthrough

1. Record the intended advertiser, account identifier and domain without collecting credentials.
2. Match each collaborator's job to the narrowest appropriate role and account scope.
3. Verify who owns payment documents and who may change payment methods.
4. Inventory imports and integrations that might survive a user-access change.
5. Draft a handover and notification update for authorised administrative review.
6. Reconcile one illustrative billing period using scoped documents, credits and tax treatment.

The output is a controlled remediation plan. It does not authorise the analyst to remove users, submit identity documents or alter billing.

## Common mistakes

Giving every employee Super Admin access creates avoidable exposure. Giving nobody durable internal administrative ownership creates the opposite problem. Least privilege requires matching authority to responsibilities, not choosing the weakest or strongest role indiscriminately.

Another mistake is treating an agency's access as proof that the merchant owns all linked assets. Check Merchant Center, UET, commerce and CRM relationships separately. A final mistake is calling a billing threshold a spending cap, which can leave finance surprised by perfectly valid campaign delivery.

## Try it yourself

Build an access-and-billing register from existing authorised records or a fictional account. Include user role, account scope, primary contact, bill-to party, verification status, connected-asset owner and review date. Use placeholders instead of personal identifiers in any shared exercise.

Choose two hypothetical incidents: a verification notice and an unexpected charge. Write who receives each, which evidence they need and who may take corrective action. If either route depends on a former contractor or an unknown payment owner, mark it unresolved before launch.

## Quick quiz

**1. Can a Standard User manage Microsoft Advertising payment methods?**

*Answer:* No. Microsoft's role guidance restricts payment-method management even though Standard Users can perform some campaign and administrative tasks.

**2. Is a postpay billing threshold a campaign spending ceiling?**

*Answer:* No. It concerns charging, while campaign budget behaviour and spend monitoring are separate controls.

**3. Does filtering Billing Summary's table necessarily filter its header totals?**

*Answer:* No. Microsoft specifically distinguishes table filters from the scope of the summary figures.

## What should be documented before import?

Confirm the correct account, authorised owner, access scope, payment responsibility and current verification status. Resolve foundational uncertainty before copying campaigns into an account the merchant cannot govern.

Previous: [Microsoft Ads Strategy: Inventory, Intent and Economics](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-strategy-inventory-economics) · Next: [Microsoft Ads Google Import: Mapping, Checks and Safe Cutover](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-google-import-mapping-cutover)

Or return to the [Microsoft Ads for Marketers track](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-for-marketers).

Related: [Microsoft Ads Strategy: Inventory, Intent and Economics](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-strategy-inventory-economics) · [Microsoft Ads Google Import: Mapping, Checks and Safe Cutover](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-google-import-mapping-cutover) · [Microsoft Ads Experiments: Troubleshooting and Monthly Ops](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-experiments-troubleshooting-operations)

## Common questions

**Can Standard Users manage payment methods?** No. Microsoft distinguishes campaign and selected administrative permissions from payment-method management. Bill-to-party ownership can impose additional restrictions.

**Should an agency use a shared merchant login?** Use authorised individual or manager access instead. Record ownership, account scope, integration responsibilities and the handover process without sharing credentials.

**Is advertiser verification identical in every country?** No. Requirements depend on the advertiser, account and location. Follow the current official account notice and workflow rather than a universal document list or deadline.

## Sources

- [How do I give someone access to my Microsoft Advertising account?](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_ssuserroles)
- [Advertiser identity verification](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_advertiseridentityverification)
- [Billing Summary in depth (enhanced)](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_billingtabenhanced)
- All accessed 8 Nov 2026 (CET).

## Frequently asked questions

### Can Standard Users manage payment methods?

No. Microsoft distinguishes campaign and selected administrative permissions from payment-method management. Bill-to-party ownership can impose additional restrictions.

### Should an agency use a shared merchant login?

Use authorised individual or manager access instead. Record ownership, account scope, integration responsibilities and the handover process without sharing credentials.

### Is advertiser verification identical in every country?

No. Requirements depend on the advertiser, account and location. Follow the current official account notice and workflow rather than a universal document list or deadline.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/microsoft-ads/microsoft-ads-account-access-billing-verification