Make the account trajectory useful to regional and finance teams
Google Ads budget pacing for enterprise teams: connect the current trajectory to accountable spending decisions
Understand completed spend, the recent daily rate and the projected period-end position. Keep account scope and regional calendars clear, then review the business response before authorising an eligible live budget change.
Define the enterprise spending mandate
Enterprise budget pacing starts with the decision the organisation needs to make. A division may have a firm spending allowance, a flexible growth envelope or a launch allocation expected to concentrate around particular dates. These arrangements can produce similar spend charts while requiring different responses. The pacing observation becomes useful when the team knows which mandate applies and who can approve a departure from it.
A request to stay close to a selected allowance is different from an instruction to spend every available unit of currency. The latter can encourage unnecessary acceleration when demand is weak. State whether unused allowance is acceptable, whether extra spending requires a finance decision and whether the account has commitments outside the advertising team's control. This business context cannot be inferred from a daily cost series.
The practical question is whether the current trajectory remains appropriate for the current plan. A projection above the allowance can be an expected consequence of a planned promotion. A projection below it can be a warning that a launch has not begun delivering. The same deviation deserves different attention depending on the intended trading pattern and the organisation's priorities.
Use ppctor to establish the account evidence and present that decision clearly. Keep the monitoring result separate from a live edit. Reading the pace should not silently change campaign budgets, stop campaigns or redefine the selected allowance. Those actions require their own explicit scope and the appropriate review.
Assign the allowance to the correct account
The saved pacer evaluates a connected Google Ads account. That account may represent one region, several brands or a mixture of acquisition and retention activity. A department's internal allocation is not automatically equivalent to the account's complete allowance. Establish the account-to-business mapping before interpreting the result as a divisional spending position.
If two business units share an account, the account-wide pacer does not independently know their internal cost centres. A focused campaign analysis can help investigate a division, but it should be labelled as that selected analysis. It should not replace the saved account result with an undocumented departmental filter. The team must understand when it is reading the whole account and when it is reading a subset.
Likewise, several accounts do not become a consolidated portfolio merely because the same person can access them. A regional owner can review each relevant account and explain the organisational relationship. A combined finance view needs deliberate currency, calendar and inclusion rules. Without those rules, adding apparently similar totals can create a misleading enterprise number.
Include the account's recognisable name in the operational discussion and identify the person responsible for the spending mandate. Public-facing summaries do not need internal customer identifiers or account-owner email addresses. The business identity and selected cycle provide useful context without exposing resource references that belong inside the tool's execution and authorisation logic.
Keep currencies and finance totals distinct
Read the pacer allowance and observed cost in the account's reporting currency. A regional team should not enter a parent company's planning amount in another currency and assume the comparison is meaningful. Currency conversion is a separate business convention with a rate, effective date and source. The account pacer does not establish that convention automatically.
For a multi-country organisation, retain local-currency results when discussing local decisions. Finance can apply its chosen conversion basis to a separately defined consolidation. This preserves the distinction between a real movement in account spend and a movement caused by the reporting exchange rate. It also makes later reconciliations easier when teams explain why two dashboards show different corporate-currency totals.
Google Ads reported advertising cost is not a complete accounts-payable statement. Taxes, invoice timing, credits and other finance adjustments can make billing records different from the performance cost selected for pacing. A pacing result should describe the source it actually used rather than call itself the definitive amount payable to the provider.
Keep rounding in presentation, not in the decision's underlying arithmetic. Displayed financial values can use sensible two-decimal formatting while the calculation preserves the returned precision. If a finance export and a Slack summary differ only because one rounds individual rows before summing, explain that presentation difference before assuming the account has an unexplained cost discrepancy.
Read the current configured cycle
The pacer uses the configured monthly start day to determine the current cycle. A start on the first follows the ordinary calendar month. A different start day creates a cycle that crosses calendar-month boundaries. The period begins on that configured day and ends immediately before the next occurrence of it.
This matters when finance uses a trading cycle that differs from the calendar month. The result should show the actual start and end dates so the team can match the allowance to the selected period. Calling every result this month's spend would be ambiguous when the configured cycle began in the previous calendar month.
The current cycle is determined from the current account date. A previously viewed period is not the reason to evaluate an old cycle as current. Historical analysis remains useful when explicitly requested, but the operational pacing question needs the active configured window. Distinguish that current window from rolling requests such as the last thirty completed days.
Cycle length can vary. The arithmetic uses the actual number of days between this cycle's start and the next start, rather than assuming every planning month contains thirty days. That affects both elapsed progress and the remaining daily allowance. The date range is therefore part of the calculation, not a decorative label added after the result is produced.
Use completed days in the account timezone
The saved pacing calculation reads through yesterday in the Google Ads account timezone. This avoids comparing an incomplete current day with completed historical days. A colleague in another timezone may already be on a different date, so their laptop clock is not the correct basis for selecting the account's cutoff.
Show the through date in the result. A report viewed early in a regional morning should make clear which completed account day it includes. The selected cutoff answers a practical question about the calculation's coverage. It does not certify that every provider adjustment for that day has become final.
On the first day of a new configured cycle, there may be no completed day inside the cycle yet. The correct result is that the current-cycle calculation is not ready, rather than carrying the previous cycle's numbers forward under a new heading. This prevents an enterprise team from interpreting yesterday's old-cycle spending as the opening day's new-cycle performance.
A complete calendar day and settled data are different concepts. Later provider processing can revise returned values. The team can use the completed-day result operationally while understanding that a subsequent read may change. When a material revision appears, preserve the reporting date and source context instead of treating every changed value as evidence that someone edited a campaign.
Retain historical spend from paused campaigns
Account-wide pacing includes the historical account cost in the selected cycle. It is not limited to campaigns enabled at the moment of the read. A campaign that spent earlier in the cycle still contributed to the allowance even if it has since been paused. Removing that spend would understate the account's actual progress.
This is especially important during enterprise launches and handovers. A discontinued promotion may account for a substantial share of elapsed spending. The current campaign list can look quiet while the account has already used much of its cycle allowance. Keep historical cost and present-day delivery status as separate dimensions of the explanation.
When investigating which campaigns drove the trajectory, request the relevant historical period and identify the selected status scope explicitly. An enabled-only diagnostic can help explain current delivery options, but it cannot serve as the complete account spending reconciliation. Both reads can be useful as long as they answer their stated questions.
The account result also does not prove that every historical campaign remains eligible for a live edit. An earlier spender can be paused, removed or otherwise unsuitable for the requested operation. The later edit preparation must resolve the current target and its supported settings. A historical contribution is evidence of past cost, not continuing authority or present eligibility.
Read two different daily rates
The elapsed average divides completed cycle spending by the number of elapsed days. It summarises the cycle so far. The recent run rate uses up to the latest seven completed days inside the cycle. It describes the more recent spending pattern used for the projection.
These rates answer different questions. A launch that accelerated after a quiet opening week can have a recent rate above its elapsed average. A promotion that ended can produce the opposite relationship. Neither rate is inherently wrong; the difference helps the team recognise that the current pattern differs from the earlier part of the cycle.
Early in the cycle, fewer than seven completed days are available. The recent rate uses the available completed days rather than borrowing days from the previous cycle. This maintains the current allowance's scope, while making the estimate more sensitive to a short opening pattern. Explain that limitation when a team tries to make a major allocation decision from very little elapsed evidence.
Successful daily evidence can include days with no reported spending, and those days belong in the average. A failed provider read is a different case and should not be converted into seven zero-cost days. Keeping this distinction prevents unavailable evidence from producing an apparently calm forecast that could mislead the enterprise owner.
Understand the projection's assumption
The projected period-end cost combines completed spending with the recent daily rate multiplied by the remaining days. It is a continuation estimate: what would the account spend if that recent rate persisted through the rest of the selected cycle? It is not a forecast that has independently learned the organisation's future promotion schedule.
The estimate is useful because its assumption is understandable. Regional teams can compare it with known future changes and discuss whether continuation is plausible. A planned campaign stop, an upcoming product launch or a major website change can make the unchanged-rate scenario unlikely. Those facts belong in the interpretation rather than being silently inserted into the calculated result.
Keep the projection's observation date available in the handoff. A projection calculated before a launch and one calculated after several launch days can differ substantially without either calculation being defective. The recent evidence changed. Understanding that timing is more useful than debating which isolated projected total should be treated as permanently correct.
The result should not be advertised as an automatic spending guarantee. Auctions, demand, eligibility and future operator decisions can all change the eventual total. Enterprise teams can use the estimate to prioritise attention and review responses, while retaining the difference between a stated scenario and an established final outcome.
Distinguish balance and future daily allowance
Remaining allowance is the selected allowance minus completed spending. It describes the amount left before reaching that planning figure. The daily amount needed to finish on allowance divides that remaining amount by the remaining cycle days, with a floor of zero for the displayed future spending requirement.
A negative remaining balance has meaning: completed spending has already exceeded the selected allowance. The future daily requirement can be zero in that case, but zero does not undo the overspend. Show the actual balance and explain its significance rather than replacing it with a harmless-looking zero balance.
The suggested daily amount is a planning reference, not an instruction that every campaign should receive that budget. It applies to the account allowance and remaining calendar, while campaign-level provider settings can cover different scopes and may share budgets. Turning one account-wide daily figure into several identical campaign settings would multiply the intended spending allocation.
Use the reference to frame the business discussion. Can the team accept the likely unused allowance? Is there enough eligible demand to spend at the required rate? Would acceleration create unprofitable activity or overwhelm operational capacity? These questions explain why finishing exactly on allowance is not always the right objective, even when the arithmetic provides a clear daily number.
Read severity with direction
The projected deviation expresses the difference between projected spending and the selected allowance as a percentage of that allowance. The current classification uses the absolute magnitude against the saved warning and critical thresholds. Direction is retained separately to distinguish projected over-spending from projected under-spending.
Threshold equality is included in the classification. A deviation exactly at the warning boundary is a warning, and one exactly at the critical boundary is critical. This avoids a gap where a value displayed at the boundary appears to contradict its status simply because the reader assumes a strict greater-than comparison.
The severity label indicates attention under the chosen configuration. It does not establish business harm. A projected shortfall can be a welcome outcome when the organisation deliberately withdrew a product. A projected overrun can require urgent action when finance has imposed a hard allowance. The direction and business mandate make the label actionable.
Choose thresholds that support the operating routine rather than merely suppressing messages. If a team finds every ordinary weekly variation critical, review whether the boundaries match its decision process. Preserve material exceptions in the discussion. A wider threshold changes when the tool flags attention; it does not alter the underlying cost, projection or remaining balance.
Calculate an invented divisional case
Consider an invented organisation, Alder Ridge Training, with a single account allowance of 8,000 in its account currency and a cycle running from October 1 through October 31. On October 19 in that account's timezone, the calculation includes eighteen completed days through October 18. This example illustrates the arithmetic; it is not a customer account or a claimed commercial result.
Suppose the first eleven completed days each spent 180, and the latest seven each spent 260. Completed spending is 3,800: the earlier days contribute 1,980 and the recent days contribute 1,820. The elapsed average is 211.11 per day when displayed to two decimals, while the recent run rate is 260.
Thirteen days remain. Continuing at the recent rate adds a projected 3,380, producing a period-end projection of 7,180. The projected deviation is 10.25% below the 8,000 allowance. The remaining balance is 4,200, and the daily spending reference needed to finish on allowance is 323.08.
With a warning boundary of 10% and a critical boundary of 30%, this is a warning in the under-spending direction. It does not tell the organisation to increase every campaign budget. The responsible owner must decide whether the remaining allowance should be used, whether a planned promotion changes the expected trajectory and whether additional demand would be commercially worthwhile.
Add the planned business calendar
Enterprise spending often follows a calendar that a recent-rate calculation cannot discover. Procurement deadlines, regional holidays, stock arrivals and enrolment windows can shape demand and campaign activity. Bring those facts into the pacing discussion with their dates and accountable owners, while leaving the observed cost series intact.
A known future launch can explain why the account is currently projected below allowance. The response might be to monitor launch readiness rather than accelerate unrelated campaigns. A known campaign stop can explain why an above-allowance continuation scenario overstates the intended remaining activity. Both cases show why the projection should be interpreted against the actual plan.
Separate a confirmed event from a hoped-for event. A product arrival with an approved date differs from an expected arrival that operations has not confirmed. The spending recommendation should reflect that uncertainty. Do not present an assumed future revenue opportunity as established evidence merely because it would make the current pacing position easier to justify.
When several regions use one account, document competing calendar priorities. One division's promotion may consume account allowance while another has a later commitment. The account projection can reveal the shared spending position, but the allocation decision still needs the organisation's business rules. A single mathematical trajectory cannot determine which regional obligation should take precedence.
Keep spending pace and outcome quality separate
A well-paced account can still produce poor outcomes. The account may spend close to its allowance while attracting unsuitable enquiries or generating insufficient purchase value. Conversely, an account below allowance may be operating efficiently in a genuinely limited market. Pace measures the spending trajectory, not the quality of the resulting business.
Bring the relevant outcome measure into the next question. For ecommerce, that may be purchase value, purchase count or the chosen return measure. For a lead business, it may be primary lead conversions and the organisation's downstream quality evidence. These definitions matter because a generic conversion-value total can include primary actions outside purchases, and a lead count does not independently establish sales quality.
Preserve the selected date and traffic scope when comparing cost and outcomes. A complete cycle cost total should not be compared casually with a revenue figure restricted to an unrelated traffic segment. Where reporting periods differ, state the difference and obtain the appropriate evidence before recommending a major allocation change.
The selected allowance is also not a profitability threshold. Spending the full amount can be inappropriate when margins, capacity or product availability changed. The enterprise owner should evaluate those business constraints alongside the pacing position. The tool can make the account trajectory visible without claiming to know the organisation's complete commercial economics.
Investigate the change in trajectory
Start an investigation with the evidence already returned. Determine whether the recent rate changed compared with the elapsed average and whether that change aligns with the planned calendar. This avoids immediately launching a large account scan when the core question can be explained by the existing daily series and a known promotion.
If campaign detail is needed, use a focused breakdown over the relevant dates. Ask which campaigns contributed to the acceleration or reduction, preserving historical cost from campaigns that have since paused. Separate the spending contribution from current eligibility and from the business reason for the change.
A sudden reduction can reflect a deliberate pause, reduced demand, an eligibility problem or another account condition. The cost pattern alone does not establish the cause. Read the relevant current status or policy evidence when it is needed for the diagnosis. If a required surface cannot be read, name the missing evidence instead of treating the absence of returned detail as proof that the account is healthy.
Current settings can help investigate a trajectory but do not prove the entire history of edits. A budget visible today may differ from the one used earlier in the cycle. Keep any historical change claim tied to available change evidence or an accountable operator's supplied context. This prevents a pacing discussion from becoming an unsupported reconstruction of who changed what.
Reuse compatible data for explanation and requested charts. A daily account-cost result can support both the projection and its visualisation without another identical provider request. A different campaign-level question justifies different evidence. Efficiency comes from matching reads to actual questions while preserving the scope required for a correct answer.
Choose the appropriate business response
The response to projected under-spending may be to accept the unused allowance, prepare an upcoming launch, investigate an eligibility issue or review an eligible budget increase. These choices address different causes and carry different business effects. Increasing a budget simply because the account is below allowance can fail to create demand and can weaken the commercial outcome.
The response to projected over-spending may be to obtain a revised allowance, reduce an eligible campaign budget, pause a precisely selected activity or preserve the current plan because the recent acceleration is temporary. The team should identify the intended response before preparing a provider edit. A broad instruction to fix pacing does not identify which account setting should change.
Record the decision's business owner. Finance may approve the allowance while the connected account owner authorises the actual Google Ads operation. Those are related responsibilities, but the application does not infer an enterprise approval hierarchy from a conversation. The team must supply its internal decision while the tool applies its actual connected-owner checks.
Keep monitoring available after a deliberate decision to hold. A team can conclude that no account edit is appropriate today while still wanting the next pacing observation. No change is a valid business outcome when it follows a clear review. It should not be confused with an unsuccessful attempted mutation or a provider read that never completed.
Distinguish allowance and provider budgets
The saved pacer allowance is a monitoring configuration. It does not create an account-wide Google Ads spending cap or automatically distribute that amount among campaigns. Changing that allowance changes the comparison used by the pacer; it does not by itself change the provider's campaign budget resources.
Google explains that average daily campaign budgets allow daily spend to vary, and describes daily and monthly spending limits for most campaigns. That provider behaviour is separate from an organisation's selected account pacing allowance.
This distinction prevents a common operational mistake. A team can raise its planning allowance and still have campaigns constrained by their existing provider settings. It can lower the allowance while provider campaign budgets remain unchanged. The new pacer comparison may become more severe, but no live campaign restriction has been created by that monitoring edit.
Shared budgets add another scope consideration. A budget resource can affect more than one campaign. A request that names one campaign should not silently modify a shared resource as though it belonged only to that campaign. The supported edit path must establish the relevant ownership and sharing conditions before preparing a precise proposal.
The planning daily reference should therefore be treated as an account-level decision aid. Translate it into an explicit campaign action only after identifying the intended allocation, supported resource and business tradeoff. The provider request must describe the actual setting being changed, not merely copy a dashboard number into a convenient field.
Prepare an eligible account edit
For a supported campaign-budget adjustment, identify the campaign and current budget relationship first. The focused convenience path checks for an eligible enabled campaign with a non-shared daily budget owned by a single campaign. These conditions protect the meaning of a request that appears to change one campaign's daily amount.
Specify the intended amount or supported relative adjustment. The proposal should express the current and intended account-currency values in ordinary language. A relative increase needs a valid positive adjustment and the correct rounding to the provider's budget unit. It should not change direction because of a malformed percentage or a mistaken currency scale.
Budget adjustment and bidding adjustment are different operations. Changing a target CPA or target ROAS affects a supported strategy setting, while changing campaign budget affects the spending resource. A request to spend more does not automatically authorise a strategy switch or removal of a business efficiency constraint.
The broader API-backed edit framework still needs operation-specific eligibility and target validation. Having a setting in the local schema is not proof that every account can use it or that a grouped request has already been verified for that combination. The assistant should prepare the supported concrete action and explain an actual limitation rather than substitute a different action without permission.
A focused account edit also does not reallocate the entire enterprise portfolio. If the business wants to move allowance between divisions, establish each intended effect and review them explicitly. Keep account-level monitoring, internal planning and live provider changes recognisable throughout the request.
Confirm the exact effect before execution
The connected owner should receive a readable proposal showing the exact campaign, relevant parent context and intended budget effect. If the request contains several supported logical actions, each action needs its own clear step within the complete proposal. Hidden additional actions make review unreliable even when the overall business objective sounds reasonable.
Preparing the proposal does not make the live change. The owner must use Confirm and Execute for the reviewed request. The pending proposal has a limited lifetime, and relevant account settings are checked again before submission. These checks protect the prepared effect when another operator changes the resource after the initial conversation.
After confirmation, a prominent progress state should make clear that the request is being handled. The final result distinguishes verified execution, provider acceptance without complete independent verification and an uncertain dispatched outcome. These states should not be reduced to an undifferentiated success message.
If submission becomes uncertain, inspect the actual resource state before another live attempt. The change may already have applied. A missing Slack update is not a reason to repeat the provider mutation. Message delivery recovery and account-write recovery have different consequences and must remain separate.
Use the detailed enterprise change-approval guidance for the broader workflow. Technical confirmation establishes the supported edit outcome. Subsequent spending, provider review and business efficiency still require later observation; the receipt cannot guarantee that the account will now finish exactly on allowance.
Communicate the position in Slack
A useful Slack pacing summary begins with the account and current cycle, then states completed spend, the projected position and the relevant direction. The reader should understand whether attention concerns projected over-spending or under-spending before reading a long explanation. Show the through date so a forwarded message retains its data coverage.
Use the remaining balance and daily reference to support the next decision, rather than burying them among implementation details. The team does not need raw query text, provider object names or account identifiers to discuss its spending plan. It needs recognisable business context and the limits of the projection.
A follow-up can ask which campaigns contributed to the recent acceleration or whether the latest pattern matches a planned launch. Retain the established account and period while resolving the new question. Conversational continuity should avoid unnecessary clarification, but it should not replace fresh current-setting checks when the user proceeds to an edit.
Creative discussion can remain conversational. Suggesting ways to explain the result to finance or drafting an internal note does not inherently require a new Google Ads call. Actual account figures, current settings and verified outcomes do require appropriate evidence. This distinction keeps a busy enterprise channel useful without turning every wording request into another provider read.
For ordinary AI replies, the user mention belongs before the feedback footer, with the feedback remaining last. Change-in-progress notices use their own visible status treatment. The output should help participants recognise the stage of work without making every message look like a technical execution record.
Set useful observation times
Scheduled observations should fit the account's operating calendar and the team's response routine. A morning review can prepare the local owner for the day's decision, while a second configured time can support another handoff. More frequent-looking messages are not automatically more useful when they rely on the same completed-day cutoff.
Choose a recipient channel whose participants can interpret and act on the result. The destination is part of the operational setup, not proof that a particular person read the message. Distinguish the calculation, delivery and human acknowledgement when discussing whether a pacing observation reached its intended owner.
Pausing the pacer pauses that monitoring configuration; it does not pause Google Ads campaigns. Resuming monitoring likewise does not enable campaigns. These similar words refer to different objects, and the message should make the target recognisable so an enterprise operator cannot mistake an app setting for a live delivery change.
When the spending mandate changes, update the relevant saved configuration deliberately and retain the business reason in the handoff. A new allowance or threshold changes how future results are interpreted. It does not rewrite the original cost evidence or prove that an earlier warning was incorrect under its then-selected configuration.
Show the trajectory with meaningful dates
A requested spend chart can reuse the successful daily account-cost evidence retained for the pacing result. The chart should identify whether it shows daily cost, cumulative cost or a comparison with another measure. These presentations answer different questions, and a title alone cannot make an unstated transformation understandable.
Use readable dates. Current-year labels can omit the year, while older periods need the year where it prevents ambiguity. Weekly aggregation should show the actual date range rather than an unexplained provider year-week code. A regional manager should be able to match the point to a business event without decoding an internal calendar identifier.
For conversational native Slack charts, keep one chart where a supported coarser breakdown makes the requested period readable. If daily detail was explicitly requested and exceeds the native point allowance, explain the necessary split while preserving the daily observations. Do not silently replace the user's daily request with a weekly series or substitute an image fallback.
The existing deterministic pacer also has its own progress-bar presentation. That is a distinct surface from a conversational request for a native time-series chart. Keep the meaning clear: progress against allowance, the daily spending trajectory and the period-end projection are related views, not interchangeable metrics.
A plotted blank can mean unavailable evidence, while an established zero is a value. Do not use invented zeros to make an interrupted query look complete. Where the full successful source supports zero-cost days, include them consistently so the chart and calculated daily rate agree.
Leave an accountable operational handoff
A pacing handoff should retain the selected account, allowance, cycle, through date and projected direction. Add the business reason for the chosen response and the person responsible for the next decision. These details allow another regional operator to continue the work without reconstructing an entire channel conversation.
Separate evidence from interpretation in the handoff. Completed cost and the calculated projection are observed or derived account information. The expectation that a promotion will accelerate demand is supplied business context. The recommendation to hold or adjust a budget is a decision proposal. Keeping these roles clear makes the note useful when later results differ.
If an account change occurred, include its recognisable target and actual outcome. A pending proposal, expired card, verified budget edit and uncertain dispatch are different states. The next owner must know which one applies before preparing another action.
Close the loop with later observation. A reviewed budget reduction may change the recent rate after enough new completed days arrive, but the next projection is still an estimate. Compare the result with the decision's stated intention and the relevant business outcome, not merely with whether the message's colour became calmer.
Connect pacing with enterprise budget tracking and stakeholder reporting. Tracking establishes the cost position, pacing explains the continuation scenario and reporting communicates the business decision. Consistent definitions across those activities prevent the same account from appearing to tell three incompatible stories.
Answer enterprise pacing questions
Does the pacer enforce an account spending cap?
No. It compares account cost and the projected trajectory with the saved allowance. Live provider settings require their own explicit supported edit.
Why does a paused campaign's cost remain included?
It spent during the selected cycle. Current paused status does not erase its historical contribution to the account allowance.
Is the projection a final spending guarantee?
No. It continues the recent daily rate across the remaining days. Future demand, eligibility and operator decisions can change the outcome.
Can a warning mean under-spending?
Yes. Severity uses deviation magnitude, while direction identifies projected over-spending or under-spending. Read both before deciding what to do.
Does recommended daily spend set every campaign budget?
No. It is an account-level planning reference. Each live campaign action needs the correct allocation, eligible resource and owner-approved proposal.
What happens at the start of a new cycle?
There may be no completed day inside that cycle yet. The result should explain that current-cycle pacing is not ready instead of relabelling the previous cycle.
Can the enterprise combine all regions automatically?
The saved pacer evaluates its connected account. Portfolio consolidation needs explicit account, currency and calendar rules; shared access alone does not establish those rules.