@happyvertical/smrt-expenses 0.57.3 → 0.57.5

package/AGENTS.md

@@ -147,14 +147,13 @@ the compatible owner alias.
 All three fields participate in the reviewed-money freeze. See the README and
 [financial facts test matrix](agents/financial-facts-test-matrix.md).
 
-Linking a new refund (or changing its source) also claims the source revision in
+Linking a refund, changing its source, or editing amount/financial facts claims the source revision in
 that same transaction through `claimRevision(source.updated_at)`. This makes a
 source edit under an older PostgreSQL `REPEATABLE READ` snapshot fail with a
 serialization error instead of missing the new refund. Reload a source after
 linking a refund before editing/reviewing it; on a serialization failure, retry
 the entire caller transaction with fresh instances. Failed outer transactions
-roll back both the refund and the source revision claim. Existing-link saves do
-not advance the source revision.
+roll back both the refund and the source revision claim. Saves without capacity-relevant changes do not advance the source revision.
 
 ## Cross-package references
 
@@ -191,3 +190,43 @@ profile ids in tests: PostgreSQL stores them as `uuid`.
 Draft amounts are lossless currency-unit text; model/review amounts remain integer
 minor units. Receipt upload is composed from Assets, never reimplemented here.
 `test` includes backend and UI SSR; `test:e2e` proves native browser submissions.
+
+
+## Exact refund capacity (#4070)
+
+All persisted linked refunds reserve gross capacity regardless of review state.
+`refundPosition(sourceId)` / `getRefundPosition()` expose exact positive cash
+magnitudes and nullable complete financial residuals. `src/refund-position.ts`
+bounds known subtotal and tax-code charged/recoverable/nonrecoverable reversals
+separately; source component identities cannot compensate for one another.
+Unknown facts stay null, and known linked facts cannot be cleared. Source edits
+and refund edits revalidate the prospective position under the existing source
+locks and revision claims. No customer credit or cash recipient is inferred.
+
+## Cash reimbursement positions (#4073)
+
+`refundRecipient` guarded JSON is explicit company/person/third-party cash receipt evidence,
+separate from payer. Third-party names are exact bounded source evidence, never
+verified identities or fuzzy joins. Missing/other-person/third-party direction
+stays unknown for person reimbursement; third-party yields
+`unknown-third-party-recipient`. Public
+`reimbursementPosition` / `getReimbursementPosition` returns nonnegative remaining
+claim and separate money owed to company; never offset economic cost basis or
+infer historical payment. `markReimbursed` stores exact full remaining
+`reimbursedAmount` with date/reference; direct payment-field writes, replacement
+payments, and later source cash-claim/payer edits are refused. Legacy payment
+markers with null amount remain unknown. Recipient changes share refund source
+locks/CAS, including rollback and stale REPEATABLE READ decisions.
+
+## Supplier payable authority (#4096)
+
+`src/supplier-payable.ts` owns exact dated retention/settlement/refund-direction
+projection, separately from incurred cost and employee reimbursement. The guarded
+`supplierPayableJson` is method-only, original snapshot + append-only child UUIDs
++ optional one-time unknown-basis completion. Current source-row locks/CAS also
+serialize this authority with linked refunds. Direct field writes/deletes and
+managed money/payer/refund mutations fail; no generated action exposes these
+methods. Unknown basis or unreconciled refund remains unknown and blocks new
+settlement. A settlement records evidence; it executes no bank/provider/journal
+operation. Preserve explicit chronological prefixes and same-day ordering.
+See README and `agents/supplier-payable-test-matrix.md` for the full contract.

package/README.md

@@ -242,12 +242,24 @@ Negative amounts require `refundOfId`, naming a positive non-refund expense
 visible in the same tenant and currency. Refund breakdown components are negative
 (or zero), including recovered tax. Self, missing, foreign-owner, currency-mismatched,
 and refund-of-refund sources fail closed. Source lookup uses the caller's database
