Map currencies and timezones before merging anything
The pre-merge map: which account reports in what currency and timezone, and the rule chosen for the merge.
IntentThe conversion and alignment rules every merged table needs.
- 2
- Steps
- 3
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before any multi-account or multi-platform table.
- Onboarding.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
No single source is required: this one reads across whatever you have connected.
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Read currency and timezone per account.
Write the merge rule: target currency, conversion basis, day boundary.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Accounts mix currencies
Conclude
Pick and state one target and one conversion basis: a merged table without the rule is unauditable.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Converting a month at today's rate distorts dailies: period-average or per-day rates, stated.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.