invoicing-service — render from snapshots

Enter cumulative-balance snapshots; the real pipeline reconstructs the per-cycle deltas (state at end − state at start) and builds the documents. Use two dates for the same position to produce a delta.

Example configurations

Each link loads and renders a scenario below (and is shareable).

Offsetting — DCA fee offset — dca_fee_offsetting on: recovered DCA fees appear as realized_payments on the invoice and are NULL on the balance sheet.

Offsetting — nothing offset — All toggles off: every recovered amount stays on the balance sheet; the invoice's realized_* lines are NULL.

Offsetting — everything offset — interest + cost + dca_fee offsetting: all three move onto the invoice (realized_*), cost VAT appears, and the balance sheet's gated lines go NULL.

Settlement mode — mode=settlement: offsetting toggles are forbidden, so the invoice nets nothing (realized_* NULL). The netting Settlement document is not produced yet (see TODO.md).

Negative delta (falling balance) — A position whose balance falls between cycles yields a negative delta — the basis for negative_amounts (the dedicated section is still stubbed; see TODO.md).

Input mode: hand-entered rows JSON cycle files

Cycle period (half-open [start, end)) — which cycle to render Start End

Account settings Template Mode VAT rate (basis points)
interest_offsetting cost_offsetting dca_fee_offsetting

Position balance snapshots

as_of	position_type	slug	rec_to_dca	rec_to_creditor	billable	vat	taxable

JSON cycle files

A list of dated cycle files, each the same envelope the service ingests from S3. Every file carries its own account_settings (mode, offsetting toggles, documents) and positions_snapshots, so the account settings above are ignored in this mode. Files are ingested in date order through the real pipeline; the cycle period above selects which movement to render.

render as PDF (shown inline)

Error

parse JSON: unexpected end of JSON input