Facebook Agency Account Reporting: Time Zone, Currency, and Reconciliation Controls

Reliable facebook agency account reporting starts before the first campaign is launched. The team must know which time zone closes each reporting day, which currency records platform spend, which exchange-rate rule converts that spend into the company’s management currency, and which data source is authoritative when dashboards disagree.

These decisions look administrative until a global team compares accounts across the United States, Europe, Southeast Asia, and Latin America. A campaign can appear to overspend, underspend, improve, or decline simply because two reports use different day boundaries or different foreign-exchange rates. If those differences are not documented, media buyers optimize against one number, finance reconciles another, and clients receive a third.

This guide provides a practical control framework for choosing account settings, accepting an agency-managed account, normalizing cross-account data, and investigating reporting discrepancies without treating every difference as a delivery problem.

The Short Answer: Keep Three Layers Separate

A controlled reporting model separates three layers:

1. Platform record: The account time zone, account currency, Ads Manager delivery data, payment activity, and platform receipts.
2. Provider record: Top-ups, balances, service charges, credits, refunds, and statements supplied under the commercial arrangement.
3. Management record: The advertiser’s chosen business time zone, reporting currency, exchange-rate policy, attribution convention, and finance period.

Do not overwrite one layer with another. Preserve the original platform values, then add normalized management fields. This gives the team a traceable path from a dashboard number back to the source account.

1. Why the Account Time Zone Matters

An ad account time zone determines how platform activity is grouped into calendar days. It affects the point at which “today” ends and “tomorrow” begins in account-level reporting.

Consider a campaign serving US customers while the media buying team works in Singapore and the finance team closes its books in London. One conversion may occur on Tuesday in New York, Wednesday in Singapore, and a different accounting day in a UTC-based warehouse. All systems can be technically correct while assigning the event to different dates.

The practical consequences include:

• Daily spend totals that do not match an internal dashboard
• Pacing alerts that trigger before or after the buyer’s working day
• Day-over-day comparisons built from unequal time windows
• Weekend and month-end spend allocated to different periods
• Automated rules that run against an unexpected account day
• Client reports that disagree with finance exports
• Incomplete “today” data when one system has already rolled into the next day

The account time zone is therefore a reporting boundary, not merely a display preference.

2. Choose a Time Zone Before Account Acceptance

The best time to resolve the issue is before campaigns, rules, exports, and client dashboards depend on the account.

Ask these questions:

1. Which market generates most of the revenue or conversions?
2. Which team owns daily budget pacing?
3. Which time zone defines the client’s reporting day?
4. Which time zone does the finance team use for month-end close?
5. Are automated rules scheduled around local trading hours?
6. Will the account be used for one market or several?
7. Does the existing data warehouse normalize timestamps to UTC?
8. Is the proposed time zone affected by daylight-saving changes?

There is no universal answer. A direct-to-consumer advertiser focused on the United States may prefer a US business time zone. A global agency may keep the platform’s native account time zone and normalize all accounts to UTC in its warehouse. A regional advertiser may align the account with its primary operating country.

What matters is that the choice is explicit, documented, and compatible with the reporting workflow.

3. Record Time-Zone Metadata, Not Just the Label

A label such as “Eastern Time” is not enough for long-term operations. Some regions observe daylight saving time, while others keep a fixed UTC offset. The relationship between two local time zones can therefore change during the year.

For each account, record:

Do not hard-code a permanent numeric offset for a region that changes clocks seasonally. Store the named time zone where the reporting system supports it, and let a maintained time-zone database calculate the applicable offset for each timestamp.

4. Why the Account Currency Matters

The account currency is the denomination used for platform spend, budgets, billing thresholds, receipts, and other monetary values associated with that account. It should not be confused with:

• The currency used to fund a provider balance
• The currency of the advertiser’s bank account
• The customer’s purchase currency
• The currency in an ecommerce platform
• The company’s financial reporting currency
• The client invoice currency

An account can spend in USD while the advertiser receives revenue in EUR and reports profit in GBP. A provider may also accept funds in a separate settlement currency. Each conversion can use a different exchange rate, date, spread, or fee.

If the team collapses these values into a single field called “cost,” it loses the ability to explain the difference.

5. Select Currency Through a Payment and Reporting Decision

Before accepting an account currency, review:

• Currency supported by the account arrangement
• Payment methods available for the account’s country and currency
• Provider funding or settlement currency
• Advertiser treasury currency
• Client contract and invoice currency
• Main revenue currency
• Foreign-exchange exposure
• Bank, card, platform, or provider conversion charges
• Tax and accounting requirements
• Existing dashboard and data-warehouse support

