Synthetic · HYP-E01
Mock interest batch excerpt · fictional DemoCore-A
Illustrates a sample eligibility check and monthly posting path; not executed or independently validated.
Financial Modernization Baseline
FICTIONAL / ILLUSTRATIVE ONLY
A proposed evidence format for one decision.
This condensed example follows one invented deposit-interest conversion question. It is a manually constructed illustration of how evidence and open questions might be presented for human review.
Proposed evidence formatInvented read-only scopeBuyer-owned decisions
01 / Decision boundary · invented example
What the fictional review is meant to inform.
Before a hypothetical conversion rehearsal, a buyer team would decide whether the available evidence is sufficient to review deposit-interest accrual and opening accrued-interest mapping for one synthetic product group, DEMO-X.
Illustrative scope
Invented eligibility, day-count basis, rounding point, and opening principal/accrued-interest mapping for synthetic DEMO-X; one component boundary and one rehearsal decision.
Explicitly outside this example
Other products, fees, payments, overdrafts, statements, ledger balancing, production populations, full conversion readiness, production changes, and approval to proceed.
Recodex Scan is described on the site as free, qualification-required, vendor-neutral, and read-only. This fictional page assumes no production access and uses only constructed records; it does not claim a Scan occurred.
02 / Synthetic evidence register
Invented inputs and their limits.
Each HYP item below is a mock artifact created for this illustration. None was supplied by an institution or inspected by Recodex.
Synthetic · HYP-E02
Mock DEMO-X product parameter export
Shows an invented legacy ACT/365 setting; the fictional target setting is absent.
Synthetic · HYP-E03
Mock conversion mapping worksheet
Lists synthetic opening-principal and accrued-interest fields; field presence does not show balances reconcile.
Synthetic · HYP-E04
Eight-row synthetic scenario pack
Five constructed rows have paired expected/target values; three have no target value. None is test-run output.
Synthetic · HYP-E05
Mock exception note
Records an invented owner assumption for this example only; it is not a buyer decision.
8
Invented · constructed scenarios
5
Invented · with paired mock values
4 align · 1 differs
Invented · synthetic comparison
3
Invented · without target values
The evidence register, lineage view, comparison summary, exception record, and residual-question format are proposed mockups. Their appearance here does not verify that a current Recodex workflow ingests, traces, compares, or generates them.
03 / Constructed rule and behavior lineage
A few synthetic examples, with uncertainty visible.
Synthetic DEMO-R-01 · eligibility
Constructed comparison · S-01
Mock DemoCore-A source checks ACTIVE status and an interest-eligible flag; a mock mapping carries the flag to fictional DemoCore-B. Invented HYP-E01, HYP-E03, and HYP-E04.
Synthetic arithmetic: 1,000 demo units × 3.65% × 30/365 = 3.00 demo units on each mock side. One constructed alignment does not establish coverage of every status or product.
Synthetic DEMO-R-02 · day-count basis
Target behavior · unknown in mock
The invented HYP-E02 shows ACT/365 for the mock legacy side; synthetic HYP-E03 leaves the target basis blank. Three constructed scenarios therefore lack paired target values. The legacy setting does not establish intended target behavior.
Synthetic DEMO-R-03 · rounding and posting
Constructed comparison · S-06
Mock notes describe monthly rounding on the fictional source side and daily rounding on the fictional target side. At 1,000 demo units, 4.00%, and 30/365, the constructed unrounded value is about 3.2877: monthly rounding gives 3.29; rounding 0.1096 daily to 0.11, then posting 30 days, gives 3.30 demo units.
Synthetic difference: 0.01 demo unit in this scenario only. It does not establish actual behavior, materiality, or aggregate impact.
Synthetic DEMO-MAP-01 · opening balance fields
Mock HYP-E03 maps invented opening-principal and accrued-interest fields between fictional DemoCore-A and DemoCore-B. No synthetic balancing or reconciliation result is included; a documented field mapping does not show that balances reconcile.
“Demo unit” and every figure, rate, comparison, rule, system name, and scenario above are fictional and constructed for illustration.
04 / Illustrative coverage gaps
What this synthetic set leaves unanswered.
- Eligibility · mock area
- Synthetic coverage is partial: two mock status cases. Suspended, closed, zero-balance, and mid-period changes are absent.
- Principal and rate mapping · mock area
- Documentary only: one invented product and rate. No buyer-approved mapping source or broader rate-change scenarios.
- Day-count basis · mock area
- Open in this example: the synthetic target basis is blank for DEMO-X.
- Rounding and posting · mock area
- Limited to one constructed paired difference. Intended rounding point, edge cases, and buyer-set materiality are unresolved.
- Opening-balance reconciliation · mock area
- Not evidenced in this mock set; no control total, balancing report, or reconciliation result is included.
These are illustrative omissions in a constructed example, not measured product coverage or a completeness assessment.
05 / Invented buyer-owned exceptions
Recording a question does not resolve it.
Synthetic EX-01 · invented status: accepted for mock planning only
Temporary ACT/365 assumption
Fictional Deposit Product Owner accepts this invented assumption for synthetic DEMO-X because the mock target worksheet is blank. It applies only to the example’s planning discussion; resolve against buyer-approved target evidence before a later buyer decision.
This fabricated acceptance is not a real approval, policy, or sign-off.
Synthetic EX-02 · invented status: unresolved illustrative difference
0.01 demo-unit difference
Fictional Deposit Operations Reviewer is named as owner of constructed S-06. No rationale or acceptance is assumed. Buyer reviewers would determine intended behavior, needed evidence, and whether an exception is acceptable.
No materiality threshold is assigned in this example.
Exception acceptance belongs to the buyer’s named owner. This invented record does not resolve its evidence question or extend acceptance beyond the stated sample boundary.
06 / Residual questions for human review
The buyer keeps the decision.
What day-count basis should the target use for synthetic DEMO-X?
Why it remains open · invented case
Three invented comparisons have no paired target value because the assumed target basis is unspecified.
Buyer-owned next step
Confirm using buyer-approved target evidence and decide whether any assumption can remain open at the named gate.
How should the constructed 0.01 demo-unit rounding difference be treated?
Why it remains open · invented case
One synthetic scenario cannot establish behavior across other cases or a wider population.
Buyer-owned next step
The buyer defines intended behavior and evaluation criteria, then decides whether more approved scenarios are needed.
Do the mapped opening balances reconcile, and are these scenarios representative?
Why it remains open · invented case
The invented worksheet lists fields but contains no balancing evidence; constructed examples do not establish actual transaction patterns.
Buyer-owned next step
The buyer selects and approves reconciliation artifacts, accountable reviewers, scenarios, and the evidence boundary.
Buyer decisions stay with the buyer
For any real decision, the buyer names accountable reviewers; confirms intended behavior from buyer-approved evidence; accepts, limits, or rejects exceptions; defines evidence for the next review gate; and decides whether to proceed, hold, or request more evidence. Recodex Scan does not approve a conversion or cutover.
No composite score or readiness rating is assigned here. This page makes no certification, compliance or regulatory conclusion, completeness claim, warranty, production change, or approval to proceed.
FICTIONAL / ILLUSTRATIVE ONLY
This is proposed collateral showing a possible evidence format. It is not a customer scan, customer result, actual evidence, or proof that Recodex currently generates these outputs. Any real scope and evidence would be agreed with the buyer first.