-executor. This link retains provenance only: it does not allocate settlements,
-cap cumulative refunds, issue credits, or determine entitlement. A source may
-be explicitly reopened and corrected, but existing same-owner refunds prevent
-changes that would make it zero/nonpositive, turn it into a refund, or change
-its currency away from theirs. Unrelated edits and positive same-currency amount
-corrections remain allowed; there is no cumulative refund limit.
+executor. Every persisted linked refund reserves gross cash capacity, including
+unreviewed or rejected rows. Cumulative refunds cannot exceed source gross.
+Known financial reversals additionally cannot exceed the source subtotal or any
+exact source tax-code component's charged, recoverable, or nonrecoverable amount;
+components cannot compensate for one another. Source and refund edits revalidate
+the prospective position. Known linked facts cannot be cleared. This records
+reversals, not settlement allocation, customer credit authority, or entitlement.
+
+`await expenses.refundPosition(sourceId)` (also `source.getRefundPosition()`)
+returns positive `sourceAmount`, `refundedAmount`, and `remainingAmount`, plus
+all `refundIds`. Its `financialPosition` contains the original breakdown, signed
+negative cumulative `refunded` breakdown, and positive/zero `remaining`
+breakdown. It is null if source facts or any refund facts are unknown; unknown
+never implies zero tax or completed reversal. Known refunds on unknown legacy
+sources remain valid, bounded by known gross. When source facts exist, all known
+refund components remain bounded even if another refund's facts are unknown.
+The read retains the caller transaction and tenant boundary. Source gross is
+preserved: recording refunds never overwrites it.
 
 Expense saves validate and persist in one transaction, including nested caller
 transactions. On PostgreSQL, source edits and refund writes acquire ordered
@@ -259,14 +271,14 @@ requires these locks and the source revision claim below. Callers must not concu
 model instance while it is temporarily transaction-bound. Direct SQL writes
 remain outside these model-level guarantees.
 
-Linking a new refund (or changing its source) also claims the source revision in
+Linking a refund, changing its source, or editing its amount/financial facts claims the source revision in
 that same transaction through `claimRevision(source.updated_at)`. This makes a
 source edit under an older PostgreSQL `REPEATABLE READ` snapshot fail with a
 serialization error instead of missing the new refund. Reload a source after
 linking a refund before editing/reviewing it; on a serialization failure, retry
 the entire caller transaction with fresh instances. Failed outer transactions
-roll back both the refund and the source revision claim. Existing-link saves do
-not advance the source revision.
+roll back both the refund and the source revision claim. Saves that do not change
+capacity-relevant fields do not advance the source revision.
 
 Financial breakdown, third-party payer name, and refund provenance join the
 existing reviewed-money lock. Save `reopen()` first, then correct facts and review
@@ -274,3 +286,111 @@ again; corrections cannot ride alongside the reopen operation. New columns are
 additive via `smrt db:migrate`; legacy amounts survive without invented facts.
 The SQLite and PostgreSQL suites execute upgrades from the preceding schema and
 check that repeat migration is a no-op.
