BAMS + NUL
Technical synergy · Working draft for review

One enforcement surface, across the bank's people and its money.

BAMS measures the workforce and computes payroll. NUL reads the bank's own policy, then returns a binding decision on every figure and every transaction before it moves. Two systems, one decision language, one audit trail.

Approve Review Block
01Where they meet

Zero overlap. One produces a number, the other judges an action.

They connect at exactly one surface: the moment a computed figure, or a transaction on the bus, becomes an action that policy governs. Neither replaces the core banking system. NUL sits above it as a gate.

System A

BAMS
Measures & computes
  • Biometric attendance capture across branches
  • HR and directory sync, employee master data
  • Shift, late, early, absence and overtime logic
  • Ethiopian overtime multipliers and holiday calendar
  • Computes payroll, delivers to the ERP
DECISION
POINT
a figure or transaction becomes a governed action

System B

NUL
Evaluates & enforces
  • Compiles written policy into a traceable rule graph
  • Real-time decision: approve, block or review
  • Each decision cites the rule that governed it
  • Tamper-evident, regulator-ready audit chain
  • Sits on the bus, never replaces the core
02How they connect

The mechanism already exists.

Attendance devices push events in real time. BAMS computes the figure. NUL evaluates it. Only approved records reach the ERP; blocked and review items are held. Every decision lands in one audit trail.

SOURCE
Devices · Directory · HR
Real-time event capture across branches
COMPUTE
BAMS
Payroll and overtime figures
EVALUATE
NUL gate
Checked against cited policy
OUTCOME
Approve · Block · Review
Approved only writes to the ERP
EVIDENCE
Unified audit
Every decision tied to its rule
03Live decision engine

Feed it a record. Watch it cite the rule and return a verdict.

Two enforcement surfaces, one engine. Toggle between a payroll figure checked against Ethiopian labour law, and a transaction checked against the national AML and due-diligence framework. Adjust the inputs, or load a preset, then run it.

NUL decision engine
Payroll record from BAMS
Statutory cap: 4 hrs/day, 12 hrs/week
Must match the statutory rate for the period
Decision & evidence
Awaiting a record.

Load a preset or adjust the inputs,
then run the decision.

Every verdict cites the rule that
produced it, with a tamper-evident hash.
04What the union unlocks

From "assumed compliant" to "proven, per record."

SurfaceToday, separate systemsCombined
Payroll releaseComputed, then written. Correct is assumed compliant.Evaluated against policy, written only if approved.
Overtime limitsPaid at configured rate, no statutory-cap check.Each figure checked against the cited legal rate first.
TransactionsMonitored after the fact, sampled in review.Gated in real time against the AML framework.
AuditabilityLogs show what synced, not why it was allowed.Every figure carries a record tied to its rule.
Rule changesA law change becomes a developer ticket.Update the policy document, recompile, both current.
05Built for the framework you already answer to

The rules the engine enforces are public statute, not assumptions.

Regulators in this market are explicitly encouraging AI-native, real-time monitoring. The combined surface is designed to produce the evidence an examiner asks for, on demand.

§

Labour Proclamation 1156/2019

Overtime caps and statutory multipliers (1.5× day, 1.75× night, 2.0× rest day, 2.5× holiday) are compiled directly into the rule graph.

AML

AML Proclamation 780/2013 & FIC Directive 01/2014

Reporting thresholds, due-diligence status and PEP senior-approval requirements gate the transaction before it settles.

Evidence on demand

Tamper-evident decision records, each tied to the governing rule, assembled into one examiner-facing view across people and money.

06Open items for technical review

These are engineering choices, not feasibility blockers.

Decide together

  • Labour rules: gate only, or move fully into the graph?
  • Real-time per record, or batch at cycle close?
  • Reconciliation design so no record bypasses the gate
  • Where the combined audit surface lives
  • Which interface hosts the shared review queue

For the bank's team to confirm

  • Which rules live in attendance config vs middleware today?
  • Does the attendance system authenticate against the directory, or only import records?
  • How is payroll written to the ERP today?
  • What is the live integration bus, and does BAMS route through it?
  • Current transaction-monitoring and reporting workflow
07Bottom line

Two systems that are compatible, complementary, and ready to wire together.

BAMS measures the workforce and computes the figure. NUL reads the policy and returns a binding decision, with the evidence attached. The core mechanism is confirmed; what remains is shape, not feasibility.

This is a working draft to illustrate fit, not a fixed claim or a commitment. The NUL capability is first-hand. The attendance and payroll behaviour is drawn from standard ZKBio Time documentation and may differ in a specific deployment. The regulatory rates and thresholds shown are public Ethiopian statute (Labour Proclamation 1156/2019; AML Proclamation 780/2013 and Financial Intelligence Center Compliance Directive 01/2014). Items for confirmation are noted above. The decision engine here is a self-contained demonstration of the decision and evidence model; it makes no live connection to any bank system.