Meta’s available payment methods can depend on account, country, and currency. The commercial provider layer may impose additional conditions. Ask for the exact configuration rather than assuming that a currency label guarantees a particular payment method or settlement process.

Meta currently states that an advertiser may change the currency used for Meta ads once every 60 days when there is no current balance. Treat this as a controlled billing change, not a casual display adjustment, and verify the current eligibility and consequences in the account before proceeding. See Meta’s official guidance on changing the currency used for Meta ads.

6. Build an Account Acceptance Record

Before launch, the advertiser, agency, and provider should confirm the account configuration in one acceptance record.

Include:

Reporting access is separate from ownership. Review the Facebook agency account access guide if the analyst, buyer, and finance roles require different permissions.

7. Preserve Native Values in Every Export

Never discard the account’s original monetary and time fields during normalization.

A useful reporting table keeps at least:

• Account ID
• Account name
• Platform date
• Platform time zone
• Account currency
• Native spend
• Management date
• Management time zone
• Management currency
• FX rate
• FX rate source
• FX rate date
• Converted spend
• Extraction timestamp
• Attribution setting or reporting context
• Data source

The normalized value should be a derived field. If native_spend is USD 10,000 and the management currency is EUR, retain the USD 10,000 and create a separate EUR value. Do not replace the original figure.

This rule allows a later reviewer to reproduce the conversion and determine whether a variance came from delivery, timing, exchange rates, or data processing.

8. Define One Foreign-Exchange Policy

The wrong question is “What is the exchange rate?” The correct question is “Which exchange rate, from which source, for which date and business purpose?”

Common policies include:

• Daily market rate by transaction date
• Daily rate by platform reporting date
• Monthly average rate
• Month-end closing rate
• Treasury rate fixed for the reporting period
• Actual settlement rate from the bank or provider
• Contractual rate agreed with the client

These methods can produce different values without any error.

Choose a policy for each reporting purpose:

Do not use a live rate to restate old reports silently. If historical values must be retranslated, label the report version and preserve the previous result.

9. Separate Platform Spend From Cash Movement

Platform spend answers how much advertising delivery the account recorded. Cash movement answers how much money entered or left a payment, balance, bank, or provider system.

They may differ because of:

• Funding before the spend occurs
• Spend that has occurred but is not yet charged
• Billing thresholds
• Pending or failed payments
• Credits or adjustments
• Taxes
• Service fees
• Currency conversion
• Bank or card charges
• Refund timing
• Unused balance
• Different cutoff dates

Do not calculate campaign ROAS using a provider top-up amount if the purpose is to measure delivered media cost. Do not use Ads Manager spend as a substitute for cash reconciliation if the purpose is to explain a bank or provider balance.

Use a bridge:

Opening balance + funds received - platform spend - fees + credits - refunds = expected closing balance

Adapt the bridge to the actual commercial arrangement and name every component. An unexplained “adjustment” field is not a reconciliation process.

10. Distinguish Delivery Differences From Attribution Differences

Time-zone and currency controls solve only part of reporting disagreement. Performance metrics may also differ because reports use different attribution settings, event definitions, conversion windows, data refresh times, or modeled results.

Before investigating a performance variance, align:

• Date range
• Account time zone
• Selected columns
• Attribution setting
• Conversion event
• Campaign, ad set, and ad status filters
• Breakdown dimensions
• Report generation time
• Currency and FX method
• Included accounts

If two exports do not share these parameters, they are not yet comparable.

Meta Ads Manager is the platform workspace for campaign creation and performance reporting. Use the platform record as the starting point for delivery analysis, then document any transformation applied in external dashboards. See the official Meta Ads Manager overview.

11. Use a Standard Daily Close

A global team needs one daily-close routine.

Buyer Close

The media buyer records:

• Native platform spend
• Budget and pacing status
• Material campaign changes
• Delivery or review issues
• Expected next-day action

Data Close

The analyst records:

• Extraction timestamp
• Source account and time zone
• Conversion into the management day
• FX rate and source
• Late-arriving data or restatement
• Dashboard refresh status

Finance Close

Finance records:

• Payment activity
• Receipts or statements
• Provider funding and balance
• Fees, credits, taxes, and refunds
• Reconciliation variance
• Unresolved owner and deadline

Do not force every team to close at the same clock time. Force them to use the same definitions and to show when each layer was last updated.

12. Handle Month-End Without False Precision

Month-end creates the highest risk because a few hours can move material spend between periods.

Define:

1. Platform period based on the account time zone
2. Management period based on the company time zone
3. Finance cutoff based on the accounting policy
4. FX rate used for the period
5. Treatment of late platform adjustments
6. Treatment of pending provider transactions
7. Restatement threshold
8. Approval owner for final numbers