+
+### Refund cash recipients and reimbursement positions
+
+A refund's optional `refundRecipient` is guarded JSON, read/written through
+`getRefundRecipient()` / `setRefundRecipient({ kind: 'company' })` or
+`setRefundRecipient({ kind: 'person', profileId })` or
+`setRefundRecipient({ kind: 'third-party', name })`. A third-party name is exact
+retained source evidence (nonblank, at most 200 characters), not independently
+verified party/customer identity. It is never trimmed, fuzzily matched or resolved
+to another party by this API. It states who actually
+received the cash, independently of `paidBy`. Missing recipient is unknown;
+historical payer fields are never reinterpreted as receipt evidence. The field
+belongs only to linked negative refunds and joins the reviewed-money freeze.
+
+For a positive person-paid reimbursable source,
+`await expenses.reimbursementPosition(sourceId)` (or
+`source.getReimbursementPosition()`) reports original `sourceAmount`,
+`personRefundAmount`, `companyRefundAmount`, retained `reimbursedAmount`,
+`remainingAmount`, and separate `owedToCompany`. Company-received refunds do not
+reduce the person's original gross cash claim. Same-person refunds do. A later
+person-received refund after reimbursement creates money owed to the company;
+it never becomes a negative reimbursement or automatically records settlement.
+These cash values remain separate from economic `getCostBasis()`.
+
+`markReimbursed({ amount?, at?, reference? })` records only the full known
+remaining claim and retains exact `reimbursedAmount`, preserving source gross.
+An optional expected `amount` must match it exactly; partial payment is refused.
+An existing payment cannot be overwritten, and its cash claim/payer remain
+fixed. Payment fields cannot be forged by direct save. Existing no-refund
+callers may omit amount and record the full original gross as before.
+
+`unknownReason` identifies an unknown recipient, another person's recipient,
+an explicit third-party receipt (`unknown-third-party-recipient`), or a historical
+reimbursement marker without retained paid cash. A third-party receipt is never
+counted as company/person cash or interpreted as income or settlement. Unknown
+positions return null liability/receivable rather than inferring zero or a
+historical gross payment. Resolve legacy evidence explicitly; this API supplies
+no automatic legacy conversion. Recording is not transfer execution. Both public
+position reads and writes preserve caller transaction affinity and source locks;
+refund-recipient changes also advance the source revision to reject stale
+REPEATABLE READ reimbursement decisions.
+
+## Supplier retention and payable evidence
+
+`Expense.recordSupplierPayable()` and the matching collection method retain an
+original supplier obligation separately from incurred money, tax recovery,
+company cost and employee reimbursement. The original `payableBasisMinor` is
+explicit or `null`; neither payer nor expense gross implies unpaid supplier debt.
+Original held/released/settled events carry exact source identity, original author,
+calendar date and explicit same-day sequence. Unknown original author is null,
+never a fabricated current reviewer. The current recorder and import
+review evidence are independent. Returned events have immutable UUIDs for host
+crosswalks. Recording evidence does not approve the expense, execute a payment,
+create a journal or contact an accounting provider.
+
+```ts
+const position = await expenses.recordSupplierPayable(expenseId, {
+  requestId, currency: 'CAD', payableBasisMinor: null,
+  source: { namespace: 'original-books', key: 'receipt-42', version: '1', author: 'Original bookkeeper' },
+  recordedByProfileId: reviewerProfileId,
+  evidenceRef: 'Reviewed original source export',
+  events: [{
+    kind: 'hold', amountMinor: 1000, effectiveOn: '2026-09-15', sequence: 0,
+    evidenceRef: 'Original retained amount',
+    source: { namespace: 'original-books', key: 'hold-7', version: '1', author: 'Original bookkeeper' },
+  }],
+});
+// position.retainedMinor === 1000; position.remainingPayableMinor === null
+```
+
+`completeSupplierPayableBasis()` can complete an originally unknown basis once,
+with explicit review evidence while preserving the original unknown snapshot.
+`recordSupplierPayableEvent()` appends a dated hold, release, supplier settlement
+or refund interpretation. Exact `recordedRetainedMinor` remains visible while `retainedMinor` is null if a
+linked refund lacks its allocation evidence. A settlement is evidence of money already paid; it is
+not a bank instruction. Current settlements require a known basis and every
+linked refund's explicit interpretation. Releases consume only retained capacity.
+The current caller remains responsible for host permissions and reviewer identity;
+these methods are not generated REST/MCP/CLI actions.
+
+A linked negative Expense does not establish how much supplier debt was reduced
+or how much cash was returned. Its explicit `refund` event therefore names
+`refundExpenseId`, `payableReductionMinor`, `retainedReductionMinor`, and
+`cashReturnedMinor`, each bounded by the owning source/capacity. Retained reduction
+cannot exceed payable reduction. Unknown refund interpretation makes the payable
+position unknown and prohibits new settlement or release; it never becomes zero or an
+inferred allocation. Expense refund gross/component caps continue to apply.
+
+Every chronological prefix conserves retained and paid capacity: obligation is
+basis minus explicit payable reductions; net paid is settlements minus cash
+returns; retained is holds minus releases and retained reductions; payable is
+obligation minus net paid and retained. No intermediate amount may be negative.
+An original unknown basis uses expense gross only as an upper validation bound,
+never as a reported payable amount. Source events precede neither the expense
+nor their exact linked refund date, and same-day events require unique sequence.
+`getSupplierPayablePosition({ asOfDate })` / collection `supplierPayablePosition`
+returns dated sums with the complete original/current authority for provenance.
+It returns null before the original Expense date, rather than projecting a future
+obligation into an earlier period.
+A later reviewed basis completion is explicit retrospective interpretation, not
+proof that the amount was known to the original author on an earlier date.
+
+Commands share Expense's transaction, source-row locks and revision guards with
+refunds. Exact retries return retained IDs; changed requests are refused. Original
+source and current completion/event evidence cannot be replaced or deleted;
+managed source money/payer/context and linked refund facts cannot be edited
+around the position. Caller rollback includes both evidence and source revision.
+Expenses with no supplier-payable authority keep their existing behavior.

