AXES Example (Fin) · Financial services · run APRUN-2026-06-09-A

Your branding here

Automation Execution Report

An example report produced to the AXES open standard.

This is an example. The branding slots show where your organisation's identity would sit. The standard is open; the report is yours to brand.

This is the audit and control view - prepared for accountants, bookkeepers, and reconciliation leads.

Read it as you would a report that crossed your desk. The questions at the end ask what it would need to be one you could rely on.

Audit & Control View - APRUN-2026-06-09-A

1. Controls relevant and evidenced

Three preventive controls (control set ctl:ap-pay/v3.2) were evaluated pre-commit for each instruction [env:0004 | controls.control_evaluation_phase]:

#BeneficiaryAmountCTL-BENEF-01 approved-listCTL-LIMIT-02 per-payment limitCTL-DUPL-03 duplicate keyHuman approval
01SUP-001€4,475.00passedpassed (17.9%)passednot_required
02SUP-002€12,880.50passedpassed (51.5%)passednot_required
03SUP-003€23,900.00passedpassed (95.6%)passednot_required
04SUP-004€9,240.10passedpassed (37.0%)passednot_required
05SUP-005€3,318.75passedpassed (13.3%)passednot_required
06SUP-006€15,602.00passedpassed (62.4%)passednot_required
07SUP-007€7,777.77passedpassed (31.1%)passednot_required
08SUP-008€1,949.99passedpassed (7.8%)passednot_required
09SUP-009€11,025.40passedpassed (44.1%)passednot_required
10SUP-010€6,890.00passedpassed (27.6%)passednot_required
11SUP-011€2,475.25passedpassed (9.9%)passednot_required
12SUP-012€8,112.60passedpassed (32.5%)passednot_required
13SUP-013€5,230.95passedpassed (20.9%)passednot_required
14SUP-014€4,527.87passedpassed (18.1%)passednot_required

Result: 42/42 control evaluations passed; 0 failed; 0 bypassed; 0 not_observed. Approval was not_required under policy v3.2’s rule for at-or-below-limit payments to approved beneficiaries [env:0004 | authority.approval_basis]; consequently no SoD/dual-control assertion is made or needed for this run - the control relied upon is the delegated-limit + approved-list pair, both evidenced above.

2. Population and completeness (IPE basis)

  • Population definition: ERP approved-invoice queue at 08:55Z (14 due) reconciled against bank statement FMB-STMT-2026-06-09 (14 booked) - independently reconciled, not self-reported [env:0073 | reconciliation.population_basis].
  • Coverage: envelopes 14/14 (100%); tamper-evident 100% [env:0073 | reconciliation.evidence_coverage_ratio].
  • Sequence continuity: envelope sequence numbers 0001–0076 contiguous, no gaps (stream-internal proof); heartbeats at 60s intervals, zero silent windows (silence semantics) [env:0009 | liveness.declared_heartbeat_interval_s].

3. Evidence quality

  • Origin/basis: runtime-observed; commit confirmations are third-party confirmed (pacs.002 ACSC per payment) and source-system corroborated (camt.053) [env:0007 | evidence_quality.corroboration_state] [env:0073 | evidence_quality.corroboration_state].
  • Corroboration coverage decomposition: anchored 100% · receipted 14/14 · provider-only 0.
  • Point-in-time validity: policy v3.2 effective from 2026-05-01, in force at every event [env:0007 | authority.policy_version]; delegation valid 2026-04-02 → 2026-12-31.
  • Model context: sampling parameters recorded (temperature 0.2, top_p 0.9); replay claim scoped - reproducible in distribution, not in instance [env:0002 | model.sampling_parameters]; reasoning artifacts provider_withheld - disclosed, not silent [env:0002 | model.reasoning_artifact_availability].

4. Findings register

No exceptions, deficiencies, or open actions arise from this run. One observation (OBS-001, advisory): peak per-payment utilisation 95.6% - recommend limit-headroom review for SUP-003. Owner: AP process owner. Due: next policy cycle.

This report is produced to AXES, an open, public working-draft standard for automation execution evidence, stewarded by Magentix AI. The standard is developed in the open and invites review.

See the standard's origin on GitHub

Other views of the same evidence

The Golden Trace example is published in several role-specific views. Each option below opens the same underlying record, framed for a stated profession. Select a view to read it, or share a link with a colleague whose role differs from yours.

Each view ends with the same review questions. The public requirements register is strengthened when multiple professions contribute.

Review this example

You have read the example report above. The questions below ask what would need to change before you could rely on a report like this in your role. Your answers are added to the public AXES requirements register.

Common questions (every reviewer)
Questions for your role

You are often first to discover unauthorised execution, usually weeks later.

Attribution and contact
E1. May we credit you as a design partner on the standard? * Design partners are acknowledged in the standard's contributor record. This is standards review, not a testimonial.