FIN-CTRL-016 / NORTHMARK CROSS-BORDER
Cross-border operations gained one decision trail
Fourteen entities and eight jurisdiction paths moved through one reconstructable control and exception record.
Northmark Cross-Border
The same client action triggered different entity, tax, currency, approval, and record requirements. Teams maintained the logic in email and spreadsheets.
14 entities · 8 jurisdiction paths · 2022 · 9 months · managed service
The problem beneath the brief
Automation proposals encoded one happy path but could not show which rule version applied, who approved an exception, or how a payment reconciled to the underlying obligation.
- 14
- entities on one control modelaccepted entity and obligation register
- 8
- jurisdiction paths modeledaccepted decision-table set
- 4
- segregated approval rolescontrol matrix
Risk constraints
What could not be traded away.
- jurisdiction-specific review
- segregation of duties
- payment reconciliation
- rule effective dates
- qualified-human decisions
Findings
What inspection changed.
- entity selection and invoice routing used different client classifications
- rule changes had no effective-date control
- exceptions could bypass the reconciliation queue
Named team and role pattern
The people attached to this engagement.
- Daniel Reyes · senior delivery lead
- CPA reviewer
- business systems analyst
- workflow engineer
- data engineer
- security reviewer
- operations owner
Architecture
The operating system we installed.
- 01jurisdiction and entity decision tablesegregation of duties
- 02versioned rule servicequalified review
- 03approval workflowrule effective dating
- 04payment and obligation ledgerpayment reconciliation
- 05exception and reconciliation queueexception aging
Delivery sequence
Four phases. Evidence at every gate.
- 01
Frame
Define the decision, outcome, work products, authority, dependencies, exclusions, and acceptance evidence.
A named sponsor and principal approve the bounded charter. - 02
Assemble
Inspect the operating reality, then assemble named specialists, context, access, controls, and a delivery plan around the actual work.
The client approves the named team, evidence plan, role boundaries, and stop conditions. - 03
Govern
Build and operate the smallest coherent change with versioned decisions, quality evidence, escalation, and acceptance attached.
The integrated state meets the agreed evidence threshold and every material exception has an owner. - 04
Transfer
Rehearse recovery, resolve exceptions, accept the work, remove temporary access, and transfer operating ownership.
The receiving owner signs the handoff with open limits visible.
Complications
Where the plan had to become more honest.
- A payment could be operationally complete while its tax evidence remained incomplete.
- One jurisdiction required a human determination where the earlier workflow expected a deterministic rule.
Outcomes
What changed—and what the record proves.
- Entity, invoice, payment, review, and evidence states shared one case record.
- Automation stopped at qualified-review boundaries instead of forcing a decision.
- Operations could reproduce the applicable rule version and approval for every completed case in the acceptance set.
Lessons
What we would carry into the next system.
- Payment completion and evidence completion are separate states.
- A rule engine needs effective dates and qualified-review stops.
- Cross-border operations become safer when exceptions are first-class records.
Handoff
The engagement ended with an operating owner.
- 01rule-owner matrix
- 02jurisdiction review calendar
- 03exception SLA and escalation
- 04reconciliation ownership
- 05quarterly control sampling
Start with the decision
Bring the priority. We will help bound the work.
If the decisions or constraints look familiar, start with the operating reality—not a preselected solution.
Start a conversation.