package/agents/financial-facts-test-matrix.md

@@ -94,3 +94,60 @@ runs pass four SQLite and seven PostgreSQL cases (`fixed-sqlite.log`,
 `fixed-postgres.log`). Final committed-head package build, full test, PostgreSQL,
 typecheck, and browser commands are recorded with HEAD and exit status in
 `validation-records.json` and their named logs in that same evidence directory.
+
+
+## Exact refund positions (#4070)
+
+Risk: high — cumulative financial reversals and concurrent edits. The shared
+SQLite/PostgreSQL suite covers partial/full/excess cash reversals (including
+rejected rows), independent subtotal/charged/recovery/nonrecoverable caps, exact
+component identities, signed residuals, unknown legacy/partial facts, source
+corrections, refund edits/reparenting, and rollback of refund plus source revision.
+PostgreSQL additionally proves stale sibling amount and financial-facts edits
+abort under REPEATABLE READ, then fail the appropriate cap on a fresh retry.
+No missing financial facts are synthesized. A former freeze fixture now uses a
+source gross sufficient for its refund and retains known linked facts after
+reopen: clearing them would erase already-proved reversal bounds.
+
+Focused commands: `pnpm --filter @happyvertical/smrt-expenses exec vitest run
+src/__tests__/expenses.test.ts`, the same PostgreSQL optional test through
+`scripts/run-with-ci-postgres.mjs`, and owning-package `tsc -p tsconfig.json
+--noEmit`. External receipts: `/home/will/Work/tmp/tc-mvp-20261016/expense-refund-caps/`.
+Coordinator owns combined prerequisites, release validation, and review.
+
+## Refund cash direction and reimbursement positions (#4073)
+
+Risk: high — retained payment amount, liability/receivable direction, additive
+schema migration, and recipient-vs-payment concurrency. Shared SQLite/PostgreSQL
+cases prove company receipts preserve gross personal claim, person receipts
+reduce it, exact full-remaining payment is retained independently of economic
+cost basis, later personal receipt creates a separate company receivable,
+unknown/other-person recipients and historical missing paid amounts remain
+unknown, direct overwrite/source-claim rewrite fail closed, recipient review
+freeze/shape apply, and caller rollback restores an unpaid claim. PostgreSQL
+pins a REPEATABLE READ reimbursement before an independent recipient correction
+and requires serialization rejection, followed by exact fresh payment. Existing
+service-backed permission tests run unchanged; optional expected amount remains
+behind the same authorization. Migration verifies new fields stay null on legacy
+rows; no historical payer or paid cash is inferred.
+
+Focused evidence: `/home/will/Work/tmp/tc-mvp-20261016/expense-reimbursement-position/`.
+No worker broad build/suite/review/PR; coordinator owns combined release gates.
+
+## Explicit third-party refund recipients (#4082)
+
+Shared SQLite/PostgreSQL cases retain exact bounded third-party source names,
+refuse blank/malformed/overlong names and extra fields, persist/reload guarded
+JSON and preserve reviewed provenance. Recipient edits claim the source revision;
+caller rollback restores both evidence and revision. Person reimbursement with
+third-party cash receipt returns unknown-third-party-recipient, nullable cash
+positions and retained actual paid cash; it cannot infer company income, person
+payment or settlement. An exact source name is evidence, not verified customer
+identity. Existing company/person and unknown legacy cases remain covered.
+
+## Complete programmatic refund reads
+
+A shared 201-refund SQLite/PostgreSQL case verifies full cumulative cash capacity,
+exact person reimbursement, over-refund refusal and source-reduction refusal.
+The internal collection reads intentionally use the unbounded programmatic
+`list()` contract; generated API page defaults do not apply to those reads.

package/agents/supplier-payable-test-matrix.md

