Put a cash position YOU computed onto the cash card.

This tool measures nothing. It takes the figure and its method as input and returns them for rendering. Call it only after you have totalled the balances yourself and can state every field below from your own work — never to "get" a cash position.

The server derives no cash figure of its own here, which is why every field below is required: the policy behind a number is the only thing that makes it checkable.

Under the number the card draws nothing. It carries the total and the moment it was read. Every other field below, required or optional, reaches no pixel. All of it comes back in this tool's text result, which is what you write the prose from. The card is the measure; the explanation is yours.

REQUIRED, because a figure whose method is not stated cannot be checked:

• amount and currency — the consolidated total. NEGATIVE is legal: an overdrawn workspace has negative cash, and this tool renders it rather than refusing it.

• as_of — the moment the reading is valid for

• accounts — every account that CONTRIBUTED, each with its native amount and currency, the converted amount, and the rate applied (null when it was already in currency). Carry institution_name and masked_account_number through from the balances read as well: your breakdown names each account by its bank, its name and its masked suffix, or by its currency when the bank and the name are both null, and never by its id.

• scope — the account types you counted as cash, and whether you counted an account whose ownership is unsettled

• excluded — what fell out, in four named groups: not owned, out-of-scope type, no readable balance, no FX rate. One merged count hides the difference between a rule the reader chose and a defect in the data.

• partial — whether the total may be a floor (the skills' is_floor), because an account with no readable balance or no rate was left out of it. The result carries the value derived from excluded, whatever you state. It never means a cut-short read: that stops before this call.

REFUSED rather than rendered, each because the caller's own figures disagree with each other:

• a total that is not the sum of the contributions listed — totalling a different set than you disclose publishes a figure nobody can audit

• a converted amount that does not follow from its native amount and stated rate

• a rate more than 1% away from Well's stored rate for the pair as of as_of, or a rate for a pair Well stores no rate for (count those accounts in excluded.no_fx_rate). Read rates from exchange_rates; never estimate one.

• an account already in currency that carries a rate other than one, or whose converted amount differs from its native one

• an account in another currency that states no rate

• the same account contributing twice

• a non-zero total with no contributing accounts

• an as_of in the future

• a covers_day that is not the day as_of falls on

• a scope.account_types naming nothing

• a balance_history that repeats a month or runs out of order

• a currency outside ISO-4217 — checked against the catalog, not its shape

OPTIONAL:

• covers_day — the UTC day the figure covers, YYYY-MM-DD. A month-end reading covers the last day of that month, and as_of MUST be that day's close, <day>T23:59:59Z. Anything earlier is refused: every rate is checked as of as_of and the stored rate is the latest one on or before it, so a figure covering August stamped earlier in the day converts at the previous day's rate under a caption that says otherwise. A live reading covers no day, so leave the field off — sending it there is an error this tool cannot catch, and it costs the reader the resolution into their own zone that a live reading is meant to get. The card draws a covered day as written, and it cannot tell a covered day from a live moment out of as_of alone: a day's close lands at 23:59:59Z, so every reader east of UTC sees the NEXT day unless you send this.

• balance_history — trailing complete month ends, oldest first. A null amount is a month no stored row covered; send it as a gap rather than dropping it or sending a zero, and never interpolate between two real points.

OPTIONAL, and send it whenever you computed a cash-flow bridge over the same cash:

• cash_bridge — { unexplained, closing }, the two terms you sent well_render_cash_flow_bridge, in this card's currency. The server applies the bridge's own tolerance and returns cash_check. "provisional": the bridge does not reconcile, the gap is in unexplained_gap, and the card marks the figure Provisional; say so in prose too: the figure stands on cash with an unexplained gap of that amount. "reconciled": say nothing about it. Leave cash_bridge off when you computed no bridge: the result is cash_check: "not_checked" and the card marks the figure Not checked.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.