Close transaction
The transaction owner freezes vouchers, approvals and transaction IDs; retain rejected items separately.
MOBILE-ID · TRUSTED LTANS
Banking & Financial Services
Reconcile transaction documents with approvals and export the exact record set for an audit period.
Problem and records to preserve
Records fragmented across systems and accounting periods complicate reconstruction of decisions.
SYNTHETIC CASE
Synthetic transaction-approval set
FIN-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Operations, internal audit, information security and bank architecture teams |
| Source system | Core banking / CRM / approval system |
| Revision | Bind vouchers, authority and time; adjustments create separately related records. |
| Record relationship | Supplements link the decision and frozen reconciliation period. |
Sector-specific record journey
Bind period
Bind period, business unit and source revision; do not infer business dates from LTANS intake.
Seal batch
Build count/digest inventory; quarantine incomplete or duplicated batches before declaring completeness.
Preserve
Track each archiveId to evidence, retaining incomplete-work alerts and custody reread rights.
Retrieve case
Authorized auditors export by case/period with scope approval, manifest and recipient checks.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Transaction/period audit package with voucher inventory, manifest and receipt. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Business units deposit, auditors retrieve, approvers authorize export scope.
Choose SaaS or on-premises by data classification, residency and bank policy; no single model fits every bank.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: A transaction and approval reconciled against source systems.
Sample dossier and tests
Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.
Download synthetic dossier| Test | Expected outcome |
|---|---|
| Intact | File inventory, size and SHA-256 match the manifest. |
| Missing / changed bytes | The verifier rejects the package without claiming inventory success. |
| Sector business case | Missing vouchers produce discrepancy lists, never a complete-period claim. |
Scope a PoC for this dossier
Reconcile counts, digests and transaction IDs; test duplicate deposits, missing batches and cross-unit access.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | A transaction and approval reconciled against source systems. |
| Revision / decision | Bind vouchers, authority and time; adjustments create separately related records. |
| Test and expected result | Duplicate transactions are not counted twice; audit export matches period and business-unit scope. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | FIN-SYN-001 |
| Source system | Core banking / CRM / approval system |
| Revision relationship | Supplements link the decision and frozen reconciliation period. |
| Recipient and output | Transaction/period audit package with voucher inventory, manifest and receipt. |
| Rights and authority | Business units deposit, auditors retrieve, approvers authorize export scope. |
| Required rejection test | Missing vouchers produce discrepancy lists, never a complete-period claim. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.