@@ -0,0 +1,24 @@
+## Expense supplier payable authority (#4096)
+
+Public methods on a persisted positive Expense, delegated by the Expense collection:
+- recordSupplierPayable(input): immutable original source snapshot, explicit currency, payableBasisMinor:number|null, original dated held/released/settled evidence, source namespace/key/version and original author/evidence; current recorder separately supplied. Stable request replay.
+- recordSupplierPayableEvent(input): append current evidenced hold/release/settlement, or explicit refund reconciliation with payableReductionMinor, retainedReductionMinor and cashReturnedMinor tied to one actual linked Expense refund. No provider/bank/journal execution.
+- completeSupplierPayableBasis(input): one explicit reviewed completion of an originally unknown basis, preserving original snapshot.
+- getSupplierPayablePosition({asOfDate?}): typed original/event lineage, stable event UUIDs, exact held/released/net-paid/available payable amounts; basis/position unknown when basis or linked refund interpretation is unknown.
+
+Dates and same-day sequence are supplied explicitly. Original author is source text, never an invented current profile. Current recorder is independently attributed. Each event retains source namespace/key/version or current evidence and request identity. No current approval is synthesized. All money is safe integer minor units in Expense currency. Original basis cannot exceed gross; actual tax/recovery/company-cost remains unchanged.
+
+Conservation: retained = held - released - explicitly retained refund reductions; net obligation = payable basis - explicit payable refund reductions; net paid = settlements - explicit supplier cash returns; available payable = obligation - net paid - retained. Every dated prefix must be nonnegative when known. Cash returns cannot exceed actual earlier settlements; retained reductions cannot exceed original retained capacity. Linked refund amount bounds both the explicit economic and cash directions independently; no inference that they are equal. New/unreconciled linked refunds make payable position unknown and prohibit new settlement/release; recorded held counters remain visible while retained availability is unknown. Current settlement requires known basis and all refund dispositions. Original settlement facts may retain an unknown basis subject to gross upper bounds. Employee reimbursement is independent.
+
+One guarded JSON authority on Expense owns these calculations; child event UUIDs are immutable concrete command evidence. Direct field writes, deletion, source money/payer/currency mutation and mapped-refund mutation/deletion are refused. Existing shared Expense source row locks/CAS serialize refunds with payable commands. Unknown refunds may be recorded but cannot authorize additional payment. Caller executor and outer rollback are preserved.
+
+| Behavior | Trigger / positive | Failure | Context / executor | Runtime / edge | Proof |
+|---|---|---|---|---|---|
+| Original authority | record holds/releases with null basis and original author | changed retry, malformed/unknown event, currency mismatch | owner tenant/current recorder, caller transaction | Node26 SQLite+PG; original source DTO | focused shared native suite |
+| Dated conservation | hold/release/settlement exact amounts, supplied ordering | overrelease/overpayment, ambiguous chronology, unsafe values | same source lock/CAS | SQLite+PG; no external I/O | prefix + native race tests |
+| Refund directions | explicit economic/retained/cash disposition against actual linked refund | absent disposition -> unknown; excess/changed refund refused | source+refund locks | SQLite+PG public Expense refund authority | native conservation and mutation tests |
+| Immutable authority | exact replay and stable event IDs | direct save/delete/source rewrite | tenant/context allow+deny | generated CRUD remains closed | native guards |
+| Atomicity | caller transaction success/retry | outer rollback, competing final capacity | supplied executor | SQLite+managed PG | focused rollback/concurrency |
+| Compatibility | no payable authority retains existing Expense behavior | no inferred cost/tax/reimbursement changes | existing public reads | supported current package | focused relevant existing Expense tests |
+
+Risk: high, shared financial capacity and concurrent mutation. No live provider calls or sandbox certification. Root coordinates one integration/release candidate and combined review.

package/dist/actions/expense-actions.d.ts

