How-To Guides
| Owner | Classification | Version | Effective | Next review | Status |
|---|---|---|---|---|---|
| Platform Engineering | Internal | 0.1 | 2026-08-29 | 2026-11-29 | Draft |
Purpose. Task-oriented guides for operating platform mechanisms — how to configure, run, and verify a capability end to end, including its operational constraints. These guides complement the reference and procedural sections rather than duplicate them.
Scope
| Section | Answers |
|---|---|
| Architecture | How is a subsystem designed? What are its components and flows? |
| Platform Operations | How are services built, deployed, and operated at the platform level, including deploy, rollback, and incident procedures? |
| Product (this section) | How is a specific business capability configured and run end to end? |
Each guide is self-contained and layered: the mechanism (only as much as is needed to operate it), the configuration, the run-and-verify procedure, and the operational constraints.
Guides
| Guide | Covers |
|---|---|
| Email & Document Ingestion | Inbound email → classification → extraction → link (remittances, invoices, journals) |
| Document Receipt — Remediation | Operator side of the doc queue — reclassify, reprocess, status-based gating; the shared lifecycle config + subcategory/LOV gotchas |
| Document Numbering Convention | How every doc gets {prefix}-{padded id} from receiptprefixes; how to number correctly in programmatic/workflow creation paths (don't ship UUIDs) |
| Cash Application Engine | Trigger the CID → match → STP engine; scope, prerequisites, verification |
| Cash Application Intelligence | Reference — CID + 4 matching legs (79 rules), operators, confidence model, bulk-vs-live parity |
| Collections — Worklist & Disputes | Sub-module of Cash/AR — worklist, strategies, dunning, disputes; rule-based scoring; the batch-nightly connected-to-cash tie; the Finni collections agent |
| Invoice — 3-Way Match & GL Coding | AP pipeline — extract → 3-way match (PO/GRN/invoice) → GL code; the vetted-PO/supplier quirks; the materiality+anomaly assessment leaf; edit-vs-notify resolution |
| Journal — Posting & Validation | JV lifecycle (create → validate → post via processjournal); the validation gap (rules defined ≠ running); sourced/automation JVs + the JV↔task source link; governed execution |
| Reconciliation Matching Engine | Matching → account → preparer chain; the transition-rule bridge; matchtype semantics |
| Reconciliation Certification & Adjustments | Variance formula; the three item classes and when a JV is required vs not; the threshold/auto-cert gate; the open-adjustment risk |
| Close Automation Tasks | How a close step runs a module engine — the automation registry, template binding, parameter resolution, config-UI input declaration, where the automation layer is authored (blueprint vs Excel), parameter rollover |
| Account Model & Chart of Accounts | Reference — where account identity lives (recon is the SoR; ideally finbase), the per-module account tables, why journal.accountmaster ⊆ reconciliation.account (loose strings, wave-2), the account key, and the modular-shipping stance (all schema ships; gate UI + API) |
| Connected Close — GL Stitching | How a close task resolves to the right GL account across modules — account key, control-variant resolution, recon as System-of-Record, where the segment comes from at onboarding, the exception loop (true-up JV draft) |
| FinHub — CFO Aggregation View | The cross-module CFO surface (not a triplet) — cfo-summary aggregation, cfo.signals pure-function curation, the FinHub Finni supervisor, relationship to FIG |
| Materiality Tiers | One canonical finbase.materialityconfig; the applicationcode domain axis (don't lowercase); the ~5 consumers; how a tier is computed and configured |
Server-side demo-data operations (Demo Control, Demo Environment Refresh) moved to Platform Operations — they are operational procedures, not business-feature walkthroughs.
Revision history
| Version | Date | Author | Change |
|---|---|---|---|
| 0.1 | 2026-08-29 | Platform Engineering | Initial section landing. |
| 0.2 | 2026-09-01 | Platform Engineering | Added Close Automation Tasks + Connected Close — GL Stitching guides. |
| 0.3 | 2026-09-04 | Platform Engineering | Added the Cash Application Intelligence reference (CID + matching rule catalog, operators, bulk-vs-live parity). |
| 0.4 | 2026-09-05 | Platform Engineering | Added Document Receipt — Remediation (reclassify/reprocess, status-tier gating, shared config, subcategory/LOV gotchas). |
| 0.5 | 2026-09-05 | Platform Engineering | Added Demo Control (server-side demo-data ops) + Demo Environment Refresh (golden pair → Railway). |
| 0.6 | 2026-09-07 | Platform Engineering | Moved Demo Control and Demo Environment Refresh to Platform Operations — they are operational procedures, not business-feature walkthroughs. |
| 0.7 | 2026-09-07 | Platform Engineering | Expanded Close Automation Tasks (config-UI declarations, blueprint authoring, parameter rollover) + Connected Close — GL Stitching (exception loop / true-up JV). |
| 0.8 | 2026-09-15 | Platform Engineering | Added Document Numbering Convention (receiptprefixes {prefix}-{padded id}; programmatic/workflow numbering pattern; non-conforming paths). |
| 0.9 | 2026-09-15 | Platform Engineering | Added Collections, Invoice (3-way match), Journal (posting/validation), FinHub, and Materiality Tiers guides — closing the module coverage gaps surfaced by the intelligence-docs audit. |