A report should state its basis. For example:

Platform spend is grouped by each account’s native time zone and currency, then translated into USD using the approved monthly average rate. Finance cash movement is reconciled separately through the period-end settlement schedule.

That sentence prevents more confusion than a dashboard with twenty unlabeled metrics.

13. Diagnose a Reporting Mismatch in Order

When two numbers do not match, use this sequence:

1. Confirm scope. Are the same accounts, campaigns, and statuses included?
2. Confirm date boundaries. Are both systems using the same start and end timestamps?
3. Confirm account time zone. Is one report using local time and another UTC?
4. Confirm refresh time. Was one report exported earlier?
5. Confirm native currency. Are the source monetary values identical before conversion?
6. Confirm FX policy. Are the rate source and date the same?
7. Confirm attribution. Are event and attribution settings aligned?
8. Confirm filters and breakdowns. Did a segmentation rule exclude data?
9. Confirm platform adjustments. Were credits or late changes posted?
10. Confirm provider components. Are fees, top-ups, refunds, or balances being compared with media spend?

Only after these checks should the team escalate the discrepancy as a potential platform, provider, or integration issue.

14. Control Changes to Currency, Time Zone, and Reporting Logic

Any change that affects monetary values or daily boundaries should follow a change record.

Capture:

• Requested change
• Business reason
• Affected account IDs
• Current and proposed values
• Current balance and billing status
• Historical report impact
• Dashboard and API impact
• Automated rule impact
• Owner approval
• Provider confirmation where applicable
• Implementation date and time
• Validation result
• Rollback or continuity plan

Export the final pre-change report and label the transition date. Do not splice pre-change and post-change values into one uninterrupted series without documenting the boundary.

Meta’s account activity history can help authorized users review certain account changes. Use Meta’s current instructions for viewing Ads Manager activity history and retain your own business change log as well.

15. Questions to Ask an Agency Account Provider

Before onboarding, ask:

1. What are the exact account time zone and currency?
2. Can we review both settings before accepting the account?
3. Who owns the account and who can view reports?
4. Which billing or funding model applies?
5. What currency do we send and what currency is credited?
6. Which exchange rate or conversion fee applies, if any?
7. How are service charges shown?
8. Who provides payment records, statements, and receipts?
9. How are credits, refunds, and unused balances recorded?
10. What happens if we need a different currency or time zone?
11. Will the change require a different account or operating process?
12. How is historical reporting preserved during a transition?
13. Which values are available through export or API?
14. What is the discrepancy escalation process?

The provider should answer with an account-specific configuration, not general marketing language.

Reporting Control Checklist

Build the Reporting Model Before Scaling Spend

A high-spend account does not create reliable reporting by itself. Reliability comes from a known account configuration, preserved source data, one normalization policy, and an explainable reconciliation between platform delivery, provider settlement, and company finance.

AdAccRun helps eligible advertisers, agencies, affiliate teams, and media buyers evaluate currently available account arrangements, including ownership, access, currency, time zone, funding, and support requirements. Availability, configuration, pricing, limits, and commercial terms depend on review and the option offered at the time.

Talk to AdAccRun on Telegram and share your target markets, expected spend, preferred account currency, reporting time zone, Business Portfolio details, and required access structure.

Frequently Asked Questions

Should Every Ad Account Use the Same Time Zone?

Not necessarily. One platform time zone may suit a single-market business, while a global portfolio may contain several native time zones. The management layer should normalize them consistently and preserve each account’s original setting.

Should We Choose the Currency of the Target Market?

Not automatically. Review supported payment methods, funding and settlement flows, revenue currency, treasury policy, client contract, accounting requirements, and provider terms. The target market is only one factor.

Why Does Today’s Spend Differ Between Ads Manager and Our Dashboard?

The systems may use different time zones, refresh times, filters, attribution settings, or data-processing rules. Compare the native account values and extraction timestamps before treating the variance as an error.

Is a Top-Up Amount the Same as Ad Spend?

No. A top-up is a funding movement. Ad spend is delivery recorded by the platform. Timing, fees, credits, taxes, refunds, and unused balances can create differences.

Can We Convert All Accounts Into USD for Reporting?

Yes, as a management view, provided the original account currency and native spend remain available. Document the FX source, rate date, method, and restatement policy.

What Should We Do Before Changing Currency?

Check the current balance, eligibility, payment method, provider terms, historical data impact, dashboard integrations, and month-end timing. Record the change and validate the resulting billing and reporting setup before restarting normal operations.