@@ -44,6 +44,8 @@ export interface ReviewExpenseActionInput {
 /** Body of the `recordReimbursement` action. */
 export interface MarkExpenseReimbursedActionInput {
     expenseId: string;
+    /** Optional expected full remaining reimbursement in minor units. */
+    amount?: number;
     /** Payroll line, payables reference, or transfer id of the payback. */
     reference?: string;
 }

package/dist/actions/expense-actions.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"expense-actions.d.ts","sourceRoot":"","sources":["../../src/actions/expense-actions.ts"],"names":[],"mappings":"AAWA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,qCAAqC,CAAC;AAE7E,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,sBAAsB,CAAC;AACpD,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,6BAA6B,CAAC;AAClE,OAAO,EAGL,KAAK,yBAAyB,EAC9B,KAAK,YAAY,EAClB,MAAM,aAAa,CAAC;AASrB,8EAA8E;AAC9E,MAAM,WAAW,wBAAwB;IACvC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,yCAAyC;IACzC,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;IACjB,oBAAoB;IACpB,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,CAAC,EAAE,YAAY,CAAC;IACtB,kEAAkE;IAClE,eAAe,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAChC,UAAU,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,QAAQ,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACzB,YAAY,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC7B,gBAAgB,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACjC,UAAU,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,kBAAkB,CAAC,EAAE,yBAAyB,GAAG,IAAI,CAAC;CACvD;AAED,0CAA0C;AAC1C,MAAM,WAAW,+BAA+B;IAC9C,SAAS,EAAE,MAAM,CAAC;IAClB,OAAO,EAAE,MAAM,CAAC;IAChB,aAAa,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,yCAAyC;AACzC,MAAM,WAAW,wBAAwB;IACvC,SAAS,EAAE,MAAM,CAAC;IAClB,4EAA4E;IAC5E,QAAQ,EAAE,SAAS,GAAG,QAAQ,CAAC;IAC/B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAED,gDAAgD;AAChD,MAAM,WAAW,gCAAgC;IAC/C,SAAS,EAAE,MAAM,CAAC;IAClB,uEAAuE;IACvE,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAyGD;;;;GAIG;AACH,wBAAsB,mBAAmB,CACvC,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,OAAO,CAAC,CAiElB;AAED;;;;;GAKG;AACH,wBAAsB,0BAA0B,CAC9C,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,cAAc,CAAC,CAkDzB;AAED;;;;;;GAMG;AACH,wBAAsB,mBAAmB,CACvC,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,OAAO,CAAC,CA8BlB;AAED;;;;GAIG;AACH,wBAAsB,2BAA2B,CAC/C,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,OAAO,CAAC,CAelB"}
+{"version":3,"file":"expense-actions.d.ts","sourceRoot":"","sources":["../../src/actions/expense-actions.ts"],"names":[],"mappings":"AAWA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,qCAAqC,CAAC;AAE7E,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,sBAAsB,CAAC;AACpD,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,6BAA6B,CAAC;AAClE,OAAO,EAGL,KAAK,yBAAyB,EAC9B,KAAK,YAAY,EAClB,MAAM,aAAa,CAAC;AASrB,8EAA8E;AAC9E,MAAM,WAAW,wBAAwB;IACvC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,yCAAyC;IACzC,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;IACjB,oBAAoB;IACpB,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,CAAC,EAAE,YAAY,CAAC;IACtB,kEAAkE;IAClE,eAAe,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAChC,UAAU,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,QAAQ,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACzB,YAAY,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC7B,gBAAgB,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACjC,UAAU,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,kBAAkB,CAAC,EAAE,yBAAyB,GAAG,IAAI,CAAC;CACvD;AAED,0CAA0C;AAC1C,MAAM,WAAW,+BAA+B;IAC9C,SAAS,EAAE,MAAM,CAAC;IAClB,OAAO,EAAE,MAAM,CAAC;IAChB,aAAa,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,yCAAyC;AACzC,MAAM,WAAW,wBAAwB;IACvC,SAAS,EAAE,MAAM,CAAC;IAClB,4EAA4E;IAC5E,QAAQ,EAAE,SAAS,GAAG,QAAQ,CAAC;IAC/B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAED,gDAAgD;AAChD,MAAM,WAAW,gCAAgC;IAC/C,SAAS,EAAE,MAAM,CAAC;IAClB,qEAAqE;IACrE,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,uEAAuE;IACvE,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAyGD;;;;GAIG;AACH,wBAAsB,mBAAmB,CACvC,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,OAAO,CAAC,CAiElB;AAED;;;;;GAKG;AACH,wBAAsB,0BAA0B,CAC9C,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,cAAc,CAAC,CAkDzB;AAED;;;;;;GAMG;AACH,wBAAsB,mBAAmB,CACvC,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,OAAO,CAAC,CA8BlB;AAED;;;;GAIG;AACH,wBAAsB,2BAA2B,CAC/C,QAAQ,EAAE,iBAAiB,EAC3B,KAAK,EAAE,OAAO,GACb,OAAO,CAAC,OAAO,CAAC,CA+BlB"}